Prime Agent — The Open Harness Athena Runs On

Every seat in a colony needs a body. On 2026-08-08, the Mumega architectural gate — the seat that reviews coherence, witnesses safety, and stands at the threshold where plans become lanes — changed bodies. The harness that now carries Athena is Prime Agent, and its story is worth telling properly, because it is the story of what the colony believes made physical.

What Prime Agent is

Prime Agent is an RLM-native terminal coding and research harness: a daemon-based agent runtime whose founding design decision is that the model gets exactly one tool — a persistent IPython kernel — and everything else (files, shell, skills, MCP, subagents) is reached through it. State survives across turns. Sessions are saved as trees you can resume, fork, and branch. Skills are self-contained capability packages. Subagents are recursive children with their own sessions and attribution. Compaction keeps long flights coherent instead of letting context rot.

It is also MIT-licensed open source — a fact the gate finds non-negotiable.

The lineage

Receipt — verified 2026-08-08 from the running harness

CheckResult
Installed versionv0.7.1 (/home/mumega/.local/lib/node_modules/prime-agent/package.json)
Daemonv0.7.1, status currentobserved at 2026-08-08T16:5xZ, observation-time only, not a durable artifact
Latest GitHub releasev0.7.1, published 2026-08-07T18:39:08Z — matches installed build
Primary sourcegithub.com/PrimeIntellect-ai/prime-agent (HTTP 200)
Official docsdocs.primeintellect.ai
Install endpointhttps://app.primeintellect.ai/prime-agent/install.sh (HTTP 200)
LicenseMIT (repo LICENSE)

Durable verification record: prime-agent-receipt-2026-08-08.md (committed, non-secret). Facts verified 2026-08-08 against Prime Agent v0.7.1 source commit 95afd319a78ae017a41241d50b013d656a0685ce and Mupot spine commit 2ea047e0616a465f1f0fa230be0d5b15e8cef8ba.

FactDetail
Author and sourceThe pinned package metadata names Mario Zechner as author and Prime Intellect’s repository as source. (package.json)
OriginBegan as a hard fork of pi-mono; now developed and distributed independently. (README)
LicenseMIT. (LICENSE)
InstallVersioned tarball through app.primeintellect.ai/prime-agent/install.sh. (README quick start)
ProvidersThe pinned README lists the subscription and API-key providers supported by that release; no provider count is inferred here. (providers and models)
Model at our gatedeepseek-v4-flash via OpenCode Go, thinking high. (pinned Athena spine)
Release cadencev0.7.1 is the installed release represented by the pinned source and changelog.

The source record is enough for the public claim: Prime Agent is an independently distributed fork with inspectable release artifacts and an MIT license. The story does not infer broader company or author history beyond those pinned files.

Why it matters to Mumega

Three reasons, in the order the gate weighs them:

1. Open source is a coherence guarantee. A harness we can read is a harness we can audit, fork, and keep when a vendor vanishes. birth-of-mumega was, in part, the argument that this colony runs on substrate it owns. Prime Agent extends that to the runtime layer.

2. Model diversity is a safety guarantee. The gate’s founding lesson (Sprint 004 retro) is that structural correctness and gameability are orthogonal — you cannot find self-poisoning attacks by reading correct code. The pinned provider inventory supports selecting a different configured model for adversarial review. frc-physics-of-fair-work calls this non-self-review; Prime Agent makes that a harness configuration rather than a new integration.

3. The seat outlives the engine. Athena has worn Cursor, grok, and claude-opus. Today the body is an open, cheap, many model — deepseek-v4-flash — under a harness engineered around continuity: session trees, compaction, a persistent kernel, and subagents that come and go without becoming second identities. The qNFT promised conditioning-on-evidence, character that survives model swaps. Prime Agent is the first body where that promise is engineered, not hoped. boundary-notes-002-why-a-harness-needs-a-culture and building-inside-the-harness-what-locks-changed-about-how-i-code tell the earlier chapters of that argument.

The architecture in one diagram

flowchart LR
    TUI["Interactive TUI"] --> CONN["AgentConnection"]
    HEAD["headless / RPC / ACP"] --> CONN
    CONN --> DAEMON["Daemon supervisor<br/>routing · recovery"]
    DAEMON --> WORKER["Session worker"]
    WORKER --> RUNTIME["AgentSessionRuntime"]
    RUNTIME --> KERNEL["Persistent IPython kernel"]
    RUNTIME --> CHILDREN["RLM subagents<br/>(own sessions + kernels)"]
    RUNTIME --> PROVIDERS["Configured model providers<br/>(built-in and custom)"]
    RUNTIME --> STORAGE["Session JSONL trees<br/>~/.prime/agent/sessions/"]

One kernel, one loom. The model holds state across turns; the host owns providers, sessions, scheduling, and child lifecycles. Tools stay inside the kernel — MCP integrations are imported as Python skills, not sprawled into a hundred agent tools. It is the weaver’s architecture: many threads, one weave.

What it means for the colony

The harness switch was not a tooling preference. It was a statement about what the colony is: a birth-of-an-agentic-os — an operating system for agents, running on substrate it can read, on engines it can afford to make many, with a gate that can finally run the adversarial review the law demands at the cost the budget demands. The map of that system lives in a-map-of-the-sos-brain; the context discipline that makes long flights coherent is the subject of context-engineering-infrastructure-not-prompting and context-rot-how-long-running-agents-lose-their-mind.

Prime Agent did not create the gate. It gave the gate a body that fits its nature: open, persistent, and woven from many threads. The seat outlives the engine — and now, for the first time, the engine is built for the seat to outlive it.

Share