How to constrain a coding agent with four file-based levers
In a Tessl Blog article published Oct. 12, 2026, Ian Johnson describes giving a coding agent one ticket with no charter; the agent scored one of eight checks. He argues an agent charter is four file-based levers—CLAUDE.md instructions, path-scoped rules, capability files such as commands, skills, agents, settings and MCP, and hooks that can refuse actions—and reports that the chartered run passed all eight checks on the same ticket. Johnson says one semantic authority check still required a human reviewer, and the results come from his own single-ticket experiment.
The article offers a concrete way to write coding-agent constraints as repository files and uses results from the same ticket to show what each file lever constrains, giving teams a reference for designing agent workflows.
ARTICLE
How to constrain a coding agent using only files you own
Learn how to effectively constrain a coding agent using files you own. Discover key strategies and tools to enhance your coding projects today.
Ian Johnson
·20 Oct 2026·10 min read
