Choose a coding-agent workspace around your code and review process. Canopy organizes supported harnesses around projects, Threads and workers. It keeps work visible while the chosen harness executes it.
Separate the harness from the workspace
The harness runs the coding agent and supplies its native capabilities. Canopy supports Claude Agent SDK, Codex app-server and Grok CLI. Its worker starts the chosen harness, while Canopy organizes instructions, recorded activity and controls around the task.
Editor, terminal and remote workflows serve different needs. Ask where commands run, how you inspect changes and what happens when you leave the viewing device. Check each product's current behavior directly.
Organize work around a concrete project directory
Add a workspace for the project's directory on a worker. Each Thread records the execution location, provider and task. Project workspaces can span computers, so choose the environment each task needs.
Use worktrees when a task should have its own Git working directory. Keep changes reviewable and exchange code through your normal Git workflow. A shared project name or linked computer does not make independent directories synchronized copies of the same working tree.
Make delegation and approvals part of the work
A main Thread can delegate a focused question to a side thread, including another supported provider. For example, one agent can implement a change while another reviews boundary conditions. Reports return to the main Thread, and you can inspect the delegated work.
Choose a permission mode before the task begins. Read only supports investigation, while Ask first keeps approval requests in view. Broader modes change what can proceed without questions. Review the actual request rather than treating a completed status as proof that a change is correct.
Connect coding to the work around it
A personal bot can gather an issue from a granted connected account, start a Thread and return with its result. A routine can repeat that responsibility on a schedule. This gives planning, external context and coding execution a visible connection without requiring one provider for every task.
Start locally or with your own server, then connect Claude Code, Codex or Grok through its official agent tool. Execution computers must remain available. Provider capabilities and history rules still differ; do not assume that a shared interface makes native sessions interchangeable across harnesses.