What is Choro?

Choro is a desktop workspace for working on software with coding agents. It brings your project files, agent conversations, tasks, docs, designs, and Git workflow together so you can move from an idea to a reviewed change in one place.

Use it to understand an unfamiliar codebase, plan a feature, ask an agent to implement a task, or inspect and refine the result. You can also open files, run commands, and review changes yourself.

The Choro demo with a project README, terminal, file browser, and the running project in Preview. All screenshots in this article use fictional demo projects.

Start with a project

A project connects Choro to a folder on your Mac. It gives the work a shared home: the files you are changing, the conversations about them, and the requirements behind those changes.

• Code and files — browse the project, edit a file, and use the terminal or saved scripts.

• Agents — describe an outcome, follow the work, and continue the conversation.

• Tasks and docs — keep a brief or task linked to the agent implementing it.

• Design and Preview — explore a visual direction and inspect the running result.

• Git — review changes and prepare them for delivery.

You can keep several projects in Choro and switch between them from the sidebar.

Keep the brief connected to the work

You can start with a message, but you do not have to rewrite an existing brief. Tasks and docs can be the starting point for agent work, keeping the original requirements within reach.

A task in the demo’s Northstar Client Portal project, with its description, linked agent, and task board visible together.

The everyday workflow

1. Give the agent a clear outcome. Choose a project and describe what you want to understand or change. Include relevant files, a task, a doc, or a visual reference.

2. Plan when the approach is uncertain. Use Plan mode to clarify the work and review the proposed approach before implementation.

3. Follow the work. Read progress, answer questions, and handle approval requests when they appear.

4. Review the result. Inspect Changed Files, follow the What to check checklist when available, and use Preview for visible behavior. Ask for a focused correction if something is missing.

5. Ship when ready. Use the Git and Ship workflow to select the intended changes and prepare a commit, push, or pull request.

Choose the right way to work

• Quick Ask helps you investigate a project question without starting an implementation task.

• Project Talk gives you space to discuss a project, including by voice.

• An agent handles work that needs implementation and an ongoing conversation.

• Band lets a lead agent coordinate delegated assignments. Managed delegation is an opt-in beta feature.

• Studio helps you create and refine visual designs, then hand them to a coding agent for implementation.

What runs on your Mac?

Choro opens local project folders and runs project commands on your Mac. Coding agents use the provider you configure, such as Codex or Claude. A local project does not mean that all AI processing happens locally; provider access, permissions, and data handling still apply.

Try one small first task

Add a project, open New Agent, choose an available provider and model, and start with a question that is easy to check:

Explain how this project is organized and identify the main entry point. Do not change any files.

Read the answer and open the files it points to. Once you understand the project, ask for one small change and review the result before taking on a larger task.

For a short walkthrough, read Get started with Choro.