Skip to main content

​
crewship onboarding

The CLI half of Crewship’s first-run flow. The web wizard runs a conversation with the Crewship Guide, which proposes a crew; these commands are the same surface without the chat, and the counterpart to the Onboarding API. The split matters more than it looks. Proposing writes nothing — it stores a roster server-side and hands you an id. Applying is a separate command that reads only that stored payload, so what you inspected and what gets built are the same object. A proposal you never apply leaves no trace but a row.

​
crewship onboarding proposal create

Resolve a crew into a full roster and store it. Creates no crew, no agent and no credential.

​
Flags

Give the roster either way: --template-slug to derive it, or --agent to name it. A bespoke crew with no matching builtin is a first-class case, and it is the one the Guide actually uses. Supplying both is allowed: the named roster wins and the template supplies the rest of the crew metadata. Only the name and the role are taken from what you type. Each agent’s system prompt, tool profile and adapter are composed server-side. Prints the proposal id, its status (PENDING) and the resolved roster. Add --output json for the full payload.

​
crewship onboarding proposal get

Read a stored proposal, including whether it has already been applied.
Takes the proposal id as its only argument. A proposal in another workspace reports as not found rather than forbidden — its existence is not disclosed.

​
crewship onboarding proposal apply

Create the crew from the stored payload. The only write in this surface.
Runs under your own session, so the crew belongs to you rather than to the agent that proposed it. Nothing you pass here can change what is built — the payload was fixed when the proposal was stored. Idempotent: applying twice returns the original crew with already_applied: true instead of creating a second one, so a retried command is harmless. Prints the crew id, slug and the agents created.

​
crewship onboarding setup-agent start

Ensure the Crewship Guide exists in this workspace and print its agent, crew and chat ids.
Idempotent — repeated calls return the same agent and the same chat, so the conversation history survives. Useful for opening the Guide’s chat from the CLI, or for confirming the reserved crew was provisioned on a fresh install.

​
See also