Installation and update

Pulse is going for macOS (Apple Silicon and Intel), Windows (x64) and Ubuntu (x64). What works on every system, and what is currently only on macOS - in Platforms.

Windows

Download Pulse-<version>-x64-setup.exe from the page Pulse downloads and open it. No questions: Pulse is installed for you, in %LOCALAPPDATA%\Programs\pulse, without administrator rights, creates shortcuts on the desktop and in the Start menu and opens itself. Another folder - from the command line: Pulse-<version>-x64-setup.exe /D=D:\Apps\Pulse. The application is not signed with an Authenticode certificate, so SmartScreen will warn about an unknown publisher: “More details” → “Run anyway”.

If Pulse was previously installed “for all users” (as the installer might have asked before 0.31.11), the new installer will offer to delete that copy - Windows will ask for administrator confirmation. If you refuse, there will be two copies left, each with its own line in the “Appendices”. If you agreed, but the shared copy was not deleted, the installer will tell you about this in a window with a code PULSE-INSTALL-001 - in the article, step by step, how to remove it yourself. The copy that you previously installed for yourself in your folder remains there: the installer finds it.

ZIP without installation is among GitLab release files; it requires access to the project.

Ubuntu

Check the release-specific files: Linux installers are not published with every release yet. If .AppImage and .deb available on Pulse website, download them. If not, compile on Linux from sources via npm run pack:linux (see Development).

Pulse-<version>.AppImage - make it executable and run:

chmod +x Pulse-*.AppImage && ./Pulse-*.AppImage

DEB is among GitLab release files and requires access to the project. It is installed in the system along with the dependencies:

sudo apt install ./Pulse-*.deb

Ubuntu 22.04 and newer: AppImage asks for FUSE

AppImage is built by electron-builder with the same performer on FUSE 2 (in package.json not specified toolsets.appimage), and Ubuntu from 22.04 installs only FUSE 3 out of the box. Without the library, the launch ends like this:

dlopen(): error loading libfuse.so.2
AppImages require FUSE to run.

Install the library - the package is called differently in different releases:

sudo apt install libfuse2      # Ubuntu 22.04
sudo apt install libfuse2t64 # Ubuntu 24.04 and later

Package fuse (no number) don't put: on 22.04 it deletes fuse3, on which the desktop depends. Without administrator rights, AppImage can be launched without FUSE - ./Pulse-*.AppImage --appimage-extract-and-run: It will unpack into a temporary folder every time you run it, it's slower. DEB is independent of FUSE.

Ubuntu 24.04: AppArmor and sandbox

As of 24.04, Ubuntu prevents regular programs from creating user namespaces (kernel.apparmor_restrict_unprivileged_userns=1), and on them there is a Chromium sandbox, inside of which the Pulse window runs. AppImage then does not open the window and writes:

The SUID sandbox helper binary was found, but is not configured correctly.
Rather than run without sandboxing I'm aborting now.

DEB does not know this problem: electron-builder includes the AppArmor profile in the package and during installation itself loads it into /etc/apparmor.d/ (template apparmor-profile.tpl in app-builder-lib; on April 22, the profile is skipped - it is not needed there).

For AppImage - your own profile. Put the AppImage in a permanent location like ~/Applications/, and resolve namespaces exactly to it:

sudo tee /etc/apparmor.d/pulse-appimage >/dev/null <<'PROFILE'
abi <abi/4.0>,
include <tunables/global>

profile pulse-appimage @{HOME}/Applications/Pulse-*.AppImage flags=(unconfined) {
  userns,
  include if exists <local/pulse-appimage>
}
PROFILE
sudo apparmor_parser -r /etc/apparmor.d/pulse-appimage

The profile repeats the one that electron-builder installs along with DEB, only it is tied to the AppImage path. Tested using the electron-builder template and Ubuntu parsing, but not run on the Pulse stand since April 24 - if the window still does not open, write to us in a bug report. Another path to the file - correct the path in your profile.

What not to do:

  • --no-sandbox will open the window, but will disable the Chromium sandbox for all processes of the Pulse window: the error in parsing the shown content is no longer locked inside the sandbox. Suitable to make sure that the problem is AppArmor, but not to work.
  • sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 removes the ban for all machine programs at once, and not just for one Pulse.

macOS

  1. Download the DMG for your processor - Apple Silicon or Intel - from Pulse downloads.
  2. Open the image, drag Pulse in “Programs”, extract the image (otherwise the application will launch directly from the image and behave strangely).
  3. Open Pulse from "Programs". If macOS asks if you want to open an app you downloaded from the Internet, click "Open".

This is the usual confirmation of the first launch of an application from the Internet - Apple describes it as separate from Gatekeeper blocking.

