Amp CLI reference - Environment variables
Amp environment variables
Amp documents 23 environment variables, including AMP_API_KEY, AMP_DISABLE_AMP_THREAD_TRAILER and AMP_DISABLE_AMP_COAUTHOR_TRAILER. Amp reads these from your shell environment. Each row gives the docs' description, accepted values and an example where one is documented.
Last verified 11 official pagesFull Amp reference
| Variable | Description | Example |
|---|---|---|
AMP_API_KEY | Access token for non-interactive environments such as scripts and CI. Must be a Settings access token starting with sgamp_; takes precedence over saved accounts. Reserved and cannot be stored as an orb secret. sgamp_... access token Docs: AMP_API_KEY | export AMP_API_KEY=your-access-token-here |
AMP_DISABLE_AMP_THREAD_TRAILER | Set to 1 to stop adding the Amp-Thread-ID trailer to agent commits, like amp.git.commit.ampThread.enabled=false. 1 Docs: AMP_DISABLE_AMP_THREAD_TRAILER | -no example |
AMP_DISABLE_AMP_COAUTHOR_TRAILER | Set to 1 to stop adding the Co-authored-by: Amp trailer. Can be set as a personal, project, or workspace environment variable for orbs. 1 Docs: AMP_DISABLE_AMP_COAUTHOR_TRAILER | -no example |
AMP_FORCE_BEL | When set, Amp sends a terminal bell for notifications instead of using host audio. Docs: AMP_FORCE_BEL | -no example |
AMP_SKIP_UPDATE_CHECK | Set to 1 to override amp.updates.mode and disable all update checks. 1 Docs: AMP_SKIP_UPDATE_CHECK | -no example |
AMP_REMOTE_CONTROL_TERMINAL | When neither terminal flag is passed, 1 enables web terminal access and 0 disables it. An explicit CLI flag takes precedence. 1 | 0 Docs: AMP_REMOTE_CONTROL_TERMINAL | -no example |
AMP_NO_GIT_SETUP | Set to 1 to make 1 Docs: AMP_NO_GIT_SETUP | -no example |
AMP_IGNORE_GUIDANCE_FILES | Colon-delimited list of globs matched against absolute paths of guidance files to skip. '*' ignores all guidance files. colon-delimited globs Docs: AMP_IGNORE_GUIDANCE_FILES | AMP_IGNORE_GUIDANCE_FILES="$HOME/.config/amp/AGENTS.md:$HOME/.config/AGENTS.md" amp -x "do the thing" |
HTTP_PROXY | Standard Node.js variable for using the CLI behind a corporate proxy. proxy URL Docs: HTTP_PROXY | export HTTP_PROXY=your-proxy-url |
HTTPS_PROXY | Standard Node.js variable for using the CLI behind a corporate proxy. proxy URL Docs: HTTPS_PROXY | export HTTPS_PROXY=your-proxy-url |
NODE_EXTRA_CA_CERTS | Standard Node.js variable pointing to custom certificates for corporate networks. path to PEM file Docs: NODE_EXTRA_CA_CERTS | export NODE_EXTRA_CA_CERTS=/path/to/your/certificates.pem |
EDITOR | Editor used by Ctrl+G and the editor command to write prompts, and by editor command Docs: EDITOR | -no example |
XDG_CONFIG_HOME | If set, system plugins are loaded from $XDG_CONFIG_HOME/amp/plugins/ instead of ~/.config/amp/plugins/. path Docs: XDG_CONFIG_HOME | -no example |
AMP_WORKSPACE_ID | Available inside an orb; the immutable workspace UUID, used for example when configuring Tailscale trust credentials. UUID Docs: AMP_WORKSPACE_ID | -no example |
AMP_PROJECT_ID | Available inside an orb; the project UUID. UUID Docs: AMP_PROJECT_ID | -no example |
AMP_ORB | Set inside an orb; the docs use it to allow all Vite hosts only inside an orb. Docs: AMP_ORB | allowedHosts: process.env.AMP_ORB ? true : undefined, |
PORT | Managed by Amp and given to every declared orb service; a service with a portal must listen on it. port number Docs: PORT | -no example |
PUBLIC_URL | Managed by Amp and given to services with at least one portal link; read it at runtime when the application needs its public origin. URL Docs: PUBLIC_URL | -no example |
AMP_THREAD_ID | Managed by Amp and given to every declared orb service. thread ID Docs: AMP_THREAD_ID | -no example |
$AMP_USER_EMAIL | The only placeholder supported in a portal entry; Amp replaces it in url, title, and description (URL-encoded in url). Docs: $AMP_USER_EMAIL | url: /__dev/log-me-in/$AMP_USER_EMAIL?returnTo=/ |
__VITE_ADDITIONAL_SERVER_ALLOWED_HOSTS | Set by Amp to the exact Portal hostname when it starts a portaled service, so Vite 6.1 and later allow it. hostname Docs: __VITE_ADDITIONAL_SERVER_ALLOWED_HOSTS | -no example |
WAYLAND_DISPLAY, DISPLAY, PULSE_SERVER | Inherited by threads served by a Linux runner started with --desktop so graphical programs open in its virtual desktop. Docs: WAYLAND_DISPLAY, DISPLAY, PULSE_SERVER | -no example |
GIT_CONFIG_COUNT / GIT_CONFIG_KEY_0 / GIT_CONFIG_VALUE_0 | Entries added under project Secrets & Env Vars to give orbs clone credentials for private repositories outside GitHub. Mark GIT_CONFIG_KEY_0 as a secret. Docs: GIT_CONFIG_COUNT / GIT_CONFIG_KEY_0 / GIT_CONFIG_VALUE_0 | GIT_CONFIG_COUNT=1
GIT_CONFIG_KEY_0=url.https://USERNAME:TOKEN@git.example.com/.insteadOf
GIT_CONFIG_VALUE_0=https://git.example.com/ |
The rest of the Amp reference
FAQ
How many environment variables does Amp have?
The official Amp docs list 23 environment variables, including AMP_API_KEY, AMP_DISABLE_AMP_THREAD_TRAILER and AMP_DISABLE_AMP_COAUTHOR_TRAILER. All of them are in the table above, in the docs' order.
What does AMP_API_KEY do in Amp?
Access token for non-interactive environments such as scripts and CI. Must be a Settings access token starting with sgamp_; takes precedence over saved accounts. Reserved and cannot be stored as an orb secret. Values: sgamp_... access token. Example: export AMP_API_KEY=your-access-token-here
Where are Amp environment variables documented?
On 11 official docs pages at ampcode.com, last read on October 17, 2026. Every row in the table links the exact section it came from.
Sources
Last verified . Names and examples are copied verbatim from the 11 official pages below, and every row above links the exact section it came from.
- ampcode.com/docs/cli/execute-mode1 item
- ampcode.com/docs/cli/settings6 items
- ampcode.com/docs/github1 item
- ampcode.com/docs/cli/remote-control1 item
- ampcode.com/docs/cli/clone1 item
- ampcode.com/docs/customize/agents-md1 item
- ampcode.com/docs/cli/keybindings1 item
- ampcode.com/docs/customize/plugins1 item
- ampcode.com/docs/orbs/customizing3 items
- ampcode.com/docs/orbs/portals6 items
- ampcode.com/docs/cli/runners1 item
Newsletter
Know when your tools change
One email per week. New coding agent releases, the flags and commands they add, and what they mean for how you work.