ompweb: A Local Workbench for ompompweb：给 omp 一张本地工作台.

omp in the terminal is “good enough”. Sessions, tool calls, permission prompts — all doable in a terminal window.

But not good.

Want to revisit yesterday’s session? ls through a pile of JSONL. Compare three branches side by side? Open three terminal windows. Check whether MCP is hooked up? Dig through config files. Switch Git worktrees? Open another pane.

I didn’t want to replace omp. I wanted a desk: the sessions, terminals, files, and MCP status that already exist, laid out where I can see them.

ompweb’s positioning is on page one of the README: a modern, high-performance, local-first web workspace and native desktop app for oh-my-pi.

The key design is just one line — don’t rewrite the agent, just read its session files.

~/.omp/agent/sessions/   ← single source of truth for sessions
        ↓ browse / branch / archive (narrow writes)
     ompweb (Next.js / Electron)
        ↓ live execution
  omp --mode rpc-ui  ← OMP stays the runtime

Local sessions get scanned straight from JSONL by Node; live work goes through omp --mode rpc-ui (NDJSON over stdio). The OMP SDK lives on the Bun side — the Node service deliberately never imports it, to avoid mixing runtimes.

In one line: OMP writes sessions, ompweb displays and orchestrates; the UI holds no authority.

Problem

Terminals have three ceilings:

1. History is invisible — sessions live in files, not in front of you
2. Multi-window has no structure — branching, comparing, rolling back all depend on manual window juggling
3. The ecosystem is invisible — MCP, skills, Git state scattered everywhere

Rewrite an agent and you split the ecosystem. ompweb chose to stand next to omp, not across from it.

Approach

The stack is Next.js 16 + Electron 44, Node ≥ 22.19.

• Web: npx @37chengshan/ompweb@latest opens it, listening on 127.0.0.1:30177
• Desktop: Electron shell, tray-resident, Dock status, independent window lifecycle
• Remote-ready: --password, --hostname, --no-open — built for servers

Later I added a Rust ompweb-host daemon: Git / PTY / session scanning / settings / supervisor, over bounded NDJSON (UDS / Named Pipe).

Features are laid out as a “workbench”, not a “chat window”:

• Session tree navigation and branching
• Real-time multi-agent collaboration
• Interactive web PTY
• Visual MCP / Skill management
• Code and rich-media preview
• Git multi-worktree switching

The boundary is clear. The write path is deliberately narrow. Session authority lives with OMP; ompweb keeps only low-risk operations like rename / archive / delete / branch-parent. Try to write everything and you’ll fight the live process.

Guard the SDK boundary. The OMP SDK is Bun-only; the Node/Next service can’t just import it for convenience. Work has to go through omp --mode rpc-ui.

The architecture gets thicker. After adding the host daemon, the debugging surface grows — UI, Next, host, omp, four layers. That’s the cost of local-first; docs and secure defaults (loopback / password) have to keep up.

Try it with one npx, or grab an installer from Releases (mac / Windows / Linux). MIT license; upstream lineage comes from the pi-web / oh-my-pi ecosystem.

It doesn’t invent a new agent — it just puts the omp sessions that already exist on a desk you can actually use.

npx @37chengshan/ompweb@latest

Main repo: 37chengshan/ompweb.

FAQ

Is ompweb meant to replace omp?

No. The author is explicit: it’s not about replacing omp, it’s about wanting a “desk”. ompweb doesn’t rewrite the agent, it just reads its session files; live execution still goes through omp — standing next to omp, not across from it.

How does it read my sessions?

~/.omp/agent/sessions/ is the single source of truth: local history gets scanned from JSONL by Node, live work goes through omp --mode rpc-ui (NDJSON over stdio). In one line: OMP writes sessions, ompweb displays and orchestrates.

Is it safe to change sessions with it?

The write path is deliberately narrow — only low-risk operations like rename / archive / delete / branch-parent. Try to write everything and you’ll fight the live process — that’s a boundary the author set on purpose.

How do I run it? What do I need?

Web version, one line: npx @37chengshan/ompweb@latest, listening on 127.0.0.1:30177 by default; desktop installers too (mac / Windows / Linux). The stack is Next.js 16 + Electron 44, needs Node ≥ 22.19, MIT license.

Can I use it remotely on a server?

Yes — with --password, --hostname, --no-open flags, built for servers. Loopback only by default; the author notes that docs and secure defaults have to keep up.