shiftover
Related Servers
Alternatives to shiftover
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenancePools multiple Claude Code and Codex subscriptions and routes each coding task to the account with the most available quota, handling cooldowns and failover automatically.MIT
- AlicenseBqualityBmaintenanceEnables 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.17MIT
- AlicenseAqualityAmaintenanceEnables Claude Code and Codex to turn an ordinary conversation into an orchestrator that spawns, names, monitors, and revives separate work sessions, aggregates their questions for a single confirmation, and throttles parallelism based on memory and usage limits. Reports results back as a summary table without needing any extra app, daemon, or tmux.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code and Cursor to delegate tasks to each other, spreading workload across both AI coding subscriptions.42 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables two-way collaboration between Claude Code and the Codex CLI: Claude can hand off plans for execution or adversarial review, while the working agent can block to ask Claude questions, report progress or findings, and receive mid-run corrections. Supports multiple named, resumable sessions per project with configurable model, effort, and sandbox settings.20 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables users to delegate coding tasks in a chosen project to the official Codex and Claude CLI agents from within an existing chat, then convene a council of configured models to gather independent opinions and review the resulting files and test runs. It also manages multi-provider API connections, model catalogs, and per-task token, time, and cost limits.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: accounts is read-only account listing, delegate starts a task, and monitor checks or cancels jobs. The boundary between delegate and monitor is clear because monitor explicitly handles status, results, waiting, and cancellation.
The names are readable but do not follow a single convention: accounts is a plural noun, while delegate and monitor are verbs. With only three tools this is not confusing, but the naming pattern is mixed.
Three tools is well-scoped for this server: one to inspect available accounts, one to run work, and one to track or cancel delegated jobs. Each tool earns its place without unnecessary surface area.
The surface covers the core lifecycle: list accounts, delegate a task, monitor results, wait, and cancel. Minor gaps exist around account management or more explicit job inspection, but the primary workflow is complete.