Make Your Coding Agent Follow AGENTS.md
Writing MUST in capitals does not make a coding agent follow AGENTS.md. A check does. Taskless turns the rules in your AGENTS.md into deterministic checks that pass or fail the same way on every run, in Claude Code, Codex, Cursor, OpenCode, and CI.
Open source CLI. Runs locally, no account required.
Why coding agents ignore AGENTS.md
AGENTS.md, CLAUDE.md, and .cursor/rules all work the same way: the harness puts the markdown into the model’s context and the model decides what to do with it. It competes with the task, the code, and everything else in the conversation. In a long session, after context is compacted, or after a model update, a rule that held yesterday quietly stops holding.
No wording fixes this. Capitals, “IMPORTANT”, and repeating the rule three times change the odds, not the outcome. A rule the agent can choose to skip is a request.
The usual fix: hooks you wire up yourself
The standard advice is to back AGENTS.md with tooling: a husky or pre-commit hook, a CI job, CODEOWNERS on the files that matter. That advice is right. A hook or CI check is something the agent cannot talk its way past.
The cost is translation. Every line of AGENTS.md has to become a lint rule, a script, or a grep that someone writes, tests, and maintains. Most lines never make it, so most of the file stays a request.
Turn each line into a check
Taskless does the translation. Describe the rule the way you would write it in AGENTS.md, and your agent writes it as a rule with pass and fail fixtures that prove it catches what you meant. Taskless decides what enforces it from what the rule depends on: a syntax tree through ast-grep, the words of a document through Vale, your own ESLint, Ruff, RuboCop, or Stylelint config, or a check that reads across files.
Then taskless check runs every rule and exits non-zero on an error, so the same check works in the agent’s loop, in a git hook, and in CI. No model is involved when a rule runs.
# AGENTS.md
- MUST use the shared http client. Never call fetch() directly.
# Ask your agent instead
> Create a taskless rule that flags direct fetch() calls
> outside src/lib/http/
# Then, anywhere
./.taskless/bin/cli.mjs check
Keep team conventions intact in pull requests
The conventions that break most often are the ones only your team knows: which module owns retries, how errors get logged, what a migration must include. A code review bot is a language model too, so it catches these some of the time and phrases it differently each run.
With Taskless Cloud, a correction in review becomes the rule. Tag @taskless on the pull request comment where you explained the convention, and Taskless delivers the rule as a pull request. From then on every developer and every agent in the org gets the same answer on every branch.
Works with the harness you already use
Taskless installs as a skill for Claude Code, Cursor, and OpenCode, and works with any harness that supports Agent Skills. Your agent can run the checks itself and fix what they find before you ever see the diff.
Keep AGENTS.md for what it does well
AGENTS.md is a good place for context: what the project is, how it is laid out, why a decision was made. Those things help an agent and cannot be checked. Move the lines that can be checked into rules, and the file gets shorter and the rules stop being optional.
Frequently Asked Questions
Why does my coding agent ignore AGENTS.md?
Can I enforce AGENTS.md with a pre-commit hook?
Does Taskless replace AGENTS.md?
Does Taskless use an LLM to check my code?
Which coding agents does Taskless work with?
Write the rule once. Check it every run.
Install the CLI, then ask your agent to onboard the project. It reads your codebase and history and writes the rules it can enforce locally.