Desktop app · macOS, Windows, Linux

Put Claude, GPT and Grok to work.All in one desktop app.

Personal bots keep up with your day: briefs, research, reminders. Coding agents build in your projects. A bot can hand a coding task to an agent and bring the result back to you.

Powered by Claude Code, OpenAI Codex and Grok. Nothing to train or host.

A bot hands a fix to a coding thread.

Monday brief

Claude · Your project companion

Bot

Monday, 9:00 AM

Good morning, Maya. Here’s what needs you today.

  • GitHub · 2 pull requests need review.

  • Linear · BK-142: booking dates need validation.

  • Slack · #support reported empty dates.

Start a thread for the booking fix.

Fix booking validation

Thread started in booking-api · Claude

You choose what your bot can do.
Example workspace with sample data. Switch between the bot and the coding thread.
  • Run several tasks at once

    Each task gets its own thread, plan and progress.

  • See what the AI is doing

    Plans, diffs and test results sit next to the chat.

  • Step in any time

    Approve a step, queue a follow-up or change direction.

How it works

You make the calls. The agents do the work.

Canopy is a desktop app for getting work done with AI. You ask, Claude, GPT or Grok does the work, and you decide what happens next.

  1. 1

    Ask in plain words

    Talk to a bot like you would to a colleague.

  2. 2

    It does the legwork

    The bot reads the tools you connected.

  3. 3

    You get the point

    A short brief, then you choose what happens next.

Coding works the same way. Open a thread, and an agent plans, edits and tests in your project.

Made for people who build things with AI

  • Developers

    Pair with AI every day without a wall of terminal windows.

  • Independent builders

    Ship your own product with agents that write, test and review.

  • Project leads

    Get briefs, research and reminders from a bot that knows your work.

Bots and threads

Two ways to hand off work

A bot handles the ongoing things. A thread is where an agent works on code. A bot can start threads for you.

01 Bots

For ongoing work

A bot remembers the conversation, checks your connected tools and follows your routines.

You

“Tell me when customers ask about refunds.”

Support bot

Two refund questions in #support today. I drafted replies.

On your schedule

Remembers the context Brings back the next step

02 Threads

For work on code

An agent works on real code in your project. Add a side thread for a second agent’s review.

src/checkout.ts +2 −1

validate(address) {
− return !!address;
+ return address.trim()
+   .length > 0;
  }

Claude Fix implemented

Codex Reviewing edge cases

Storefront Workstation

Runs on your computer Follows your permissions

Your bot starts the thread, follows the work, and brings the decision back to you.

A day with Canopy

Your whole workday, in one window

Stop copying context between terminals, tabs and chats. The conversation, the code and every decision stay together.

  1. 9:00 AM

    Start with a brief

    Your bot checks GitHub and Linear on a schedule and tells you what needs you.

  2. 9:20 AM

    Hand off two tasks

    Each task gets its own thread. They run side by side, each with a plan you can follow.

  3. 11:05 AM

    Step in when it counts

    Approve a step when the agent asks. Queue a follow-up without waiting for the turn to end.

  4. 4:30 PM

    Wrap up without loose ends

    Your bot reminds you of what you asked it to track. Tomorrow, every thread is where you left it.

Example day with sample data.

Get started

From download to your first task

Three steps. No Canopy account needed.

  1. 01

    Install Canopy

    Download the desktop app and open it. Canopy sets up what it needs on first start.

  2. 02

    Connect a provider

    Use Claude through Claude Code, GPT through OpenAI Codex, or Grok. Sign in or add API access. One is enough.

  3. 03

    Start a bot or a thread

    Describe the task. Add a project when an agent should work on code.

Works with the models you already know

Canopy uses the official agent tools: Claude Code from Anthropic, Codex from OpenAI for GPT, and Grok from xAI. There is no model to train or host. Model access comes from your provider, and their plans and usage limits apply.

Read the setup guide

Examples

See it on real work

A morning check-in. A bug that needs a second look. A project left running at home. Pick an example and watch it play out, step by step.

01

Start the day with the useful part

Ask for the blockers, changes, and decisions that matter today. Your bot can check connected accounts and existing threads before investigating a question in a new thread.

Sample workflow Step 4 of 4

All steps shown · Reduced motion

Project bot

Weekdays at 9:00 AM · Storefront

Your request

“Every weekday at 9, brief me on Storefront. Check Linear and GitHub, then investigate any checkout blocker without changing files.”

Your bot

There’s a checkout issue and a failing check. I’ll ask a read-only thread whether they’re connected.

