dibs

io.github.polymatxPublished by GitHub account polymatxv0.1.1Updated Oct 24, 2026

Coordination for parallel coding agents: file claims, enforcement hooks, git-native lessons.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that coordinates parallel coding agents through file claims, enforcement hooks and git-native lessons.

What you can do
Coordinate multiple coding agents working in parallel by claiming files so they do not collide on the same work. Enforce those claims through hooks that block conflicting edits. Record and share lessons in a git-native form so agents can reuse what was learned. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when several coding agents or sessions edit the same repository at once and you want to avoid overlapping or conflicting changes, and when you want lessons from past runs kept alongside the code in git.
Requirements
Runs as a local process on the user's machine over stdio, distributed as a container image from ghcr.io. A container runtime is needed to run it. Desktop only; no authentication, environment variables or headers are declared.
Before you install
It enforces claims through hooks that can block or alter agent edits, so misconfiguration may interrupt normal editing. It writes coordination state and lessons into the repository, which can affect version control history. The manifest lists no tools, so review what it actually does before relying on it.

Installation

In SourceWeft

  1. Open dibs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.