Useful answers
What Concise checks, what it leaves alone, and how to keep intentional text.
Before you install.
A specific edge case? Open an issue on GitHub.
For exact host coverage, see supported tools and host features.
What runs without configuration?
The three core checks: comment length, file length on whole-file writes and additions, and inline GitHub PR/issue body length. Supported test-runner output is also filtered. Em-dash and AI-writing checks are disabled until you enable them.
Does Concise rewrite my code?
No. It denies a supported tool call and gives the agent the exact finding. The agent can then submit a rewrite. The website examples illustrate that exchange; this website does not run an agent or change your files.
What if I want to keep the text?
Style checks use confirm mode by default: resubmit the identical text to keep it. You can exempt a line with concise-ignore, allow a phrase, ignore a path, or enable softFail for flagged allows. Core checks and deny mode also have a retry escape after two denials on the same target.
Does it scan the whole repository?
No. It checks the submitted write or added text in supported edit and patch calls. It does not rescan surrounding existing content. The 300-line limit applies to whole-file Write calls and patch Add File operations, not ordinary update hunks.
Are the writing checks an AI detector?
No. They match configurable phrasing, punctuation, and text-statistics patterns. Human writing can trigger them, and generated writing can pass. Use exceptions and choose categories that fit your project.
Which agents does it support?
Claude Code, Codex CLI 0.152.0 or newer, and omp. In Codex, review and trust each Concise hook under /hooks; Codex asks again after a hook definition changes. In omp, subagent replies are not checked.