The app is a native macOS workspace for agentic engineering. It keeps each task in its own Git worktree, connects terminals and chats to the code they change, and gives you one place to run, review, and ship parallel work.
Bring your own coding-agent CLIs, accounts, and subscriptions. Provider traffic goes directly from the local provider process to that provider; the app does not proxy prompts or hold provider credentials.
Choose your path
Section titled “Choose your path”| Goal | Start here |
|---|---|
| Complete one task from setup through cleanup | Your first workspace |
| Understand how the app organizes work | How it works |
| Configure and run a coding agent | Agents |
| Coordinate a cross-provider team | Orchestration |
| Inspect, verify, and ship a change | Review and ship |
| Build a repeatable workflow | Automation recipes |
Why use it
Section titled “Why use it”- Native and fast. The interface is written in Rust and rendered on Metal. Browser and HTML-preview tabs use macOS WebKit; the app does not ship an Electron runtime.
- Choose the right surface. Use a rendered Chat UI with markdown and inline diffs, or run a provider’s native CLI in a terminal.
- Run tasks in parallel. Each branch-backed task gets a separate working directory, terminal state, chat history, diff, and pull-request context.
- Orchestrate across providers. Put a frontier lead, specialized implementers, and independent reviewers into one visible, controllable team.
- Keep contexts separate. A workspace can group one repository or several related projects while preserving project-specific settings.
- Review before you ship. The Git action button follows the current worktree from first commit through checks, review, merge, and cleanup.
- Resume where you stopped. Workspaces restore their tabs, split views, terminal sessions, browser tabs, sidebars, and picture-in-picture windows.
- Stay local-first. App state stays on your Mac; an SSH workspace intentionally runs repository and provider work on the host you chose. Telemetry is anonymous and can be disabled.
- Automate repeatable work. Repository config can define setup, named run, teardown, and cleanup scripts. The
scCLI gives agents and scripts a stable worktree-aware interface.
Complete your first task
Section titled “Complete your first task”- Install the app and its companion tools.
- Follow Your first workspace from first launch through a completed task.
- Learn how workspaces, projects, and worktrees fit together.
- Configure your providers and models.
- Explore agent orchestration for cross-provider team workflows.
- Use Git actions and pull requests to ship the result.
Mental model
Section titled “Mental model”These objects organize the app:
| Object | What it represents | What it owns |
|---|---|---|
| Workspace | A durable context, such as a company, client, or personal work | Projects, theme, layout, and scoped defaults |
| Project | A repository or folder | Branch defaults, scripts, provider routing, and worktree location |
| Worktree | One checked-out branch and task | Files, Git state, target branch, tabs, and pull-request context |
| Tab | One tool inside a worktree | A chat, terminal, file, diff, browser, or other focused activity |
| Section | A manual or filtered sidebar group | Worktree organization by assignment, branch, PR/MR, checks, agent, or run state |
| Shared Context branch group | One feature spanning related repositories | FEATURE.md, shared instructions, and lazily materialized child worktrees |
The starred primary worktree is the project’s original checkout. Use it for quick questions or small edits. Create a task worktree for substantial work, especially when another task or agent may run at the same time.
A typical task
Section titled “A typical task”- Select a project and create a worktree with
+or ⌘N. - Describe the task in the new chat or terminal. By default, the first meaningful prompt also gives the temporary worktree a durable branch name.
- Work in chat, terminal, files, or a split view. Start any configured run scripts from the right panel.
- Review changed files and the diff against the worktree’s target branch.
- Follow the adaptive Git action: commit, push, create a PR or MR, fix blockers, merge, then delete the finished worktree.
Get help
Section titled “Get help”Use Troubleshooting for setup and runtime problems. Join the Discord community for product questions and feedback.