Codex Team Workbench
Related Servers
Alternatives to Codex Team Workbench
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents like Codex, Grok Build, and Antigravity to share persistent local memory, preferences, project context, tasks, and handoffs using Markdown and SQLite.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables task management with persistent SQLite storage, along with tools, resources, subscriptions, prompts, and completions over stdio or Streamable HTTP with per-user authentication.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve project briefings, reserve and track tasks, and record checkpoints, passages, messages, and durable context so another AI can resume work using local SQLite-backed project memory.10,856 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to persist and resume shared working state—tasks, progress, decisions, commands, tests, checkpoints, and handoffs—backed by SQLite while keeping Git authoritative for files and repository state.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and write persistent local memory during sessions, storing and semantically searching project decisions, preferences, error patterns, guidelines, and cross-project standards from SQLite stores on the user's machine. An optional companion server also exposes an autonomous task queue for executing queued work.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store, search, and manage persistent memories, todos, kanban boards, reminders, and progress trackers in a local SQLite database.1Apache 2.0
TDQS
Scored across 16 tools
Six tools (team_report_member, team_observe_runtime, team_record_execution, team_append_record, team_import_thread_page, team_bind_agent_activity) all revolve around relaying and recording observations of agents, differing only by which artifact is captured, which is a heavy cognitive load for selection. The long, caveat-laden descriptions do carve out boundaries (reported vs observed vs execution receipt vs thread page), but the distinctions require careful reading rather than being obvious from the names.
All tools share a consistent team_ prefix in snake_case with a mostly verb_noun structure (team_create_task, team_update_task, team_observe_runtime, team_read_records). Minor deviations are team_panel and team_snapshot, which are noun-only rather than verb-led, plus the slight verb variance between 'record' and 'report'.
At 16 tools this is at the upper edge of a well-scoped set, and the bulk of the surface is dedicated to provenance/observation plumbing rather than the core board operations. The count is defensible given the layered trust model, but several recording tools could plausibly be consolidated into a single parameterized record call.
Board lifecycle (create, bind, archive/restore, snapshot), task lifecycle (create, update with claim/release/complete/reopen/edit/reassign/soft delete), and rich observation/record coverage are all present. Gaps are minor and mostly intentional: no record update or deletion, no member removal, and no explicit way to close out or retire a recorded workflow group.