Quilt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_sessionA | Register an actor and start a session in this repo, pinning this server to that identity. Optional: if several agents share one server, skip this and pass |
| get_statusA | Show who owns which working-tree changes, plus caught collisions and active claims. Call before editing and before committing. |
| get_my_changesA | List the changes YOU own in the working tree: the files and hunks attributed to your actor id, with per-file added/removed line counts. The 'what have I done so far' view, scoped to just you. Review your own work with it before committing — use get_status for who-owns-what across all actors, or preview_mine for the exact patch commit_mine would produce. |
| get_conflictsA | Show overlapping/shared changes and collisions that were caught. |
| preview_mineA | Show the exact patch commit_mine would create right now: only your owned hunks as a unified diff, plus the files, whole-file additions, and added/removed line totals. A dry run, nothing is written. Review it before commit_mine to confirm you are committing your lines and nothing else. |
| commit_mineA | Commit ONLY your owned hunks as an ordinary git commit, leaving every other actor's changes untouched in the working tree. This is how each agent lands its own work in a shared checkout without sweeping up anyone else's. The committed files' claims auto-release, so no separate release call is needed. Preview it first with preview_mine. |
| claimA | Reserve files BEFORE you edit them — a claim placed before editing is also what BINDS your external edits to your actor id, so claim whole files first as the default. Use a bare path for a whole file, a trailing slash for a whole directory (e.g. convex/_generated/ — right for codegen output), or |
| releaseA | Release your claims on the given paths. Omit |
| escalateA | Flag a collision you CANNOT reconcile (e.g. two opposed intents on the same line) for a human. Use this instead of forcing a change through when a denied claim's holderIntent conflicts with yours. It shows up under 'Needs you' until resolved. |
| resolveA | Mark a collision as sewn/handled after you reconciled it — closes its 'Needs you' flag and records the audit trail. Use after you've merged or adapted so the work accounts for both intents. |
| quilt_editA | Edit a file through Quilt instead of your raw editor. Replaces the unique |
| quilt_writeA | Create or overwrite a whole file through Quilt instead of your raw editor, recording YOU as the author of its contents at write time, so attribution is exact even when several agents share this checkout, with no claims or reconcile guesswork. Use this for new files; use quilt_edit to change part of an existing one. Pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have distinct roles: start_session, claim/release, preview_mine/commit_mine, and quilt_edit/quilt_write are clear. However, get_status, get_my_changes, and get_conflicts overlap somewhat since get_status already covers ownership and collisions, which could cause misselection between the overview and specialized views.
The names are consistently snake_case and mostly verb-first, with clear pairs like claim/release and escalate/resolve. Minor deviations exist: bare imperative verbs sit alongside get_* noun-object names, and quilt_edit/quilt_write use a different prefix pattern, but the naming remains predictable overall.
Twelve tools is well-scoped for the multi-agent collaboration domain. Each tool maps to a distinct workflow step—session setup, inspection, claiming, editing, committing, and conflict resolution—without obvious bloat.
The set covers the full lifecycle: start a session, inspect ownership, claim files, edit/write, preview, commit, resolve conflicts, and escalate. Minor gaps like no explicit revert/abandon-changes tool exist, but agents can work around them with release and raw git operations.