<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Permissions on FindPicked</title><link>https://findpicked.com/tags/permissions/</link><description>Recent content in Permissions on FindPicked</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 30 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://findpicked.com/tags/permissions/index.xml" rel="self" type="application/rss+xml"/><item><title>Least-Privilege Setup for AI Coding Agents</title><link>https://findpicked.com/blog/least-privilege-ai-coding-agents/</link><pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate><guid>https://findpicked.com/blog/least-privilege-ai-coding-agents/</guid><description>&lt;p&gt;AI coding agents can save hours, but they can also turn a bad prompt, poisoned repo, or overpowered tool call into a real incident. The safest pattern is to assume the agent is useful but not fully trustworthy, then design its environment around &lt;strong&gt;least privilege&lt;/strong&gt;, &lt;strong&gt;ephemeral credentials&lt;/strong&gt;, &lt;strong&gt;approval gates&lt;/strong&gt;, and &lt;strong&gt;sandboxed execution&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This guide shows how to build that setup in practice. It focuses on the controls that matter most now for developers: narrow repo access, just-in-time credentials, policy-enforced tool use, and isolated runners that keep one unsafe action from becoming a production problem.&lt;/p&gt;</description></item><item><title>AI Coding Agent Guardrails: Safe-by-Design Guide</title><link>https://findpicked.com/blog/ai-coding-agent-guardrails/</link><pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate><guid>https://findpicked.com/blog/ai-coding-agent-guardrails/</guid><description>&lt;p&gt;AI coding agents can be useful in production workflows &lt;strong&gt;only if you treat them like untrusted automation with constrained power&lt;/strong&gt;. The safest approach is not “trust the model less” in the abstract, but to build concrete controls around &lt;strong&gt;permissions, budgets, sandboxes, approvals, logs, and rollback paths&lt;/strong&gt; so a bad prompt, tool bug, or prompt-injection attempt cannot turn into a repo-wide or account-wide incident.&lt;/p&gt;
&lt;p&gt;Recent discussion around agent security has made one thing clear: &lt;strong&gt;guardrails alone are not enough if they are easy to bypass, overly broad, or so strict that teams disable them&lt;/strong&gt;. This guide shows how to design practical, layered controls for AI coding agents without relying on vendor promises.&lt;/p&gt;</description></item><item><title>Safe AI Coding Agents in Production: Practical Guardrails</title><link>https://findpicked.com/blog/safe-ai-coding-agents-production/</link><pubDate>Thu, 25 Jun 2026 00:00:00 +0000</pubDate><guid>https://findpicked.com/blog/safe-ai-coding-agents-production/</guid><description>&lt;p&gt;AI coding agents can be used in production safely, but only when you treat them like &lt;strong&gt;powerful junior operators with fast hands and incomplete judgment&lt;/strong&gt;. The biggest mistakes usually come from giving agents broad permissions, weak review paths, or direct access to critical systems without reliable rollback and audit trails.&lt;/p&gt;
&lt;p&gt;This guide explains how to run AI coding agents with &lt;strong&gt;least privilege&lt;/strong&gt;, &lt;strong&gt;approval checkpoints&lt;/strong&gt;, &lt;strong&gt;sandboxing&lt;/strong&gt;, &lt;strong&gt;observability&lt;/strong&gt;, and &lt;strong&gt;recovery workflows&lt;/strong&gt; that reduce the blast radius when things go wrong. If you&amp;rsquo;re evaluating platforms first, it also helps to understand the broader landscape of an &lt;strong&gt;&lt;a href="https://findpicked.com/agent/"&gt;AI agent development ecosystem&lt;/a&gt;&lt;/strong&gt; before you wire agents into real delivery pipelines.&lt;/p&gt;</description></item></channel></rss>