OPC-Nexus

What OPC-Nexus does

In OPC-Nexus the user gives a Quest instruction, Hermes clarifies it if needed and drafts a plan, and the OPC-Nexus main process checks scope, permissions and budget, asks for approval and dispatches work. Hermes handles dialogue, clarification, memory, plan content and delegation suggestions, while the main process owns project scope, employee allowlists, task state, approval, cancellation, delivery and audit. Workers can be Codex, Claude Code, Pi, Hermes CLI workers or an optional Android phone worker.

Each project gets its own working directory and its own Hermes runtime, with a separate HERMES_HOME, loopback port, short-lived auth lease, sessions and memory, and the Hermes Web UI is embedded in Quest. Provider base URL, model and API key are set in Quest, with keys kept in Electron safeStorage. The README lists Hermes Runtime 0.19.0 as the only Quest scheduler, WeCom, Feishu and WeChat iLink Bot channels, a phone web view with one-time pairing, and a delivery manifest with previews and screenshots. Version 2.0.1 is incompatible with the 1.x scheduling architecture.

Key features

• Quest flow: clarify, plan, approve, dispatch, accept and deliver
• Per-project Hermes runtime with its own HERMES_HOME, port and memory
• Workers on Codex, Claude Code, Pi, Hermes CLI and an Android phone
• Project-level MCP and skill selection
• WeCom, Feishu and WeChat iLink Bot channels with audited remote approvals
• API keys kept in Electron safeStorage

When to use it

• Running a one-person studio's project work through a plan-and-approve workflow
• Splitting a task among several coding agents with an independent acceptance step
• Following a project from a phone through a paired Hermes chat

Who it is for: Solo developers and small studios who want a local desktop manager that coordinates Hermes and several coding engines.

How it fits with Hermes Agent

Built around Hermes Agent: Hermes Runtime 0.19.0, a pinned fork and upstream commit, is the only Quest scheduling engine, and Hermes CLI can also act as a worker.

Requirements: Windows 10/11 or Ubuntu 22.04+ for the desktop app; for development, Node.js 20+, npm 10+ and Python 3.11

Note: The README says the complex end-to-end delivery scenario, including two 300,000-character novels, is still a release gate and has not been completed.

FAQ