devStudio 1.0.185

Set a credential once, and let every CLI the app launches see it

A token pasted against one MCP server reaches that one process and nothing
else — not the skills the CLI runs, not its hooks, not its other servers. The
only way to share one was to copy it onto every agent that might reach for it.

Global settings now carry a list of environment variables handed to every AI
CLI this install launches, and so to everything those CLIs spawn as children.
Each variable can be switched off without losing its value, and each decides
for itself whether it may travel to a remote instance — off by default, because
sending a secret to another machine is a decision somebody makes rather than a
side effect of setting one. A remote applies its own shared environment
underneath anything that arrives, so the usual answer is to set it over there.

Shared variables are the weakest layer: they go down first, under each
adapter's own HOME and account selection, then the CLI definition, the agent,
and the turn. A stray HOME row in Settings therefore cannot point a turn at
somebody else's login.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>