crewship agent
Create, configure, and inspect the AI agents that do the work inside a crew. Reach for these commands to provision a new agent, tweak its adapter or model, browse its runs and chats, or peek inside its container (files, logs, git history, peer inbox).Subcommands
crewship agent list
List all agents in the workspace.
Output columns: SLUG, ROLE, CREW, STATUS, ADAPTER, MEMORY
crewship agent get
Show detailed information about an agent.
<cron> (enabled|disabled)), Schedule Prompt, Next Run, and Last Run. When --webhook-require-timestamp is set on the agent, a Webhook Auth: timestamped signature required row appears.
crewship agent create
Create a new agent.
crewship agent update
Update an existing agent. Only changed flags are sent.
--self-learning is applied via its own audited endpoint and cannot be
mixed with other field updates in the same invocation — run it on its own:
crewship agent update <id> --self-learning[=false] --learning-reason "…".crewship agent rotate-webhook-secret
Mint a new webhook signing secret for an agent. The new secret is printed only
once; the previous secret stops validating immediately.
POST /api/v1/agents/{id}/webhook-secret/rotate. Table output shows
the secret once; --format json or --format yaml returns webhook_secret
and rotated_at.
crewship agent delete
Delete an agent. Prompts for confirmation unless --yes is passed.
crewship agent runs
List runs for an agent.
crewship agent stop
Stop a running agent.
crewship agent logs
Show agent container logs.
crewship agent debug
Show agent debug info including container state, environment variables, and crewshipd status. Output defaults to JSON (there is no table form); --format yaml and --format ndjson are honoured too.
crewship agent skills
List skills assigned to an agent.
crewship agent credentials
List every credential this agent receives — both the ones assigned to it directly and the ones it gets by belonging to a crew.
GRANT says where the credential comes from, which decides how you take it away:
A
crew row shows - for ID because no assignment row exists behind it. SOURCE is a different question: it names the approval that put a lease on the grant (manual, keeper_allow, escalation_approve), and is - for a standing grant.
crewship agent avatar
Inspect, set, or clear an agent’s stored avatar.
Normally an agent’s face is drawn on the fly from its avatar_seed and
avatar_style, which means it depends on the installed generator version —
upgrading the avatar library repaints every agent. Once a render is stored,
that exact image is served instead and the face stops moving.
An agent with no stored render is in the normal, pre-persistence state, not
a broken one.
crewship agent avatar show
Write the stored avatar SVG to stdout, or to a file with -o. Errors if the
agent has no stored render.
crewship agent avatar set
Store an SVG as the agent’s avatar.
The server validates the SVG against an allowlist of inert drawing elements;
anything that could load or execute something (scripts, event handlers,
external references) is refused. Maximum 64 KiB.
Storing is write-once — an agent that already has a stored avatar fails
with a conflict. Run
avatar clear first to replace one.
crewship agent avatar clear
Drop the stored render, returning the agent to generate-from-seed.
You rarely need
clear by hand: changing an agent’s --avatar-seed or
--avatar-style, or applying a crew-wide style with crewship crew apply-avatar-style, drops the stale render automatically.crewship agent mcp
Show or set MCP server configuration for an agent.
The JSON must contain a
"mcpServers" object at the top level. --set and --set-file are mutually exclusive. --resolved cannot be combined with set operations.MCP bindings subcommands
Beyond the bare config form above,agent mcp has CRUD subcommands over per-agent MCP server bindings (backed by /api/v1/agents/{id}/integrations):
add — binds a workspace or crew integration to the agent.
update — patch an existing binding (at least one flag required).
List output columns: ID, SERVER, SCOPE, ENABLED, CREDENTIAL.
crewship agent chats
List the agent’s recent chat sessions — id, title, status, message count, and start/end timestamps. Mirrors the SessionsSidebar panel in the web UI. Alias: sessions.
GET /api/v1/agents/{id}/chats.
crewship agent channels
List the notification channels an agent is allowed to post to. An empty list is
normal because channel access is default-deny.
GET /api/v1/agents/{id}/notification-channels.
crewship agent files
List the agent’s /output/<slug>/ working-directory artefacts, or download a single file. Same view the web Files panel renders.
Downloads stream into a tempfile next to the target and
rename(2) only on success — Ctrl-C or transport errors mid-copy do not clobber an existing good file with a truncated one.
Backed by GET /api/v1/agents/{id}/files and GET /api/v1/agents/{id}/files/download?path=….
crewship agent file-write
Upload bytes to the agent’s working directory. Source comes from --from (local file), --content (inline string), or stdin when neither flag is given. --content and --from are mutually exclusive.
Backed by
PUT /api/v1/agents/{id}/files/save?path=<path>. The handler reads r.Body raw — no JSON envelope — so binary uploads round-trip byte-for-byte.
crewship agent inbox
List peer-to-peer messages addressed to this agent. Useful for debugging cross-agent collaboration: did the message arrive? was it read?
GET /api/v1/agents/{id}/inbox.
crewship agent git-log
Show the git commit log from inside the agent’s container — useful for inspecting what code-writing agents have committed locally before any push.
[...] and {"commits":[...]} shapes from the server side.
Backed by GET /api/v1/agents/{id}/git-log.