Intel 0.32.1 · as of October 11, 2026: The published DMG is signed by Developer ID AVATEK, OOO and accepted by Apple after notarization. Apple Ticket added to the image; Gatekeeper accepts both the image and the application as Notarized Developer ID. 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. To install manually, close Pulse and replace the application in Programs from the DMG.

Current version and link for each processor - in your platform card. Below are verified notarized files for October 11, 2026:

Processor Verified file
Apple Silicon darwin-arm64-0.31.14-Pulse-0.31.14-arm64-notarized.dmg
Intel darwin-x64-0.32.1-Pulse-0.32.1-x64.dmg

Apple Silicon 0.31.14 installation history October 6: if you already have 0.31.14 installed from the previous DMG, close Pulse, download the notarized image and replace the application in “Programs” manually. Auto-update only offers a newer number and replacing the file with a notarized one with the same number will not show.

October 6 release history: Intel 0.31.15 and Apple Silicon 0.31.14 are signed by Developer ID AVATEK, OOO, have been notarized by Apple and verified by Gatekeeper; ticket added to each DMG. The previous Intel image 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.

Why does macOS block the first launch?

As of October 5, 2026 the previous files 0.31.14 already had a Developer ID signature, but Apple notarization had not yet been completed: Gatekeeper responded Unnotarized Developer ID. Even earlier files were locally signed Pulse Dev or ad-hoc.

October 6 both assemblies have been notarized and verified by Gatekeeper. If macOS still shows the unverified developer warning, check the name of the downloaded file in the table above and download the latest DMG from the site. If the warning remains with the new file, please report the exact file name and error text in the problem report.

What macOS will ask when you first launch it

Request Why What to press
Key access «Pulse Safe Storage» in a bunch of keys it's the encryption key, not the secrets themselves. API keys, GitHub/GitLab tokens and cloud session are in secrets.json in data folder and are read with this key "Always allow". “Allow” covers one access. The number of times the window appears per launch is not recorded.
Management Terminal.app agents login: Pulse opens Terminal with the command claude auth login, codex login, kimi login "Allow." You can then change it in System Settings → Privacy → Automation
Access to Documents / Downloads / Desktop git operations in repositories that are located in these folders “Allow” for those folders where you have the code
Notifications Pulse notification center: the agent has fallen off, an update has been released at your discretion

“Allow always” is remembered by macOS for the signature of the Pulse that requested access, and not for the version number. Another signature for the keychain is another application: ad-hoc (each assembly has its own code hash), the local Pulse Dev certificate and Developer ID do not convey consent to each other. As long as the signature of the same copy does not change, there is no need to repeat consent, and a request after each update is not necessary. If the window appears every time you run the same copy, see If something went wrong.

Setup Wizard

When you first launch Pulse, it opens a wizard. It is needed so as not to search through the settings to see what is turned on where. Five steps; the step about the model is not shown if the agent or its own model has already been found. The counter only counts visible steps.

  1. Which agent will be first? — agents that are already on the computer. If not found, the installation command is visible: “Install” opens it in the terminal, “Check again” searches for programs again. Login to the Pulse agent account does not intercept: a terminal opens with the CLI command itself.
  2. What will the agent think? - only if there is neither an agent nor a ready-made model: subscription, your own server or GigaChat.
  3. How agents work — each task has its own branch and working copy; what the agent does himself and what he asks about.
  4. Appearance - theme, fonts and scale.
  5. Notifications, remote and integrations — when Pulse says that the agent is finished or is waiting for you, and tasks from GitHub and GitLab.

The master is shown until he is closed, and not “until the agent appears.” You can close at any step. Reopen - Settings → Help → “Setup Wizard”. After the wizard, the “What are we working on?” step opens.

Agent connection

Pulse doesn't bring a model with it: it connects agents that you already have installed. In addition to the wizard, the same thing is on two pages: Settings → Agents and Settings → Models (group “Agents and AI”). Details - in Agents and models.

Updates

Go to 0.31.10. The update signing key has been replaced: any version before 0.31.10 trusts the old key and will not accept the new release. Download installer 0.31.10 or later for your system once from Pulse website, close Pulse and install manually. The cards show the actual published versions: if there is no new build for your platform yet, a previous release is available. After manual installation, the client checks the next releases with a new key. Intel DMG 0.31.10 is ad-hoc application signed and is installed manually.

  • If enabled cloud (Settings → Cloud), Pulse itself checks the update server and shows a notification in the bottom line: “a version has been released...”. The update is downloaded and installed using the button.
  • Mandatory updates are marked separately: it is better to install them immediately, otherwise the old version may not understand the new data.

What Pulse checks and what it doesn't know

