Claude Code config check

Find the agent config Claude Code silently ignores.

Claude Code skips an agent file whose frontmatter doesn't parse. It ignores a misspelled field. It never loads project settings from a parent folder.

Drop your project folder to see what won't apply.

See a sample reportTake the tour · 5 min

Your project is on a computer? Send yourself the link for later.

Check
No account. It runs in your browser; your files are not uploaded.
Blueprints
Sign in to design, version and release a team's setup.
check ./webapp11 files read, nothing uploaded

Error.claude/agents/release-manager.md:8

Agent "release-manager" has hooks written as a list; it must be a map of hook events.

Warning.claude/agents/tester.md:4

Agent "tester" has a field Claude Code ignores: allowed-tools.

3 errors, 5 warnings, 1 note

The sample project, checked in the browser.

How it works

  1. 1 · Drop a folder

    Drag your project in, or choose it. Only Claude Code's config files are read.

  2. 2 · See what won't apply

    Each finding says what won't apply, why, and how to fix it, with a link to the docs.

  3. 3 · Fix and check again

    Edit the file, then check again. The map shows what actually loads.

For engineering leaders

Run agent config like production code

Your team's agents, skills, settings and gates become one blueprint. It is checked, versioned and released the way you ship code.

Take the lifecycle tourRead how releases work
Versions
Every published version is immutable and content-hashed.
Releases
Production only takes the version already in staging. Your organization can require a second person to approve it.
Policy
Your organization policy blocks risky settings, like bypassPermissions, at the build gate.
Audit
Every change, release and export is logged. Export the log as JSONL or CSV, or read it through the API.

Blueprints · sign in

Stages, owners and gates that Claude Code enforces

Lay out the stages your agents follow, give each a lead, and attach exit gates: a command that must pass, a rubric, or a person's approval. Context Canvas checks the design, versions it, and exports the files, including the hooks Claude Code runs to enforce the gates.

Start from a templateImport your setup
  • Each stage has one lead agent and exit gates. A failing test gate keeps the agent working until it passes.
  • Approvals become skills only a person can run.
  • The same blueprint always exports the same files, so every change arrives as a reviewable diff.

Release notes

Major releases only. Questions or feedback go through the contact form.