Skip to main content

Module sessions

Module sessions 

Source
Expand description

omni-dev sessions — track the Claude Code sessions running across every terminal and VS Code window, via the daemon’s sessions service.

Four subcommands, split by role:

  • list is a read client (like omni-dev worktrees list): it asks the daemon’s sessions service for the live set and renders it.
  • hook is the feed sink: Claude Code runs it per hook event; it reads the hook JSON on stdin, maps it to an observe/end op, and fire-and-forgets it to the daemon socket. It must never block or fail a Claude turn — a missing daemon, a bad payload, or any other error is swallowed and it always exits 0.
  • install-hooks / uninstall-hooks idempotently merge (or remove) the hook block in ~/.claude/settings.json, preserving any hooks already there.

The register/heartbeat feed from the companion VS Code extension talks to the socket directly (like the worktrees companion), not through this CLI.

Structs§

HookCommand
The Claude Code hook sink: reads one hook event’s JSON on stdin and reports it to the daemon. Fire-and-forget and infallible-by-design.
InstallHooksCommand
Installs the sessions-tracker hooks into ~/.claude/settings.json.
ListCommand
Lists the live cross-window set of running Claude sessions.
SessionsCommand
Sessions: see the Claude Code sessions running across every terminal and VS Code window, kept live by the daemon.
UninstallHooksCommand
Removes the sessions-tracker hooks from ~/.claude/settings.json.

Enums§

SessionsSubcommands
Sessions subcommands.