Conductive

Conductive is a coding tool at conductive.build, in the browser and in a Mac app. Each workspace has its own cloud computer, where agents powered by Claude and Codex work, and one branch at a time. It can hold one task after another. The agents run only in the cloud. It replaces Conductor Cloud, which shuts down on 20 November 2026.

Status

Today the repository holds:

• the architecture doc and the protocol docs, which state the requirements
• the mockup catalogue, which draws every screen at phone and desktop sizes
• the app package, with tests against fake GitHub and Boat servers and local D1 storage, and the complete gate, which GitHub Actions runs
• the Mac app in desktop/, with signed packages and update support, as Mac app says

A test deployment runs at conductive.build. Each push to main deploys it, as Automatic deploys says. The project is not in production yet. Deployment inputs lists what a deployment needs.

Features

Conductive has these features. The protocol docs state each one. A feature that is not complete yet says so.

• Sign in with GitHub. The product is free, with no plans or billing, as Orgs and members says.
• A waitlist. A new account waits until an operator approves it, or an invite code, a referral code, or an org invitation lets the person in. An operator can turn the waitlist off. Each new person then gets in at once, unless sign-ups are paused.
• Every cloud computer runs in the app's own Boat account, so users need no Boat account.
• A new workspace starts as an empty chat. The first message creates it, with its own cloud computer and branch.
• Chat with agents powered by Claude and Codex. A workspace holds several sessions, and one picker sets the model and the effort.
• Send a message during a turn, or stop the turn.
• Attach files of up to 100 MB each to a message.
• Each user connects a Claude subscription token, a ChatGPT plan through device code sign-in, an API key, or an own endpoint in Account or Get started.
• Files and Changes, a terminal, and port previews. The live desktop is hidden for now, as Desktop says.
• A pull request bar with the GitHub state of the branch and its checks. It sends the agent fixed requests, such as Create PR and Fix checks, and merges as the member. After the merge, Continue moves the workspace to a new branch, with the same cloud computer and sessions.
• One prepared cloud computer image for each org, built from an install script, with a startup script and env vars.
• Agents can create workspaces and sessions. They can read chats and message sessions across the org.
• Routines run a saved prompt on a schedule or on a pull request event, each time in a new workspace.
• Each workspace has a number, such as W-395. A press on the number in the header copies the link of the workspace. A workspace link in chat shows as a chip with the number and the name.
• Orgs with members, sections, reassignment, Archive, and Delete org.
• A menu on a workspace row moves, reassigns, renames, or archives the workspace.
• A command palette, on ⌘K or Ctrl+K, finds the workspaces of the org, runs the actions of the page, and opens the settings.
• Keyboard shortcuts, which each person can change on the Account page.
• Send feedback from the command palette, with screenshots. The team gets each message by email, and replies to the primary verified GitHub email.
• The web app works on phones and on desktops.
• A Mac app for macOS, with the native window buttons in its own top bar. An agent can ask to run a command on the Mac of the person who sent its turn. Published packages update themselves from GitHub releases.

What a user needs

• a GitHub account
• at least one agent login:
  • for Claude, a Claude subscription token, an Anthropic API key, or an own endpoint that serves the Anthropic Messages API
  • for Codex, a ChatGPT plan with device code sign-in enabled, an OpenAI API key, or an own endpoint that serves the OpenAI Responses API

An own endpoint is a gateway or a proxy that the user chose, with its key. Own endpoint logins states its address rule and its other rules.

Get started

The Run it section of the web app README says how the app runs in development and in the production build.

1. Install Node 24, as .nvmrc says. The mockups README lists the Node versions that Mokly refuses.
2. Run npm install. The .npmrc file sets legacy-peer-deps, which @firna/ui needs. Then run npm --prefix desktop ci for the Mac shell's check dependencies. Run npm ci --prefix runner for the check dependencies of the agent runner.
3. Run npm run db:migrate to create the local D1 tables.
4. Run npm run dev, and open http://127.0.0.1:5173.
5. Open http://127.0.0.1:5173/api/health to check the Worker. It returns {"status":"ok"}.
6. Run npm run check before you submit a change.

Local development needs no Cloudflare account. Wrangler provides local D1, R2, and Durable Object storage under .wrangler/. The D1 ID and the R2 bucket name in wrangler.jsonc name the production database and bucket. Local commands, such as npm run db:migrate and npm run dev, use only the local storage.

This local setup creates no Cloudflare resources and deploys nothing. Put local secrets in .dev.vars, which Git ignores.

This is the beginning of the README. Read the rest at the original. Read the full README ↗