Skip to main content
A session is a Claude Code instance running on your machine, connected to the Anyware cloud for remote monitoring and control.

​
What is a Session?

When you run anyware, Anyware:
  1. Creates a session on the server
  2. Connects to the WebSocket for real-time streaming
  3. Spawns Claude Code locally with hooks to capture events
  4. Streams all output to the web dashboard
The session continues until you exit Claude Code or press Ctrl+C.

​
Session Lifecycle

Sessions have two states: active and ended.

​
Active

  • Claude Code is running on your machine
  • Output streams to the web dashboard
  • You can switch between local and remote modes
  • Others can view (and control, if permitted) from the web

​
Ended

  • Claude Code has exited
  • Session is marked as ended on the server
  • No reconnection possible (start a new session)

​
Local vs Remote Mode

Within an active session, you can switch between two modes:
ModeInput SourceUse Case
LocalYour terminalTyping directly, full keyboard access
RemoteWeb dashboardControlling from phone, monitoring
See Local vs Remote Mode for details on mode switching.

​
Session Events

Everything that happens in your Claude Code session is captured and streamed:
  • Output: All terminal output (stdout/stderr)
  • Tool calls: File edits, bash commands, etc.
  • Permissions: When Claude requests permission
  • Mode changes: Switches between local and remote
The web dashboard shows these events in real-time.

​
Multiple Sessions

Run multiple sessions in parallel by opening multiple terminal windows: 
# Terminal 1
cd project-a
anyware

# Terminal 2
cd project-b
anyware
Each session appears separately in the web dashboard.

​
Session Security

  • Sessions are tied to your user account
  • Only you can view your sessions in the dashboard
  • WebSocket connections are authenticated
  • All traffic uses HTTPS/WSS

​
See Also