Docs · Using BetterC0de
Workspace views
Editor, Agent and Canvas — the three views of the BetterC0de desktop workspace and when to use each one.
BetterC0de connects AI coding tools with the place where their changes actually happen. You can discuss a task, inspect files, use a terminal, preview the result and review diffs without hopping between separate apps.
The pieces
| Concept | Meaning |
|---|---|
| Project | The folder or repository you are working on. It gives files, tools and conversations a shared context. |
| Provider | The coding agent (and its CLI) that runs your AI requests. |
| Model | The AI model available through the selected provider. |
| Conversation | A task's messages and activity. You can return to it as the work develops. |
| Diff | A comparison showing what changed in your files. |
| Preview | Your running web project, rendered inside BetterC0de. |
| Worktree | A separate checkout of a Git repository, for tasks that need independent branches and files. |
Editor — understand and refine
Use Editor when files are the center of the task. Explore the project tree, search for text, edit files and keep the chat beside your code. Open a changed file from the Diff view to inspect it in place.
Agent — discuss and delegate
Use Agent when conversations and task progress matter most. Arrange panes for the chats, terminals, plans and diffs you need to follow.
Several conversations can work on the same repository. Keep their responsibilities clear — separate chats alone do not isolate file changes. Use separate worktrees when tasks need independent checkouts.
Canvas — see the project in context
Use Canvas to arrange projects and their previews on one visual surface. Check desktop, tablet and mobile layouts, inspect runtime information and keep a project's conversation next to its preview.
In browser previews, Select lets you pick elements and attach visual context to a request. Browse restores normal interaction. Live style tweaks are preview-only — use Send to AI to ask for the matching edits in the project files.
A working rhythm that holds up
- Describe the outcome. Goal, relevant context, constraints.
- Follow the work. Read responses and review permission requests.
- Inspect the result. Files, diffs, the running preview.
- Refine and save. Request adjustments, verify behavior, commit what you want to keep.
Remote access
Another device can pair with the running desktop app over your network. The desktop must stay running and reachable for the connection to work.