pleach
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLEACH_HOME | No | Override the directory where pleach stores its data. Defaults to ~/.pleach/. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pleach_logA | The Claude Code session branch graph for this project: an ASCII git-style graph plus one record per session (id, name, parent, live, subject, merges), newest first. Start here to see what branches exist. |
| pleach_showA | Full detail for one session: lineage (parent, branch point, children), transcript path, entry count, merges it took part in, and the command to resume it. |
| pleach_grepA | Full-text search across session transcripts (conversation text, not tool dumps). Answers 'which branch was the one where we worked out X?'. Returns matching sessions newest-first with snippets. |
| pleach_exportA | A session's conversation rendered as readable markdown (tool dumps elided). Local and free. Long transcripts are truncated at max_chars; prefer pleach_summary for a whole-branch digest. |
| pleach_summaryA | Summarize what a branch attempted, what worked, what failed, and what was decided. Cached per branch head; a cache miss makes model calls (small cost, works at any transcript size). |
| pleach_branchA | Fork a session into a new tracked branch (copies the transcript under a new id, exactly like |
| pleach_nameB | Label a session; labels show in the graph. |
| pleach_merge_planA | Dry-run a merge of two branches: branch point, merge-base method and confidence, and the exact prompt the merge agent would get. Dispatches nothing and writes nothing (summaries are computed, cached, small cost). Review this before calling pleach_merge. |
| pleach_mergeA | SIDE-EFFECTFUL: materializes a merge base and dispatches a background Claude agent to reconcile the two branches (read-only unless allow_writes). Use pleach_merge_plan first and confirm with the user before calling this. |
| pleach_statusB | What pleach is tracking for this project: session/fork counts, live sessions, observed vs inferred edges. |
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 10 tools
Each tool targets a distinct aspect of session branching: graph overview, session details, search, export, summary, forking, labeling, merge planning, merging, and tracking stats. There is no meaningful overlap between any two tools.
All tools share the consistent 'pleach_' prefix and snake_case, but the second part mixes verbs (show, grep, export, branch, name, merge) and nouns (log, summary, status, merge_plan). This is mostly consistent with minor deviations.
Ten tools is well-scoped for a session branching system, covering the full range of operations without redundancy or bloat. Each tool earns its place in the set.
The tool surface covers core operations: branch, merge (with planning), inspect (log, show, grep, export, summary), label, and status. A minor gap is no delete/archive operation for sessions, but this is likely intentional and does not block primary workflows.