macOS · Apple Silicon

Agents write the code.
You see every move.

Every task gets its own worktree. Claude Code, Codex, GigaChat and local models work in parallel, and every move shows up on a live graph. You accept the result.

  • Any agentCLI, ACP and API models
  • Everything on your machinemodel keys never leave it
  • Task graphevery move on a live graph
  • Terminal and Git insideno window switching
02 · How it works

From task to commit. Four steps.

01 · Task

SMS sign-inPUL-142
projectpulsebranchpul-142copyworktree
3 agents

You set a taskPulse creates a separate copy of the repository for it: a git worktree and a branch.

02 · Agent sessions

workingpul-142-1
needs youpul-142-2
workingpul-142-3
+ call another agent

You call the agentsOne or several. Each writes in its own copy and stays out of the others’ way.

03 · Graph

PUL-142taskmove 7 · editworkingquestion for youneeds youmove 4 · testsworkingsms-code.ts+64 −3otp.test.ts+38

You see every moveCommands, edits and questions land as nodes on the graph. You see at once who is working and who is waiting for you.

04 · Diff and Accept

M sms-code.ts  +64 −3
− sendSms(phone, raw)
+ const code = otp()
+ sendSms(phone, code)
Accept resultSend back

You decideAccept, send back, or hand over to another agent. Only what you accept reaches the branch.

03 · Two paths

Through the graph or the terminal.
Same tasks.

PUL-142taskmove 7 · editworkingquestion for youneeds youmove 4 · testsworkingsms-code.ts+64 −3otp.test.ts+38

The agent path

A task, an agent session, a graph of moves, a chat with files. For those who run the work from above.

task→session→graph→chat with files
claudecodexzsh
❯ claude "SMS sign-in"
✓ block 12 · 4 files · 38 s
  M sms-code.ts  +64 −3
  A otp.test.ts  +38
❯ git diff --stat

The terminal path

Your CLI agents in the Pulse terminal, the way you are used to. Command blocks, history, Git alongside.

claude codexyour CLI→command blocks→Git
Both share the same tasks, one graph and one feed. Switching takes one action.
04 · System and project

You always know
where you are.

At the top, sections for all of Pulse and the machine. Below, your projects. Inside a project everything is its own: tasks, graph, Git, terminal and files.

05 · Your data

Your code and keys stay with you.

Model keys stay on your computerNever sent to the Pulse cloud. Agents talk to their providers directly.
Telemetry is offUntil you turn it on yourself. The settings spell out exactly what is sent.
An agent sees only the task copyThe read boundary is enforced by the operating system, not by a model’s promise. The rest of the disk is closed.

Control and data in detail →

06 · Why we build this

People looked at the stars for thousands of years.
Once they set out, it happened fast.

1957The first satellite.
1961A human in space.
1969Humans on the Moon.
1988Buran returns from orbit and lands on the runway by itself. No crew. Fully automatic.

Every time it took an enormous will and thousands of engineering problems. And people who solved them.

Today you hold the full power of AI. Pulse gives you the tool to see any idea through. We are building the best ADE in the world.

08 · Access

Set your first task today.

This is a closed alpha: you need an access code. The build is for macOS on Apple Silicon.

Request access →

We answer within a few days. No mailing lists, and we never pass your address to third parties.

Request received We will reply to the email you gave.
What is an ADE and how is it different from an IDE?

An IDE is built around a file and a cursor. AI editors added a suggestion and a chat, but you still sit in one file on one branch. An ADE changes the unit of work: a task instead of a file; several agents in parallel instead of one assistant; and instead of accepting a suggestion, you see and decide what of the agents’ work reaches the code.

Which agents and models work in Pulse?

The CLI agents you already have installed, such as Claude Code and Codex. Agents from the ACP catalog. GigaChat and local models through an OpenAI-compatible server. The list is open, and you choose the default agent. Agents and models →

What leaves my computer?

Agents talk to their own providers, just as they would from a terminal. A local model talks only to your server. Model keys are stored on your computer and are never sent to the Pulse cloud. Telemetry is off until you turn it on yourself. Control and data in detail →

How much does it cost?

Taking part in the alpha is free. You pay your model providers directly: Pulse resells nothing and adds no markup on tokens. Pricing for Pulse itself has not been announced yet.

When will Windows and Linux arrive?

Today we test and build Pulse only for macOS on Apple Silicon. Windows and Linux are on the roadmap. We give no date until those builds pass our own checks. Roadmap →

How do I get an access code?

Leave a request on this page and we will email you a code. You redeem it on the activation page: email, name, password, and the license is issued at once. It is tied to your account, not to a machine.

More questions →