The update is the only place where Pulse itself takes a file from the network and offers to install it, so the response from the update server is checked as someone else’s data:

  • the file is taken only on the same server, that responded to the check, and according to the same protocol: a spoofed response cannot divert the download to someone else’s address;
  • filename must be package for this system (.dmg/.zip, .exe/.msi, .deb/.rpm/.AppImage) — script or arbitrary executable file will not be accepted by Pulse;
  • the server must call sha512; without it, the release is rejected before being downloaded;
  • version, platform, channel, file name, amount and size must have Ed25519-signature, which the client verifies with the release's built-in public key;
  • only version offered newer than installed — rollback is not performed by the update;
  • the amount is verified twice: after downloading and again at the moment you click “Install”. Hours pass between these two moments, and the file lies in the data folder - if it has been replaced, the installation will not start, the file will be deleted, and Pulse will tell you why;
  • downloaded won't start on its own: Installation starts only after your “Install”. On Windows, after this Pulse closes, and the installer installs the new version in the background, without windows, and opens it. If Pulse asks about running agents and you stay, the update will occur when you close Pulse. Only the copy supplied for you is silently updated; the "for all users" copy and ZIP receive the installer window.

The manifest signature confirms that the release is approved by the key owner and associates the file with the declared amount. She doesn't prove who collected this file, and does not replace the application signing certificate for the operating system. That's why Pulse doesn't replace itself without your click (and that's why it doesn't have an electron-updater): silently replacing an application with a file whose publisher has nothing to confirm is more dangerous than manual installation. On Windows, the installer window did not add anything to the check - the file downloaded by Pulse itself is not checked by SmartScreen, and the installation does not ask for rights for the user - therefore, after “Install” the installer goes without windows; checks of the amount and signature of the manifest are the same. What exactly will happen when you click “Install” is listed step by step in Settings → Cloud → Updates - before pressing, not after.

  • After installation, the new version itself removes downloaded packages that are not newer than itself (updates in the data folder), and on macOS it also extracts the image of the previous update. If the volume is still busy, cleaning will be repeated the next time it starts.
  • Without the cloud, update manually: download the latest file from the site and place it on top of the installed one. Data, tasks and keys remain in place.
  • The update server distinguishes between systems: the application requests a file specifically for its system and architecture combination. Extracting images after updating - macOS only.

Where is the data located?

  • macOS: ~/Library/Application Support/Pulse (for a build from source - .../pulse)
  • Windows: %APPDATA%\Pulse
  • Linux: ~/.config/Pulse

Same inside:

Path What
pulse-tasks.json, pulse-sessions.json tasks and sessions
transcripts/<sessionId>.jsonl full session recording: every turn, challenge, resolution
pulse-activity.json activity log (last 400 entries)
pulse-settings.json agents, folders, appearance, swarms, policies, MCP, profiles
secrets.json keys and tokens, encrypted via keychain, rights 0600
logs/pulse.log application log (secrets are masked)
memory/<name>-<hash>.md repository memory: results of problems and solutions
worktrees/<taskId> working copies of tasks
scratch/<taskId> tasks without a repository
exports/ export audit and saved bug reports

The data folder can be opened with the button: Settings → Help → Data Folder → In Finder.

Removal

Windows. “Settings → Applications → Pulse → Uninstall” (or right-click Pulse in Start → Uninstall). Uninstaller step by step:

  1. Asks whether to delete Pulse.
  2. If Pulse is open, it offers to close it; processes from the Pulse folder are terminated along with it: the terminal daemon and built-in codex.exe, claude.exe, rg.exe. CLI agents delivered via npm are not affected.
  3. Asks whether to delete data %APPDATA%\Pulse; the default answer is “No.” Working copies of tasks with uncommitted changes will be lost along with the data. If some of the files are busy (terminal or editor in the working copy), the uninstaller will tell you about this with a window with code PULSE-UNINSTALL-001.
  4. Removes files, shortcuts, Markdown's Open With option, and outline pulse://, if it leads to this copy.

No questions asked: "%LOCALAPPDATA%\Programs\pulse\Uninstall Pulse.exe" /S leaves data with --delete-app-data deletes them too. Items 3-4 in the list below also apply to Windows.

macOS.

  1. Drag Pulse from "Programs" to the trash.
  2. Delete data if it is no longer needed: ~/Library/Application Support/Pulse.
  3. Worktree tasks are located inside the data folder; If you changed the worktree root in “Settings → General”, delete it too.
  4. Branches pulse/<id> remain in your repositories - delete them normally git branch -Dif they are not needed.

Build from source

git clone https://github.com/NameLucky2205/pulse.git
cd pulse
npm install
npm run dev # hot boot window

If you are launching from another Electron process (for example, from an agent), remove the variable, otherwise Electron will start as a normal Node:

env -u ELECTRON_RUN_AS_NODE npm start

Build your DMG and publish it in Development.