Version history

What’s new

The patch comes out on every delivery, the minor is on the milestone. Below are the latest releases and major milestones in detail, followed by a list of the remaining releases. Further according to plan - road map.

0.36.4 · current Release history from September 16, 2026
0.33.0 October 18

Screens in layers: tasks, graph, Git and “Task Result”; unified menus and section links

  • Screen in layers. Content - from the first frame, one summary line with one main action, secondary - hover and "View ▾", reference - in "Information" on the side, at the bottom - a line of keys. Nothing working has been removed.
  • "Task result." Diff and one solution are the main ones, notes in a thread under the line, keys J/K, ]/[, V, C and R - rollback the file to the database only for the version shown.
  • Tasks and board. A single line bar with status segments, “Ready” - only through acceptance, a task panel on the side, “Check result ▾” in the header.
  • Graph. The canvas is free: the feed of turns at the bottom, “View ▾” and “Details”. A commit is brighter than an edit without a commit, the call edge is the color of the tool, halos and flow are preserved. The graph of all agents is in one grid.
  • Git. One summary bar with “Send / Take / Commit” by status, branch color by name, path and merge location highlighting, conflict in the same bar, branches by folders.
  • One menu and connections. Right click, Shift+F10 and “⋯” - one menu in 28 places. Git ↔ task, progress → graph, node → file, “Reports” → task, local addresses - in the built-in browser.
  • Terminal. One strip of tabs, entering into your shell - with a human gesture, “Deal with the agent” at the fallen block.
  • Security. Subverted by an agent .git working copy - refusal; git-delta and difftastic in git settings no longer break Pulse; recording tasks in GitLab and GitHub - only on your host.
  • Which is not the case yet. Highlighting the graph path on hover also redraws the layers (target - 16 ms per frame); We didn’t measure it on a Mac with a GPU. Live run on Windows and Linux has not been tested for this release.
  • What is verified. 15,201 application tests, assembly, entire terminal stand - 203 out of 203, ui-smoke - 40 groups, Git, task, review, lifecycle and browser stands, screenshots without layout violations.
0.32.3 October 15

Your tasks: board and creation with agent selection; the terminal does not confuse other people's lines

  • Your tasks. The task lives without a working copy: PUL-12 type number, columns, priority and description. A copy with a branch appears at startup, and there may be several of them. Old tasks are transferred at the first start on their own, without loss. You can record a task without a license.
  • Board like Plane. The project columns are renamed, cards are dragged, the task is added directly in the column and opens on the side. “Pending” and “Error” are icons on cards, not columns.
  • "New challenge." “Create” and “Create and Start”. One list of agents: where the model thinks - the cloud, this computer or server on the network - and whether the agent is ready; for the unready one - “Login” or “Install”. The first task no longer crashes with "Authentication required". The work path is “Graph” or “Terminal”.
  • Projects and hosts like Orca. Grouping, selecting multiple tasks, renaming using F2. “Add Project” and cloning via link on SSH host.
  • Terminal. A long insert goes out in chunks and the macOS echo doesn't make it into the output. The agent's team is no longer responsible for a person's lines that have not yet been read.
  • Which is not the case yet. The CLI agent from the Terminal path is launched by a person - outside the Pulse read boundary. There are no connections between tasks and the “List” for your tasks yet.
  • What is verified. 14,305 application tests, build, board stands, task creation, project columns and panels, hosts with real clone via SSH and task lifecycle; terminal matrix 70 out of 70 on Linux. Five laps of safety checks.
0.32.1 October 11

Permanent access to agents, update fixes and file monitoring

  • Constant trust - in the agent in a specific project. In an external agent request, you can allow further actions of the selected agent in the connected project once. The rule persists after restarting Pulse. In Settings → Policies → “Accesses of external agents” the agent, project, full path and date are visible; access can be revoked individually or together with others. The new trust does not extend to another agent or another project. The old permanent rights of precision instruments are shown separately and retain the same general scope.
  • What queries does this cover? The setting applies to requests from external agents that come into Pulse. The current Codex connection does not pass its own permission requests here - they remain in the CLI. This setting does not replace macOS system permissions, keychain and browser. The project scope determines the automatic confirmation of the request; The file access boundary is set by a separate mechanism.
  • A successful download is not considered a failure. The loader distinguishes between the normal closure of a request and the interruption of the file stream itself. The transfer continues, and the real break saves the downloaded part for the next attempt. Size, release signature and SHA-512 are still checked before installation.
  • Track files on Mac. A late event about an unchanged file no longer causes unnecessary rereads. True edits, atomic replacements, and records with reconstructed change times remain visible; windows that have stopped monitoring the file do not receive late notifications. The repository memory checks metadata once every two seconds and notices someone else's edit, even if the system did not send an event. In case of conflict, the choice remains with the person.
  • File memory limits. Static symbolic and hard links and files that are too large are rejected before being read. On Linux, read, write, and delete keep selected directories open; on macOS, opening a file for reading disallows symbolic links in the entire path. Parent directory spoofing on read on Windows and path changes on write or delete on macOS and Windows remain known limitations.
  • What is verified. The Mac ran 29 boot loader tests, 11 file tracking tests, and 27 memory tests; six Linux-only checks on Mac are skipped. The native check for a break with resuming passed. On real Linux, there were eight exact source checks, including synchronization without a tracking event. Persistent access is verified by 144 tests and six scenarios on the assembled Electron, including restarts and recall through settings. The four configurations were type checked and the application was built. In the merged Linux source, 13,971 application tests passed, with one expected failure and 80 misses reported separately; The type checks and build of this source code in GitLab also passed. Before building on a Mac, temporary paths are reduced to one form, the limit of open files is checked, and the entire set of tests is executed sequentially.
  • Installation and update. GitLab also passed end-to-end UI testing on Linux and 504 cloud testing. A separate CI warning lists scenarios outside the required set; it does not confirm full E2E. Download cards show the actual published version separately for each platform. An old version with a faulty bootloader may need a ready-made installer: the fix will start working after installing the new package.
0.32.0 October 10

New interface: Dashboard with tabs, project column, Git in one screen

  • Why 0.32 and not 0.31.17. The interface is rebuilt along the human path: login → my projects → Git and project branches → tasks on them, and each task can be managed both through the agent graph and through the terminal. Nothing has been removed from the previous one - the graph, terminal, swarm, files, any agents and CLI are still there, just put in their places.
  • Dashboard - one section. Instead of Dashboard, Activity, Reports and Space - one section with tabs “Overview”, “Activity”, “Reports” and “Team”. In the “Review” there is only operational: “Requires attention” with the “Allow / Reject / Reply” buttons right in the line (dangerous - only through the card), work, queue, projects; task tiles open a list with the same number. “Reports” - analytics for the selected period with uploading to CSV. Connecting a team, role and invitation, including by letter, in Settings → “Team”.
  • One column on the left. Rail and panel became one column: search and commands ⌘ K, signed sections, below are your projects in a tree: workspaces, repositories, tasks and their copies, sessions. ⌘ B folds the column into a narrow rail.
  • The task is a workplace. When a task is open, the board goes away, the header occupies one row, and the main action is one and depends on the state: start, answer, stop, check the result or continue. The status bar only indicates deviations, notifications are stacked and do not cover buttons, notes open as a list window.
  • Git - one screen everywhere. The “Git” tab of an issue is the same screen as the Git section, and can be accessed from the tree, inspector, and dashboard. “Waiting for you” - one word and one amber color on the screen, in notifications, on the graph and in the remote control. There is a graph in every path; it now has a mini-map and a simplified view when viewed from a distance.
  • Tour and “First Steps” again. The primary tour is 12 steps along a new path: it itself opens the right place and brings you back. “First Steps” - 12 stages, which are closed according to the facts, each one has it written where it is in Pulse.
  • The agent suggests the line rather than typing it for you. If you type a command in a terminal tab, the agent's command comes as a sentence above the terminal: your Enter sends it, the edit is corrected, the refusal is sent in words. The agent still writes to his tasks tab himself.
  • ACP registry agents are installed by Pulse. “Install in Pulse” in the agents directory puts the npm or uv package in the Pulse folder with a SHA-256 checksum, and the program is verified before each launch. Didn't match - card PULSE-AGENT-005 with "Reinstall"; Pulse does not bypass.
  • The update downloads itself. The found version is downloaded immediately; the indicator in the window panel shows the percentage, “ready” after signature verification or “postponed” with a reason. You can install it when the agents are finished, at the next startup (except Linux) or now - with confirmation sessions stopped. This is how 0.32.0 and newer works: the version you have installed is updated to 0.32.0 in the same way.
  • macOS: The agent below the border has access to your tools. Under the read boundary, the Mac runs node and python3 from Homebrew, git and clang from Xcode, Java and Docker - just like on Linux; the home folder is still closed. Checking on Mac found and closed a bug that prevented task copy files from opening in preview, diff, conflicts, and line history on Mac.
  • More honest in case of failures. Without a connection to the cloud, “Reports” and “Team” say “no connection” with words, not the text of a network error, and do not pass off “I don’t know” as “no.” Unknown is “unknown”, not zero; The inaccessible commit button states the reason. The parcel box shows all incoming ones, not the first 50. The swarm pause is visible, and there is a way out of it - “Continue swarm”. The remote control reports errors in words and code. Dates are in Russian format.
  • What is verified. Source checks in CI on Linux: 13,903 application tests and 504 cloud tests. Previous interface acceptance: 30 stands and 282 scenarios, terminal stand - 200 scenarios, settings audit - 24 pages without violations; new among them are seven negative scenarios: empty profile, cloud crash, double reply, editing a note from outside, commit failures. Interface smoke - 40 out of 40. Signed and notarized Intel Mac installer published, first run tested on Mac. Windows and Linux builds and installation tests took place in CI; Windows was tested via Wine.
  • What we don't know yet. Installer 0.32.0 for Apple Silicon is not built. The full suite of tests on macOS for 0.32.0 did not complete successfully. Automatic replacement of the application when updating to macOS and installation with the first launch on real Windows 10 have not been tested live. Pictures on the site still show the previous interface.
0.31.16 October 7

Swarm base roles, memory limits and fair keychain

  • Swarm base. Migrations play a separate role. Runtime reads and writes the journal and does not change the layout. One base address does not pretend to be divided rights.
  • Memory Vault. A lost usage record is not confirmed. Diff larger than 32 MB is rejected with words. Hidden files are read in one batch by git. The seal does not start on its own.
  • Empty interface package. It no longer promises Vue. The application's working interface is React in the src/renderer directory.
  • A bunch of keys. The docs call the encryption key and secrets.json file. Different macOS signatures do not share consent. It is not recorded how many times the system will ask for a password per launch. There is no repeat on the second Mac.
  • What else is there in this release? Main included packets from the terminal of another thread. Git screen: branches, tags and remotes with synchronization, search throughout 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. Agent in the terminal program: answers the question y/n, runs in a REPL, and the human intercepts the input in one action and returns it to the agent. "Make it a task" from the folder tab, “~” and block. ACP Registry Agent runs a task session. Saved SSH hosts and terminal plugins. A separate local run of these packs for 0.31.16 was not installed. Release Verification - Pipeline: Application, Cloud, and Linux Interface.
  • CLI agent in the tab - on the phone. The remote control sees a tab with Claude Code, Codex and other CLI agents: status, reason for waiting and output tail without secrets. The agent’s question is answered with text or the “1 / 2 / 3 / Reject” buttons - only to the agent who is clearly waiting, and only on the launch that the person saw. The machine confirms the first answer in the session with a system question.
  • The travel belt is three times denser. Calls - in lines, readings and searches - in one series, edits are collapsed to “file +N −M”, the fallen ones are opened. The same turn - 1.2 screens instead of 3.0 at 1440x900. Tight/Normal/Detail setting in Appearance.
  • Composer session with short chips. The agent is familiar, the effort is in a word, the context is a percentage with details on click. On a 900x600 window, the basement is placed in one row instead of two.
  • Files in session context. The file outside the working copy goes to the model only after a system question with the real path; secret-like names are rejected before questioning. The turn header shows which files it left with.
  • Terminal. Ligatures, view settings (font, line height, cursor, contrast), built-in themes, underlining a non-existent command, add-ons for git, npm, docker and kubectl, visible focus when working with the keyboard. Shell tokens are signed, and “typed by a person” is proven by clicks, not time. The folder tab from which the task was created shows the commands “before the task” in the graph.
0.31.15 October 6

Intel: fixed agent start; the update is downloaded after a break

  • Initial agent check on Intel Mac. In signed 0.31.14, the child Electron could not read its own library and showed an Apple report. The fix is ​​included in the new installer: it works on every Mac running 0.31.15 without requiring you to manually change permissions.
  • Resuming the update after changing VPN or network interruption. The cloud now delivers the rest of the file, and the client checks the boundaries of the response and saves the already downloaded part until the next attempt. Signing the release and verifying the entire file after downloading remain mandatory. The server response with the remainder of the real installer is verified on the public address.
  • First display of the site. The selected theme is applied before styles are loaded; visible content is not hidden for the sake of the appearance animation. The constant flickering of the entire background after loading has not yet been reproduced.
  • The version depends on the platform. The download cards show the actual published build for each system. For Apple Silicon, notarized 0.31.14 remains; a new ARM build is not included in this release. Transition to Intel 0.31.15 - by installation instructions.
  • What else came in from the terminal stream. Agents reading limit: the agent sees only a working copy of the task, and the system keeps it - bwrap on Linux, sandbox-exec on macOS; files ~/.ssh, keys and tokens outside the task cannot be read by the agent, even if the hint in the code asks. This is a file read boundary, not complete isolation: macOS local services and inter-process pipes are not tested. The file tools of the built-in agent under the border are closed - it works through bash. First launch: four-step wizard - which agent is first, how agents work, appearance, notifications and remote control; a step where there is nothing to decide is not shown. After the wizard, there is a “First Steps” checklist, the items of which are completed based on facts, not ticks. Git section with a commit graph, "Files" section with quick opening ⌘ P and viewing Markdown and PDF, ACP registry agent directory in the terminal menu: the agent command is placed in the new tab line, you launch it.
  • What is verified. Passed 65 access tests to application libraries, 75 download and update tests, 474 cloud tests, 14 site first impression tests, type checking and application assembly. Full run on Intel Mac: 10,433 passed, 17 dropped, 257 missed. README version bug fixed; Of the remaining crashes, 13 were repeated on the original version, two timeouts were not repeated separately, and one more depended on the settings of the stand. The full local set is not considered green.
  • What else is being researched? Repeated keychain request on ARM and flickering windows when starting Windows 10 remain open. Live update check on Windows 10 has not yet completed.
0.31.14 October 2

Ctrl+R sees the whole history, both Mac builds are accepted by Apple

  • Notarization for Apple Silicon and Intel · October 6. Apple has accepted both already signed 0.31.14 builds, with a ticket added to each DMG. Gatekeeper accepts the image and application as a Notarized Developer ID: the first launch is from “Programs”, with the usual “Open” confirmation if the system shows it. If 0.31.14 is already installed, download the new DMG and replace the application manually: the version number is the same.
  • What was checked on October 6th. Two Apple Accepted tickets, two DMG tickets, four Gatekeeper checks, and 50 strict nested Mach-O checks. In each build, all 4409 application content records, including 3605 files and 14 symlinks, matched the original signed image. The code, resources and built-in CLIs are the same; The ARM application was not launched in this test.
  • Search the entire team history. Ctrl+R responds instantly and finishes reading the database in the background: all 50,000 commands are searched, and not the latest tail. Secrets do not go down in history - they have been verified on a database of 120,000 lines.
  • The load is measured and recorded. New measurement log: 200 agent sessions, a flurry of 300 notifications, large repositories - indicators are recorded on each version, degradation can be seen by comparing strings.
  • Panel on graph canvas does not interfere with clicks at the nodes when there is not enough space for the canvas.
  • Signature for Intel Mac · on October 5th. The application and DMG 0.31.14 are signed by Developer ID AVATEK, OOO. As of October 5, Apple notarization had not yet been completed: Gatekeeper blocked the first launch of the downloaded application. Migration from Intel 0.31.10 with local signature - manual installation from DMG instructions.
  • Signature for Apple Silicon · on October 5th. For ARM 0.31.14, the local signature of Pulse Dev has been replaced: the application, nested components and the new DMG are signed by Developer ID AVATEK, OOO. The code and dependencies are the same, the built-in CLI signatures are preserved. The version number is the same, so replacing the application is manual. As of October 5, Apple's notarization had not yet been completed; running on ARM was not performed in this test.
  • What tested on Intel Mac on October 5th. Signing the application and DMG, launching the application and running the terminal shell. It was not possible to check the terminal interface in the new profile: access is prohibited by the license. In the total run, 10,098 tests passed, 13 failed, 257 were missed; on a separate repeat, all 13 fell again.
0.31.13 October 2

Dashboard analytics and design system 1.3

  • "Analytics" on the dashboard. The bar of indicators is revealed by an arrow: trends for 28 days - turns, agent time, waiting for your permits and cost - with a personal norm; “Dynamics” for 30 and 90 days or a year - with a chart or grid of days, like GitHub; analysis of the day by the hour, scrolling through with arrows; ring of agents and projects. What Pulse doesn’t know, it writes with the words: “no data” - not zero, unknown price - “from” or “unknown”, today is signed “day goes by”.
  • More airy. The main button is in tone like the selected section, and not with a dark green fill; softer statuses; your drop-down lists; the selected tab flows to the new location. Panels, cards, Diff files and settings - planes with highlights and soft shadows instead of frames.
  • Dense travel tape. Successful call - line, reads and searches in a row - one line “3 reads · 1 search - files”, edit - “+N −M” with diff by click. The same turn takes up 1.3 screens instead of three.
  • Task header - one line on all tabs; board - one panel. “Focus” (⌘.) removes everything unnecessary, task status and new notifications remain visible.
  • Permission card. First consent, then “Allow in session”, refusal - last; there is always a one-time “Reject” option.
  • File hint by “@” in the task chat and on the graph. Files with secrets - .env, keys, folders secrets/ and .ssh/ — are not offered and models do not leave.
  • Terminal and graph are one ADE. “On the graph” from the terminal selects a node of the same work; “Continue in terminal” - and at the session node on the graph; a swarm of tasks in the sessions panel is one block; the task stage sees MR opened from outside Pulse; history search Ctrl+R fits into 50 ms per 100,000 commands.
  • Notifications in the window — about a session that is not on the screen, with the “Show” button. The CLI agent card on the graph says what the agent did and answers its permission request right in the node.
  • What is verified. The entire set of tests, assembly, end-to-end scenarios of the terminal and dense tape, screenshots of what was/was. This version has not yet been seen on real macOS and Windows; commits and files are not included in Analytics yet.
0.31.12 October 2

First touch: first project, then task

  • What are we working on? Before the first task, Pulse shows the repositories found on the computer and offers to open a folder, clone, create a new project, or take a demo with a failing test. After choosing, there are three ready-made tasks.
  • “Read only” mode. The first task cannot change anything: edits and commands are prohibited by the Pulse policy for all agents, and Claude Code and Codex have their own plan mode enabled.
  • Your own model. Models section: Pulse itself finds Ollama, LM Studio, vLLM, LiteLLM and llama.cpp on this computer. Points with the roles “primary”, “fast” and “spare”; if the main one does not answer, the spare one takes the lead, and the tape says so.
  • Entrance without dead ends. Registration in the application - by access code; The code can also be redeemed on an account that is already logged in. Logging in via GitHub without an invitation no longer waits forever for the browser.
  • The computer speaks. Notification "agent finished" or "awaiting permission" when Pulse is not in focus and a number on the icon.
  • Transfer from Cursor, VS Code and Windsurf. MCP servers and project rules - on one screen; servers are switched off, keys are only available with your consent.
  • Network for agents. The proxy and root certificate reach the agents and their terminal.
  • What is verified. The path from registration to the first task is run through an end-to-end scenario. Notifications and Models step on real macOS and Windows have not yet been tested.
0.31.11 October 2

Windows: starts, installs in one click, updates quietly

  • Pulse for Windows launches again. Build 0.31.10 for Windows closed at startup with the error “Invalid or incompatible cached data”: it was compiled on Linux, but Windows does not accept the part of the program compiled for Linux. Now such assemblies are assembled without this part. If you installed 0.31.10 on Windows, download 0.31.11 from Windows card and install on top.
  • Installation - double click. Without questions “for whom” and “where”: the progress window and Pulse is open. Placed for you, in %LOCALAPPDATA%\Programs\pulse, without administrator rights; own folder - key /D=. SmartScreen still warns the first time you run a downloaded file: assemblies do not have an Authenticode signature.
  • Transition from the “for everyone” setting. If Pulse is in Program Files, the installer will offer to delete that copy; Windows will ask for administrator confirmation. Settings and data remain.
  • Windowless update. After “Install” Pulse checks the file, closes, installs the new version in the background and opens itself. If you remain in Pulse while asking about running agents, the update will appear when you exit. The "public" copy and ZIP receive the installer window as before.
  • No flashing consoles on startup. Agent searches, CLI version checking, and git calls no longer open console windows.
  • Clean removal. The uninstaller offers to close Pulse and its processes, removes the “Open with” option and the link pulse:// and asks whether to delete the data. The default is “No”: the data contains working copies of tasks. Branches pulse/… remain in your repositories.
  • Notifications named Pulse. Windows recognizes notifications and the taskbar icon as Pulse.
  • What is verified. Installation, update on top, transition from a copy “for everyone” and removal were run under Wine; there the new assembly is launched. The interface on real Windows has not yet seen this version.
0.31.10 October 2

Git, Browser, Plugins and Space - next to tasks

  • New update signing key. As of 0.31.10, the old client will not accept the new signature: to upgrade from any version prior to 0.31.10, including the published 0.31.3, download the 0.31.10 or later installer once for your platform from download cards, close Pulse and install manually. The new client then checks the next releases with the new key. The cards show the actual published versions; build 0.31.10 may not be available for every platform yet.
  • Git is a separate screen. Select a repository or working copy of an issue: changes and diffs, index and commits, pull and push changes, branches and history are all in one place. The path and branch are visible above the actions; The task terminal opens in its working copy.
  • Browser inside Pulse. HTTPS pages and local dev servers open next to tasks: address, back/forward, update and retry after error. While one tab is available, new windows and file downloads are not supported; the page is isolated from the Pulse API, cookies live until the application exits.
  • Plugins - MCP section. The connection can see access, verification status and server tools; There is a “Code Memory” preset. The new server remains offline until you decide. Disabling or changing access prevents new calls to the embedded agent and stops the CLI sessions that the server was passed to. Skills and roles remain in the Library.
  • Space - team projects. Previous projects open under the same name in navigation, tour, and tooltips. Participants, invitations, boards, discussions, submissions, and published copies of the terminal work with the same data; control of someone else's shell does not appear from Space.
  • Skills reach built-in agents. Team /name transfers content to the Local Model or GigaChat SKILL.md from a working copy, and in its absence - a global skill. The menu shows available files, including Russian names; lines that look like secrets are masked.
  • The dashboard and graph are more precise. A CLI in a tab is counted as an active job, even if the task itself is idle; the hook and tab of the same agent do not count twice. Rewind refers to a visible graph and shows the days and dates of events, the age of the task is signed “Since creation” and includes pauses. Stopping auto tracking leaves the agent to work.
  • Readable states. The task stage is accessible to a screen reader, the lead swarm label is more contrasty, the empty measurement history explains the lack of data, the schedule actions fit on a narrow screen.
  • Since the last published 0.31.3. The distribution also included versions 0.31.4–0.31.9 below. The stage for Git and MR facts is visible on the board, graph and remote control, the Pulse session is visible in the terminal panel, their requests are visible in “Waiting for me”. Network commands like curl and ssh and editing existing tests by default ask a person; running tests, installing dependencies, and regular Git sharing continue to work.
  • Installation on Intel Mac. The application in Intel DMG 0.31.10 is locally signed ad-hoc; automatic replacement of macOS with this build is not confirmed. Install it manually from DMG by instructions.
0.31.9 September 30

Design system from the sign: flow, glass, living graph

  • The agent graph has come to life: the swarm’s task flows to the participant in a running dotted line, the report flows back to the architect, and the road from the task to the node waiting for your response is entirely illuminated in amber. In “Options” a “color by state” mode has appeared.
  • Glass sign throughout the platform: dashboard cards, task previews, ⌘K palette, notifications, toasts and cloud entrance are assembled from one glass tile with a glare; The main buttons respond with a flash.
  • The tape speaks Russian: the end of the agent’s turn is translated (“turn completed”, “turn stopped”), the technical code remains a hint; the agent's plan shows a live dot instead of a symbol.
  • Typography is organized into a named scale of font sizes - from micro-graph marks to large statistics numbers; The mobile remote control received the same scale, filled buttons and highlight cards.
  • Fresh pictures of all sections - on this page, on the website and in the documentation; they are filmed by a reproducible stand of 22 scenes.
0.31.8 September 30

One ADE: terminal and agent work on the same task

  • One task terminal. The “Terminal” tab in the task and the “Terminal” screen are the same panel: the same tabs, shell, blocks and agent status; “Full Screen” opens a screen with the same tab. The separate task terminal with its shell has been deleted.
  • Session panel and files on the Terminal screen. Folder tabs and "~", file column with Markdown viewer (footnotes, drop-down blocks, search, highlighting) and PDF (search, table of contents, thumbnails, links, password, rotate, quote in prompt), tab folder follows cd, start page and list views.
  • CLI agent is one graph node. Claude Code, Codex or Gemini in the terminal tab is visible on the task graph as one node with four states: working, waiting for a response, finished its turn, silent - “Pulse does not know”. The waiting agent ends up in the “Requires Attention” and the feed; agents outside of tasks - on the dashboard with the “Make a task” button.
  • Transitions in one step. “Open terminal” at the graph nodes and “On the graph” at the panel and block lines; “Make a task” from the folder tab, “~”, block and start page; “Continue in Pulse session” for Claude Code conversation from the terminal and “In terminal” from the session; "Swarm in this folder..." from the terminal.
  • Chat with files and edits in chat. “In session context” from the files column and the “Files” tab: chip with checksum and size, @path/file in the text, refusal words for files similar to secret. The agent's edits are shown as a diff right under the progress with the transition to “To file” and “In the Diff tab.”
  • Factual task stage. Next to “↑↓” in the task header are “Research”, “Development”, “Review” or “Done”, calculated by git and MR, and not set by hand; “to merge” - only when it’s clean, running and MR is open, otherwise the tooltip says what’s interfering. Without git - “stage unknown”.
  • Laboratory of agent trajectories. npm run evals: cases as data, policy and fairness gates, real model via proxy, repetitions with median and worst, threshold in the pipeline. What the system does not yet do: one model of sessions for the panel, graph and board, tasks in a tree, a stage for facts on the board and in the console - the specifications are written, the code is after them.
0.31.4 — 0.31.7 September 29

Four versions in a day: CLI installation on Windows and live model lists

  • 0.31.4 - CLI installation on Windows. The missing Claude Code, Kimi Code or OpenCode is marked in the list of agents, in the card there is a command and an installation button: Pulse launches it in the PowerShell window, waits, searches for the CLI again and shows the result or error; the same path works in the first run wizard. New CLI directories in PATH are found without restart.
  • 0.31.5 - readable lists of roles and models. In the profile and swarm editor, the lists are drawn by Pulse, not the Windows system list: opaque background and contrasting text in both themes.
  • 0.31.6 - current supplier models. The list of models is not frozen in the cache: Pulse updates it in the background at startup and requests it from the agent when opening the model menu in the composer, session, profile, settings and swarm; While the request is in progress, the menu shows the status; if there is an error, it leaves the last known list.
  • 0.31.7 - new Claude models. The built-in Claude ACP adapter and Claude Agent SDK have been updated to include Opus 5.5 and Sonnet 5.5 in the menu - those that are available for user login from the vendor.
0.31.3 September 29

Signed updates and working panel buttons

  • The update manifest is verified against a separate Ed25519 signature and checksum. For legacy clients and macOS builds without a publisher's certificate, upgrading to 0.31.3 requires a one-time manual installation from the download page.
  • If the installation fails, the card saves the downloaded file, shows the reason and allows you to repeat the action.
  • “New Task” opens the composer from any section. Links to the cloud and the error report lead to the desired page even from already open settings.
0.31.2 September 27

Agents are updated inside Pulse - no more Terminal windows

  • Previously, the “Update” button next to the “Claude Code: version available...” card opened a new standard Terminal window and started the installation there. Now the command is executed inside Pulse, and the card itself shows the progress: progress and the last line of output during operation, “ready” after, the reason and the tail of the output if it fails.
  • The manual way has not gone away: if the installation did not work out (for example, there were not enough rights), the card honestly shows the reason and suggests “Open in Terminal” - as a backup option, and not as the only one.
0.31.1 September 27

The update installs itself - no more dragging and dropping from the image

  • Previously, “Install” closed Pulse and opened the downloaded image, where the application was dragged into “Programs” by hand - as during the first installation, and each time with a system question. Now, when you press Pulse, it mounts the verified image, replaces itself with a new version and restarts: the window closes for a few seconds and opens with the updated one.
  • Before replacement, the application from the image is checked: the same package identifier, the same version from the release, complete signature and the same signer as the working copy - Pulse will not put someone else’s signature. If you cannot replace yourself (for example, the application was installed by another user), the image will open - installation by drag and drop, as before.
0.31.0 September 27

Your own window panel on macOS and terminal rules from the command card

  • “Always allow” and “Always deny” in the agent’s command card. A policy rule is created from the card: command prefix and chain protection - “a && b” is not covered by the rule for “a”. You can now go to the terminal block from the graph, transcripts and tapes, and the keys from the secret storage are masked in all channels: once a token gets into the output, it goes out as asterisks.
  • The macOS window panel is now all ours. Built-in titlebar: “traffic lights” follow the interface scale, and the entire bar drags the window. “New task” with a menu of methods, machine chip and cloud status, feedback, settings and account are available from any section; with a narrow window, the controls are collapsed by stages.
0.30.40 September 24

The five-second silence that made main red

  • The first main pipeline on its runner passed 6369 tests out of 6380 and failed on one: the swarm audit test runs a full audit of a real repository and lived with a default of 5 seconds - on a Mac it lasts a couple of seconds, and on a runner with four cores it exceeded the limit every other time: in the MR pipeline it is green, in main it is red. The limit is now explicit, like the neighboring tests of the same file - 180 seconds. The audit code has not changed.
0.30.39 September 24

The main repository has moved to its own GitLab

  • Everything that was on GitHub has been transferred: code, 16 branches, 43 tags, 366 issues and 71 PR - they became MR with the same numbers - tags, issues and releases; verified by the number and SHA of each branch and tag. Fourteen GitHub Projects boards became tags and one “Tasks” board. GitHub remained a code mirror for the sake of Actions.
  • The rules and pipeline have been rewritten for GitLab. Instructions for agents stated “GitHub only” - according to them, the agent would open a PR that no one would see. A .gitlab-ci.yml I didn’t understand it at all: the anchor was in Cyrillic, and the conveyor did not create a single task - it looked like “no runner”. Now the pipeline runs on its own runner: an image with the necessary git, one task at a time, system libraries for building Electron.
0.30.38 September 23

Swarm 24/7: decisions by rules, not by guessing

  • The deterministic belongs to the rules: destructive operations are a confident prohibition on a rigid list without a model, recording within the authority of a role is a confident permission, and the unknown is an escalation to a person, not a guess. Each decision is written in a journal with a source, the share of coverage by the rules is calculated.
0.30.37 September 23

Swarm 24/7: MR only after security reviewer

  • Security checking has become a property of the pipeline: a merge request is allowed only if the security reviewer approves this particular version of the diff - there is no verdict or there are findings, a ban, and approval for the old version is not counted. A server with a GitLab webhook has appeared: merging an issue branch turns it to “done”.
0.30.36 September 23

Swarm 24/7: seven roles, and reviewers only read the diff

  • A registry of seven roles - from the scheduler to the database reviewer: each has a fixed model and a system prompt on disk. Reviewers work as cold readers: they are given only the diff and description of the task, and passing on the author’s history or the role’s memory is an error at the code level, a lack of agreement in the prompt.
0.30.35 September 23

Swarm 24/7: agent network perimeter - code, not prompt

  • A local proxy is raised for each session: the agent accesses the network only through it, and the proxy only allows addresses from the task manifest - the rest are rejected without connecting to the target. A blocked request does not ask the agent again: only a log entry from which the dashboard will collect a picture of blockings.
0.30.34 September 23

Swarm 24/7: task queue for pg-boss

  • The manifest has become work: the queue accepts the task manifest as a payload, statuses live in their own table, and errors are typed by contract - the orchestrator decides whether to retry by code, not by text, and the retry always gets the reason for the previous failure. Tested against real Postgres: the task is set, fails, repeats with a reason and, having exhausted attempts, honestly becomes failed.
0.30.33 September 23

Swarm 24/7: one task manifest on all inputs

  • Any swarm input - import from Backlog.md, MCP call, manual setup - goes through one scheme: an invalid input is rejected at the input and written to the deviation log with the source. Outgoing traffic is denied by default: an empty list denies everything, while an allowing rule requires a reason. The swarm packages are connected to common checks.
0.30.32 September 23

Swarm 24/7: own repository area and package framework

  • The thirteenth area of the repository is dedicated to autonomous development: orchestrator, executors, memory and swarm security, API server with GitLab webhook and proxy to H200. While there are frames with entry points, the filling is carried out with epic tasks. At the same time, the check of areas, which was red on main even before this wave, became green.
0.30.31 September 22

Settings can again be reached with the mouse

  • The “account and settings” list, which appeared at 0.30.30 a few hours earlier, was not opened by clicking - the button did not have a handler - but it lived in the header of the task board and disappeared in other sections. The menu has moved to a permanent shell strip, which is present in all sections. The assembly and 3689 checks were green: not a single one presses this button - I found a through run that could not reach the settings.
0.30.30 September 22

Report from a live user, parsed down to its causes

  • The mouse reached the modal windows. “I can’t select the repository folder, only ESC works” turned out not to be a broken window: the cloning and repository selection windows are drawn inside a wrapper that completely disables the mouse, and the prohibition is inherited downwards. The window was drawn, the clicks fell through. The same thing explained “does not allow you to edit a swarm after creation” and “the list of projects does not open” - three different complaints and one line of reason.
  • Double indentations between paragraphs in chat. The line break rule was declared twice, and the file loading order won: line breaks between blocks became visible empty lines, and the row occupied 374 pixels instead of 167. The same class of error was found in the notes editor - the layers diverged by 29 pixels, and the caret moved away from what was visible.
  • Chat no longer drags you down while you're reading a history. The sign “man at the bottom edge” did not exist at all before.
  • Links open in the browser, Shift or Alt copies the address.
  • The built-in Codex login works on Windows. The “Login” button substituted the command of another agent, and even in a syntax that PowerShell does not parse.
  • When you first launch Pulse, it checks itself and the agents' CLI itself: what is installed, what is outdated, what is not there at all - with the installation command from the one who is missing. Previously, the check only knew about already installed agents, that is, it was silent exactly on a fresh machine, where there was something to say. “Not checked” is shown separately from “everything is updated”: network silence is not order.
  • Shell. Account and settings - in one list at the top right, where you can see whether the work is happening locally or through the cloud; pressing again takes you back to where you were working. Version and red "alpha" are always in the bottom band. Sending a message - your choice: Enter or modifier with Enter.
  • What this release doesn't do. The prompt and the result of the inspector’s work are still not visible to humans: the prompt is cut during recording, and the result of the session is not in the product in any form. The project memory file remains empty - only the swarm can write to it. This version does not have an Android package: the signing key is not included in the assembly.
0.30.28 September 22

Nine versions at once: the update is checked before installation, parcels go on their own, consumption is visible everywhere

  • The update is reviewed before it is offered. Previously, the file address, name and checksum were taken from the server response, and only the version was checked: the address could point to any host, the name could be anything, the sum could be an empty string. Now the file is taken only from the same host and using the same protocol that responded to the check, the name must be a package for your system, and the amount must be the real amount. The verification is repeated the moment you click “Install”: hours pass between downloading and installation, and the file replaced during this time will not open.
  • The expense is visible on all machines in the account. Previously, each machine knew only its expenses.
  • The message with the task reaches the person itself and closed with an envelope signed by the sender. Transferring work to a colleague no longer means sending a file via instant messenger. In this case, the provider token no longer goes to someone else’s server.
  • Agent race with fair comparison. Several agents take on the same task, and the result is compared using the same standards. The sandbox worked on Linux, and closing the window became a choice, not a break in work.
  • Rewind stopped lying about the past. Showing data that did not exist at the selected moment is considered an error in Pulse, on par with an incorrect number.
  • The missing working task folder is restored. If the folder was deleted, the card looked intact, and the launch crashed inside git. Now the folder is recreated before startup, and if the previous work is lost, the system says so directly, and does not silently substitute an empty one.
  • Responsiveness: first we measured, then we fixed. Five surfaces were measured, the measurements were double-checked, and six places were corrected.
  • Which this episode doesn't prove. Everything listed was verified by tests and end-to-end runs, but there was no live pilot on paid agents. Windows and Linux have not been manually checked, there is no macOS notarization - the installer is still opened through the security settings.
0.30.19 September 21

Second device: the settings are moving, but the window is no longer waiting

  • Settings move between account machines. Agent profiles, swarm compositions, policies and budgets no longer need to be reconfigured. Yours is laid out on its own, what came from another device is applied only after confirmation - and the window shows before use what will arrive, what will be left for the device and which of the visitors is distributing permits. The paths, keys, and consent to send the code remain with the machine: moving them would mean handing over settings that look configured and don’t work.
  • The login on a clean installation went to localhost. The “Login with GitHub” button led to a non-existent address. Adding settings with defaults only worked if the file was available, but the first launch of the file did not—the window substituted its own backup address. It broke exactly for those who opened Pulse for the first time, and it was repaired itself the first time the settings were saved.
  • The window opens in a tenth of a second instead of four. Poll of agents launches several processes for each; the window is no longer waiting for him - the list arrives next. At the same time, a startup measurement appeared in the log: previously the application recorded the moment of startup and did not record when the window opened.
  • Unsolicited mode is no longer offered. There was a ban, but the mode remained on the list: the choice was accepted and ticked, but upon launch it was rejected. Now such modes are not shown, and it is said where the desired one lives.
  • Three places where the product was lying. The screensaver named the reason for waiting at random. The download page marked both Mac cards as your system and immediately selected Apple Silicon - even for those with Intel Macs. DMG version 0.30.18 showed the number 0.30.10 in the background.
0.30.18 September 21

Rewind stopped lying about the swarm

  • When rewinding the history, the task, sessions and turns were rewinded, but the swarm was not: in the middle of the work, the participant could sign “task cancelled,” although the cancellation happened an hour later. Now the tasks are rewound along with everything else, and the duration is counted from the real start and again shows the real number.
0.30.17 September 21

Careful borrowing: three points out of four

  • The mode that does not ask for permission can no longer be selected even from a stopped session - the refusal comes where the choice is made.
  • Adapter capabilities table. The agent’s card shows what he can actually do, along five axes - and this is visible before choosing an agent, and not in the middle of the work. There are three states, not two: “not tested” means lack of knowledge, not lack of opportunity.
0.30.16 September 21

The application could not reach the cloud

  • The packaged remote control responded “no connection to the cloud” when the Internet was live: the content policy prohibited accessing someone else’s address, and the server did not answer the browser’s preliminary question. Both obstacles looked the same - like a network loss, and this is the worst property of such an error.
0.30.15 September 21

The remote control has become an application: both on the Home screen and a real package

  • Manifest, icons and service script: the remote control is placed on the Home screen and opens without an address bar. For Android, a real package is being assembled with its own code scanner - in an installed application, the system camera would open the browser, not it.
  • The phone no longer gets rejected immediately after pairing: the frequency ceiling has devalued itself, and an unknown phone is now read out of turn.
0.30.14 September 21

Insurance against regressions - and the very first regression she caught

  • Two checks against something that breaks without being noticed. Both paid off immediately, the second - with a large margin.
0.30.13 September 21

Git in the window, requirements from the tracker task and honest token numbers

  • Git tab. Branches, last forty commits and pending changes. For this, a person used to go to the terminal, and the promise of “one window instead of the usual development environment” remained incomplete.
  • Acceptance criteria are parsed from the body of the tracker task into the contract, and do not go entirely into the text of the prompt: the connection “requirement → accepted result” is no longer broken at the first step.
0.30.12 September 21

The session continues with the provider rather than starting over

  • The provider session ID is saved and survives the restart: the agent rises with its entire history instead of retelling a truncated transcript excerpt. This hit the very purpose of the product - to carry out a large task for weeks.
0.30.11 September 21

Five places where the product misled people

  • The phone showed accepted work that was waiting for acceptance. A failed merge was reported as a file conflict. And three more of the same: all five are small in scope of edits and all five tell a person lies - and this is worse than a missing function.
0.30.10 September 20

Measurements instead of promises in interface checks

  • The note editor mode buttons were 17 pixels high—hard to hit with a finger or an imprecise mouse. The rest is tests that now measure rather than imply.
0.30.9 September 20

A straight line of counters and a clear path to AI agreement

  • Counters on the dashboard. There are eight of them, and the strip was drawn in seven columns: on a wide window, the last card remained alone on the second line, and the strip looked chopped off. At the same time, the cost of sessions was transferred to two lines. Now the rows are completely filled, and the value is not broken.
  • Consent to send code to the AI provider. The “consent required” refusal was a dead end: no button, no prompt, and there was no consent switch in the AI settings at all. The reason turned out to be deeper than the text - the error code was lost on the way from the main process to the window, so the consent window was never shown. Now, if you refuse, a window appears with the “Allow” and “Open AI settings” buttons, in the settings there is a switch itself, and the button leads directly to the desired line: the page scrolls to it and circles it for a few seconds. The API key string and provider selection are opened in the same way.
0.30.8 September 20

Conflict exit buttons are no longer hidden

  • In a narrow window, when a preview of the application was open next to the files, the “file version has diverged” bar crawled beyond the border of the panel, and the “Reread” and “Overwrite with your version” buttons ended up under the adjacent panel: it intercepted the click. These are the only two ways out of the conflict, which means it was impossible to get out of it. Now the message occupies the entire line, the buttons go to the next one and can be compressed, the file panel adheres to its boundaries, and when the window is low, the editor scrolls and the entire bar is visible. Tested on five widths from 1280 to 768 pixels and with a larger system font.
0.30.7 September 20

Lost connection does not stop progress

  • A loss of connection is just a loss of connection. The phone fell off in the middle of the turn - the device turns to the end, no cancellation or stop occurs. Upon returning, the phone reads the outcome using its key, and repeating the same request returns the previous receipt, rather than triggering a second turn. Stop can only be an explicit command, and it is recorded.
  • The remote control distinguishes between a restart and a break. Each Pulse launch has its own number. We connected back, the number is the same - the phone just finishes reading the feed. The number changed - the warning “Pulse on the machine was restarted...” and the list “Requires attention.” The header honestly says what is happening: “the connection is lost - the machine continues to turn” or “the machine is not in touch.”
  • A receipt from a previous launch is not a promise from a current one: Each request registry entry is marked by the launch that accepted it, and the external agent sees the same number in the list of commands.
  • Honestly about limits: the work lives as long as Pulse is running. Moving execution to a separate process or to another machine is a separate project; this issue sets the stage for it, but doesn't make it itself.
0.30.6 September 20

Environment and Schedule Commands

  • List of commands for external agents. Pulse announces to the outside what can be done with it: view tasks, sessions and feed, pick up a receipt by request number, create a task in the connected repository, open a session, send a prompt, interrupt the progress, stop the session, change the stage. Reception, infusion and removal from outside are not intentionally available.
  • You can't do more from the outside than from the inside. Each changing team undergoes the same license and budget checks as the button in the window, receives a request register entry with receipt and outcome, and a line in the activity log - including denials. Repeating with the same key returns the same result rather than creating a second task.
  • Pulse MCP Server: The external agent itself finds the running application and accesses it at the local address with a token. Pulse is not running - an understandable failure, but reading tasks and git files works as before.
  • Schedules in “Settings → Schedules”: the task runs at a specified time by day of the week or every N minutes, the time zone is stored in the schedule itself. Before launching, you can run a verification command - if it fails, the launch is skipped, and no one wakes up the agent. The launch has its own budget, “new task” or “continue previous session” mode, and a rule in case of a miss: skip or complete once. The history of the last fifty starts is visible with the reasons and verification output, there is a “Run now” button. One launch is scheduled at a time; works while Pulse is open.
0.30.5 September 20

Your code and app in one window

  • The "Files" tab in the task. Next to the chat is a working copy of the task or selected isolated session: a list of files taking into account gitignore, search by path, editor with line numbers. Save by ⌘ S checks the file version: it has changed - the “Reread / Overwrite with your version” bar, and not the silent loss of other people’s edits. While the folder is occupied by an agent, the entry is rejected. Binary files and anything heavier than a megabyte are only viewable, and “Open on line N” takes you to an external editor exactly to the desired line.
  • Preview of the application. The development team is remembered for the task and is raised directly in the working copy of the tab on the dedicated port: the live application is visible next to the code. The state, port, working copy, and tail of the output are shown. Each working copy has its own process and its own port; exiting Pulse extinguishes the launches, and they do not rise by themselves at the next start.
  • Point at an element and take it into the session. Select mode highlights the element in preview and shows the selector, text and markup; “To the session composer” adds it to the draft - the person sends it anyway. The location in the code is indicated only when it is known exactly, otherwise it is honestly “undefined”.
  • Three layouts: “Files”, “Files + Preview”, “Preview”. The selection is remembered along with the rest of the window's working context.
0.30.4 September 20

Shared board as a group workplace

  • The card now has a responsible person and an inspector - from the project participants. The lines of the board have become addressable: your own task opens, someone else’s task has a “Request transfer” button, and the observer can only read. Receiving a card does not mean launching someone else's agent.
  • Discussion directly on the card: notes, transfer requests and review requests. The card holder with a designated reviewer has a “Request Review” option. The card owner, its author, or the project owner can close a post.
  • Work without a network. The board shows the last confirmed photo with a timestamp, rather than a blank screen. Actions go into the “Waiting to be sent” queue and are sent in order when connected. The server refused - the version is outdated, there are no rights - the action remains with an error until the person decides: other people's changes are not overwritten silently.
  • “Requires attention” knows about the board: the assignment to you, the role of the reviewer and open requests on your card come in separate records with a transition to the project, and your own card goes directly to the task.
  • The application recognizes the old server and speaks about it directly, and does not break down: the board and publication work at the same time. Honestly about testing: the script was not run on two live machines with an updated server.
0.30.3 September 20

Full review cycle

  • Task contract. The task has a goal, acceptance criteria, restrictions and verification commands - these are edited on the “Diff” tab. The same text goes to the author as the first turn and when resuming, and to the inspector as a check prompt. Acceptance remembers which version of the requirements was accepted: if the requirements were changed, acceptance is removed and the task is returned for review.
  • Notes on version, file and lines. The notice is tied to a specific result version, file, diff side, and lines. A new version has been released - the link is marked as outdated, and the person decides: “Relevant” or close. The inspector's findings become the same observations. A package of comments is sent to the selected author session with one button, the task receives the “Needs improvement” stage. Only a person closes a comment, and it is impossible to accept a task with unclosed ones.
  • Two certificates instead of one. Verification commands from the contract are run in the working copy, and the result is stored along with the version: next to the inspector’s assessment you can see whether it is for this version or is already outdated. The Require Passed Inspections setting makes a successful pass a condition of acceptance - this is the release policy, not the inspector's opinion.
  • New stages “Needs improvement” and “Vlita” - on the board, in the column and as a result. The “Review” view has appeared in the activity feed, and the full result is shown by file with a comment button for each.
0.30.2 September 20

Recovery and work context

  • Register of requests. Each command - prompt, stop, cancel - receives a record: a receipt (turn number, place in the queue) separately from the outcome. Repeating with the same key returns the previous receipt even after a restart, rather than triggering a second turn. Requests caught in an application exit are marked “outcome unknown”—they are not replayed silently. The source of the command—window or phone—is saved.
  • You can see why the session stopped: you stopped, the application restarted, the agent crashed, the budget ran out, the time ran out, the swarm was canceled. The reason is written under the session name. Open swarm jobs after a restart are canceled with the label "Interrupted by application restart" rather than "Stopped by owner".
  • “Requires attention” - one list of everything that awaits a person: resolution, agent question, error, check result, swarm member's merge conflict, interrupted turn, unknown outcome of request, limit reached. Each entry has a navigation link—directly to task, session, and tab—and “Submit Again” and “Close Issue” buttons. The “Dashboard” section shows the number of hanging blockers. Reading does not close the record.
  • The application opens in the same place where you closed it: section, task, tab, selected sessions, board search and filters, graph depth and direction, settings page, graph camera for each task. The snapshot is checked against reality - the deleted task will not open - and the recovery does not start anything on its own.
0.30.1 September 20

Input safety and state reliability

  • Typed text no longer disappears. The draft belongs to the session, not the tab: the transition “Session → Diff → Session”, failure to send and restarting the application do not erase it. The field is cleared only after confirmation and only if you have not added a new one. A click in the graph panel while the composer is still waiting for an answer does not trigger the second turn, and the repetition after a refusal goes away with the same key.
  • One task stage for board, graph and result. The end of the agent’s turn no longer displays the task as “completed”: during check it is still marked “under review”, only the one accepted by a person has a green status.
  • A canceled swarm mission is not a report: it has its own condition and its own reason, and not a fictitious result. The presenter can see the cancellation counter.
  • The cost of a task is the sum of sessions. Previously, the graph took the figure of one session: two at $2 and $3 gave $3. Now the costs are added up, the counter is reset when transferred to another agent, and if part of the turns are without a price, it is written: “from $X · incomplete.”
  • Rewind shows the past, not the future. When rewinding back, the call line already carried the status and output, which did not yet exist at that moment. Now you can see exactly what happened at the selected moment, the task stage is signed “now: …”, and the events of the old format are shown as they are.
  • Unpublishing works without a network: the task immediately becomes local, the command page says "withdrawal awaiting sync", and background sync no longer republishes the card after a restart.
  • The manual infusion race is closed: a working copy occupied by an agent cannot be intercepted, and deleting a task waits for the folder to be freed and does not destroy what the agent writes to.
0.30.0 September 19

QR pairing and end-to-end encryption

  • The phone and the device get to know each other via QR. “Settings → Cloud → Phones”, “Show code” button: on the QR screen, the same link in text and countdown. The code lives for two minutes and ten seconds before the end it updates itself - otherwise the person takes out the phone to the dead code. Below is a list of connected phones with key fingerprints and a “Recall” button.
  • The server transmits ciphertext for which it does not have the key. Everything is encrypted except the handshake: remote control operations, machine responses, events. The frame cannot be repeated, reflected back to the sender, or transferred to another machine-phone pair, and the machine does not fulfill an unencrypted request at all - otherwise encryption would be done with the request “let’s go without it.”
  • Stealing a phone tomorrow will not decipher what was recorded yesterday: For each connection, both parties create one-time keys, and long-term keys prove that at the other end is exactly the right machine and exactly the right phone.
  • The phone key is not removable and lies only on the phone - even we don’t have its bytes. The machine key is stored in the same place as the other application secrets; there is no separate file with the key. The received device key is checked against the fingerprint from the link: it doesn’t match - “The device could not be verified, try pairing again,” and then nothing happens.
  • You cannot connect unnoticed: the phone connection is written in the activity feed - “Pixel phone has connected.” A phone whose key is unknown to the machine is rejected and no operations are performed.
  • Why was this done before release and not after? The frame format and trust model are set in the first version: adding encryption “to the second” means simultaneously breaking all installed phones. What is not yet available and what is written directly about: biometrics before the session is shown, auto-recall of a long-silent phone and scanning with a QR camera - the code is entered with a link.
0.29.0 September 19

Repeater: device and phone meet on the server

  • Why through the server, and not directly. The phone cannot call the machine: the home router does not allow incoming connections, most providers have a common address and are still moving, nothing goes through someone else’s network at all. Asking a person to forward a port means losing him on the first step. Therefore, the machine itself opens the outgoing connection and holds it, the phone opens its own, and the server transfers frames between them. From the network side, this is regular HTTPS to a regular website.
  • The repeater deliberately does not understand anything: it parses only the outer envelope - who is who, when and how many bytes. The phone’s frame only reaches his device, the device’s frame only reaches its phones, and you can’t substitute someone else’s “from”: this field is set by the server itself.
  • Off by default. “Settings → Cloud → Control from phone”: until the switch is pressed, the connection does not open at all, not a byte goes out. The same switch is in the personal account, and turning it off immediately breaks the connections between the machine and its phones. Recalling the phone terminates its connection in the same instant - otherwise the “Recall” button would close the door behind which the phone is already sitting.
  • The device returns on its own: after the break, attempts occur after 1, 2, 4 ... up to 60 seconds with a random spread, so that after restarting the server, all machines do not arrive in one second. A machine that is silent for a minute and a half is considered offline, and in the account it says so - “in touch” or not.
  • You can't do more from your phone than from a window: The remote control operations call the same facade as the window, so the prompt from the phone runs into the exhausted task budget in exactly the same way. There are limits to prevent the repeater from becoming a free tunnel: frame size, frames per second, connections per person, prompts per minute per session. The outward refusal texts do not contain paths and file names - the details remain in the machine log.
  • Honestly about this release: the load was running open inside the TLS connection. The place for encryption in the frame was built in, but the encryption itself did not exist yet - it appeared in the next version.
0.28.2 September 19

The prompt responds with a turn number, permissions are visible in the list

  • Sending is no longer a throw into nowhere. Previously, “Send” returned control instantly - before anything happened - and if the agent did not rise, the reason went to the developer console: the person saw an empty chat and did not understand whether the progress was ongoing or everything was already broken. Now the sending responds with a turn number - the same one that appears in the “Turn N” card and in the “Go to turn” list. A prompt sent during someone else’s turn honestly responds with “in queue” and its future number, and a refusal - no license, task budget has been exhausted, agent has not started - is shown in a line under the input field.
  • Dangling permissions can now be listed. The request “allow writing to file?” lived only as a card on the screen, and anyone who connected later - a second window, and tomorrow a phone - saw only “the session is waiting for something.” A general list of unanswered requests appeared: what was asked about, what options are there when the request expires on its own. The response to a request that has already been answered from another screen no longer falls into silence - it returns “late” and the card simply disappears.
  • All actions are collected in one place. Tasks, sessions, feed, prompts, permissions, stops and limits flow through a common façade, and license and budget checks are built into the operations themselves. This is not a decoration: the second input - the phone - otherwise it would bypass the task cost limit, and the closed license screen would remain a decoration.
  • Repeating the prompt does not produce a turn: the same key returns the same response within an hour, and a repeat that arrives while the first request is still on the way waits for the same response. The connection is broken precisely between the sending and the response - you need to ask again with impunity.
0.28.1 September 19

Event cursor and transcript pages

  • Each event in the session now has a number — monotonous and continues after restarting the application. It was impossible to continue downloading the tape in time: there are dozens of events per second, and the labels match. Both the window and the telephone see the same number, so they won’t number the same tape differently.
  • The tape is read from the correct end. Previously, opening a session parsed the entire transcript file; Now pieces from the end are read backwards, and the right place forward is found by dividing in half. The desktop also wins: a long session opens faster.
  • Pages out. The tape can be retrieved in portions with the cursor. Heavy tool inputs and outputs larger than 4 KB are replaced with a label with the original size and the beginning of the text, and the full output is loaded separately and in chunks. If the cursor is older than the oldest saved record, the client receives a break sign and displays it, rather than silently merging the tape.
  • There is no network here yet: this is the first step towards a mobile remote control - preparing the application itself, without which there is no point in writing a gateway.
0.28.0 September 19

UI catalog: human and agent interface blocks

  • Ten ready-made interface blocks: application framework, metric cards, data table, form with checks, empty state, confirmation dialog, notifications, log style cover, bento grid, tariffs. Each block is not a picture, but a working page with its own styles: dark theme, visible focus, adaptive up to 360 px, accessibility and behavior - focus trap in a dialog, sorting in a table, displacement in a notification stack.
  • To a person — “Settings → Library → Catalog UI”: search, sections, live block preview and two buttons — “Copy markup” and “Copy rules for agent.”
  • Agent the catalog is available as a tool: he can look at the list of blocks and pick up the one he needs along with the rules, and the hint has been added “look in the catalog before layout.” Why: an agent who was told “make a page” by default produces what was most often encountered in training - a centered heading, three identical cards, gray text on white. A preparation, not a product.
  • The rules come first, not the code: Each block has a description of what it holds, what not to do in it, and what accessibility cannot be lost. Having received only the markup, the model changes exactly what the block was made for - the asymmetry of the grid, different button weights, the connection of the field with the signature.
0.27.0 September 19

Terminal panel with blocks, its own library of skills, code base memory

  • The terminal has become a panel and opens by ⌘ J from any section, and not just in the task tab: tabs for working copies, switching from the keyboard, the height is dragged with the mouse and remembered.
  • “Command → Output” blocks. In addition to the regular flow, there is a “Blocks” view: for each command you can see what exactly was launched, how it ended and how long it took. The block is collapsed and copied as a whole, arrows scroll through the command history, and a failed command has an “Explain Output” button - it will send the command and the tail of the model output and return parsing.
  • The library of skills became our own. The installed skill can be removed, compared with the library version and updated. Your skills are written directly in the application, they have a version history with rollback, and the “Rate” button gives the skill a score from 0 to 10 with a short analysis - the list is sorted by it.
  • The quality inspectors got it right. The inspector's advice is applied with one button: it is added to the agent's instructions with a new version. Dynamics of ratings for agents and a quality threshold before merging have appeared - the work of a swarm member is not merged until it reaches the required score.
  • Codebase memory. Pulse builds a map of the project - the files that they give and what they take from each other - and makes it searchable by name. The map is prepared in the background when a task is created, and the agent uses it instead of blindly re-reading the repository.
0.26.3 September 19

Cloning from GitHub and GitLab

  • The “Clone” button understands everything people paste: a link from the address bar, “Clone with HTTPS” and “Clone with SSH”, short owner/repository, GitLab groups and their servers. Private ones work in the same way - the password is asked by a regular window, the token from “Integrations” is substituted. And a folder without git is no longer an error: Pulse suggests creating a repository here or cloning someone else’s.
0.26.2 September 19

Section "My Account"

  • The avatar at the bottom of the sidebar was just a picture, but became the entrance to your section: who you are and on what plan, the license key and how many days are left, how much has been done - tasks, sessions, turns, tool calls, affected files and money spent, activity for 30 days in columns, which agents you work with most often and which repositories are occupied. Everything is calculated from the tasks that are already in the application, so the numbers cannot diverge from the board.
0.26.1 September 19

Updates are checked once an hour

  • Previously, once every six hours, and then only if the cloud was turned on, but by default it was turned off: no one knew about the released version. Now the check occurs once an hour and again when returning to the window, so you will hear about the update the same morning.
0.26.0 September 19

License required, assembly closed

  • Without a valid license, Pulse does not work: does not create tasks, does not launch sessions and does not make turns, but explains on the screen what happened and where to go. The rights are signed by the server, the application checks the signature - you won’t be able to issue a license for yourself by replacing the cloud address with your own, and editing the settings file also doesn’t do anything.
  • You can work without a network for 30 days. Changing the clock back does not help: the lower limit is the time of the last connection with the server.
  • States separated - there is no license, the term has expired, there has been no communication for a long time, the signature does not match: everyone has their own text and their own buttons, and not one common “access denied.”
  • No one working was left without access: Before inclusion, everyone who was already registered was issued perpetual licenses. There is a switch left on the server that returns the previous beta mode to everyone at once - in case the delivery goes wrong.
  • The assembly is closed. The code no longer comes out in a readable form, the core of the application is compiled into bytecode, and a debugger cannot be attached to it. Honestly about the limits: this stops the curious, but not the one who purposefully disassembles the application. The only real border is the server one: the issuance and revocation of licenses live where strangers do not go.
0.25.2 September 18

Windows build starts working

  • The very first test run showed that the assembly would not have gone beyond installation. Fixed: rebuilding the commit history, removing stuck operations by an entire tree of processes (otherwise the next one would run into “another git process is already running”), searching for installed agents, the “Login” button and prohibiting destructive commands - the rules were written for macOS and did not protect on Windows.
0.25.1 September 18

First Launch Wizard

  • Four steps when starting for the first time: how it generally works; install agents - each one shows whether it is found, and the command for your system is shown, it can be opened in the terminal with one button; log into their accounts; first task. The state of the steps is calculated by the live list of agents, and not by the buttons pressed: the wizard can be closed, delivered programs manually and returned - it will show what remains.
  • At the same time, an error in one section no longer blanks out the entire window: only the section itself crashes, and in its place is a card with the text of the error and the “Try again” and “Copy error” buttons.
0.25.0 September 18

Windows, Ubuntu and macOS on Intel

  • Installers for three new platforms: Windows (regular installer and zip), Ubuntu (AppImage and deb), macOS on Intel processor. Each combination of system and architecture is assembled on its own machine - otherwise agent programs from someone else’s platform would be included in the assembly, and they simply would not start.
  • So that this is not a showcase, everything that was previously written for macOS is divided into systems: the terminal shell, searching for installed agents, launching them, the “Login” button, working with git and passwords, links pulse://, key storage.
  • The sandbox remains only on macOS and he speaks honestly about it: it is built on a system mechanism that is not found in other operating systems. Previously, the toggle switch promised isolation everywhere.
  • Android - you can't, and it's not a matter of effort. Pulse works by running agents, git, and a terminal on your machine, while your phone doesn't. A smart way is a mobile remote control for a work machine; he stays on track.
0.24.2 September 18

Notes are saved themselves

  • Edits to notes could get lost: the field disappeared when switching to “View” and when leaving the task, and along with it, the unsaved text disappeared. Now notes are saved automatically after a pause after typing and are added when closing the task.
0.24.1 September 18

Chat turns are numbered consecutively

  • After restarting the application, the numbering of turns began again, and in one session there were 1...11 in a row, and then again 1, 2, 3 - it looked like these were different sessions. Now the numbering continues, and each line shows the time and source of the turn: from you, a participant’s report, an architect’s assignment, a session transfer.
0.24.0 September 18

Note editor and left column

  • Full Markdown editor in task notes and in the repository memory: insert panel (bold, italic, code, title, list, checklist, quote, table, code block, link), markup highlighting directly in the field, “Edit”, “View” and “Nearby” modes, “full screen” button, familiar hotkeys.
  • The sessions column stretches to the right edge and remembers the width; double clicking returns the original one. Long role names and task lines are moved to the next line instead of an ellipsis.
  • Corrected: the “give a task” button to a swarm member silently did nothing. Now a window opens with a field and an explanation of where the task will go: the participant will do so on your behalf, and his report will be returned to the architect.
0.23.4 September 18

The installer window has been redesigned

  • The DMG background is re-drawn: window 600x450, a header with an icon and version, two nesting tiles for the application and “Programs”, an arrow with a gradient, tips about the first launch and a bunch of keys. Tooltips are raised from the bottom edge - Finder cuts the window to the height of the title bar, and previously the bottom line went off the edge.
  • Cleaning after renovation. Installing via the cloud opened the DMG in Finder and did not clean up anything after itself: one of the alpha participants ended up with eight mounted volumes and 4 GB of downloaded images. Now Pulse itself extracts volumes and deletes outdated images eight seconds after startup.
0.23.3 September 18

Login to Codex without system node

  • The login command is run by the application itself: in a packaged build of the system node there may not be, and the “Login” button was silently not working.
  • Login using ChatGPT account - normal codex login: The browser confirms the subscription, no API key is needed. The key remains an alternative for those with API access.
0.23.2 September 18

Codex without installation and any model manually

  • Codex no longer requires installation: its CLI comes inside the Pulse ACP adapter dependency. The card shows the “built-in CLI” and version, the “Login” button opens Terminal with the desired command. Your own codex in PATH is still a priority.
  • Manual Model field in the agent card: the id of a model that is not yet in the list goes into the “Model” chip and becomes current for new sessions. Providers release models faster than agents update listings - now this is no longer a problem.
  • The same model can be used with the built-in Pulse agent: Local Model card, address https://api.openai.com/v1 and a key. Then Pulse tools and its sandbox work.
0.23.1 September 18

Chat opens on last action

  • When switching sessions, the chat panel showed the first turn, not what the agent did last. Now both panels - the task chat and the graph panel - open the session at the last event, like a regular messenger, and remain nailed to the bottom until you scroll up.
  • Tested on a long transcript: before the correction, the graph panel was 3309 px from the bottom, after - 0 px.
0.23.0 September 18

Quality inspectors: which agent writes better

  • Quality inspection. A strong model reads the diff of someone else’s work and makes an assessment along six axes - correctness, readability, tests, security, within the task, comments - writes findings “file: line - problem - how to fix”, makes a verdict and one correction to the author for the future.
  • Quality button in the task header and automatic start, when the agent has completed the entire queue of turns and there are no other ongoing sessions in the task. The same work is not checked twice, the budget of the task is taken into account.
  • Inspector roles in a swarm: “Front-end inspector”, “Back-end inspector”, “Quality inspector”. The policy prohibits them from editing files and running commands. New ready-made composition “With inspection”.
  • Agent comparison in “Settings → Quality”: table for the key “agent + model” with average score, axes, critical findings and last adjustment.
  • Tested live: Claude Opus 5 as a frontend inspector rated GigaChat-2-Max - 0.5 out of 5, “rework”, ten finds, including a non-assembling token module and 543 files node_modules in the commit.
0.22.7 September 18

GigaChat: tools working

  • GigaChat has ceased to be a chat window and has become an agent: it reads and edits files, runs commands, responds to permission requests, and works in the swarm along with others.
  • The format for calling functions in GigaChat differs from OpenAI - the differences are encapsulated in the built-in agent, there is no difference for the interface and graph.
0.22.5 September 18

Log file and bug report

  • Pulse keeps a log of application and interface errors, masking secrets by field names before writing to disk.
  • In “Help” you can see the path to the file, you can look at its tail, describe the problem and send a report to the developers - it will include the version, environment and log tail. Nothing goes away until you hit send.
0.22.0 September 18

Context compression for the built-in agent

  • At 75% of the model window, compression is turned on with the goal of returning to 50%: first, the tool leads in the old turns are trimmed, then the old turns are collapsed into one summary, and only then - hard trimming.
  • The fresh result of the tool is never touched, the “call → result” pairs are not broken. The transcript contains a line like “Context compressed: 3 turns compressed into a summary (≈28k → ≈9k out of 32k).”
  • Token evaluation is calibrated based on server responses - Pulse is adjusted to the specific model of tokenizer.
0.21.0 September 18

Instructions Versions

  • Each saving of a modified instruction of an agent or swarm member variant creates a version: number, date, difference to the current text, full text, “Return” button.
  • The session shows which version was sent to the agent with the first turn. The selection of prompts has ceased to be a guess: “he did better on v2” - now a verifiable statement.
0.20.0 September 18

Swarm: your own worktree, merging, auto-repeat

  • Each swarm developer has his own working copy on a branch <task branch>-<role>. Before the task, the task branch is transferred to the participant, and after the report, his work is transferred back.
  • Merge conflict rolls back, the architect gets the list of files and decides who rules.
  • Auto repeats: the fallen participant receives the task again up to two times; If frozen for more than twenty minutes, it is interrupted by the guard and is considered a failure.
0.18.0 September 18

Policies, budgets, sandbox, audit

  • Tool Policies: "allow/ask/deny" rules by tool and regular expression. They are checked before the auto mode - what is prohibited by the rule remains prohibited.
  • Task budget in dollars with warning threshold; When exhausted, sessions are stopped.
  • Sandbox for built-in agent commands: write only to worktree, tmp and package manager caches.
  • Export audit in Markdown: prompts, turns, calls, permissions and who gave them - a person, a rule or an auto mode.
Full list

All issues list

From the first build on September 16, 2026 to the current one. Technical details of each version are in CHANGELOG.md repository.

  1. 0.31.10October 2Git, Browser, Plugins and Space - next to tasks
  2. 0.31.9September 30Design system from the sign: flow, glass, living graph
  3. 0.31.8September 30One ADE: terminal and agent work on the same task
  4. 0.31.7September 29New Claude models in the supplier's list
  5. 0.31.6September 29Current supplier models
  6. 0.31.5September 29Readable lists of roles and models
  7. 0.31.4September 29Installing CLI on Windows
  8. 0.31.3September 29Signed updates and working panel buttons
  9. 0.31.2September 27Agents are updated inside Pulse - without the Terminal window
  10. 0.31.1September 27The update installs itself - without dragging it from the image
  11. 0.31.0September 27Your own window panel on macOS and terminal rules from the command card
  12. 0.30.40September 24Swarm audit test does not turn main on its runner
  13. 0.30.39September 24The main repository has moved to its own GitLab
  14. 0.30.38September 23Swarm 24/7: decisions by rules, not by guessing
  15. 0.30.37September 23Swarm 24/7: MR only after security reviewer
  16. 0.30.36September 23Swarm 24/7: seven roles, and reviewers only read the diff
  17. 0.30.35September 23Swarm 24/7: agent network perimeter - code, not prompt
  18. 0.30.34September 23Swarm 24/7: task queue for pg-boss
  19. 0.30.33September 23Swarm 24/7: one task manifest on all inputs
  20. 0.30.32September 23Swarm 24/7: own repository area and package framework
  21. 0.30.31September 22Settings can again be reached with the mouse
  22. 0.30.30September 22A report from a live user, parsed down to its causes; checking for updates on first launch
  23. 0.30.28September 22Nine versions at once: the update is checked before installation, parcels go on their own, consumption is visible everywhere
  24. 0.30.19September 21Second device: the settings are moving, but the window is no longer waiting
  25. 0.30.18September 21Rewind stopped lying about the swarm
  26. 0.30.17September 21Careful borrowing: three points out of four
  27. 0.30.16September 21The application could not reach the cloud
  28. 0.30.15September 21The remote control has become an application: both on the Home screen and a real package
  29. 0.30.14September 21Insurance against regressions - and the very first regression she caught
  30. 0.30.13September 21Git in the window, requirements from the tracker task and honest token numbers
  31. 0.30.12September 21The session continues with the provider rather than starting over
  32. 0.30.11September 21Five places where the product misled people
  33. 0.30.10September 20Measurements instead of promises in interface checks
  34. 0.30.9September 20A straight line of counters and a clear path to AI agreement
  35. 0.30.8September 20The conflict bar in “Files” does not go under preview
  36. 0.30.7September 20Lost connection does not stop the device from moving
  37. 0.30.6September 20Environment and Schedule Commands
  38. 0.30.5September 20Code and application in one window: “Files” and preview
  39. 0.30.4September 20Shared board as a group workplace
  40. 0.30.3September 20Full review cycle: contract, comments, inspections
  41. 0.30.2September 20Recovery and work context
  42. 0.30.1September 20Input safety and state reliability
  43. 0.30.0September 19QR pairing and end-to-end encryption
  44. 0.29.0September 19Repeater: device and phone meet on the server
  45. 0.28.2September 19Operations façade: prompts with response and dangling permissions
  46. 0.28.1September 19Event cursor and transcript pages
  47. 0.28.0September 19UI catalog: human and agent interface blocks
  48. 0.27.0September 19Terminal panel with blocks, your skills, code base memory
  49. 0.26.3September 19Cloning from GitHub and GitLab
  50. 0.26.2September 19Section "My Account"
  51. 0.26.1September 19Updates are checked once an hour
  52. 0.26.0September 19License required, assembly closed
  53. 0.25.2September 18Windows build starts working
  54. 0.25.1September 18First Launch Wizard
  55. 0.25.0September 18Windows, Ubuntu and macOS on Intel
  56. 0.24.2September 18Notes are saved themselves
  57. 0.24.1September 18Chat turns are numbered consecutively
  58. 0.24.0September 18Note editor and left column
  59. 0.23.7September 18“What eats the limit” and tokens on the graph
  60. 0.23.6September 18Model limit in chat and transmission of session with report
  61. 0.23.5September 18Settings: single column width
  62. 0.23.4September 18Installer window redesigned, cleaning volumes after update
  63. 0.23.3September 18Login to Codex without system node
  64. 0.23.2September 18Codex without installation and any model manually
  65. 0.23.1September 18Chat opens on last action
  66. 0.23.0September 18Quality inspectors: which agent writes better
  67. 0.22.8September 18README and documentation
  68. 0.22.7September 18GigaChat: tools working
  69. 0.22.6September 18“Agents and Models”, checking the model server, scrolling columns
  70. 0.22.5September 18Log file and bug report to developers
  71. 0.22.4September 18Activity: search, filters, sorting, time
  72. 0.22.3September 18Status bar in all sections, timeline only on the graph
  73. 0.22.2September 18Descriptions of skills in Russian
  74. 0.22.1September 18GigaChat selects the access type itself, task timeout in the swarm
  75. 0.22.0September 18Context compression for the built-in agent
  76. 0.21.0September 18Instructions Versions
  77. 0.20.0September 18Swarm: your own worktree, merging, auto-repeat
  78. 0.19.0September 18External MCP servers and code memory
  79. 0.18.0September 18Policies, budgets, sandbox, audit
  80. 0.17.0September 18Repository memory and task notes
  81. 0.16.4September 18Changing agent in open session, installer
  82. 0.16.3September 18Keychain stopped asking for password after update
  83. 0.16.2September 18Fixed empty window on startup
  84. 0.16.1September 18The local model crashed at the start - fixed
  85. 0.16.0September 18Swarm of agents: compositions, roles, mission protocol
  86. 0.15.5September 18Network layer, secret encryption, single git facade
  87. 0.15.4September 17Notifications in the bottom bar
  88. 0.15.3September 17Positioning: the first Russian ADE
  89. 0.15.2September 17README as product page
  90. 0.15.1September 17Full view of the chat on the board graph
  91. 0.15.0September 17“Agents” section redesigned, OpenCode, local model
  92. 0.14.0September 17Calls and groups in the graph, live events in batches
  93. 0.13.0September 17GitHub and GitLab integrations
  94. 0.12.2September 17White window title bar in dark theme
  95. 0.12.1September 17Call cards, drop-down lists, agent list
  96. 0.12.0September 17Repository and resources in composer, "/" menu
  97. 0.11.0September 17Graph of the entire fleet in one canvas
  98. 0.10.0September 17Settings: sections, themes, default folders
  99. 0.9.0September 17Side panel preview of task, list groups
  100. 0.8.0September 17Session summaries and activity log
  101. 0.7.0September 17Chat session in the graph, effort, token consumption
  102. 0.6.0September 17Graph depth and petal layout
  103. 0.5.0September 17Single right column, subagents as separate nodes
  104. 0.4.0September 17Agent cards with statuses, Claude authorization
  105. 0.3.0September 17Sessions: several agents for one task
  106. 0.2.0September 17Shell, Agent Graph, ACP transcript
  107. 0.1.0September 16First version: tasks, worktree, Claude Code, Codex and Kimi by ACP

How to read version numbers

Patch - for each delivery: repair, small opportunity, documentation editing. Minor - at a milestone, which makes sense to call a release: a closed phase of the plan, a new large set of capabilities. While the product is in alpha, both numbers are growing quickly.

What's next

Issues from GitHub and GitLab as task resources, scanning the pairing code with a phone camera, execution that lives longer than an open window. The full list with the marks “in progress” and “offered” is in road map.