Road map

What has been done, what is in progress, what we offer

Pulse releases a patch for each delivery and a minor for each milestone. Below is an honest picture: closed phases with version numbers, what is being done now, and proposals that have not yet been accepted into the plan. If you need some item before others, write, this is how priorities are set.

0.36.4 · current 122 versions since September 16, 2026 7 phase harness closed What's new →
Done 40
0.32.0 Interface

New interface along the human path

Login → my projects → Git and branches → issues, each through both the graph and the terminal. Dashboard - one section with tabs “Overview”, “Activity”, “Reports” and “Team”; rail and project panel - one column; Git - one screen everywhere; primary round and “First steps” - along a new path. Nothing that has been done has been removed.

0.32.0 Updates

The update downloads itself and does not stop agents

The found version downloads immediately, the chip in the window panel says only what has been verified: percentage, “ready” after checking the signature and SHA-512, “postponed” with the reason. You can set it “when the agents are finished”, at the next startup (except Linux) or now - with the confirmation sessions stopped. Replacing the application on macOS and Windows has not yet been tested live.

0.32.0 Terminal

The agent suggests the line rather than typing it for you

The agent command comes to your terminal tab as a sentence of a line: your Enter sends it, the edit is corrected, the refusal is sent in words. The agent still writes to his tasks tab himself.

0.32.0 Agents

Registry Agents ACP puts Pulse

“Install in Pulse” in the agents directory: the npm or uv package is placed in the Pulse folder, next to it is a manifest with SHA-256, and the program is verified before each launch. Didn’t match - card with “Reinstall”, bypassing through npx Pulse doesn't work.

0.31.16 Around the code

Git screen

Commit graph with its working copy, branches, tags and remotes with synchronization, search through the entire history, Git commands in the palette ⌘ K. Agents are visible in the graph, conflicts between their branches are visible in the matrix; SHA and a branch in the terminal block open the graph.

0.31.15 Security

Agent Read Bound

The agent sees a working copy of the task and what it cannot start without - the system holds it: bwrap on Linux, sandbox-exec on macOS. There is no mechanism or the test did not pass - the agent team does not start. This is a file read boundary, not complete isolation: macOS local services and inter-process pipes are not tested.

0.31.15 First launch

Four-screen wizard and “First steps”

The found agent is already selected, a step without solutions is not shown, each screen explains its part of the product. After the wizard, there is a checklist that is closed based on product facts, not ticks, and is returned from “Help”.

0.30.20 Integrations

Issues as task resources

A task from an issue GitHub or GitLab with one click - in the “Resources” chip of the composer and in the list of issues on the “Diff” tab. The title, text and acceptance criteria are transferred to the task, the link to issue remains its source. GitLab - including self-hosted and groups with subgroups.

0.30.7 Reliability

Lost connection does not stop progress

Each Pulse launch has its own imprint. The phone has lost the network - the device turns on; returned - finishes reading the tape, and repeating the same prompt returns the previous receipt, and not the second turn. Restarting the remote control application distinguishes it from a break and shows that it requires attention.

0.30.6 Ecosystem

Pulse as MCP server and environment commands

List of operations with the schema version: read tasks, sessions and feed, create a task or session, send a prompt, interrupt the progress. Tools pulse_commands and pulse_command they themselves find the running Pulse. Each team goes through a license and budget and receives a receipt—including waivers.

0.30.6 Automation

Schedules: time task

Launch by day of the week or every N minutes, with your own time zone and budget. Preliminary check by command: non-zero code - skip without launching the agent. History of the last 50 launches with reasons and “Launch now”.

0.30.5 Around the code

Files tab and application preview

A working copy of the task next to the chat: search by path, editor with file version control - the discrepancy gives “Reread / Overwrite with your version”, and not the silent loss of someone else’s edits. The development team rises in the same copy on its port, and the element selected in the preview goes as a draft to the composer.

