Chat or terminal
Use the structured chat or work in the coding CLI you already know.
A little direction.
A lot of progress.
Brief your agents, give them the context, and keep work moving. One conversation or a band of specialists, with you deciding what ships.
Pulse / Shareable dashboard linksOne brief, connected work
Pulse · interface
In progress
Build the share dialog
Following the design
Using the project’s spacing and color tokens.
Using the project’s spacing and color tokens.
DashboardShare.tsx +23
ShareDialog.tsx +48
Pulse · shareable links
Waiting for you
Agree on the plan. Then build.
Signed link with a seven-day expiryRead-only view of the dashboardShare dialog and copy confirmationPlan ready for your approval
Pulse · backend
Ready for review
Make the link safe to share
Access checks covered
Expired links and private dashboards tested.
Expired links and private dashboards tested.
share_link.ts +48
share_link.test.ts +32
Illustrative project workflow
Claude Code
Codex
OpenCodeStay in the conversation.
Questions, plans, progress, and review belong together. Choro keeps each run’s status and history visible, so you can steer the work without reconstructing what happened.
- Answer questions where the work is happening.
- Review a plan before implementation.
- Return to a conversation with its history intact.
Agent · a decision that matters
Choose the behavior
Seven days by default, or a custom expiry for each link?
Seven days by default, or a custom expiry for each link?
The plan follows your decision
Add expiry to the token and cover the expired-link state.
Add expiry to the token and cover the expired-link state.
Tell the agent what you have in mind…
Put your band together.
Give design to one specialist and backend to another. Your lead assigns the work, brings the results together, and checks the complete feature.
Save bandmates with the skills and instructions you want them to bring to the next project.
Beta feature. Delegation is available in Codex and Claude chats when enabled in Settings.
Band · shareable links
Your lead coordinates the work
UI DesignerShare dialog, copied state, expired links
WorkingBackend EngineerToken generation, expiry, access checks
ReadyLead agentIntegrate and verify the complete flow
ReviewingGive parallel work its own space.
Solo gives an agent its own Git worktree. Files, changes, and preview follow that lane, so you can keep several tasks moving and review each result in context.
- Work on separate features in separate worktrees.
- Preview the app in the active lane.
- Rejoin the project or ship a pull request.
Solo · worktree lanes
mainYour project’s shared working tree
solo/share-linksShareable links · own files and preview
solo/fix-timezonesReport timezones · separate changes
Your choice of provider
Choose your supported provider and model for the task. Provider access and plans remain separate from Choro.
Review before you ship
Inspect changes, verify the result, and decide what belongs in the final commit.
A few things
to know.
Visit the help center Does every agent need its own worktree?
No. Use a regular agent for work in the project, or Solo when you want a separate Git worktree for a task.
Is delegation available everywhere?
Band delegation is a beta feature for Codex and Claude chats. Enable it in Settings and choose the delegation limits that fit the task.
Does Choro include a coding-provider subscription?
No. Choro connects to supported coding providers. Their account requirements, usage limits, and charges still apply.
There is more to Choro
Explore Project contextMake room for your next idea.
A native workspace for your Mac.