Inspect, rename, delete

Day-to-day housekeeping commands. All of them are read-only or near-read-only (except delete, which is destructive).

List agents

cast list

Output looks like:

Agents in ~/.cast/agents/

  email-assistant   [deployed: railway, v1.6]
  research-bot      [local: running on port 21357]
  slack-helper      [local: stopped]

The status suffix is one of:

Describe an agent

cast describe email-assistant

describe prints:

The deployment table uses the same SHA you’ll see in cast registry and when connecting.

Rename

cast rename email-assistant mailer

rename moves the directory and rewrites references in the SQLite database. It does not change git history if the agent is a Git repo — the old name remains in the commit log.

In the TUI, rename opens a modal that prompts for the new name with the same validation rules as the CLI.

Delete

cast delete email-assistant
cast delete email-assistant --force     # skip confirmation

delete removes the agent directory, all release tarballs, all deployment rows, and the database entry. This is destructive and unrecoverable — Cast refuses without confirmation unless --force is passed. To delete safely, first:

cast git push <name>          # backup to a remote
cast release <name> <ver>     # make sure the current state is in .cast/releases/
cast delete <name>

What “deleted” means in Cast

Cast does not currently support a soft-delete for agents (only for deployments — see deployment overview). When you cast delete, the agent is gone. The release tarballs under ~/.cast/agents/<name>/.cast/releases/ go with it, since they live inside the agent directory.

If you want a recoverable delete, push to a Git remote first (cast git init + cast git push); the repo retains the full history.