Skip to main content
After installation, run through these checks to verify everything is working.

​
1. Agent Is Running

> sudo turen-watchdog status

turen-watchdog status:

Paths:
  Data directory: /Library/Application Support/Turen
  State file:     /Library/Application Support/Turen/state.json
  Log directory:  /Library/Logs/Turen
  Socket:         /var/run/turen/watchdog.sock
  PID file:       /Library/Application Support/Turen/watchdog.pid
  Plist:          /Library/LaunchDaemons/dev.turen.watchdog.plist

Launchd:
  Label:   dev.turen.watchdog
  Loaded:  true
  Running: true
  PID:     25668

Daemon (via IPC):
  Client ID:      4a0105xxxxxxxxxx
  Registered:     true
  Policy version: 
  Last check-in:  2026-02-18 10:17:37.929257 -0600 CST
  Uptime:         36s
  Proxy:          running (PID 25683)
You should see the agent reporting as registered and running.

​
2. Proxy Is Reachable

curl -s http://127.0.0.1:7778/health
Expected response: 
{"rules":0,"status":"ok","uptime":"13m16.18142825s"}

​
3. Agent Appears in Dashboard

Open the Turen dashboard and navigate to Agents. Your machine should appear with:
  • A recent Last Checkin timestamp
  • Status showing Active
  • Your macOS version and architecture

​
4. Claude Code Works Through the Proxy

claude "Say hello"
Claude Code should respond normally. After the session ends, check:
  • Monitor > Replay — your session should appear within a few minutes
  • Dashboard > LLM — you should see the request counted in analytics

​
5. Rules Are Active

Start a Claude Code session and ask it to do something that Turen should block (e.g., a destructive command). Turen should intercept it before execution. Check the dashboard under Monitor > Events to see any blocked events logged.

​
Troubleshooting

If any of these checks fail, see the Common Issues guide.