Agree on the scope.
Plan the account view with your Chief of Staff. Confirm the permission checks and acceptance criteria before assigning implementation.
Your ideas.
Your AI team.
You lead.
For developers coordinating coding agents.
Give your agents a shared workspace to plan, build, and review a feature. Keep the brief, tasks, and results connected, with clear responsibilities and scoped execution approvals.
At home on macOS. Available in your browser.
YouStart with what you want to achieve.
“Let’s build a customer portal. I need an implementation agent and a reviewer.”
Chief of StaffCustomer portal · implementation + review
Let’s agree on the account view and permission checks first. The implementation agent will build the feature; the reviewer will check the changes against that brief.
IMImplementationBuild the feature
RVReviewerCheck the result
The next move is yoursProposed
Build the customer dashboardReview the scope before the team begins.
Explore execution approvalsIllustrative workflow · example project, agents, and scope
Keep the project connected.
Across agents and handoffs.
When a feature spans separate agent chats, you can become the link between the brief, the implementation, and the review. Here’s how that coordination lives in an Agentic project.
| The coordination work | Across separate agent chats | In an Agentic project |
|---|---|---|
| Keep the brief consistent | Carry the requirements and decisions from the planning chat into each agent’s instructions. | Save shared project instructions and knowledge. Keep acceptance criteria and decisions on the task. |
| Hand work to a reviewer | Bring the reviewer the brief, the changes, and the implementation agent’s handoff. | Assign the reviewer to the same project, with its tasks, repository, and shared reference material. |
| Decide what happens next | Bring together the chat replies, task updates, and code changes before choosing the next step. | Review the task discussion, repository changes, review records, and run details within the workspace. |
Illustrative comparison for the customer-portal feature shown below.
Walk through
one feature.
An illustrative customer-portal workflow.
From an agreed brief to a reviewable change.
Assign build and review.
Give implementation and review separate owners. Keep shared project instructions and reference material available to both.
Inspect the result.
Authorize the defined work, then inspect changes, task discussions, and review records. Decide whether to refine the feature or continue.
One project for the brief,
the code, and the review.
See task ownership, inspect repository files, and check who’s on the team. Explore the same customer-portal project from each view.
Customer portal
A clearer way for customers to manage their account.
WORKOWNERSTATUS
Define the account experienceChief of StaffChief of StaffReviewed
Build the customer dashboardImplementationImplementationWorking
Review the account permissionsReviewerReviewerQueued
Document the new workflowDocumentationDocumentationQueued
Requirements, decisions, and handoffs live with the task.
Explore the preview: switch between Tasks, Files, and Team.Example project and agents
From task to reviewable change.
Connect repository work with issues, branches, pull requests, and reviews through Gitea. Keep ownership and delivery evidence close to the original request.
Keep decisions available.
Save requirements and technical decisions in project knowledge. Share company guidance across projects, and inspect, correct, or forget an agent’s personal memories.
Approve the scope.
Review the changes.
Review the proposed assignment before it enters the queue. Follow its run and inspect the result against the brief.
- Approve a clear scope
- A saved proposal contains a title and scope. Choose Discuss to refine it or Allow execution to queue that assignment.
- Set the pace
- Chat only holds new autonomous assignments while current work can finish. Holiday holds covered work across the company.
- See the work behind the result
- Inspect run history, token reports, and CPU and RAM usage. Give each role the tools and credential access it needs.
Execution proposalWaiting for your decision
A clear brief.
Before work begins.
ObjectiveBuild the customer dashboard
Assigned toImplementation agent
Proposed scope
Implement the agreed account view, add permission checks, and submit the changes for review.
You choose whether to discuss or allow execution.
Illustrative proposal · scoped approval, visible responsibility
Know where work runs.
And what it can reach.
Storage, access, and authorization depend on the setup you choose. These are the boundaries behind the workflow.
- Where your data lives
- Desktop project data lives in a private local virtual machine. Server deployments store application data on their server; remote Coder workspaces keep working files in the selected environment. Connected AI and voice providers receive the content sent in requests.
- What agents can access
- Configure tools and credential grants per agent. Connected services enforce their own account permissions. Workspace commands use the access available in their execution environment.
- What an approval covers
- Authorize a direct Execute request or approve a saved proposal. Approval covers the assignment, not a separate prompt for every tool call. Working mode also allows eligible autonomous assignments.
Stay close to the work.
At your desk or on the go.
Founders can organize a product launch; engineering leads can supervise ongoing maintenance. Chat, voice, and Telegram connect back to the same team.
A conversation for every moment
Talk directly to an agent, gather several in a group, or keep your Chief of Staff close in the company chat dock.
Talk it through, out loud
Use supported real-time voice with Gemini Live or ElevenLabs configured. Voice and text share the conversation context.
Check in from Telegram
Pair a private account with a dedicated bot. Ask your Chief of Staff questions and review execution proposals on the go.
Your Mac. Your workstation.Persistent local data and desktop resource controls.
A workspace that can reach further.Supported remote Coder environments and a browser console.
From an agreed brief
to a reviewable change.
Plan the feature with your Chief of Staff. Assign implementation and review.
Keep the work and its evidence in the same project.