If something went wrong

A quick way to help yourself and us: Settings → Help → Log and error report. There you can see where the log is, you can look at its tail, describe what happened, and send a report to the developers. The report includes the version, environment and tail of the log; keys and tokens are masked.

Keychain asks for password every time

In the keychain entry Pulse Safe Storage — encryption key. The API keys themselves, GitHub/GitLab tokens and cloud session are in secrets.json in the application data folder (where is she). Do not delete the entry from the link and do not open it to all applications: without this key it is already recorded secrets.json cannot be deciphered.

"Always allow" macOS remembers for the app's signature, not the Pulse name or version number. Consent does not transfer to another signature. Regular build from source (npm run pack) is signed with the “Pulse Dev” certificate if it is in the bundle, otherwise ad-hoc - and ad-hoc has its own code hash for each assembly. The released DMG may be signed with a Developer ID; this is not the same certificate as "Pulse Dev", and the certificate is not visible by version number. The same signature between runs preserves agreement. The code does not promise “once forever”, nor that the request will come exactly once after each update: a new assembly with the same signature may not ask again, an assembly with a different signature will ask as a new application.

If the request is still made on each launch of one installed copy, the signature by version number is not visible. Check the path and access list, not the key:

  1. Launch the application from Programs, not from the mounted DMG.
  2. In Keychain Access, open Pulse Safe Storage → “Access” and make sure that this Pulse is in the list. Do not delete the entry and do not enable access for all applications.
  3. Sign your build from sources with one certificate: once scripts/make-signing-cert.sh. This does not apply to DMG that has already been released.

Two Pulse in Launchpad

After building from sources, an unpacked copy appears next to the installed application dist/mac-arm64/Pulse.app. The packaging script hides it automatically; if a copy remains, delete the folder dist/mac-arm64.

The window opened empty

Happens when the interface loading fails. Pulse shows a loading screen and after a few seconds prompts you to “Restart window”; When the process crashes, it reboots itself. If the window remains empty, close and open the application; the data will not be affected.

"git not found"

Pulse makes everything about the repository real git. If it is not on the machine, any operation - create a task, show changes, make a commit - will report this directly and tell you what to install:

System What to do
Windows Install Git for Windows from the page https://git-scm.com/download/win and start Pulse again. By default, git is not included in any distribution.
macOS xcode-select --install in Terminal - git comes with Xcode command line tools.
Ubuntu, Debian sudo apt install git; in Fedora - sudo dnf install git.

Git is installed, but Pulse doesn’t see it, which means it’s not in PATH (portable installation, non-standard prefix, or Windows Installer did not add it to the variable). Specify the full path of the environment variable PULSE_GIT_PATH:

# Windows, PowerShell: for the current account, once
[Environment]::SetEnvironmentVariable('PULSE_GIT_PATH', 'C:\PortableGit\cmd\git.exe', 'User')
# macOS and Linux: in ~/.zshrc or ~/.bashrc
export PULSE_GIT_PATH=/opt/git/bin/git

After this, the application needs to be started again - it receives environment variables at startup.

You can put your own git into the assembly, then the system one will not be needed at all: see. "Where does git come from".

Agent doesn't connect

  • "not found" - there is no binary in PATH. Specify the path manually in the agent card or install the CLI.
  • "login required" - click “Login”: Pulse will open Terminal with the desired command (claude auth login, codex login, kimi login, opencode auth login).
  • Button "Check" in the header of the list of agents, double-checks everyone.

The agent does not access the network behind the corporate proxy

The Pulse window accesses the network via Chromium and sees the system proxy itself. Agents are separate programs (Claude Code, Codex, Kimi, OpenCode), and an application launched from the Dock or Start menu does not pass your shell variables to them. Hence errors of the form ECONNREFUSED, ETIMEDOUT or self-signed certificate in certificate chain at the agent's first request.

