komnet
Related Servers
Alternatives to komnet
- AlicenseNot gradedqualityBmaintenanceMultiplayer coordination for AI coding agents: Claude Code, Codex CLI and Cursor share one room per repository. An agent claims a path glob before it edits and a conflicting claim is refused at claim time, so collisions are prevented rather than resolved at merge. Metadata only — source code and diffs never leave the machine.MIT
Related Servers
- AlicenseBqualityAmaintenanceA coordination layer for coding agents that provides memorable identities, inbox/outbox messaging, searchable message history, and file lease management to prevent conflicts. Uses Git for human-auditable artifacts and SQLite for fast queries, enabling multiple agents to collaborate across projects without stepping on each other.412,217MIT
- AlicenseAqualityAmaintenanceCoordination for parallel coding agents: TTL file claims stored in the git common dir (visible across all worktrees), enforcement hooks that block colliding edits, agent presence, handoff notes, and a git-committed lessons knowledge base with BM25 search. Single static Go binary — no server, no database.82MIT
- AlicenseAqualityAmaintenanceOne local memory every coding agent on your machine shares — Claude Code, Cursor, Claude Desktop, OpenCode. Answers from past sessions, commits, CLAUDE.md/AGENTS.md and ADRs with the exact source, and withholds work another agent has claimed so two agents don't rewrite the same thing.35,161 PyPI1MIT
- AlicenseAqualityAmaintenanceThe infrastructure for AI teams: a self-hosted server that gives a fleet of agents shared semantic memory, tasks, direct messages, and session handoff. Any agent that speaks HTTP participates: Claude Code, AutoGen, raw API scripts, anything.479MIT
- FlicenseNot gradedqualityAmaintenancePersistent memory for AI coding agents: local-first semantic search, dependency graphs, git history.1-
- AlicenseAqualityAmaintenanceConnects multiple AI coding agents on a team through a shared hub, giving each agent live teammate status, a versioned master prompt, a shared task board, questions and answers, and file claims so agents don't overwrite each other's work. Works across Claude Code, Codex, and Cursor while code itself continues to flow through git.101,771 npm5MIT
TDQS
Scored across 17 tools
Every tool has a clearly delineated purpose, with descriptions that explicitly contrast neighboring tools (e.g., send vs. ask vs. answer vs. decide). Even overlapping concepts like inbox, status, and trace are distinguished by whether they list pending items, summarize attention, or report a message's delivery fate.
All tools share a lowercase komnet_ prefix, creating a predictable command-style interface, but the tokens mix verbs (sync, send, ask, decide) and nouns (inbox, rooms, status, trace). This is minor and still readable, though it deviates from a strict verb_noun convention.
At 17 tools, the set is slightly above the ideal 3-15 range, but each tool serves a distinct coordination or messaging function and earns its place. The count reflects a genuinely broad domain rather than redundancy.
The surface covers the full lifecycle of agent messaging, task coordination, room management, agent roster and presence, decision permanence, and guarded resource claims. Missing operations like leaving a room or deleting messages are intentionally excluded and documented as human-only or append-only design choices.