One Permission System for Three Coding Agents
Most people run coding agents on Full access because approval prompts wear them out. I rebuilt the permission system behind Claude Code, Codex and my own runtime around one goal: prompts you still read.
00 / Introduction
Software developer
Open-source builder
Curious about how things work
Currently building Prokop and writing about AI agents, TypeScript, software ownership, open source, and shipping ambitious systems alone.
Daniel Bilek
Prague, Czech Republic
2026
01 / Selected
Most people run coding agents on Full access because approval prompts wear them out. I rebuilt the permission system behind Claude Code, Codex and my own runtime around one goal: prompts you still read.
AI gives us access to more knowledge and capability than ever. That does not mean we will understand more, think better, or remain in control.
02 / Dispatches
Most people run coding agents on Full access because approval prompts wear them out. I rebuilt the permission system behind Claude Code, Codex and my own runtime around one goal: prompts you still read.
An agent's experience and a project's accumulated knowledge are not the same thing. Treating them as separate scopes changed how my agents work.
AI gives us access to more knowledge and capability than ever. That does not mean we will understand more, think better, or remain in control.
04 / Current work
● Active development
Open-source agentic coding workspace for persistent agents, parallel sessions, and inspectable context across projects.
Project details05 / Contact
Freelance development, collaboration, speaking, podcasts, technical conversations, or a concrete disagreement.
Get in touch