Set GOOSE_DOCS_ROOT and wire structured compaction templates
Goose v1.45.0 adds GOOSE_DOCS_ROOT for air-gapped docs, structured summary templates for compaction, model tab-completion/provider switching, latest Gemini support, and the ability to disable built-in skills.
Why this loop
Air-gapped and regulated teams can now point Goose at a local docs tree instead of the network. Compaction gains structured summary output with template rendering, so long sessions keep consistent, reviewable context instead of opaque shrinks. The model command’s tab completion and provider switch, plus latest Gemini and restored Grok/DeepSeek naming, make provider changes a first-class CLI step. Disabling built-in skills cuts noise when only a subset of skills should run. Adopt these together so agents stay usable offline, compact predictably, and only load the skills and models you intend.
Proposed actions
- export GOOSE_DOCS_ROOT=/opt/goose-docs && mkdir -p "$GOOSE_DOCS_ROOT" && rsync -a ./docs/ "$GOOSE_DOCS_ROOT/" && echo "GOOSE_DOCS_ROOT=$GOOSE_DOCS_ROOT" >> ~/.goose/.env
- In Goose CLI, run: model <TAB> to complete model names, then model --provider google <latest-gemini-id> (or your Gemini model) to switch provider/model in-session
- Add a compaction summary template for structured output (per #10471), e.g. create ~/.goose/compaction-template.md with sections Goals, Decisions, Open TODOs, File map—then enable template rendering in your compaction config
- Disable built-in skills you do not want loaded (per #10600), e.g. goose configure skills disable <skill-name> for each unused built-in, leaving only team-approved skills enabled
- Verify air-gapped docs: disconnect network, start goose in the project, ask ‘open the Goose docs for compaction templates’, and confirm reads come from $GOOSE_DOCS_ROOT
Agent prompt
Paste into your agent or query via MCP (`get_agent_prompt`) — free, no extra AI costPaste into Claude Code / CLAUDE.md task
# DevAgentRadar → Claude Code You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features. ## Context Assistant: Goose Proposal: Set GOOSE_DOCS_ROOT and wire structured compaction templates Summary: Goose v1.45.0 adds GOOSE_DOCS_ROOT for air-gapped docs, structured summary templates for compaction, model tab-completion/provider switching, latest Gemini support, and the ability to disable built-in skills. Primary source: https://github.com/aaif-goose/goose/releases/tag/v1.45.0 ## Why it matters Air-gapped and regulated teams can now point Goose at a local docs tree instead of the network. Compaction gains structured summary output with template rendering, so long sessions keep consistent, reviewable context instead of opaque shrinks. The model command’s tab completion and provider switch, plus latest Gemini and restored Grok/DeepSeek naming, make provider changes a first-class CLI step. Disabling built-in skills cuts noise when only a subset of skills should run. Adopt these together so agents stay usable offline, compact predictably, and only load the skills and models you intend. ## Suggested actions 1. export GOOSE_DOCS_ROOT=/opt/goose-docs && mkdir -p "$GOOSE_DOCS_ROOT" && rsync -a ./docs/ "$GOOSE_DOCS_ROOT/" && echo "GOOSE_DOCS_ROOT=$GOOSE_DOCS_ROOT" >> ~/.goose/.env 2. In Goose CLI, run: model <TAB> to complete model names, then model --provider google <latest-gemini-id> (or your Gemini model) to switch provider/model in-session 3. Add a compaction summary template for structured output (per #10471), e.g. create ~/.goose/compaction-template.md with sections Goals, Decisions, Open TODOs, File map—then enable template rendering in your compaction config 4. Disable built-in skills you do not want loaded (per #10600), e.g. goose configure skills disable <skill-name> for each unused built-in, leaving only team-approved skills enabled 5. Verify air-gapped docs: disconnect network, start goose in the project, ask ‘open the Goose docs for compaction templates’, and confirm reads come from $GOOSE_DOCS_ROOT ## Config surfaces this release may change - context and compaction settings — check your repo before applying - skills — check your repo before applying - MCP servers — check your repo before applying ## Your job 1. Restate the change in one sentence. 2. Propose a minimal plan for my repo (or a throwaway pilot). 3. Implement only what I approve; prefer small diffs and tests. 4. Call out risks (permissions, breaking APIs, cost). Start by confirming you understood the proposal.
Your loop
This browser · no sign-in · not shared as “you”Community signal · 0 approved · 0 deferred · 0 ignored
Anonymous public tally (one vote per visitor; changing choice updates your vote). Not moderated product truth.