Installation

Set up Pulse in five minutes

Windows, macOS and Ubuntu. Below is what the machine needs, what the system will ask when it first starts, and how to get to the first task.

page texts - 0.36.4; the build on the card may be older Windows · macOS · Ubuntu Links to assemblies →
Installation

Download for your system

The version and size of the card are taken from the update server - the same one that updates the application itself. Access is granted using a code: it is activated upon first login.

Your system macOS · Apple Silicon M1 and newer, macOS 13+. DMG file Checking the version… Download
Your system macOS · Intel Macs before switching to Apple Silicon. DMG file Checking the version… Download
Your system Windows · x64 Installer EXE Checking the version… Download
Your system Ubuntu · x64 AppImage File Checking the version… Download

In 0.31.10 the update signing key changed. To upgrade from any version prior to 0.31.10, including 0.31.3, download build 0.31.10 or later once from your platform card above, close Pulse and install it manually. The new client then checks the next releases with the new key. If the card still has a version lower than 0.31.10, a new build for this platform has not yet been published.

To operate, you need an access code: it is activated on activation page and binds the license to your account, not to the machine. No code - leave a request, we will send. Already activated - the key and deadline are visible in account.

New update key from 0.31.10 - one manual installation

Any client version prior to 0.31.10, including 0.31.3, will not accept the new signature. To switch, download installer 0.31.10 or later from cards of your platform, close Pulse and install manually once. After installation, log in to your old account: the new client checks the following releases with the new key. The cards show the actual published versions; If the version for your platform is lower than 0.31.10, the new build has not yet been released.

You need an access code to work

The application is free to download, but without a valid license it does not create tasks or launch agents. The code is activated on activation page and is linked to an account, not a machine. No code - leave a request.

Requirements

System requirements

System
Windows 10 and later (x64) macOS 13 Ventura and later Ubuntu 22.04 and later (x64)
Processor
x64 for Windows and Ubuntu; for macOS - both Apple Silicon and Intel. There are no builds for ARM for Windows and Linux yet
Disk
≈ 600 MB for the application plus space for working copies of tasks - each task takes up the same amount as your repository
Git
2.30 and newer - Pulse works through regular worktrees
Agents
CLI of the agents you will use: claude, kimi, opencode, grok. Codex is built into Pulse; for GigaChat and the local model you do not need to install anything. The First Run Wizard will show you the installation command for your system
Access
access code: activated on /signup, the license is tied to the account. Without a network, the application works for up to 30 days from the last connection with the server: that’s how long the signed copy of the license lasts (login to your account lasts a little longer - 32 days)
Models
your subscriptions and keys. For local models - Ollama, LM Studio or your own OpenAI-compatible server
Procedure

From your invitation to your first task

Download the assembly for your system

Links - on the main page: they take the version and size from the update server, so they always show what is actually posted. On a Mac, the page automatically selects Apple Silicon or Intel if the browser tells you to; if not, it shows both assemblies, select yours (Apple menu → “About This Mac”: “Apple M Chip...” - Apple Silicon, “Intel Processor” - Intel). Each platform has its own build number: the product version in the header does not replace the installer version in the card.

The card says “the build is being prepared,” which means that there is currently no file for this system on the update server and there is nowhere to get the link. For those who have access to the project, installers are available at GitLab releases.

Install

macOS: open the DMG, drag Pulse to “Programs”, then extract the image - you don’t need to run from a mounted image, otherwise the updates will fail.

Intel · 0.32.1 · as of October 11: The published DMG is signed by Developer ID AVATEK, OOO and has been notarized by Apple. The ticket is added to the image; Gatekeeper accepts the image and application. The first launch in a separate profile is checked up to the login screen. Automatic app replacement when updating to macOS has not yet been confirmed. For a manual installation, close Pulse and replace the application from the DMG.

Apple Silicon · 0.31.14 · installation history October 6: The released assembly for Apple Silicon is 0.31.14, it has an interface of 0.31, not 0.32. The description of 0.32.1 on this page applies to Intel, Windows and Linux. If you already have 0.31.14 installed from a previous file, close Pulse, download the notarized DMG and replace the application manually using the steps above. Automatic upgrade to the same version number is not offered.

Verified files as of October 11, 2026: for Apple Silicon - darwin-arm64-0.31.14-Pulse-0.31.14-arm64-notarized.dmg, for Intel - darwin-x64-0.32.1-Pulse-0.32.1-x64.dmg. For the current version and link for each processor, see in your platform card.

macOS · 0.31.14 · October 6 · release history: Both Apple Silicon and Intel assemblies are notarized by Apple. The former notarized Intel DMG was called darwin-x64-0.31.14-Pulse-0.31.14-x64-notarized.dmg; in signed 0.31.14, the starting agent check could show an Apple report. The fix is included in Intel 0.31.15.

Windows: run the EXE installer - no questions asked, Pulse is installed for you without administrator rights and opens itself. SmartScreen will warn you about an unknown publisher: “More details” → “Run anyway.”

