The shared REPO_POLICIES.md lists the files allowed in the repo root, and AGENTS.md is not one of them. Unlike FORMAT.md and contrib/ (moved by #74), there is no obvious place to move it: tools that read agent instructions look for it in the root. It was flagged in #74 (comment), with the recommendation to keep it in the root and change the shared policy to allow it.
Definition of done
Either the shared REPO_POLICIES.md allows AGENTS.md in the repo root and this repo takes that copy, or AGENTS.md moves to an allowed directory and every reference to it is updated.
Model: opus-5-5
The shared `REPO_POLICIES.md` lists the files allowed in the repo root, and `AGENTS.md` is not one of them. Unlike `FORMAT.md` and `contrib/` (moved by https://git.eeqj.de/sneak/mfer/issues/74), there is no obvious place to move it: tools that read agent instructions look for it in the root. It was flagged in https://git.eeqj.de/sneak/mfer/issues/74#issuecomment-45629, with the recommendation to keep it in the root and change the shared policy to allow it.
## Definition of done
- Either the shared `REPO_POLICIES.md` allows `AGENTS.md` in the repo root and this repo takes that copy, or `AGENTS.md` moves to an allowed directory and every reference to it is updated.
Model: opus-5-5
Question for sneak: may AGENTS.md stay in the repo root?
The shared REPO_POLICIES.md (in https://git.eeqj.de/sneak/prompts) lists the files allowed in the root, and AGENTS.md is not one of them; the current copy there still leaves it out.
Options:
A. (recommended) Keep AGENTS.md in the root and add it to the shared list. Tools that read agent instructions look for it there.
B. Move it to docs/ and update every reference.
Until you answer, AGENTS.md stays where it is; nothing else waits on this.
Model: opus-5-5
Question for sneak: may `AGENTS.md` stay in the repo root?
The shared `REPO_POLICIES.md` (in https://git.eeqj.de/sneak/prompts) lists the files allowed in the root, and `AGENTS.md` is not one of them; the current copy there still leaves it out.
Options:
A. (recommended) Keep `AGENTS.md` in the root and add it to the shared list. Tools that read agent instructions look for it there.
B. Move it to `docs/` and update every reference.
Until you answer, `AGENTS.md` stays where it is; nothing else waits on this.
Model: opus-5-5
sneak
was assigned by clawbot2026-10-04 02:03:41 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The shared
REPO_POLICIES.mdlists the files allowed in the repo root, andAGENTS.mdis not one of them. UnlikeFORMAT.mdandcontrib/(moved by #74), there is no obvious place to move it: tools that read agent instructions look for it in the root. It was flagged in #74 (comment), with the recommendation to keep it in the root and change the shared policy to allow it.Definition of done
REPO_POLICIES.mdallowsAGENTS.mdin the repo root and this repo takes that copy, orAGENTS.mdmoves to an allowed directory and every reference to it is updated.Model: opus-5-5
Question for sneak: may
AGENTS.mdstay in the repo root?The shared
REPO_POLICIES.md(in https://git.eeqj.de/sneak/prompts) lists the files allowed in the root, andAGENTS.mdis not one of them; the current copy there still leaves it out.Options:
A. (recommended) Keep
AGENTS.mdin the root and add it to the shared list. Tools that read agent instructions look for it there.B. Move it to
docs/and update every reference.Until you answer,
AGENTS.mdstays where it is; nothing else waits on this.Model: opus-5-5