`sbx secret set <sandbox> github` doesn't update env vars (sentinel values) for existing sandbox

[busyerakli]

Similar issue - #17

From docs it seems like doing sbx secret set <sandbox> github will set both GH_TOKEN, GITHUB_TOKEN in sandbox right away.

A sandbox-scoped secret takes effect immediately, even if the sandbox is running.

but even after sandbox restart it isn't changed

gh pr list
  ⎿  To get started with GitHub CLI, please run:  gh auth login
     Alternatively, populate the GH_TOKEN environment variable with a GitHub API authentication token.

workaround is to set both envs through /etc/sandbox-persistent.sh to

export GH_TOKEN=proxy-managed
export GITHUB_TOKEN=proxy-managed

sbx version:

Client Version:  v0.24.1 a67ca22761740c5c3450227ae723f069e92c9257
Server Version:  v0.24.1 a67ca22761740c5c3450227ae723f069e92c9257

[kiview]

sbx secret set would not set environment variables, but only allow the secret injection to be performed. But ack on this being a sub-par UX and thanks for sharing your valid workaround.

[H0R5E]

I have tried to work around this by setting GH_TOKEN directly with a fine grained token but the github cli won't authenticate, saying that the token is invalid. Is the proxy doing something to the token?

[posita]

sbx secret set would not set environment variables, but only allow the secret injection to be performed. But ack on this being a sub-par UX and thanks for sharing your valid workaround.

I lost a couple hours on this, too. Your docs say, quite clearly:

GitHub token

The github service gives the agent access to the gh CLI inside the sandbox. Pass your existing GitHub CLI token:

echo "$(gh auth token)" | sbx secret set -g github

This is useful for agents that create pull requests, open issues, or interact with GitHub APIs on your behalf.

Yet no agent or shell in the sandbox is able to run plain gh commands after this step.

Also, you mention secret injection, but don't explain it. Is it expected that we should understand what that means and how to use it? Unless I missed something, your secret docs do not mention proxy-managed at all, nor do these.