Linear
Reads checkout issues and their current status.
GitHub
Checks recent changes and pull request context.

Connected accounts allowed · Investigation stays read-only

Workstation

Storefront

Coding thread

Investigate the checkout blocker

Claude traces the failed check. A Codex side thread gives the findings another look.

Claude

CodexSide thread

Investigation · Read only SHOP-128 → checkout validationFailing check → guest address case Finding: the same missing validation

The result comes back

A brief with a next step

The bot brings the investigation back into your morning brief.

  • Checkout issue linked to the failed check
  • Suggested next step: prepare a validation fix

No files changed. You decide whether to start the fix.

Illustrative examples, not live activity. Connected accounts need your grants. Threads follow the permissions you set.

Connected work

From loose end to next move

Morning triage

Your routine · Weekdays at 9:00 AM

  1. 01

    A new issue

    Linear SHOP-128

    Checkout accepts empty addresses

    Bug Checkout

    “An empty address gets through validation.”

  2. 02

    Your bot picks it up

    Project bot

    Reads the issue.
    Starts a coding thread.

    Allowed in Storefront

  3. 03

    Agents do the work

    Workstation

    Fix checkout validation

    Claude
    Writes the fix
    Codex · Side thread
    Reviews the changes
  4. 04

    You make the call

    Needs your approval

    Open a pull request?

    The fix and review are ready.

    Waiting for you
Your accounts. Your approval rules. The whole loop in view.
  • GitHub
  • Slack
  • Linear
  • Notion
  • Atlassian
  • Microsoft 365

Powered by remote MCP. Bring your own server for more tools. Microsoft 365 uses your organization’s endpoint.

Linked computers

Same work,
different desk

Leave your agents working at your desk. Pick up the thread from wherever you are.

StorefrontFix checkout validation

Runs on Workstation

  1. Claude read src/checkout/validate.ts

  2. Claude edited validate.ts+2 −1

    − return !!address;+ return address.trim().length > 0;
  3. bun test checkout24 passed

  4. Check guest checkout too.

    From LaptopDelivered to Workstation

  5. Codex Side thread

    Reviewing guest checkout

Reply to this thread

Workstation

Linked computers

Linked
  • Workstation

    Home · 2 threads running

    Runs the work
  • Laptop

    This computer · Following

    You’re here

Shared between them

  • Settings
  • Providers
  • Connected accounts
  • Skills

Stays on each computer

  • Project files
  • CLI logins

On your phone, open the web app when web access is configured.

Example thread with sample activity. Remote actions need the home computer to be reachable.

Mobile apps · Coming soon
A setup that travels
Share settings, skills, and connected accounts between linked desktop computers.
A clear place for the work
Each thread runs on the computer you choose. Send prompts and approvals through the link.
History that stays close
Read mirrored history offline. Reconnect to continue the work.

Questions

Good to know before you start

What Canopy is, what it needs and where it runs.

Read the setup guide
Is Canopy an AI model or a chatbot?

No. Canopy is a desktop app. It runs Claude Code, Codex and Grok, the official agent tools from Anthropic, OpenAI and xAI, and gives their work one place.

Do I need my own AI model?

No. You use models like Claude, GPT and Grok through their official agent tools. Sign in to a tool, or add API access. Provider plans and usage limits apply.

How do I connect Claude Code, Codex or Grok?

Install the agent tool on your computer. Canopy can install it for you on supported platforms. Then sign in through the tool, or add API access in Settings → Providers.

What’s the difference between Bots and Threads?

Bots keep an ongoing conversation, use connected tools, and follow routines. Threads let coding agents work with files and commands in a project on your computer.

Can a bot start a coding agent for me?

Yes. A bot can start a thread, send follow-up instructions, and report back when the work finishes. You choose what it can do. Approvals also appear in the bot conversation.

What syncs between linked computers?

Linked desktop apps can share settings, providers, connectors, skills and plugins. They keep readable copies of bot and thread history. Project files and native CLI logins stay on their own computers.

Can my bots work while I’m away?

Yes. Set a recurring routine or a reminder, and tell your bot when to message you. Scheduled work needs its home computer or server and assigned worker to stay available.

Do I need a server?

No. The desktop app runs Canopy on your computer and sets up its local services. The first start needs internet. You can also run Canopy on your own server. Either way, your provider processes model requests.

Get Canopy

Claude, GPT and Grok.
One app.

Install the app. Connect a provider.
Give your first bot or thread something to do.

macOS Apple Silicon · Windows x64 · Linux x64

Set up your own server

Model access comes from your provider. Their plans and usage limits apply.
The first start needs internet to set up local services.