Error codes · Launch
PULSE-START-005 The system did not provide the encryption key
What does this mean
At startup, Pulse asked the system for the key that encrypts your API keys and terminal command history, and did not receive it. On a Mac it looks like this: macOS shows the “Pulse wants to use sensitive information in Pulse Safe Storage in your Keychain” window with a password field. If you close the window or click “Deny”, Pulse remains without a key.
Pulse works: tasks, agents and terminals are in place. But API keys in this launch are not read or saved (an attempt to save the key in Settings will show the same card), the command history is not read, and new commands are added to the history without encryption, with a mark. API keys are saved in clear text only if there is no key file yet. Pulse says this on the card rather than being silent.
Why does this happen
The encryption key is in the macOS keychain with the entry “Pulse Safe Storage”, and the keychain remembers which application created it. If the record was created by a Pulse build with a different signature—for example, a developer build or an early release—and Pulse is now running, signed with an Apple developer certificate, it's a different app for the link. macOS asks for your password every time you start it until you allow access permanently.
Before this version, Pulse accessed the link from two places separately, and the password window was shown twice in a row. Now there is only one request, at startup, there is only one window.
On Linux, there may not be a keyring at all (you need gnome-keyring or kwallet) - this is a different situation: there is no card, and Pulse writes about storage without encryption in the log and in the history statistics.
What to do
- In the macOS window, enter your account password and click “Always Allow” - once. From the next launch the window will not appear, the saved keys and history are read again.
- If the window has already been closed, restart Pulse, it will appear again.
- If you want to start with a clean entry: open Keychain Access (Launchpad → Other → Keychain Access), find Pulse Safe Storage, delete the entry, and restart Pulse. It will create the entry again; API keys saved earlier can no longer be read - enter them in Settings again, the command history up to this point will remain unreadable.
When to write to support
Write to us if the password window appears on every startup after “Always Allow”, or if the card is shown, but the macOS window was not there. Click “Send report” in the error card - a report form will open, where the code and details have already been entered: what the system responded to the keychain test. Secrets are not included in the report. Add which Pulse build was installed earlier and click “View and Submit.”