Deployments and sessions

​

Deployments

​

Aliases

• zap deploy --watch rebuilds on change and advances only development.
• zap deploy --alias production --sha <sha> moves the production pointer to an existing deployment — it never builds a new one.

​

Sessions

zap session --agent transcode@production --json "transcode in.mp4 to h264"
zap session --agent transcode --session <id> --json "now to webm"
zap sessions ls --json

• The alias resolves once, at session creation; the resolved deploymentId is stored in the session. Later alias moves (including advancing production) never change a running session.
• Resume does not rebuild history locally — transcripts stay inside the VM under /zap/sessions/<id>/; only metadata (agent, alias, deployment id, turn count) mirrors to the control plane.
• Each turn streams JSONL events: turn.started, render, text.delta, tool.planned, tool.call, tool.result, turn.completed, turn.failed.

​

Development loop

zap deploy --watch                       # dev: rebuild + advance development on save
zap session --agent my-agent "try it"    # talk to the development alias
zap deploy --alias production --sha <sha>  # promote explicitly, by sha