Inspecting remote sessions over SSH
claude-devtools reads ~/.ssh/config for host aliases, opens SFTP to remote ~/.claude/, and isolates each host's state. Useful for CI machines, cloud instances, and team servers.
claude-devtools can inspect Claude Code sessions on any remote machine. It reads your ~/.ssh/config for host aliases, supports agent forwarding and key auth, and opens an SFTP channel to stream session logs from the remote ~/.claude/ directory.
Each SSH host gets its own isolated context. Switching between local and remote is instant — the app snapshots your state before the switch and restores it when you return.
This is useful for inspecting sessions that ran on:
- CI machines — debug a Claude Code job that failed in CI without SSH'ing in by hand
- Cloud instances — production-side automation runs that produced unexpected results
- Team servers — shared dev boxes where multiple people invoke Claude Code
If you'd rather avoid SFTP entirely, the standalone Docker build runs a web UI on the remote machine over HTTP, served on port 3456 with zero outbound network calls.
Related
Setting up notification triggers
System notifications for .env access, tool errors, and high token usage. Plus custom regex triggers on any field with per-repo scoping — no Claude Code hooks required.
Where are Claude Code logs stored?
Claude Code writes JSONL session logs to ~/.claude/ — the hidden folder inside your home directory. The path is the same on macOS and Linux; on Windows it's %USERPROFILE%\.claude\.