Desktop app with Network Access
Enable Network Access on the machine running Cogpit. Put HTTPS in front of it, then connect from another device's browser using its network password.
The agent stays running. You can step away.
Open Cogpit from your phone, connect another machine, or run a headless server. Review progress and answer an agent without sitting at the computer doing the work.
Choose how you connect.
A headless Cogpit server
Run Cogpit on a dedicated machine without the desktop app. Your session history and agent processes stay on that host. The self-hosting guide covers setup and remote access.
More than one machine
Add a device with its Cogpit address and credentials. The device switcher shows one machine at a time and restores the view you left on each device.
Your phone's browser
Read conversations, review activity, and answer your agent from your phone. Connect to the machine that holds the session through its authenticated HTTPS address.
Remote browser access requires HTTPS. A server listening beyond loopback requires a network password of at least 16 characters. See the self-hosting guide for TLS proxies, authentication, and session expiry.
Know when you're needed.
Desktop notifications
Cogpit notifies you when an agent finishes or needs an answer, including sessions started in a terminal. Open a notification to return to the relevant session.
Optional phone push
Configure ntfy to receive push notifications while the desktop is unattended. Headless servers count as unattended. Notification links can take you to your configured Cogpit address.
Share a Claude Code session with a guest.
Create a passphrase-protected link for one live Claude Code session. The guest connects to that session over HTTPS. Manage active shares in Configuration → Network. Guest sharing is not available for Codex or Copilot CLI.
Keep your next session in view.