Settings → General → “Network for agents”:

  • Proxy — http://server:port or http://login:password@server:port. Sent to agents and teams in their terminal as HTTPS_PROXY/HTTP_PROXY (and lowercase). The password is stored in the settings in clear text, as in the variable itself; The address appears in the log and on the screen with asterisks instead of a password. SOCKS is not accepted: most CLIs have it through HTTPS_PROXY don't understand.
  • No proxy - exceptions separated by commas; localhost, 127.0.0.1 and ::1 are always added so that the local model and gateway do not go to the proxy.
  • System proxy - if yours is not specified, Pulse asks Chromium (session.resolveProxy for https://api.anthropic.com/) and sends the answer. The PAC file has the right to assign different proxies to different addresses: if your agent provider has a different proxy, set it explicitly. The proxy with which Pulse itself is launched (HTTPS_PROXY in its environment) is not rewritten: the generated programs inherit it anyway.
  • Root certificate (PEM) — path to the file; transmitted as NODE_EXTRA_CA_CERTS. This is a Node.js variable: it is read by Claude Code and the ACP adapters that Pulse runs on its Node. Whether Codex, Kimi and OpenCode themselves read it has not been verified. A file that does not exist or that does not look like PEM is not transferred, and the card says so in words.

Affects agents and terminals launched after the change: a live process has an environment set at startup. Terminal tabs that you open yourself are not proxyed - your shell has its own profile. A built-in agent with a local model accesses the network via Chromium and is seen by the system proxy; GigaChat runs as its own client (the NCA chain of the Ministry of Digital Development), and the proxy from these settings is not transferred to it. The MCP servers that Pulse launches for the built-in agent are also not yet sent a proxy.

Codex: "not found" or new model not available

  • There is no need to install a CLI: it is built into Pulse, the card shows the “built-in CLI” and the version. Login is required - the “Login” button (ChatGPT account) or the OpenAI API key in the same card.
  • The required model is not in the list - enter its id in the “Model manually” field (for example gpt-6-astra). If the account is not yet allowed to access it, the request will return an access error: this is a limitation of OpenAI, not Pulse.

Local model: “server not responding” or “no models available”

Click "Check" in the card - Pulse will tell you what’s wrong:

What does it show What to do
the server is not responding check the address and that the server is running (ollama serve, Local Server in LM Studio); if the server is behind a VPN, the tunnel is up
requires a key specify the server API key (LiteLLM, vLLM for proxy)
no models upload the model on the server (ollama pull qwen2.5-coder)
tools: no the model does not know how to function calling - take qwen2.5-coder, qwen3, llama3.1, devstral, gpt-oss

GigaChat

Symptom Reason and solution
«scope from db not fully includes consumed scope» the key was issued for a different access type. Pulse selects the scope itself; if it doesn’t help, check if the key is the one from the account
402 Payment Required the account has no tokens for selected model. Not every model may be included in the tariff: select another one in the “Model” chip or top up the package in your personal account
Replies with text but doesn't use tools update Pulse to 0.22.7 or later: it fixes three incompatibilities in the function call format
“The root certificate of the NCA Mintsifra was not found” in the assembly from sources - update; the certificate is in resources/certs

Swarm stands still

  • Look at the “Swarm” column: who has a task “in progress”, who has a report.
  • A task without a report for more than 20 minutes is automatically interrupted and repeated.
  • The participant could fall - Pulse will repeat the task twice, then inform the architect.
  • If the architect did not distribute tasks, he most likely did not design the block pulse-assign — write to him in the chat: “distribute tasks using the pulse-assign block.”

The update doesn't arrive

Check Settings → Cloud: whether the cloud is turned on and whether the address is correct. The manual way is to download the DMG from Releases. The update is installed on top, the data is saved.

The task broke the repository

Each task works in its own worktree on a separate branch, the main clone is not touched. Delete the issue (the worktree and the branch will go with it) or rollback the branch using the usual git commands. Section Worktree (⌘ 3) shows all working copies and allows you to remove orphaned ones.

Where else to look

  • Activity (⌘ 4) - what happened: turns, errors, resolutions, maintenance. There is a search, filters by type and task, periods.
  • Log — logs/pulse.log in the data folder: complete technical picture.
  • Task audit — a button in the task header: who launched what and what permissions were issued.