guitaripod

Omp Bridge — Development skill for Claude Code

Development community

Oh My Pi as structured HTTP sessions, on claude-bridge's wire protocol.

How to install Omp Bridge

This entry records only its repository, not the path inside it, so there is no exact command to give. Open guitaripod/omp-bridge and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Omp Bridge does

Oh My Pi as structured HTTP sessions, on claude-bridge's wire protocol.

Alternatives in Development

  • 10 Context And Prompts — Prompt 10: Wire Up System Prompt, Context Gathering & Memory System 2.3k ★
  • Harness Remote — Native-session control plane for Codex, Claude Code, OpenCode, OMP and PI 356 ★
  • Claude Code Wechat Channel — Claude Code Channel plugin for WeChat — bridge WeChat messages into Claude Code sessions via the official Claw 255 ★

README

omp-bridge

A bridge that puts an [oh-my-pi](https://github.com/can1357/oh-my-pi) (omp) coding agent on a tailnet, so remote clients can drive it like any other agent server. Sibling to `claude-bridge`: same wire protocol, same self-update contract, different engine underneath.

omp speaks NDJSON over stdio (`omp --mode rpc`). This bridge owns those processes, one per conversation, and exposes them as plain HTTP + Server-Sent Events.

What it serves

Area Routes
Handshake GET /health, GET /status (agent: "omp", proto: 2)
Streaming GET /stream (sequenced, replayable, epoch-cursored), GET /sessions/:id/events
Sessions GET/POST /sessions, GET/PATCH/DELETE /sessions/:id, /revision, /wait, /message, /abort, /clear, /fork
Interruptions GET /sessions/:id/interruption, /resume, /interruption/dismiss, /auto-resume
Subagents GET /sessions/:id/agents[/:agentID]
Money GET /sessions/:id/usage, GET /sessions/:id/spend, GET /analytics?days=N
Models GET /models (omp's own catalog: provider, thinking levels, context window; cached 5 min)
Search GET /search?q=&limit= over every omp transcript on the machine
Commands GET /commands?session= (live slash-command catalog from omp), GET /commands[?directory=] (the machine's catalog with no chat open — a scratch omp asked in that directory, cached 5 min)
Files GET /files, /files/content, /files/raw, GET /attachments/:session/:name
Git GET /git, /git/diff, /git/commit (read-only)
Auth GET /auth, POST /auth/login, /auth/code, /auth/cancel (omp provider login)
Update GET/POST /update, POST /update/restart, POST /update/auto

Everything is read-only or conversational; nothing stages, commits, pushes or deletes outside its own state directory. 404 means *this server cannot say*.

Mapping omp → wire

  • One omp --mode rpc child process per conversation, cwd = the