0.30.4 Team

Roles and discussion on the common board

The common board card has the responsible and reviewing member of the project, notes, transfer requests and review requests. Without a network, the board shows the last confirmed snapshot with a timestamp, and actions wait in the "Waiting to Send" queue and leave when connected.

0.30.3 Quality

Full review cycle

Task contract - goal, acceptance criteria, restrictions and verification commands with their version of the requirements. Comments are tied to the result version, file, and lines; the package goes to the author in one request, the task receives the “Needs improvement” stage. Only the person closes the comment.

0.30.2 Reliability

Request Register and “Needs Attention”

Each team has a record with an acceptance receipt and separately with the outcome: a repeat with the same key does not trigger the second turn even after a restart. The reason for the stopped session is visible. The list of blockers on the dashboard leads directly to the task, session and tab, and a new window opens where the previous one was closed.

0.30.1 Reliability

The draft is not lost, the status does not lie

The composer's text lives on the session, and not on the tab: switching to “Diff” and back, failure to send and restarting it do not erase it. The task stage is the same for the board, graph and result - green only for the one accepted by the person. The cost of a task is considered the sum of sessions; rewinding does not show the future.

0.29.0 — 0.30.0 Platform

Phone control

The device and the phone meet at the repeater - the phone does not need to make its way to the home router. Pairing via QR from the device screen, then the frames are sent in ciphertext, for which the server does not have a key. From the phone - respond to permission, view tasks and feed, send a prompt, stop the session. The default is off: until the switch is pressed, not a byte goes out.

0.28.0 Frontend

UI directory for frontend roles

Ten ready-made interface blocks with live previews - for a person in the Library, an agent with a tool, along with the rules: what the block contains and what not to do in it.

0.27.0 Around the code

Terminal as a panel in any section

⌘ J opens a terminal on top of any screen: tabs for working copies, the “Blocks” view with return code and duration, “Explain output” for a failed command.

0.27.0 Library

Your skills with versions

“Remove” and “Update” for installed skills; your own are written directly in the application, with version history and rollback; “Rate” gives a score and sorts the catalog.

0.26.3 Repositories

Cloning from GitHub and GitLab

The "Clone" button understands the link from the address bar, HTTPS and SSH, short owner/repo and GitLab groups. Folder without git is no longer an error.

0.26.2 Account

Section "My Account"

License and term, how much has been done - tasks, turns, calls, money, activity for 30 days, statistics on agents and repositories.

0.26.0 Protection

License required

The server signs the rights with the key Ed25519, the application verifies the signature. Offline is allowed for 30 days. The assembly is minified, main is compiled into V8 bytecode.

0.25.1 First launch

Setup Wizard

Four steps: how it works, install agents with ready-made commands, log into accounts, first task. The status is calculated according to the live list of agents.

0.25.0 Platforms

Windows, Ubuntu and macOS on Intel

Build each bundle on your own GitHub runner. The shell, program search, agent launch, git credentials and sandbox are separated by system.

0.23.7 Usage

"What Eats the Limit"

Analysis of consumption by reason per day, week or month; sections “who spends” and “the most expensive tasks”. Tokens are signed under the nodes of the graph.

0.23.0 Quality

Quality inspectors

A strong model evaluates the work of other agents along six axes, by button, automatically and as a swarm role. Table “who writes better.”

0.23.2 Agents

Codex without installation, any model manually

CLI Codex runs inside Pulse; The “Manual model” field connects models that are not yet in the agent lists.

0.22.7 Agents

GigaChat with tools

The built-in agent on top of the GigaChat API reads and edits files, runs commands, and works in a swarm. The access type is selected independently.

0.22.5 Operation

Log and bug report

Log file with masking of secrets, viewing the tail in “Help”, report to the developers using the button.

0.22.4 Observability

Activity with search and filters

Event feed with search, filters by type and task, periods, time of each entry. Status bar in all sections.

