Skip to main content
Glama

Related Servers

Alternatives to Selvedge

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Local-first memory layer for AI coding agents — captures issues, attempts, fixes, and decisions, and warns at git commit before you repeat a mistake.
      19
      978 PyPI
      877
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a memory layer for AI coding agents with Git-powered version control, enabling automatic tracking of prompts, context, and code diffs.
      194
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to maintain persistent working memory across sessions by capturing decisions, invariants, lessons, and bugs, retrieving them within token budgets, and auditing proposed diffs against active constraints. It also supports duplicate detection, supersession and invalidation lineage, and local SQLite-backed storage with optional PostgreSQL.
      5
      83
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables intent-driven version control on top of Git, turning commits into auditable intents with prompts, AST deltas, and signatures, and providing tools for blame, context, replay, and verification.
      4
      MIT

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct scopes: log_change is the only writer; diff is entity-scoped history, history is cross-entity, changeset groups by id, and search is full-text. The main ambiguity is diff vs. blame — blame returns only the newest event and adds a status field, but it is effectively the first row of diff, so an agent could reasonably pick either for 'what changed most recently.'

    Naming Consistency3/5

    The naming mixes three conventions: git-style single-word verbs (diff, blame, search), bare nouns (history, changeset), and descriptive snake_case phrases (log_change, prior_attempts, stale_decisions). The styles are individually readable and the git-inspired cluster ties the read tools together, but there is no single predictable verb_noun pattern across the set.

    Tool Count5/5

    Eight tools is well within the ideal 3-15 range and each tool earns its place in the change-logging domain: one writer, four retrieval views (per-entity, latest, global, changeset-grouped), one search, one pre-edit decision helper, and one maintenance/review tool. The count feels tightly scoped with no obvious redundancy or bloat.

    Completeness5/5

    The surface fully covers the domain's lifecycle: log_change handles all event types (including rename, reject, revert, and supersede), and the read side provides entity-scoped history, latest state, cross-entity filters, changeset reconstruction, full-text search, pre-edit attempt lookup, and stale-decision review. The append-only design intentionally omits update/delete, which the descriptions explicitly justify, so there are no real dead ends for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data