Leetcoder

Leetcoder lets a live Hermes agent hand a bounded job to a native oh-my-pi session without surrendering control of the conversation. Each delegation gets an isolated git worktree, its own persistent OMP root session, a visible title, live steering, durable follow-ups, native Advisor review, an electable OMP task/hub swarm, and a mandatory Librarian handoff.

Nothing starts on the first tool call. Hermes receives the proposed scope and every active Leetcoder title, checks for duplicate work itself, and confirms on the second call. This is agent lifecycle control, not a human permission prompt.

flowchart LR
  H["Hermes conversation"] -->|"delegate proposal"| M["Leetcoder MCP"]
  M -->|"active titles + confirmation token"| H
  H -->|"agent confirms no duplicate"| G["Leetcoder gateway"]
  G --> W["isolated git worktree"]
  G --> O["persistent OMP RPC root"]
  O --> A["native read-only Advisor"]
  O --> F["Firecrawl / Camofox / Retrieval / Codebase Memory"]
  O -->|"elects bounded delegation"| S["OMP task + hub"]
  S --> C["isolated native subagents"]
  C --> R["agent:// artifacts + history:// transcripts"]
  O -->|"completion claim"| V["fresh read-only OMP auditor"]
  V -->|"incomplete"| O
  V -->|"complete + clean + aligned"| FCT["accepted-fact ledger"]
  FCT -->|"mandatory memory_add"| L["Librarian OKF handoff"]

Hermes elects whether a bounded assignment deserves Leetcoder. The persistent OMP root then elects whether to work directly or use native subagents. OMP owns child concurrency, isolation, lifecycle, revival, and merging; Leetcoder owns the cross-harness root, durable control contract, outer draft, recovery, and final knowledge handoff.

What it owns

• two-stage, one-use agent confirmation before a task begins, with an exact duplicate check at confirmation time;

• up to three concurrent root workers by default, each continuously reviewed by OMP's native Advisor; three worker/Advisor pairs plus Hermes and Librarian fit the configured eight-sequence local model ceiling;

• native OMP protocol v2 root sessions, steering, follow-ups, and resumption;

• OMP-native task batching, bounded concurrency, isolated child edits, and hub reuse without exposing another Hermes management surface;

• one git branch and worktree per delegation, preserved after completion;

• SQLite root/child lifecycle, event history, transcript offsets, and compact transcript excerpts under ~/.local/share/leetcoder;

• nested subagent status trees with live intent/tool activity plus durable agent:// and history:// references after Hermes compaction;

• automatic recovery of interrupted turns after a service restart;

• a bounded execute/audit/repair loop at completion milestones, using a fresh MCP-free, skill-free OMP auditor and a fail-closed typed verdict;

• a durable accepted-fact ledger: acting-agent claims remain provisional until the auditor reports complete, clean, and aligned against the original contract and unchanged worktree fingerprint;

• graceful and force-close semantics with truthful handoff status;

• a required mcp__librarian_memory_add OKF handoff after every completed implementation or follow-up turn.

Leetcoder does not parse a TUI, call an OpenAI-compatible endpoint, create a second model configuration, or copy uncommitted source-checkout changes. OMP receives its ordinary tools and MCP integrations through an isolated profile cloned from the user's current OMP configuration.

Related MCP server: pi-subagent

Requirements

• Debian or another systemd-user Linux environment;

• Bun or Sandwich on PATH;

• native omp, hermes, and git commands;

• Librarian registered in OMP before setup. The handoff is a hard completion condition, not an optional integration.

Install

git clone https://github.com/CommanderTurtle/leetcoder.git ~/Hermes/leetcoder
cd ~/Hermes/leetcoder
bun install
bun run setup

Setup performs a frozen Bun install, builds local artifacts, creates the leetcoder OMP profile, installs the user service, registers the Hermes MCP, installs the small Hermes routing skill, and restarts the Hermes gateway.

The generated paths are deliberately outside git:

~/.config/leetcoder/config.json   lifecycle configuration
~/.config/leetcoder/token         loopback API bearer token
~/.local/share/leetcoder/         database and isolated worktrees
~/.omp/profiles/leetcoder/        autonomous OMP profile
~/.omp/profiles/leetcoder-auditor/ read-only, MCP-free verifier profile

Hermes tools

Templates cover implementation, bug fixes, audits, refactors, tests, research, interactive web work, and source comparisons. They provide execution shape, not canned answers; the full delegation remains authoritative.

Operations

bun run doctor
bun dist/cli.js health
bun dist/cli.js sessions --all
bun dist/cli.js service status
bun dist/cli.js service restart

An interrupted gateway marks in-flight roots paused and running children interrupted, preserves their OMP session paths and artifact identities, and automatically queues a recovery turn after restart. Steering and follow-up messages are stored before deferred execution and survive service restarts. leetcoder_status refreshes the live OMP registry through RPC, reads child transcripts incrementally, and reconstructs the complete control view after Hermes compaction from SQLite rather than relying on conversation memory. A detailed session inspection also reports the live root's model, streaming and compaction state, queued messages, todos, throughput, and context utilization.

The Leetcoder profile enables OMP's native Advisor at the persisted profile and every headless RPC launch. The runtime flag matters because OMP intentionally resets workflow-altering Advisor/task/memory settings to safe defaults in RPC mode. Advisor subagents remain disabled: each root worker gets one passive, read-only reviewer rather than an uncontrolled review tree. Native task recursion remains one level and concurrency remains one child per root by default. Inner async execution is disabled because Leetcoder itself already runs the root in the background; a child therefore replaces rather than overlaps its parent's generation slot. This keeps three root/Advisor pairs, Hermes, and Librarian inside the configured eight-sequence local model ceiling.

Verified completion

Leetcoder does not replace OMP Goal Mode or Hermes continuation. Those harnesses remain the single continuation owners. At the end of a Leetcoder implementation turn, the gateway opens a separate ephemeral OMP session with only read,grep,glob,bash,lsp, no skills, no project rules, no extensions, and an MCP-empty profile. It receives the original contract, draft location, and the acting agent's claimed result, then independently inspects the worktree.

The response uses LongHorizon-Harness' three-part completion boundary:

Status: complete | incomplete | blocked
Integrity: clean | suspect | violation
Contract audit: aligned | unknown | needs_revision | invalid

Only complete + clean + aligned enters the SQLite accepted-fact ledger and the Librarian handoff. Any other result is routed back to the persistent OMP root as concrete repair guidance, then a new auditor session checks again. The default limit is two rounds, configurable under verification.maxRounds (1–5). Malformed output and auditor-caused worktree changes fail closed. Status after Hermes compaction includes the latest verdict, evidence, and accepted facts.

Closing never deletes a branch or worktree. Review, merge, archive, or remove them explicitly with ordinary git commands after the parent Hermes session has accepted the result.

Updating

cd ~/Hermes/leetcoder
git pull --ff-only
bun install --frozen-lockfile
bun run build
bun dist/cli.js service restart
hermes gateway restart

Run bun run setup once after this verified-completion update so the isolated leetcoder-auditor profile is created. Later reruns are idempotent and keep the token and existing Leetcoder state.