Network Access
Your agents don't care where you watch them from — or how many people are watching. Enable network access and monitor sessions from your phone, your iPad, or a second machine. Share the URL with teammates and everyone sees the same live sessions simultaneously.
Try it yourself
Walk through the setup flow — toggle network access on the left, set a password, then use the same password to sign in from the phone mockup on the right.
Network Access
Allow other devices to connect
Network access disabled
Enable it in settings to connect from this device
How it works
Enable in settings
Open Cogpit's settings and flip the Network Access toggle.
Set a password (minimum 12 characters) and save. Cogpit restarts its embedded server to bind on
0.0.0.0:19384 instead of localhost.
Share the connection URL
The header bar shows your LAN IP and port — something like
http://192.168.1.100:19384.
Open it on your own devices or send it to teammates on the same network. Everyone signs in with the same password and sees the same live sessions simultaneously.
Sign in and collaborate
Enter the password on the login screen — each viewer gets a session token valid for 24 hours. The full Cogpit dashboard loads with live SSE streaming, tool call inspection, branching, and everything else. Multiple people can watch and interact with the same agent sessions at the same time.
Not just multi-device — multi-person
Most monitoring tools are single-viewer. Cogpit's network access is designed for multiple simultaneous connections. Everyone who signs in sees the same live sessions with the same SSE streams, the same tool calls, the same diffs — in real time.
This turns agent work into a collaborative experience. A senior dev reviews output from their machine while a teammate guides the session from theirs. A team lead checks long-running Claude or Codex work from their phone. No screen sharing — just a URL and a password.
Security first
Exposing a web server on your LAN is a responsibility. Cogpit treats it seriously with multiple layers of protection.
Password authentication
Every remote connection requires a password. Local requests (127.0.0.1) bypass auth for zero-friction desktop use.
Rate limiting
5 login attempts per minute per IP. Brute-force attacks are stopped before they start — with timing-safe password comparison.
Session tokens
Passwords are hashed with salted SHA-256. After login, you get a session token (24h TTL) — the raw password is never stored or transmitted again.
Restricted operations
Dangerous endpoints (kill-process, undo, kill-port) are scoped to tracked PIDs, home directory paths, and unprivileged ports only. Security headers and body size limits are enforced on all requests.
Use cases
Team collaboration on agent work
Multiple people connect to the same Cogpit instance and see Claude Code and Codex sessions in real time. Review edits from one machine while a teammate guides the work from another.
Monitor from your phone
Kick off a long agent task, then grab your phone and watch it work from anywhere. The full live dashboard, prompts, and approvals stay within reach.
Multi-machine setup
Run agents on your desktop and monitor from your laptop in the same room. No tunnels, no cloud — just your local network.