CLI

bun alchemy <command> [options]

Every command operates on an alchemy.run.ts stack file (or a custom entrypoint passed with --config <file>, which must exist) and targets a stage.

Command map

alchemy
├─ deploy              # plan → approve → apply
├─ plan                # preview changes, apply nothing
├─ destroy             # delete every resource in a stage
├─ drift               # detect (and optionally repair) infrastructure drift
├─ unsafe nuke         # delete everything a provider can list, tracked or not
│
├─ dev                 # hot-reloading development loop
├─ logs                # fetch past log entries, or tail live with --tail
│
├─ profile create|rename|edit|refresh|current|list|show|delete
│                      # manage credentials and accounts (bare `profile` opens the dashboard)
│
├─ state list|read|delete        # inspect and manage the state store (bare `state` opens the explorer)
│
└─ provider
   ├─ check-env           # CI preflight: verify required provider env vars are set
   ├─ aws bootstrap|teardown
   └─ cloudflare bootstrap|teardown|token|state logs

Each command has its own page: deploy, plan, destroy, drift, unsafe nuke, dev, logs, profile, state, AWS provider commands, and Cloudflare provider commands. The workflow guides cover adopting resources and inspecting state.

Common options

Option	Description
--stage <name>	Stage to target. Falls back to $ALCHEMY_STAGE, then live_$USER (dev_$USER for alchemy dev). Must match [a-z0-9]+([-_a-z0-9]+)*.
--profile <name>	Auth profile from ~/.alchemy/profiles.json. Overrides $ALCHEMY_PROFILE; defaults to default.
--env-file <path>	File to load environment variables from. Defaults to .env.
--yes	Yes to all prompts.
--no-input	Disable prompts and the interactive TUI. Commands that would need input fail instead of hanging.
--config, -c <file>	Stack entrypoint. Defaults to alchemy.run.ts; must exist.

Use --profile with deploy, plan, destroy, dev, logs, drift, or state.

The interactive TUI

In an interactive terminal, deploy, destroy, and plan render a live TUI: the rendered plan, an arrow-key approval prompt, and per-resource apply progress that unmounts into the final output. Everywhere else the same commands emit plain line-oriented logs.

The --no-input flag and environment variables override the detection, in this order:

Signal	Effect
--no-input flag	Force plain output
ALCHEMY_PLAIN=1 or ALCHEMY_NO_TUI=1	Force plain output
ALCHEMY_TUI=1	Force the TUI
No TTY, CI=1, or a known agent env var (CLAUDECODE, CLAUDE_CODE_ENTRYPOINT, CURSOR_AGENT, AIDER_MODEL, CODEX_CLI)	Force plain output

Interactive terminals use the animated TUI; redirected and non-interactive runs use append-only output.

Plain mode never prompts — it prints the plan, makes no changes, and fails with error: Cannot approve this operation without terminal input. Pass --yes to continue. In CI, always pass --yes.

Exit codes

Exit codes are script-safe: 0 only means the command actually completed.

Code	Meaning
0	Command completed
1	Failure, including a declined plan or bare profile/state without a terminal
130	Cancelled by the user (Ctrl-C, or Escape inside a prompt)

Running these commands in a pipeline? See CI.

Where next

• deploy — plan, approve, and apply changes
• dev — hot-reloading development loop
• profile manages credentials and connected accounts
• state — inspect and manage the state store
• Stages — how environments are isolated
• CI — run the CLI in pipelines