Releases · marvs/kantan-dev

Kantan now keeps each repo's conventions small and up to date, and puts them in the files your agent actually loads.

Recording patterns (`kantan-finish-feature`)

Each new pattern goes into the topic file that fits, not into CLAUDE.md or AGENTS.md. A topic file covers one subject and loads only for matching files. Kantan uses .claude/rules/ in Claude Code, .cursor/rules/ in Cursor, and AGENTS.md files in subdirectories in Codex. The main file keeps only the rules every session needs, and stays under 200 lines.
Kantan searches before it adds. If an entry on the topic already exists, it extends or corrects that entry instead of adding a second one.
Entries that the feature makes out of date are fixed or removed in the same change.
Entries stay short: the rule, one line of why, and the file to look at. Entries refer to each other by file name, never by "above" or "below".
Facts about a single feature go in that feature's .kantan-dev/docs/ file, not in the conventions.
A new topic file only gets glob patterns that match real files in the repo. If the main file has an index of topic files, Kantan adds a row for the new one.
If the repo has its own rules for recording patterns, those rules win.

Claude Code writes to CLAUDE.md. It uses AGENTS.md only when the repo has no CLAUDE.md, or when CLAUDE.md just imports @AGENTS.md. Cursor and Codex write to AGENTS.md. Before this release, AGENTS.md always won, so repos that keep their rules in CLAUDE.md went out of date.
If a repo has no conventions file at all, Kantan creates the right one for your agent and tells you.
Behavior change: If the repo's conventions exist only for a different agent (for example, only CLAUDE.md while you run Codex), Kantan now stops and asks where to write. It no longer starts a second set of rules.