The April Update: Captain Takes the Helm
The April update simplifies how work happens in Capy. Build mode is deprecated, and Captain now handles every task from one conversation.
Captain now plans, delegates, monitors, and ships without asking you to switch modes.
Captain-only workflow
Build mode is deprecated. All tasks now start in Captain, where the conversation, plan, execution, and PR stay connected.
Captain plans the work, delegates implementation to Build agents, monitors progress, and creates pull requests when the task is ready. You describe the outcome once, then Captain keeps the workflow moving.
Tasks are now thread-local. Instead of global task numbers, each thread gets its own Task 1, Task 2, Task 3 sequence.
The result is simpler: one conversation, one workflow, and task numbers that make sense in context.
Smarter model configuration
Model selection is now thread-scoped. You can pick the Captain model and Build model for each thread instead of changing a global setting before every task.
Speed and reasoning toggles give you finer control over how a thread behaves. Use faster settings for small edits, deeper reasoning for complex planning, and change them without affecting other work.
Claude Opus 4.7 is now the default Captain model.
Every thread also gets a unique identifier like SCO-1234. You will see it in the sidebar, dashboard, and Slack so it is easy to connect a conversation to the work it produced.
CI awareness
Captain is now CI-aware. When Captain opens a pull request, it subscribes to the PR checks and watches them as they run.
If a check fails, Captain detects the failure, reads the output, and can send the fix back through the workflow. You no longer need to copy CI logs into chat or explain which job failed.
This makes PR follow-up feel much closer to a real teammate. Captain sees the signal as it happens and can react before the failure gets stale.
Try it now
Start a new thread and describe what you want to build. Captain will plan the work, choose the right execution path, track the result, and react when CI needs attention.
The new workflow is available now. One conversation is enough.
