Real Time Session Discovery And Auto Refresh With File System Watching

via “real-time session discovery and auto-refresh with file system watching”

The missing DevTools for Claude Code — inspect session logs, tool calls, token usage, subagents, and context window in a visual UI. Free, open source.

Unique: Combines native file system watchers (local) with SFTP polling (remote) and implements debouncing/throttling at the parsing layer to prevent UI thrashing, using incremental JSONL parsing to update only changed turns rather than re-parsing entire sessions

vs others: Provides live session visibility without manual refresh, unlike static log viewers that require explicit reload, while avoiding the resource overhead of naive file watching by implementing intelligent debouncing and incremental parsing

via “persistent session recovery and state restoration”

Manage multiple Claude Code, OpenCode agents from either TUI or Web for easy access on mobile. Also supports Mistral Vibe, Codex CLI, Gemini CLI, Pi.dev, Copilot CLI, Factory Droid Coding. Uses tmux and git worktrees.

Unique: Implements profile-scoped session persistence (src/session/storage.rs) with automatic metadata serialization and recovery on startup. Maintains a session index for fast lookup and supports orphaned session cleanup, enabling seamless session recovery across system restarts.

vs others: More reliable than tmux's default session persistence (which is lost on server restart) and more lightweight than full database-backed session management, with explicit profile isolation.

via “real-time filesystem monitoring with automatic dependency graph updates”

** - Analyzes your codebase identifying important files based on dependency relationships. Generates diagrams and importance scores per file, helping AI assistants understand the codebase. Automatically parses popular programming languages, Python, Lua, C, C++, Rust, Zig.

Unique: Integrates filesystem monitoring directly into the MCP server lifecycle, automatically updating the dependency graph on file system events rather than requiring explicit refresh calls. Uses incremental re-analysis (only affected files) rather than full re-scans.

vs others: More responsive than polling-based approaches but less precise than AST-aware change detection; suitable for AI assistants that need current codebase state without manual refresh