--- title: Get Into Agentic Development From the Shallow End description: A developer describes incrementally building trust with AI coding agents by moving from manual approval of every action to a data-driven permission system.... canonical: https://daily.dev/posts/get-into-agentic-development-from-the-shallow-end-qro4g7gz6 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Get Into Agentic Development From the Shallow End | daily.dev og:description: A developer describes incrementally building trust with AI coding agents by moving from manual approval of every action to a data-driven permission system.... og:url: https://daily.dev/posts/get-into-agentic-development-from-the-shallow-end-qro4g7gz6 og:image: https://api.daily.dev/og/posts/QRo4g7GZ6.png og:image:alt: Get Into Agentic Development From the Shallow End og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Get Into Agentic Development From the Shallow End **[Atomic Spin](https://daily.dev/sources/atomicobject)** · 5 min read · 0 upvotes · 0 comments ## Summary A developer describes incrementally building trust with AI coding agents by moving from manual approval of every action to a data-driven permission system. Starting from a deny/approve/assess model inspired by another engineer's approach to permission fatigue in Claude Code, the author implemented similar rules in Codex using command rules, sandboxing, and guard hooks. To decide which routine operations to safely allow, an observability layer was added that logs approval requests, groups them by intent rather than exact command text, and generates reports ranking candidates for broader permission by frequency and risk. The system only suggests configuration changes; the developer still reviews and manually approves each new rule before adoption, treating autonomy as a gradual feedback loop rather than an all-or-nothing switch. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I reduce approval prompt fatigue when using Codex or Claude Code as a coding agent? Reduce prompt fatigue by implementing a deny/approve/assess permission model: block dangerous operations like recursive deletion or .env access, allow routine operations like local git commands and project-scoped file edits, and continue reviewing everything else. Adding an observability layer that logs and groups approval requests by intent, rather than exact command text, helps identify which recurring prompts are safe to allow permanently. _daily.dev surfaces more workflows like this for developers tuning agent autonomy without losing control._ ### How do you decide which AI agent permission prompts are safe to turn into permanent allow rules? Group recorded approval requests by intent instead of exact command text, then rank them by frequency, approval rate, and risk level. In one 248-prompt sample, apply_patch writes to a temp directory were approved 98/98 times (100%) and became a top candidate, while GitHub API calls were excluded from broad allow rules despite 100% approval because a generic rule could also permit mutating actions. _developers automating agent permissions can track these evidence-based rollout patterns on daily.dev._ ## Similar posts on daily.dev - [Why Coding-Agent Governance Needs More Than Approval Gates](https://daily.dev/posts/why-coding-agent-governance-needs-more-than-approval-gates-t38o2w3nq) · Telerik · 3 upvotes · 1 comments - [Medium](https://daily.dev/posts/medium-t4qlwxuej) · Medium · 0 upvotes · 0 comments - [Design an Agentic AI Systems Enterprises Can Actually Trust?](https://daily.dev/posts/design-an-agentic-ai-systems-enterprises-can-actually-trust--zbtfpdwup) · Build5Nines · 1 upvotes · 0 comments - [How I Use Agents Without Stopping My Own Growth](https://daily.dev/posts/how-i-use-agents-without-stopping-my-own-growth-ribjpan0v) · Atomic Spin · 62 upvotes · 11 comments - [Agentic AI in Software Development: From Coding to Orchestration](https://daily.dev/posts/agentic-ai-in-software-development-from-coding-to-orchestration-bl6akhr3q) · Syncfusion · 1 upvotes · 0 comments --- Tags: [#ai-coding](https://daily.dev/tags/ai-coding), [#observability](https://daily.dev/tags/observability), [#claude-code](https://daily.dev/tags/claude-code), [#openai-codex](https://daily.dev/tags/openai-codex) [View this post on daily.dev](https://daily.dev/posts/get-into-agentic-development-from-the-shallow-end-qro4g7gz6) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Get Into Agentic Development From the Shallow End","url":"https://daily.dev/posts/get-into-agentic-development-from-the-shallow-end-qro4g7gz6","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/get-into-agentic-development-from-the-shallow-end-qro4g7gz6"},"datePublished":"2026-10-01T12:02:24.104Z","dateModified":"2026-10-01T12:02:45.474Z","description":"A developer describes incrementally building trust with AI coding agents by moving from manual approval of every action to a data-driven permission system....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/08471d2da76fdf5cd9585805b7c1a5e4?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/08471d2da76fdf5cd9585805b7c1a5e4?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Atomic Spin","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Atomic Spin","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/e2af5ce3adaa403a8cf029268b62419f","url":"https://daily.dev/sources/atomicobject"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/get-into-agentic-development-from-the-shallow-end-qro4g7gz6","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-coding,observability,claude-code,openai-codex","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Atomic Spin","item":"https://daily.dev/sources/atomicobject"},{"@type":"ListItem","position":3,"name":"Get Into Agentic Development From the Shallow End"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/get-into-agentic-development-from-the-shallow-end-qro4g7gz6#faq","mainEntity":[{"@type":"Question","name":"How can I reduce approval prompt fatigue when using Codex or Claude Code as a coding agent?","acceptedAnswer":{"@type":"Answer","text":"Reduce prompt fatigue by implementing a deny/approve/assess permission model: block dangerous operations like recursive deletion or .env access, allow routine operations like local git commands and project-scoped file edits, and continue reviewing everything else. Adding an observability layer that logs and groups approval requests by intent, rather than exact command text, helps identify which recurring prompts are safe to allow permanently. daily.dev surfaces more workflows like this for developers tuning agent autonomy without losing control."}},{"@type":"Question","name":"How do you decide which AI agent permission prompts are safe to turn into permanent allow rules?","acceptedAnswer":{"@type":"Answer","text":"Group recorded approval requests by intent instead of exact command text, then rank them by frequency, approval rate, and risk level. In one 248-prompt sample, apply_patch writes to a temp directory were approved 98/98 times (100%) and became a top candidate, while GitHub API calls were excluded from broad allow rules despite 100% approval because a generic rule could also permit mutating actions. developers automating agent permissions can track these evidence-based rollout patterns on daily.dev."}}]} ```