Find your way around the workspace

Choro keeps a project and the work happening around it in one workspace. You can move from an agent conversation to the project’s files or preview without losing track of which project you are working on. This guide explains the main areas and gives you a short route through them.

The Choro demo above shows a fictional Northstar Client Portal project. From left to right: the project sidebar, an open code file, a running preview, and the file tree. A terminal is open beneath the code. Your layout can look simpler when fewer tools are open.

Start with the project sidebar

The left sidebar is your starting point. Select a project to work in its context, then open one of its conversations when you want to return to an existing agent task. Check the project name at the top of the workspace before sending a request or inspecting files.

Search and the Add project control sit at the top of this sidebar. Projects can be organized into sections and favorites, so the exact grouping in your workspace may differ from the demo. Those groups help you find projects; the selected project determines what you are currently viewing.

Use the right-hand tools to change what you are looking at

• Agents brings you back to agent work. Use a conversation for a task you want the agent to investigate or carry out, and return to it to answer questions or give a follow-up.

• Code opens the project’s files. Select a file in Files to read it in the editor, compare it with the agent’s explanation, or inspect the result of a change.

• Tasks is where you work with the project’s tasks. Open a task to read its description and context before deciding what to work on.

• Docs gives you access to project documents. Use a document when a brief or longer explanation should remain available beyond one chat.

Manage, Help, and Settings appear near the bottom of the right-hand toolbar. Settings holds app-wide preferences such as appearance, AI generation, voice, and keyboard shortcuts.

Understand the code, terminal, and preview areas

In the example, README.md is open in the editor and the Files tree is on the right. These are two views of the same project: the tree lets you choose a file, while the editor shows its contents.

The terminal below the editor shows output from the demo’s preview script. Run controls are at the top of the workspace; the available scripts depend on the project. Starting a project is a separate action from adding it to Choro, so an empty preview does not mean the project failed to open.

Preview shows the running page beside your work. Use it to inspect the visible result of a change. In this screenshot the fictional website is already running locally; your project needs its own runnable page or suitable local content before you can see a similar result.

Try a short orientation walkthrough

1. Select a project in the left sidebar and check its name at the top.

2. Open Code, then choose a familiar file such as README.md from Files. Confirm that its contents belong to the selected project.

3. Open Tasks or Docs and inspect an item if the project has one. An empty area can simply mean nothing has been added yet.

4. Return to Agents and open an existing conversation, or start a new one in the same project. Review the conversation before sending another message.

5. When you need to see a running result, use the project’s run workflow and open Preview. Keep the relevant conversation available so you can describe what you found.

When the workspace looks different

The panels you have open, the selected project, and your previous activity affect what appears in the center. You do not need to reproduce every panel in the screenshot. Start with the project and one tool, then open additional views as needed.

If a file or conversation appears to be missing, first check which project is selected. If a shortcut does not match an instruction, open Settings → Keyboard shortcuts to see your current binding. The toolbar remains a useful way to find the same feature while you are learning.

Next step

Once you can switch between a conversation and its project files, try one small agent task. Inspect both the agent’s explanation and the resulting files or preview before deciding what to do next.