Skip to content

docs: record why goose global rules do not emit ~/.agents/AGENTS.md #2289

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dyoshikawa merged 1 commit into from
Jul 16, 2026
Merged

docs: record why goose global rules do not emit ~/.agents/AGENTS.md #2289

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions src/features/rules/goose-rule.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,15 @@ export type GooseRuleSettablePathsGlobal = ToolRuleSettablePathsGlobal;
* is `undefined`). This mirrors the grokcli, warp, and deepagents targets.
*
* Goose uses plain markdown files (.goosehints) without frontmatter.
*
* Global scope emits only `~/.config/goose/.goosehints`. Goose v1.41.0 (PR
* block/goose#9736) additionally loads the vendor-neutral
* `~/.agents/AGENTS.md` alongside the config-dir hints, but rulesync
* deliberately does not emit that shared path from the goose target: the
* config-dir hints remain fully loaded (no capability loss), and the
* cross-tool `~/.agents/AGENTS.md` is already written by targets that own it
* (e.g. cline in global mode) — a second writer would need cross-target
* shared-file coordination for zero gain (decision recorded in issue #2207).
*/
export class GooseRule extends ToolRule {
static getSettablePaths({
Expand Down
Loading