crewship seed
Replaces the old prisma/seed.ts script. Creates a full demo environment — admin user, workspace, four connected crews, agents with system prompts, credentials, integrations, routines, schedules, and sample issues — entirely through the REST API so business logic (validation, encryption, audit logging) is exercised end-to-end.
On a fresh database, seed bootstraps the admin user (demo@crewship.ai) itself. On an existing database, it requires authentication (run crewship login first) and a selected workspace.
Flags
| Flag | Default | Purpose |
|---|
--nuke | false | Delete all workspace contents before seeding. Runs after auth, so a missing/invalid token won’t wipe the wrong workspace. Prompts for confirmation — see below. |
--yes | false | Skip the --nuke confirmation prompt (for CI/scripts). Without it, an interactive nuke requires typing the workspace slug; a non-interactive session refuses to nuke unless --yes is set. |
--skip-issues | false | Skip the issue/project/label phase. Useful when you only need crews + agents and want a faster seed. |
--password <pw> | password123 | Admin password used by bootstrap. The default is the dev convention password123 — override in any non-local environment. |
--smoke-test | false | After seeding, send a test prompt to each agent to verify end-to-end execution. Implies --wait-provision. |
--smoke-timeout <s> | 60 | Per-agent timeout (seconds) for the smoke test. |
--provision-timeout <s> | 900 | Per-crew provisioning timeout (seconds). |
--wait-provision | false | Block until all crews finish provisioning. Default is fire-and-forget — seed returns while provisioning runs in the background. |
--test-backup | false | After seeding, run a backup/restore round-trip self-test on one crew. Implies --wait-provision. |
--with-memory | false | Pre-seed agent memory tiers (AGENT.md / CREW.md / PERSONA.md / pins.md / daily/{date}.md / learned.md) for the demo workspace; useful for memory-recall demos and live GDPR/RBAC tests. |
--with-users | false | Add four extra users (ADMIN, MANAGER, MEMBER, VIEWER) to the workspace for RBAC matrix testing; requires CREWSHIP_ALLOW_SIGNUP=true on the server. |
Examples
First run on a fresh dev DB
crewship seed
# Bootstrapping...
# Using dev default admin password: password123
# (override with --password for production)
# Bootstrapped admin: demo@crewship.ai
# Workspace: w_abc123
# …
# Provisioning 4 crew(s) in the background.
# Agents in these crews become runnable once provisioning finishes (~few minutes).
# Status: crewship crew provision status <slug> (or re-run `crewship seed --wait-provision`)
#
# ✓ Seed complete: 4 crews, 14 agents
# Login: demo@crewship.ai / password123
~/.crewship/cli-config.yaml, so any follow-up command picks up the demo session.
Reset and reseed
crewship seed --nuke
# ⚠️ NUKE permanently deletes ALL contents of workspace "Acme Engineering" (acme)
# on https://crewship-dev2.unifylab.cz — 4 crew(s), 12 agent(s), plus every
# issue, project, label, pipeline, schedule, webhook, credential, inbox item,
# and escalation, and each crew's docker container(s)+volumes (cached images
# are kept). This cannot be undone.
#
# Type the workspace slug "acme" to confirm the wipe: acme
seed --nuke is an alias for crewship nuke all — the full teardown: DB entities plus inbox items, escalations, and each crew’s docker container(s)+volumes. Cached devcontainer images are preserved, so the reseed reuses them instead of forcing a rebuild. Use the nuke subcommands directly when you want to clear just one thing (e.g. crewship nuke inbox --kind failed_run to drop failed-run spam without touching data).
Wipes the active workspace’s contents first, then seeds. Two guards:
- Auth before nuke — the auth step runs before
--nuke, so a typo in --server or a stale token fails before anything is deleted (it can’t trash a different workspace).
- Typed-slug confirmation —
--nuke prints a blast-radius summary (workspace, server, crew/agent counts) and requires you to type the workspace slug exactly before it proceeds. This is the guard against an accidental wipe of the intended workspace.
For CI or scripted resets, pass --yes to skip the prompt:
crewship seed --nuke --yes
--nuke refuses to run unless --yes is given — it never wipes unattended on a guessed confirmation.
--yes removes the only interactive safety on the most destructive command in the CLI. Reserve it for automation against throwaway/dev instances; never wire it into a script that could point at a real workspace.
CI-friendly run that waits
crewship seed --wait-provision --smoke-test
pnpm test:e2e after this lands.
Skip the issue phase for a faster crew-only seed
crewship seed --skip-issues --password "$(op read op://Dev/crewship/admin)"
--skip-issues halves wall-clock time for crew-development work.
Backup self-test (CI guardrail)
crewship seed --test-backup
--wait-provision. Picks the first provisioned crew (preferring research because its container is small and dependency-light), runs a backup/restore round-trip via the admin self-test endpoint, and fails the command if the canary doesn’t verify. Use as a CI guard for the backup pipeline.
Seed phases (in order)
| Phase | What it does | Failure mode |
|---|
| 1. Bootstrap / auth | Hits /api/v1/bootstrap on a fresh DB; falls back to existing CLI token | Fatal |
0. Nuke (if --nuke) | Wipes workspace contents | Fatal |
| 2. Crews + members | Creates four crews and links the admin user | Fatal |
| 2a. Crew connections | All-pairs bidirectional crew_connections so missions can hand off | Non-fatal (logs and continues) |
| 2b. Provision crews | Triggers devcontainer image builds in parallel | Errors deferred to end |
| 3. Agents | Inserts agents with system prompts | Fatal |
| 4–5. Skills + assignments | Workspace skills + per-agent skill bindings | Fatal |
| 6–7. Credentials + assignments | Demo API keys + per-agent credential bindings | Fatal |
| 8–9. Integrations + bindings | MCP servers, GitHub/Slack stubs | Fatal |
| 9b. Routines | Starter routine library + eval scenarios (deterministic recipes, a morning briefing, an agentless feed-watch probe and its wake-gated change report) | Non-fatal |
| 9b. Schedules | Demo crons so /activity has data on first load — including a wake-gated feed watch whose agentless probe runs token-zero every 15 minutes | Non-fatal |
| 10. Issues | Sample issues, projects, labels (unless --skip-issues) | Fatal |
| 10b. Wait for provisioning | If --wait-provision, blocks until images are ready | Fatal in sync mode, deferred otherwise |
| 10c. Backup self-test | If --test-backup, full round-trip on one crew | Fatal |
| 11. Summary | Prints Seed complete: N crews, M agents | — |
| 12. Smoke test | If --smoke-test, one prompt per agent | Fatal on any failure |
crewship seed returns quickly (~seconds for the API mutations) while crew containers warm up in the background. Pair with crewship crew provision status <slug> to check on individual crews.
Common errors
bootstrap request failed (is the server running at http://localhost:8080?) — the server didn’t answer. Start it with crewship start and retry.- **
DB already initialized. not logged in — run \crewship login` first** — the database has a user but the CLI has no token. Log in (or use crewship admin reset-password` if you’ve lost UI access).
--test-backup requested, but no crew successfully started provisioning — every crew failed to trigger provisioning. The seed wasn’t going to be useful anyway; the explicit error is so CI doesn’t go green on a broken pipeline.Routine seeding hit an error (continuing): … — printed but non-fatal. Routines depend only on crews, so a parse error in one DSL doesn’t torpedo the rest of the seed.
See also
crewship init — minimal admin-only bootstrap if you don’t want demo data.crewship setup — interactive template picker for a single-crew workspace.crewship crew — crewship crew provision status <slug> for checking background builds.crewship apply — declarative manifest as a longer-term alternative to seed.
