Skip to main content
If you close the terminal, the connector stops and your AI stops hearing you. To keep it running, let your computer start it for you. This is optional, and zapbip never installs it for you: you create the file yourself. After a restart or a lost connection, the connector reconnects and picks up every message that was not answered. The file holds your connection link, which works like a password. Give it permission 600 so only your user can read it, and never share it or commit it. Replace <path to npx> with the result of which npx, <your folder> with the folder your AI works in, and <host> and <secret> with the parts of your connection link. Use codex instead of claude-code if that is your AI.

​
macOS (launchd)

Create the file with the right permission first, then fill it:
PATH must include the folder where claude or codex is installed. Start it, and stop it later:

​
Linux (systemd)

Keep the link in its own file with permission 600:
Put one line in ~/.config/zapbip/connector.env:
Create ~/.config/systemd/user/zapbip-connector.service:
Start it, and make it run even when you are not logged in:
Read its lines with journalctl --user -u zapbip-connector. They carry no message text and no link. If the link is revoked, the connector exits with an error and the service keeps restarting it. Stop the service, put the new link in the file and start it again.