Authenticate with forges

Give the agent a project-scoped token when it needs to push or use forge APIs.

Authenticate

Use your normal devcontainer terminal, outside the agent. With the host launcher, open the equivalent terminal first:

claude-sandbox shell        # Skip if already in your devcontainer terminal

In either terminal, choose a forge:

claude-sandbox gh-auth
claude-sandbox glab-auth gitlab.example.com

The helpers prompt for a token without placing it in shell history. With the host launcher, exit the shell and run claude-sandbox to resume. In your devcontainer, stay in the terminal and run claude.

Note

DLS: Diamond GitLab Use claude-sandbox glab-auth with no hostname for gitlab.diamond.ac.uk. The shipped network config already allows its IP. Other internal forges need an allow-ip entry.

The agent can read the resulting token store. Tokens stay in the project container and must be entered again after recreation.

Choose permissions

Restrict access to the project and use a short expiry, such as 7–30 days.

For GitHub, select only the required repository. Pushing needs Contents: Read and write; add Issues or Pull requests write permission only for those tasks. The helper currently suggests read-only Contents, which does not permit push. Avoid workflow or administrative permissions unless required. See GitHub’s permission reference.

For GitLab, prefer a project access token. Git-over-HTTPS push uses write_repository; broader API operations may require api. The helper’s prompt recommends broader scopes; grant only what the intended workflow needs. See GitLab’s token scopes. Project tokens can also read Internal-visibility projects in some circumstances; see GitLab’s project-token documentation.

The helpers do not enforce token permissions.

Run without push access

When the agent does not need forge access, omit the token stores and credential helpers. With the PyPI launcher, add this to the host config:

no-forge

Or set the flag when creating the project container:

CLAUDE_SANDBOX_NO_FORGE=1 claude-sandbox

For an existing container, add --recreate to apply a changed environment variable. Recreation removes container-local packages and forge logins.

In your own devcontainer, set CLAUDE_SANDBOX_NO_FORGE=1 in the launching terminal or remoteEnv, or add no-forge to /etc/claude-sandbox.conf.

This removes the sandbox’s supplied credentials; it cannot prevent pushing with another token placed in the workspace or explicitly given to the agent.