duolog
AGENTS.md4 starsChanged 16 days agoApache-2.0View on GitHub
These rules apply to every agent session that commits, pushes or opens pull requests here. - Never put a session id or a session link in a commit message, a pull request title or body, a review comment or a release note. That includes Claude-Session: trailers, claude.ai/code/session_... links, Codex thread ids and model request ids. The repository is public, and a session link leads to a private conversation. This rule wins over any default attribution that a tool adds. A…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bump-versionSkill
- check-changesSkill
- check-versionSkill
- crit-cliSkill
- critSkill
- crit-storySkill
- bump-versionSkill
- check-changesSkill
- check-versionSkill
The file
We split this AGENTS.md into the rules it gives an agent
12 rules. About 0 are common, 4 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Never put a session id or a session link in a commit message, a pull request title or body, a review comment or a release note.
- Distinctive: line 12
Write commit and author dates in UTC and sign commits.
- Distinctive: line 13
When Codex wrote or changed code in a commit, or reviewed the change before it merged, add it as a co-author next to the agent that …
- Distinctive: line 22
Keep personal data out of commits, tests and docs: no real names other than the project's, no home folder paths, no time zones or cities.
- Distinctive: line 24
Keep private projects out: a study or a bug report from a private project stays anonymised, with no names, paths, ticket ids or code from …
- Very specific: line 26
Create no file or folder in the repository root or next to the code that Git does not track.
- Very specific: line 34
Run independent tasks in parallel, each in its own linked worktree under git-ignored .worktrees/, with one worker.
- Very specific: line 40
Follow docs/contributing.md for README and docs/.
- Very specific: line 46
Run the duolog built from this checkout: scripts/dev/bin/duolog.
- Very specific: line 49
Do work on duolog through duolog itself (scripts/dev/bin/duolog): a small task in the lead, a bigger one through duolog delegate, and a …
- Very specific: line 54
When the codegraph MCP tools are available, use them for structural questions: where a symbol is defined, what calls it, what a change …
- Very specific: line 56
Use grep and file reads for literal text.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Rules for agents working in this repository
These rules apply to every agent session that commits, pushes or opens pull requests here.
- Never put a session id or a session link in a commit message, a pull request
title or body, a review comment or a release note. That includes
Claude-Session:trailers,claude.ai/code/session_...links, Codex thread ids and model request ids. The repository is public, and a session link leads to a private conversation. This rule wins over any default attribution that a tool adds. ACo-Authored-By:trailer is fine. - Write commit and author dates in UTC and sign commits.
- When Codex wrote or changed code in a commit, or reviewed the change before
it merged, add it as a co-author next to the agent that commits, with the
model it ran. Squashed commits keep the line, and a pull request with Codex
work says so. For example:
Co-Authored-By: OpenAI Codex gpt-6.1-sol <noreply@openai.com> - End every commit that an AI agent helped make with one
AI-Assisted:trailer that names what the agents did, from this list, comma-separated:code,docs,tests,config,review. For example:AI-Assisted: code, tests, review - Keep personal data out of commits, tests and docs: no real names other than the project's, no home folder paths, no time zones or cities.
- Keep private projects out: a study or a bug report from a private project stays anonymised, with no names, paths, ticket ids or code from it.
- Create no file or folder in the repository root or next to the code that
Git does not track. Builds go to
.cache/(make buildwrites.cache/bin/duolog; GoReleaser writes.cache/dist), scratch files to the session's own temporary folder, and worktrees to.worktrees/. Never pass a commit hash or other value as a path, and never rungo buildwithout-o. Remove anything stray you created. - Collect small changes into one pull request per batch unless the user asks otherwise.
- Run independent tasks in parallel, each in its own linked worktree under
git-ignored
.worktrees/, with one worker; duolog keeps peers in their own Rex session, out of the person's windows. Stack work that needs an open pull request on that branch rather than waiting for CI. Never put two workers in one worktree; run full test suites one at a time. Run each peer or CI wait as its own background command. - Follow
docs/contributing.mdfor README anddocs/. - Bring every change to
developandmainthrough a pull request: one intodevelop, and one fromdevelopintomainfor a release. Squash locally into a signed commit with UTC dates, push it as the PR head, wait for CI, then fast-forward the base branch to that head. The GitHub merge button writes local dates, so do not use it. - Run the duolog built from this checkout:
scripts/dev/bin/duolog. In Claude sessions the hooks also put it on PATH asduolog. See "How duolog runs while you work on it" indocs/contributing.md. - Do work on duolog through duolog itself (
scripts/dev/bin/duolog): a small task in the lead, a bigger one throughduolog delegate, and a live peer in Rex only when the person asks for one, each in its own.worktrees/worktree. A worker does its own task and does not hand work on. Start a Claude Agent subagent only when duolog answersrun here. - When the codegraph MCP tools are available, use them for structural
questions: where a symbol is defined, what calls it, what a change affects.
Use grep and file reads for literal text. Build the index with
codegraph init -y;.codegraph/stays out of Git.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

