Skip to main content
Glama

Related Servers

Alternatives to session-manager

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude Code to launch and supervise multiple concurrent Claude Code sessions in tmux, sending them briefs, reading their progress, answering their prompts, and managing isolated git worktrees.
      20
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code to act as a project manager that delegates coding tasks to a pool of worker agents (Codex and OpenCode) defined as aliases in a YAML config, handling priority-based budget routing, parallelism with queues, resumable sessions, isolated git worktrees, and non-destructive merges. It returns token-cheap result reports with diffs and costs, plus Windows toast notifications and papercraft-style HTML round summaries.
      17
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Pools multiple Claude Code subscriptions on one machine so a single conversation keeps running after a usage limit is hit by continuing automatically on another account, and lets Claude hand heavy tasks to another account or to the Codex CLI with a chosen model and effort while returning the result to the current session.
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code or any MCP client to delegate hands-on coding work to OpenAI Codex over a persistent app-server process, keeping long-lived threads with follow-ups, async polling, approvals, steering, and interrupts. Supports native code review, resuming existing sessions, structured output, and parallel worktree-isolated tasks.
      10
      24 npm
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: start/send/stop/read/list sessions, report/read_reports, todo, wait_events, and get_usage are easy to separate. There is some overlap between set_session_name and update_session because both modify supervisor-side metadata, and stop_session's markAs state can be confused with update_session's state field, but descriptions mostly clarify these boundaries.

    Naming Consistency4/5

    All tool names use consistent snake_case, which is predictable and readable. Most follow a verb_noun pattern (list_sessions, read_session, start_session, send_message), but standalone names like report and todo are minor deviations from the pattern.

    Tool Count5/5

    The 12-tool surface is well scoped for a session supervisor managing conversations, reports, TODOs, usage, and event waiting. Each tool appears to earn its place without obvious redundancy.

    Completeness4/5

    The tool set covers the main lifecycle: start, list, read, message, stop, update, report, todo management, usage checks, and event waiting. Minor gaps remain around explicitly deleting or archiving sessions and separating some metadata operations, but agents can work around these through existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive