---

name: simulabractl description: Use simulabractl when managing or debugging Simulabra processes. Start, stop, restart services, check their status, or tail their logs. allowed-tools: Bash

List with JSON output (for parsing)

bun run bin/simulabractl.js list --json

Start a service

bun run bin/simulabractl.js start

Stop a service

bun run bin/simulabractl.js stop

Force stop (SIGKILL after timeout)

bun run bin/simulabractl.js stop --force

Restart a service

bun run bin/simulabractl.js restart

Get the log file path

bun run bin/simulabractl.js logfile

Tail the logs in real-time

tail -f "$(bun run bin/simulabractl.js logfile )"

Copy</Commands>

<ExampleOutput>

bun run bin/simulabractl.js list SERVICE STATUS PID UPTIME agenda running 12345 5m32s

bun run bin/simulabractl.js list --json [ { "name": "agenda", "status": "running", "pid": 12345, "runnerPid": 12340, "uptime": 332000, "logFile": "/home/user/simulabra/core/logs/pm/agenda.log" } ]

bun run bin/simulabractl.js start agenda Started agenda (pid 12345)

bun run bin/simulabractl.js stop agenda Stopped agenda

Copy</ExampleOutput>

<ServiceStatuses>
- `stopped` - Service is not running
- `running` - Service is running normally
- `starting` - Service is in the process of starting
- `stale` - State file says running but process is dead (will be cleaned up on stop)
</ServiceStatuses>

<ExitCodes>
- 0: Success
- 2: Unknown service
- 3: Service not running (for stop command)
- 4: Start failed
- 5: Stop timeout
</ExitCodes>

<DebuggingTips>
1. **Service won't start**: Check the log file with `tail -f "$(bun run bin/simulabractl.js logfile <service>)"`
2. **Stale status**: Run `stop` to clean up, then `start` again
3. **Logs location**: `logs/pm/<service>.log`
4. **State files**: `tmp/pm/<service>.json`
</DebuggingTips>

<AvailableServices>
Services are defined in `misc/pm/services.js`. Currently available:
- `agenda` - Personal productivity system
</AvailableServices>