docs: record why goose global rules do not emit ~/.agents/AGENTS.md - #2289
Merged
Conversation
Goose v1.41.0 (aaif-goose/goose#9736) additionally loads the vendor-neutral ~/.agents/AGENTS.md global hints alongside the config-dir hints. The goose target keeps emitting only ~/.config/goose/.goosehints: the config-dir hints remain fully loaded (no capability loss), and the shared ~/.agents/AGENTS.md is already written by the targets that own it (e.g. cline in global mode) — a second writer would require cross-target shared-file coordination for zero capability gain. Closes #2207 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
Author
|
@dyoshikawa Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Goose v1.41.0 (block/goose#9736) additionally loads the vendor-neutral
~/.agents/AGENTS.mdglobal hints alongside the existing config-dir hints. Issue #2207 framed the follow-up as an explicit Option A (also emit the shared path from the goose target) / Option B (document that the surface is already covered) decision.This resolves it as Option B, recorded as a comment in
goose-rule.ts:~/.config/goose/.goosehintsremains fully loaded — there is no capability loss today (the issue itself confirms "nothing breaks").~/.agents/AGENTS.mdis already written by the targets that own it (e.g.clinein global mode). Makinggoosea second writer of a shared global file would require cross-target shared-file coordination (the same class of problem the antigravity targets needed shared-file keys for) for zero capability gain.Comment-only change; no behavior difference.
Closes #2207
🤖 Generated with Claude Code