OrbStack#2418 opened
2 comments
Use cases
Put a crew to work.
What teams hand to Crewship first. Each use case shows what starts it, which agent does the work, the steps it takes and what you need to set it up.
Story 01 / 08
Featured
Code review
A crew reads every pull request and comments on it, so people review faster.
Illustrative workflow. Times, data and outcomes are examples.
Pull request #2418 opened
RileyReviews every pull request on the Release crew.Reading the diff2s3 files · +42 −7
Running the tests in the crew container38sarm64 job is missing a cache key.
Posting the review1s
Review is on the PR: 2 comments on ci.yml, tests pass. Suggest caching ~/.cache/go-build before merging. Waiting for Paul.
Story 02 / 08
Featured
Incident response
An alert starts a routine that gathers logs and proposes a fix. Add an explicit approval step before starting the rollback run.
Illustrative workflow. Times, data and outcomes are examples.
Alert: checkout p95 above 2 s
MorganOn call for the Operations crew.Gathering logs from the last 15 minutes6sDB pool exhausted after deploy 14:02.
Preparing a rollback to v124s
Asking Paul to approve the rollback
Rollback to v12 is ready. Pool size dropped from 40 to 10 in the last deploy. Approve in your Inbox and I will run it and watch p95 for 10 minutes.
Story 03 / 08
Featured
Ship a feature
A lead agent plans the work, member agents build it, and you merge.
Illustrative workflow. Times, data and outcomes are examples.
Mission: CSV export for invoicesRileyLead of the Release crew. Plans and delegates.Splitting the work into 4 tasks3s
Sam builds the endpoint, Quinn the docs14mBoth in the same crew container.
Opening the pull request2s
PR #2431 is open: endpoint, tests and docs. All checks green. You merge when you are happy.
Story 04 / 08
Featured
Issue triage
New issues go straight to the crew that should handle them.
Illustrative workflow. Times, data and outcomes are examples.
New issue: “Export fails for 10k rows”Triage rulesRoute new work automatically.
Matched label “billing” and source GitHub0s
Assigned to the Release crew0sRiley was mentioned and picked it up.
Issue #2433 is with the Release crew. Riley reproduced it and linked a draft fix.
Story 05 / 08
Featured
Nightly maintenance
Backups, cleanups and reports run at night. Repeat failures trip a breaker and land in your Inbox.
Illustrative workflow. Times, data and outcomes are examples.
02:00 · nightly-maintenanceMorganKeeps backups and cleanups running.Backing up the workspace2m412 MB, AGE-encrypted.
Rotating backups older than 14 days8s
Checking the restore with a dry run40s
All done at 02:03. Backup is 412 MB, restore check passed. If it fails three nights in a row, the breaker pauses it and you get a Repair item.
Story 06 / 08
Featured
Big migration
Long work keeps checkpoints, so a crew can resume or fork instead of starting over.
Illustrative workflow. Times, data and outcomes are examples.
Mission: move billing to the new cluster
AveryRuns long jobs with checkpoints.Copy 1 finished, checkpoint saved3h
Server restarted, resuming from checkpoint
Copy 2 matches by checksum2h
Both copies match. Ready for cutover on 15 December. You can fork from any checkpoint if you want to try a different plan.
Story 07 / 08
Featured
Docs from code
A routine notices when guides drift from the code and opens a pull request.
Illustrative workflow. Times, data and outcomes are examples.
Every Monday · docs-drift
QuinnKeeps guides in step with the code.Comparing guides with the code20sinstall.md still mentions port 3000.
Opening a pull request2s
PR #2440 fixes install.md (port 8080, new flag). Written in your docs style skill.
Story 08 / 08
Featured
Fully local
Run agents on your own hardware with Ollama. No API key, and inference stays on the machine.
Illustrative workflow. Times, data and outcomes are examples.
You: “Summarise these logs”AveryOpenCode with a local Ollama model.Running on your own GPU12sInference stays on your hardware.
Summary is in the chat. 3 errors, all from the same disk. Inference ran locally, no API key used.
Engineering
4 use casesp95 latency 2.4 sOn-call approves
Plan the APIBuild endpointWrite testsOpen PR
New issue
FinanceReleaseDocs
Operations
4 use cases02:00nightly-maintenance
Copy 1CheckCopy 2Cutover
install.md
PR opened
qwen3-coder:30bOpenCodeNo API key
How a use case works
Five parts, the same every time.
A workflow can combine a routine, a crew and credentials. These are the pieces, and where to read about each.
- TriggerA schedule, a webhook, an alert or a message starts it.Routines
- CrewAgents with the right tools work in their own container.Crews
- StepsA written scenario, step by step, with timings.Routines
- You decideAdd explicit approval steps where work needs sign-off.Inbox
- On recordEvery call and decision lands in the journal.Journal
- Email triageComing soon
- App designComing soon
Start from a recipe
Your crew is waiting.
Install Crewship on your own machine in a few minutes.