Ubuntu: Make AppImage executable and run: chmod +x Pulse-*.AppImage && ./Pulse-*.AppImage. AppImage mounts itself via FUSE 2, but in Ubuntu 22.04 and newer it is not available out of the box - without it, the launch is terminated with the words “AppImages require FUSE to run”. Install the library: on 22.04 - sudo apt install libfuse2, on 24.04 and newer - sudo apt install libfuse2t64. Package fuse do not install: on 22.04 it deletes fuse3, on which the system depends.

Additional ZIP and DEB are in GitLab release; they need access to the project. DEB is installed via apt install ./file.deb.

First launch and activation

On macOS Open Pulse from Programs. If the system asks if you want to open an application downloaded from the Internet, click "Open". For the above notarized DMG Intel 0.32.1 and Apple Silicon 0.31.14, the Gatekeeper check is passed.

On October 5 the previous signed DMG 0.31.14 had not yet been notarized, and Gatekeeper blocked the first launch. If you see this warning, check the file name and download the new DMG from the link on the main page. If the warning remains with the new file, please provide the file name and the exact text of the error.

On Ubuntu 24.04 AppArmor prevents regular user namespace programs running the Chromium sandbox. AppImage then does not open the window and writes “The SUID sandbox helper binary was found, but is not configured correctly.” The DEB package does not know this problem: it installs the AppArmor profile itself. For AppImage - manual profile, step by step from instructions. Launch from --no-sandbox the window will open, but will disable the Chromium sandbox for all Pulse windows - this is a one-time workaround, not a way to work.

Sign in with GitHub or email using the account linked to your access code. You can create tasks without a license; an active license is required to start an agent. You can activate your code in advance at /signup.

When asked to access your keychain, respond "Always allow": it contains the key with which Pulse encrypts agent keys - they themselves are stored in the application profile. Answer “Allow once” - the question will be repeated every time you start.

Master and Agent

After logging in, a wizard opens. If the computer has neither an agent nor its own model, the first question is what the agent will think about. Next - “Which agent will be the first?”: the found programs are already in a grid with a status, the first ready one is selected. Not installed - the “Install” button runs the installation command; Codex is built-in - you only need to log in using a button. Then - how the agents work, appearance, notifications and remote control. For those whose agent has already been found, the step about the model is not shown. Each screen is passed ⌘ ↵. After the master - “What are we working on?” and the “First Steps” checklist in the left panel.

For GigaChat, insert the Authorization key from your personal account - Pulse will select the access type itself. For a local model, enter the server address and click “Check”: Pulse will request a list of models and make a test call to the tool so that you can immediately see whether the model can function calling. All this can be changed later in “Settings → Agents” and “Settings → Models”.

Run the first task

In Composer, select the project folder, describe the task in words, and click Run. Pulse will create a separate copy of the project for the task and launch the agent. Inside the task you can see file changes and the terminal by ⌘ T.

It’s better to take the first task small and verifiable: “add a test for such and such a case” or “put this in a separate module.” This will make it easier to understand how the agent reads your project.

For developers

Run from source

If you have access to the repository, there is no need to build - Pulse is installed normally npm run dev.

$ git clone https://github.com/NameLucky2205/pulse.git
$ cd pulse
$ npm install
$ npm run dev
 
# tests and type checking
$ npm test
$ npm run typecheck
 
# build DMG for Apple Silicon
$ npm run pack
Platforms

Where does Pulse work now?

Done

macOS Apple Silicon and Intel

macOS 13 and later, both architectures. Updates come within the application once an hour; Pulse cleans up mounted volumes and old images.

Done

Windows · x64

Installer and zip. The terminal works through PowerShell, policy restrictions are written for it. ARM64 is waiting for a suitable build runner.

Done

Ubuntu · x64

AppImage and deb. The shell is bash. The agent's read boundary is kept by bwrap; On live Ubuntu the behavioral run fails. There is no mechanism on Windows; the agent commands stop there.

Impossible

Pulse entirely on Android and iOS

Pulse works by running agents, git, and a terminal on your machine—the phone doesn't have those. But the remote control for your device is already working: the web remote control opens at /mobile/, the phone connects to the device using a QR code from “Settings → Cloud → Phones”, and the frames between them are end-to-end encrypted - the repeater does not read them. Board, session feed, response to permission and prompt - from the phone; A broken connection does not stop the device from moving.

Phone

Remote control for Android

The same remote control that opens in the browser, only with an application: the client lies inside the package, and is not pulled up from the site.

Your system Android package APK signed with Pulse key. Updated by replacing the package: Pulse is not available in app stores Checking the version… Open the remote control in the browser

The package is assembled and signed along with the release, and the address, version and size of the card are taken from the update server - the same one that distributes desktop assemblies. This means that here is exactly what is actually on the server: until the next release package is uploaded, the card says so, and there is no link to the file. Pulse does not have an app store on any platform - the package is installed and updated by replacing the file. The phone connects to the device using a QR code from “Settings → Cloud → Phones”, frames between them are end-to-end encrypted.

Closed alpha

Leave a request

We will respond to the specified email and send you a link to the assembly along with short instructions.

  • Builds for macOS, Windows and Ubuntu, instructions in Russian
  • Direct communication with developers
  • The license is tied to the account - works on any of your computers
  • Participation is free

We respond within a few days. We do not send mailings and do not share the address with third parties.

Application accepted We will respond to the specified email.