Add `GOOSE_TERMINAL` environment variable to spawned terminals under the goose agent for custom profile changes

[simonsickle]

Please explain the motivation behind the feature request.
Having certain aliases or disallowed commands, like find, only for goose would be a great addition.

Describe the solution you'd like
When goose spawns a terminal / executes a command, add an environment variable GOOSE_TERMINAL=1 to signify that the terminal is running under the goose agent.

Then in my ~/.zshrc I could have something like

if [[ -n "$GOOSE_TERMINAL" ]]; then
  alias find="echo 'do not use find, use rg (ripgrep) instead'"
fi

Additional context
Add any other context or screenshots about the feature request here.

• I have verified this does not duplicate an existing feature request

[iamrajiv]

@simonsickle can i work on this if its ok can you assign me this

[simonsickle]

@iamrajiv I haven't started this yet, so if you'd like to submit a PR I'd be happy to take a look!

I do want to disclose that while I do work at Block I am not directly on the Goose team and don't have final say in what can be merged and things like that.

Thanks for the interest in Goose and willingness to help out!

[DOsinga]

Go for it @iamrajiv - this seems like a sensible use of environment variables

[cgwalters]

I think it'd make sense to make some attempt at standardizing this environment variable across tools? Probably we shouldn't block on that of course...but still, it's annoying for people that need to support multiple tools (cursor, claude, gemini cli etc). At a quick glance (asking claude to run env it seems that CLAUDECODE=1 is set there); gemini CLI doesn't seem to do this.

In the container world (where I come from) we tried to standardize the container= environment variable i.e. container=docker|podman e.g.

[simonsickle]

I see value in being able to customize and restrict to the quirks of the agent. Besides, I could just have a meta

"If AI_AGENT_TERMINAL" block and inside of my if CLAUDECODE || GOOSE_TERMINAL || FIREBENDER_TERMINAL block I set AI_AGENT_TERMINAL to 1 myself.

The flexibility here as a user is much nicer, at least to me, because I know the tools I'm going to be running.

[DOsinga]

yeah, good points. I think we should merge the current proposal for now. we can talk to anthropic etc to see if we can unify on one AGENT_TERMINAL variable that we can then add (you can have a meta, but of course then any new comer will have to adopt that too)