After installation, run through these checks to verify everything is working. The commands below work the same on macOS and Linux; the paths shown in the turen-watchdog status output differ (/Library/... on macOS, /etc/... and /var/lib/turen on Linux).
1. Agent Is Running
You should see the agent reporting as registered and running.
Registered: true appears once the machine has been registered. If you did a keyless install on Linux or macOS and haven’t signed in yet, you’ll see Registered: false until you launch the Turen desktop app and sign in (it registers the machine over local IPC). If you registered with a key, the agent registers on its own the first time the service runs. Either way, the end state is the same.
2. 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 OS version and architecture
3. Claude Code Works
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
4. 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. 
