Terminal Integration

Talk to goose directly from your shell prompt. Instead of switching to a separate REPL session, stay in your terminal and call goose when you need it.

Setup

zsh

Add to ~/.zshrc:

eval "$(goose term init zsh)"

bash

Add to ~/.bashrc:

eval "$(goose term init bash)"

fish

Add to ~/.config/fish/config.fish:

goose term init fish | source

PowerShell

Add to $PROFILE:

Invoke-Expression (goose term init powershell)

Restart your terminal or source the config, and that's it!

Usage

Just type @goose (or @g for short) followed by your question:

npm install express
    npm ERR! code EACCES
    npm ERR! permission denied

@goose "how do I fix this error?"

goose automatically sees the commands you've run since your last question, so you don't need to explain what you've been doing. Use quotes around your prompt if it contains special characters like ?, *, or ':

@goose "what's in this directory?"
@g "analyze the error: 'permission denied'"

Named Sessions

By default, each terminal gets its own goose session that lasts until you close it. Named sessions let you continue conversations across terminal restarts and share context between windows.

zsh

eval "$(goose term init zsh --name my-project)"

bash

eval "$(goose term init bash --name my-project)"

fish

goose term init fish --name my-project | source

PowerShell

Invoke-Expression (goose term init powershell --name my-project)

Named sessions persist in goose's database, so they're available anytime, even after restarting your computer. Reopen later and run the same command to continue:

# Start debugging
eval "$(goose term init zsh --name auth-bug)"
@goose help me debug this login timeout

# Close terminal, come back later
eval "$(goose term init zsh --name auth-bug)"
@goose "what was the solution we discussed?"
# Continues the same conversation with context

Show Context Status in Your Prompt

Add goose term info to your prompt to see how much context you've used and which model is active during a terminal goose session.

zsh

PROMPT='$(goose term info) %~ $ '

bash

PS1='$(goose term info) \w $ '

fish

function fish_prompt
    goose term info
    echo -n ' '(prompt_pwd)' $ '
end

PowerShell

function prompt {
    $gooseInfo = & goose term info
    "$gooseInfo $(Get-Location) PS> "
}

Your terminal prompt now shows the context usage and model name (shortened for readability) for the active goose session. For example:

●●○○○ sonnet ~/projects $

Troubleshooting

goose doesn't see recent commands: If you run commands but goose says it doesn't see any recent activity, check if terminal integration is properly set up in your shell config. You can also check the id of the goose session in your current terminal:

# Check if session ID exists
echo $GOOSE_SESSION_ID
# Should show something like: 20251209_151730

To share context across terminal windows, use a named session instead.

Session getting too full (prompt shows ●●●●●): If goose's responses are getting slow or hitting context limits, start a fresh goose session in the terminal. The new goose session sees your command history, but not the conversation history from the previous session.

# Start a new goose session in the same shell
eval "$(goose term init zsh)"