Put the right agent account on the job.
Keep work and personal CLI logins separate, then choose the profile new agents should use without signing in again.
Software work rarely begins at a blank prompt. It begins with an outcome, a ticket, a failed check, a review comment, or a question. Canopy keeps each path connected to the same local project.
These workflows now sit alongside terminals, Git, previews, and agents. Each one preserves the useful context around the action, so it can become work later without starting over.
Keep work and personal CLI logins separate, then choose the profile new agents should use without signing in again.
Save a bug, idea, or follow-up against the project and return to the exact work that was on screen when you noticed it.
Summon a named companion with the current project and open-view context to explain code, review a PR, or start a saved service.
Keep the question, sources, findings, recommendation, and unresolved choices together instead of losing them in a terminal transcript.
Completed agent jobs remain searchable with their brief, outcome, touched files, timing, and retained evidence—ready to continue or run again.
Use Canopy’s guided Build lens or work directly in Engineer. Both routes preserve the same project, processes, agent activity, and evidence underneath.
Start with what should be different. Canopy scopes the task, selects an eligible route, keeps the attempt durable, and records observed checks before calling it done.
Open an issue, give an agent an isolated worktree, keep its native terminal in view, then inspect the resulting files, commits, and pull request.
Read the diff and existing discussion, run a bounded agent review, edit its findings as drafts, and return follow-up work to the recorded conversation.
Give each session a visible identity. Agents exchange messages, claim files, refuse unsafe overlap, and surface stalls while you keep the whole project in view.
Start from an open question, retain source-backed findings with the project, then hand the recommendation to an agent when it becomes implementation work.
Enable access when you need it, check agent state from a phone or browser, answer a question, start work, or stop a process without moving the project to the cloud.
Switch at any point. There is no export, hosted fork, or context rebuild between the two sides.
Canopy keeps the route visible and the project yours.