Skip to main content
Glama
Cohexa-ai

Agent Coherence — Stale Write Guard (FS)

Official
by Cohexa-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Agent Coherence — Stale Write Guard (FS)

No user-submitted related servers found.

    Related Servers

    • agentclaim

      volkangunay
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to safely collaborate in the same git working tree by managing file ownership, merging writes, and preventing snapshot races.
      3 npm
      2
      MIT

    • scoped

      OrenSegal
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coordination of concurrent Claude Code agent sessions by providing file claiming (claim/release/check) and automatic PreToolUse enforcement to block edits on files owned by other sessions.
      7 npm
      MIT

    • dibs

      polymatx
      A
      license
      A
      quality
      A
      maintenance
      Coordination 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.
      8
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a clear role in the workflow, but swg_write and swg_write_cas are both write entry points and could be misselected by an agent. The detailed descriptions distinguish normal write from CAS merge write, while the other tools are cleanly separated.

    Naming Consistency4/5

    All tools use the swg_ prefix and lowercase snake_case, so the set is immediately recognizable and predictable. However, swg_status and swg_gate are noun-style command names rather than verb_noun action names, a minor deviation from the otherwise verb-oriented pattern.

    Tool Count5/5

    Six tools is well-scoped for a stale-write guard: read, write, CAS write, reacquire, gate, and status each serve a distinct purpose. No tool feels redundant, and the count matches the focused domain.

    Completeness4/5

    The core stale-write lifecycle is covered end-to-end: read, write, recover, verify before external action, and inspect status. Minor gaps remain around explicit path registration and the referenced reconcile step, which is not surfaced as a named tool, but agents can work around these with existing tools.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources