Everyday Controls

You control PRIMA Bot from Terminal on the Mac. Paste a command from the table below and press Return.

The Commands

Task	Command
Check that PRIMA Bot is running	screen -ls
Read the log	tail ~/Library/Logs/prima-bot-remote-server/launchd.log
Follow the log as it grows	tail -f ~/Library/Logs/prima-bot-remote-server/launchd.log
Check the service	launchctl print gui/$(id -u)/com.$(id -un).prima-bot-remote-server
Restart PRIMA Bot	launchctl kickstart -k gui/$(id -u)/com.$(id -un).prima-bot-remote-server
Stop PRIMA Bot until the next login	launchctl bootout gui/$(id -u)/com.$(id -un).prima-bot-remote-server
Start it again after stopping	launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.$(id -un).prima-bot-remote-server.plist

A line that contains prima-bot in the output of screen -ls means PRIMA Bot is running.

Watching PRIMA Bot Work

PRIMA Bot runs in a hidden screen window, which shows its connection status and the tools Claude uses. Open it with the command below.

screen -r prima-bot

To leave it running, press Control and A together, let go, then press D.

Caution

Pressing Control and C inside that window stops PRIMA Bot. macOS starts it again after 60 seconds, and any session in progress ends.

What the Log Records

The launcher writes a line each time it starts, with the folder, permission mode and spawn mode it uses. It also writes a line when it cannot start, such as a missing workspace folder or a missing Claude Code program. Troubleshooting lists those messages and what to do about each one.

Running Only One Server

The launcher never starts a second server. If a screen window named prima-bot already exists, for example one you started by hand, the launcher waits and writes a line to the log every minute. It takes over when that window closes.