Skip to main content

0xRay — a suit for coding agents

4.1 — a suit that survives the context window

0xRay — A Power Suit for AI Agents. survive compaction. build foundries. monitor the swarm.

Bifrost is the live board. Goggles views one plane. A search runs inside that card.

0xRay is a three-subsystem autonomous engine. The suit is the wear. Inference remembers. External Governance judges. The Autonomous Engine runs the work. The host you already run wears it: Grok, OpenCode, Hermes, OpenClaw, or Cursor. Memory, judgement, and payments come on with the suit. When the window closes, the next session wakes with the job, the page, and the laws. Bifrost turns each pull request, issue, and comment into one card and a line in the right seat's inbox, then wakes that seat. Confer still completes only on a real yes.

The product is the skeleton you wear.

The suit wears the three-subsystem autonomous engine (Inference · External Governance · Autonomous Engine). Ceremony tempers by host so free-model OpenCode/Hermes stay fully checked while a frontier host is warned. The 4.0 record is 4.0 vision · 4.0 handoff · Suit temperament.

  • Bone: three subsystems, Codex PreToolUse, four chat adapters plus Cursor hooks
  • Always on: Codex 11 / 29 / 69 — no any, no eval, no new MCP/skill/handler surface
  • Temperament: lead-dev intake / spawn-plan deny required for guided hosts; lite on frontier (warn, not deny)
  • Muscle: Repertoire auto-enables when the module resolves; session-start one-line resume
  • Fat still called: duplicate orchestrators and extra *.server.ts — trim list

Quick Start​

npm install 0xray
npx 0xray wear

npx 0xray status # verify
npx 0xray setup # optional extras

# Per-platform (same bridges wear writes, idempotent)
npx 0xray opencode install
npx 0xray grok install
npx 0xray hermes install
npx 0xray openclaw install
npx 0xray skill:install

How It Works​

Every code change is checked against a 69-term Codex, deliberated by 3 specialized reviewers (code review, security audit, research), and approved, revised, or blocked before it touches your codebase.

┌─────────────────────────────────────────────────┐
│ Inference │
│ Reasoning · Memory routing · Execution │
├─────────────────────────────────────────────────┤
│ External Governance (Dynamo) │
│ Codex enforcement · v3 gate + CI validators │
│ 7 MCP servers (3 deliberate on proposals) │
├─────────────────────────────────────────────────┤
│ Autonomous Engine (thinDispatch) │
│ Task routing · AsideContext · Confidence gate │
└─────────────────────────────────────────────────┘

What's New Since 3.1​

VersionHighlights
4.1.0Bifrost is the collector board. A cloud agent is a board row. A stuck card's L1 stays with the owner. Goggles views one plane. The card is in LENS.md. A search runs inside that card.
4.0.43Confer completes only on a real PASS. Cursor gate events fail closed, except EACCES when a cloud wrapper cannot write dest.
4.0.42Confer votes. Burst runs the swarm.
4.0.9Mill target: postinstall does not mill npm global prefix or _npx as a consumer. Isolated HOME skips machine ~/.grok.
4.0.0Exo + temperament. Constitution always on. Repertoire organ on (vendored 0.2). On npm. vision
3.4.1install-bridges.cjs on postinstall — all 4 platforms + 7 MCP via npx. Canonical release pipeline.
3.3.1Orchestrator confidence gate in execution planning.
3.3.0Pluggable memory routing — Repertoire default in framework repo.
3.2.0AsideContext wired, SelfProposalEngine, pre-tool-use hook, typecheck hardening, Hermes/Grok E2E green.
3.1.1StringRay → 0xRay rename, marketplace discovery, consumer AGENTS/SKILLS seeding.

Removed: hermes bridge CLI (use hermes install), .opencode/xray/ fallback, stale version JSDoc tags, advanced-features/.

Why 0xRay?​

ProblemSolution
AI hallucinates bad codeGovernance gate blocks non-compliant proposals
No quality enforcementv3 enforcement: hooks + CI validators + governance MCP
Single-agent blindspots3 specialized reviewers debate each proposal
Scattered editsMulti-agent orchestrator coordinates work
Repeated mistakesMemory routing enriches selection (Repertoire organ on in 4.0)
Deep sub-tasks lose contextAsideContext subcontexts inherit session + memory routing (v3.2+)

Next Steps​