Sheshiyer Supacode CLI
Control Supacode from the terminal. The supacode command is available in all Supacode terminal sessions.
CRITICAL: ID Tracking
NEVER call supacode tab new or supacode surface split without capturing
the output. They print the new UUID to stdout. Without it you cannot target
the resource afterward.
NEVER omit -t/-s when targeting a created resource. The env vars point
to your own shell, not to anything you created.
For new tabs, surface ID = tab ID.
Correct:
TAB_ID=$(supacode tab new -i "npm start")
SPLIT_ID=$(supacode surface split -t "$TAB_ID" -s "$TAB_ID" -d v -i "npm test")
supacode surface close -t "$TAB_ID" -s "$SPLIT_ID"
supacode tab close -t "$TAB_ID"
WRONG:
supacode tab new -i "npm start" # BAD: not captured
supacode surface split -d v -i "test" # BAD: missing -t/-s, targets your shell
Commands
supacode worktree [list [-f]|focus|run [-c]|stop [-c]|script list|archive|unarchive|delete|pin|unpin] [-w <id>]supacode tab [list [-w] [-f]|focus|new|close] [-w <id>] [-t <id>] [-i <cmd>] [-n <uuid>]supacode surface [list [-w] [-t] [-f]|focus|split|close] [-w <id>] [-t <id>] [-s <id>] [-i <cmd>] [-d h|v] [-n <uuid>]supacode repo [list | open <path> | worktree-new [-r <id>] [--branch] [--base] [--fetch] [--name] [--location]]supacode settings [<section>]supacode socket
list outputs one ID per line (percent-encoded for worktrees/repos, UUIDs for tabs/surfaces).
worktree script list outputs tab-separated <uuid>\t<kind>\t<displayName> rows; running scripts are ANSI-underlined.
Use these IDs directly as -w, -t, -s, -r, -c flag values.
Flags: -w (worktree), -t (tab), -s (surface), -r (repo), -c (script UUID for worktree run/stop), -i (input), -d (direction), -n (new ID).
Env var defaults only target your own shell session. Pass explicit IDs for created resources.