0.22.2 Language

Descriptions of skills in Russian

English descriptions of other people's skills are translated in the background and cached - menu “/” and Library in Russian.

0.22.0 H6 Context

Compressing history under the model window

The built-in agent at 75% of the window trims old findings and collapses the turns into a summary; Token valuation is calibrated by server.

0.21.0 H5 Prompt

Instructions Versions

History of agent and swarm member option instructions: date, difference, “Return”; The session shows which version is gone.

0.20.0 H4 Swarm

Your own worktree, merging, auto-repeat

Swarm developers in their working copies, merging into a task branch, conflict to the architect, replay of a fallen participant, task timeout.

0.19.0 H3 Tools

External MCP and code memory

MCP servers for all agents from the settings; preset “Code Memory” - code graph on tree-sitter.

0.18.0 H2 Control

Policies, budgets, sandbox, audit

Allow/ask/deny rules, cost limit per task, sandbox-exec for the built-in agent, audit report.

0.17.0 H1 Memory

Repository memory and task notes

Memory file for the repository, which is written by the swarm architect and read by each new session; notes in the context of the task.

0.16.0 Orchestration

Agent swarm

Named roles, architect-leader, task protocol pulse-assign, reports, waves.

0.15.0 Base

Terminal, auto mode, agent options, GigaChat

Terminal in worktree with up to six tabs, auto mode for session and agent, options with roles and skills, the first GigaChat.

In progress 1
stage 7 Platform

Remote control with separate application

Signed package for Android and QR scanner with system camera - now the pairing link is inserted by hand. There are already notifications in the browser remote (0.30.20, Web Push); the package needs its own, through the Google service. The tails of the fifth stage - a lock with PIN and biometrics before showing the session and auto-recall of a silent phone - are closed at 0.30.20 in the browser remote control.

We offer 9
offer Swarm

Merging conflicts with a model

Now the merger conflict goes to the architect. The next step is for the model to receive the conflict as diff3 and return a solution with confidence; low confidence - “check manually.”

offer Swarm

Evaluation of the team's result

The “Team” chip launches several agents per prompt. The final thing is missing: compare the diffs of sessions side by side, choose the best one or collect from several, pour in.

offer Around the code

Agent's work - in meaningful commits

The agent leaves one big difference. Decompose it into atomic commits with messages, with preview and editing before use.

offer Team

Central politicians

A signed organization policy file that is applied over local ones and is not weakened on the machine. For teams with security requirements, this is the first question.

offer Team

General command memory

The repository memory lives on the machine. Synchronize it between participants - through a branch in the repository itself or through the Pulse cloud, at the team's choice.

offer Team

Expense report

Cost by agents, models, repositories and people per period; export to CSV. The data is already there in each turn - what is missing is the cutting and unloading.

offer Exchange

Import and export of compounds and variants

Swarm and agent options as a file: share the “With inspection” composition with a colleague, put it in the repository, pick it up on a new machine.

offer Ecosystem

Sessions running outside of Pulse

Claude Code, launched in the terminal, is registered in Pulse and ends up on the graph with its calls and permissions - without moving to the application.

offer Platform

Execution that is window independent

The turns live as long as Pulse is running: I closed the application and the work stopped. Turn the execution to a separate process or to another machine so that the task can be completed without a window. The owner of the launch and receipts for this have already been made.

How it works

Versions and priorities

Patch - for each delivery: repair, small opportunity, documentation editing. Minor - at a milestone that can be called a release: a closed phase, a new large set of possibilities. All 116 versions with dates are on the page "What's new".

The “Suggest” column is ideas that follow from what already exists, but have not yet been accepted into the plan. They turn to "In Progress" when requested by pilot commands. Nothing in this column is promised on time.

What are you missing?

The shortest way for an item to be included in the plan is a request that states that without it you will not be able to use Pulse. We read such letters first.

Write in the application