A coding task needs more than the latest answer. It needs a project, an execution computer and a readable history. Canopy Threads keep those pieces together while agents work with your files and commands.
Choose where the task runs
A project groups related work. Its workspaces point to real directories on workers, including computers with different operating systems. When you start a Thread, choose the workspace with the code and tools the task needs.
The Thread records its provider, worker and directory. Switching the viewing device does not move execution. You can follow a desktop task from a laptop while the agent continues using the original computer's files, installed tools and access.
Follow the work between messages
The transcript brings messages, plans, tool activity, commands and file changes into one timeline. It gives you a place to understand the current result before adding another instruction. Approval requests and agent questions appear alongside the work.
Queue a follow-up while a turn is running, or steer the active turn when the harness supports it. Queued messages can be edited. If the direction changes, interrupt the turn and leave the next instruction in the same Thread.
Use another agent for a bounded task
Side threads let agents delegate focused work, such as reviewing a validation change or inspecting a failing test. A side thread can use another supported provider without inheriting the original provider's session. Its report returns to the main Thread.
For an alternative approach, fork from a finished turn. Shared-history forks follow provider compatibility rules. A fork does not provide a general way to transplant a native session between different harnesses or computers. Choose the intended history and placement before starting.
Start with a reviewable task
Connect Claude Code, Codex or Grok and add your project workspace. Start with a concrete change and choose a permission mode. Ask first keeps approvals visible; Read only suits investigation. Broader modes need a deliberate choice.
Worktrees can give a task its own Git working directory. They still need normal review and a sensible Git workflow. Canopy does not automatically synchronize project files between computers, and queued work on an offline worker resumes there when it reconnects.