Goose native reference
Start with the Goose setup. Output keys are listed under output settings.
Native mappings
Rules
- Rules go in the
## Rulesblock ofAGENTS.md. outputs.goose.rules-file: .goosehintsalso writes all rules into one.goosehints. Goose reads it only with theDeveloperextension enabled (using goosehints).- Goose reads context files (
CONTEXT_FILE_NAMES, defaultAGENTS.mdand.goosehints) in the subdirectories it works in. - Scoped rules go to a nested
AGENTS.md. Withrules-fileset, abackend/scope goes tobackend/.goosehints. - Rules with the same scope share one file.
Agents
- Each file has
name,description, an optional free-formmodel, and the prompt body. - OpenHands reads the same path and fields, so the file is written once.
- A generic
toolslist is dropped with a note, because Goose does not document it. x-goosefields work. If they make the file differ from what another tool gets, set a differentoutputs.goose.agents-dir.
Skills
.agents/skills/is Goose's recommended path. Goose reads it ahead of.goose/skills/and.claude/skills/.- Other
.agents/skills/tools, Crush included, get the same files, so the shared folder is written once. Shared rendering drops Crush invocation fields; separate itsskills-dirto keep them. - Goose lists every skill for the model, and
/<skill-name>loads one by hand. It has no user-only field, sodisable-model-invocationis dropped with a note and commands are skipped.
Hooks
- Written as an Open Plugins package:
.agents/plugins/agnostic-ai/plugin.jsonplushooks/hooks.json. - All 12 documented events work.
matcheris a regular expression.timeoutis in seconds (default 30). x-goose.on_failuretakesalloworblockforPreToolUsefailures.agnostic-ai hook runtests hooks with Goose's event data, shell, and timeout.sync --globalwrites a separate package to~/.agents/plugins/agnostic-ai-global/, which Goose loads for every project.- The global name differs because Goose keeps only the first plugin of a name, and a project
disabledPluginsentry would turn off both. - Global sync ignores
outputs.goose.hooks-fileand an absoluteGOOSE_PATH_ROOT, for hooks and agents, and writes under~.
Plugin skills
- Set
outputs.goose.skills-dir: .agents/plugins/<name>/skillsto bundle skills as a plugin, with or without hooks. Skills and hooks share one manifest. - Goose prefixes names with the plugin name:
reviewinagnostic-ailoads asagnostic-ai:review. - A skills directory inside a plugin folder but outside its
skills/folder is not a Goose component and gets no manifest. - Sync keeps an existing
plugin.jsonit did not write and prints a note. Manifests from an earlier sync stay managed.
Reviews
Goose 1.60.0 removed goose review. Review specs are reported as unsupported, and sync writes no root or scoped review files. outputs.goose.review-file remains accepted but has no effect.
Portable Review specs stay valid for other supported targets. agnostic-ai import goose still reads a legacy root .agents/REVIEW.md into a portable review spec. Scoped review files need manual reuse. Sync leaves user-owned review files untouched; previously generated review files follow the normal cleanup of managed output.
There is no automatic rewrite because Goose has no equivalent native review surface.
MCP
Skipped with a warning.
Import
agnostic-ai import goose reads Goose files back into specs.
| Source | Becomes |
|---|---|
AGENTS.md embedded ## Rules block (### <name> children) | <rules>/<name>.md per rule |
.goosehints | the same, read only when AGENTS.md carried no rules |
.agents/agents/<name>.md | <agents>/<name>.md, unchanged except for the generated-file header |
.agents/skills/<name>/SKILL.md (+ bundled files) | <skills>/<name>/SKILL.md (folder copied unchanged) |
.agents/plugins/<name>/skills/<skill>/SKILL.md | the same, for every enabled plugin in the project |
.agents/plugins/<name>/hooks/hooks.json | one hook spec per matcher group and distinct timeout and on_failure pair, on_failure under x-goose |
Legacy .agents/REVIEW.md | <reviews>/review.md for supported review targets |
AGENTS.md | .agnostic-ai/AGNOSTIC_AI.md |
.goosehintsis a fallback. Withrules-fileset, both files hold the same rules.- Import reads every enabled plugin, hand-installed ones too.
- A plugin in
disabledPluginsin the user, project, or local Goose settings is skipped. A plugin named inenabledPluginsin a closer file stays enabled. - The
pluginsswitch in Goose'sconfig.yamlis not read, so a plugin turned off there still imports. agnostic-ai import alldetects Goose only from.goosehints,.agents/REVIEW.md, or a plugin withhooks/hooks.jsonunder.agents/plugins/. Antigravity shares.agents/plugins/, and OpenHands, Antigravity, and others share.agents/agents/and.agents/skills/, so those alone do not count. For a project with only rules or plugin skills, runagnostic-ai import goose.
Import has these limits:
- Only the rules block in the root file is read back, as with
import claudeand nestedCLAUDE.mdfiles. - A legacy root review file becomes one portable spec. Goose no longer emits it.
- Scoped
<scope>/.agents/REVIEW.mdfiles are not read back. - A plugin's
scripts/folder is not copied. Import warns when a written hook command uses$PLUGIN_ROOTor${PLUGIN_ROOT}, outside the plugin sync writes to. Copy the scripts there before it can run. - A hook group splits into one spec per distinct
timeoutandon_failurepair, so each command keeps its values. The emitted file merges them back into one group.
See scoped context.