• The difference is +4.2 percentage points with a 95% confidence interval of [−1.9, +10.2] (task-level paired bootstrap). The interval includes zero, so this is not a statistically significant improvement.

• OMK cost about 23% less per trial but was slower: 482 s median per trial against 376 s.

• Audit corrections: trials that tried to read Terminal-Bench sources or answers score 0, which turned 4 mini-swe-agent passes and 1 OMK pass into failures. prove-plus-comm is excluded from both sides because our OMK adapter failed to start in that task's working directory. Two transient provider errors were retried; no trial was excluded.

• OMK failed all three pytorch-model-recovery trials because the CLI rejected an instruction starting with a dash and a space (fixed in #84). Without that task the difference is +5.4 pp [0.0, +10.7].

• Not a leaderboard run: 3 trials instead of the official 5, our own network allowlist and apt cache proxy, and OMK alone had 150 s extra for a workspace snapshot used in rescoring.

• Costs count only the graded attempt, excluding prior failed retry attempts and 42 auxiliary model calls made by code inside one mini-SWE-agent task. They are not total experiment spend.

Method, per-difficulty results, audit and reproduction notes: Terminal-Bench 2.1 report.

OMK's provider-neutral coding-agent CLI also exposes a multi-agent control plane for explicitly configured workflows. The stages describe that design, not what every prompt automatically runs.

The v0.98.3 SDK rejects incomplete first-party judge responses and exposes deterministic ties; it is not an automatic TUI judge.

1. Scope the goal, paths, resources, and acceptance predicates. A selected orchestration workflow may also supply a DAG; an ordinary prompt remains one agent/tool loop.
2. Route work to models, agent skills, MCP tools, and extensions without changing the evidence contract.
3. Verify declared checks in explicit evidence workflows. Required failing checks block those workflows; advisory judging cannot replace them.
4. Preserve receipts and replay state for bounded session recovery; continue durable goals from explicit reducer state.

OMK keeps routing separate from control and evidence. Codex, Claude Code, OpenCode Zen/Go, Kimi, GLM/ZAI, native xAI/Grok, NVIDIA NIM, and local providers can participate through omk-ai while the run contract stays stable.

Native xai keeps subscription OAuth and XAI_API_KEY billing separate. See provider setup, provider resilience, and Grok integration.

Published packages

npm install omk-agent-core
npm install omk-ai
npm install omk-protocol
omk install npm:omk-book-to-skill@0.98.3
npm install omk-tui

v0.97.0 shipped the OpenWiki policy and workflow, but no versioned corpus or integrity checker. The following integrity/output guards shipped in v0.98.0; the generated corpus remains optional and is not bundled:

• openwiki/ — absent. The previous untracked corpus was removed after the hardened gate proved it carried fabricated evidence: 8 frontmatter symbols that no declared source path defines (AgentLoop, getModel, DeepWall, loadExtensions, createExtensionRuntime, main), 45 references to @omk/* package names this repository does not publish, and a restatement of this README's Scope -> Route -> Verify -> Replay loop as a strict engine state machine, which is not what the source implements. CI regenerates the corpus; nothing is lost.
• scripts/check-openwiki.mjs — shipped integrity checker. An interrupted corpus now fails unless openwiki/.manual-review.json binds a review to the exact corpus digest, and every frontmatter symbol must bind to one of that page's own source_paths as a whole identifier.
• scripts/check-openwiki-output.mjs — output gate. The scheduled workflow may write, upload, and open a PR for openwiki/ and nothing else, so a model reading this repository cannot reach AGENTS.md, CLAUDE.md, or the workflow that runs it. The gate runs once before the artifact leaves the read-only generating job and again before the PR, because the publishing job holds write permissions the first one does not.
• .understand-anything/ — optional local structural graph used by Pi Lens; it is not published or injected into prompts by default. To reach a session, attach it through OMK's MCP client like any other server; there is no second, bespoke path for it.

Source and tests remain authoritative. Shipped guards do not turn a generated index into authority: treat corpus pages as local advisory data and recheck source.

Retrieval

A corpus no session can read is documentation of a plan, not a feature, so the pages are now candidates for prompt budgeting. Enable contextBudget.openwiki alongside contextBudget.enabled (settings) and each page becomes a low-priority evidence item ranked against the turn's query. Pages compete for leftover budget and can never displace instructions or skills; most turns carry titles and declared symbols alone, and a page's text arrives only when the query earns it.

Admission mirrors scripts/check-openwiki.mjs rather than restating it. A complete corpus at the current HEAD offers page text; one whose HEAD has moved offers titles only and is marked stale; an interrupted corpus is refused unless a review binds to its exact digest. The default is off, and with the setting off the prompt is byte-identical to one built without a corpus.

The design decisions behind OMK's context, routing, memory, and orchestration layers are grounded in published work rather than invented in isolation. Each row below was retrieved and read directly; claims are at abstract level, which is the evidence grade this table asserts and no more.

Entries include implemented mechanisms and design proposals; check the runtime status guide for availability. The wider survey, including approaches not adopted, is working material that is not published with the repository.

Historical correction: the immutable v0.97.0 notes below announced a versioned OpenWiki corpus, but that release still ignored /openwiki/ and did not contain the corpus or checker. See the current repository-understanding section above for the shipped guards and optional-corpus boundary.

Release v1.5.10

Fixed

• Bound adaptive-effort tool-call deduplication state. If its limit is reached, the adaptive wrapper passes through the configured reasoning effort for the rest of its lifetime; other limits may still apply.
• A compaction is no longer stamped earlier than the messages it covers when the wall clock steps backward (observed on WSL2 as ~6.8 second resyncs). Previously the compacted history's old usage still counted after compaction, so the next prompt was rejected with context_input_capacity_exceeded. The compaction timestamp now follows the newest message on its branch for steps up to one minute.
• Usage estimates, input admission and compaction gates now use active-branch entry order to distinguish covered messages from new responses. Assistant usage and overflow errors arriving after compaction while the wall clock is still recovering are no longer discarded as stale; repeated compactions are distinguished by entry ID even when their timestamps match.

Release notes live in RELEASE_NOTES_v1.5.10.md.

Release v1.5.9

Added

• A default-on deepseek_harness built-in for native DeepSeek and recognized DeepSeek model IDs on gateways. It adds scoped execution guidance and projects oversized successful tool results to Unicode-safe head/tail excerpts at 80% context pressure, preserving original session history. OMK_DEEPSEEK_HARNESS=0 independently disables it. No upstream runtime, credentials, session-log uploads, or protocol changes are introduced. See DeepSeek harness.
• Project context documents. omk init --project creates missing PRD.md, ARCHITECTURE.md, DESIGN.md, RULES.md, TASKS.md and PROGRESS.md without overwriting files, and the project-directory walk loads each once as context. A bare omk launch in an otherwise empty Git repository root creates them too; OMK_PROJECT_CONTEXT_BOOTSTRAP=0 disables that bootstrap. See User context setup.
• Acceptance diagnostics behind OMK_GOAL_DIAGNOSTICS (flag, default off, spec 094). After a failed /goal acceptance check, the repair follow-up carries a bounded excerpt of the check output anchored at the first error line, falling back to head/tail (#170).

Changed

• Seventeen OMK_* harness flags are now on by default: OMK_EDIT_DIAGNOSTICS, OMK_EXEC_TRUNCATE_MIDDLE, OMK_JSON_SESSION_INFO, OMK_GOAL_AUTONOMY, OMK_SKILL_ADMISSION, OMK_SKILL_AUTO_LOAD, OMK_EVIDENCE_LIFECYCLE, OMK_ADAPTIVE_EFFORT, OMK_DOMAIN_ROUTING, OMK_GOAL_OUTPUT_RECALL, OMK_LANE_READY_QUEUE, OMK_LANE_FAILURE_SCOPE, OMK_RTK_OUTPUT, OMK_SESSION_CONTROL, OMK_VERIFIED_MEMORY, OMK_RESPONSE_REASONING_CAP and OMK_PREFIX_BOUNDARY. Set any of them to 0, false or off to restore the 1.5.8 behavior; with all of them off the G0 session hash is unchanged. OMK_EVIDENCE_LIFECYCLE now deletes only verified goal-recall files (observe deletes nothing), subagent workers keep OMK_SKILL_AUTO_LOAD and OMK_ADAPTIVE_EFFORT off, and an unset OMK_SESSION_CONTROL never fails startup. There is no on/off benchmark for these defaults yet (#279, #281).
• Evidence receipts store commands verbatim. Command credential redaction and its credential preflight are removed; existing v3 receipts with commandRedaction and commandBinding remain readable. Keep secrets out of command lines and pass them through the environment or credential storage (#223).
• The GitHub Copilot default model is now gpt-6.1-sol. Copilot retired gpt-5.4, which left Copilot without an automatic default during first-run onboarding.

Fixed

• A durable goal whose approved acceptance check passed no longer stays active on a loaded host. The goal workspace binding now allows each git call 10 seconds instead of the 1.5 second per-bash-call bound, which git status could exceed and which then refused completion as an unavailable workspace scope. A git that hangs past the longer bound still fails closed; the bash tool scope keeps its 1.5 second bound.
• Repeated local skill searches reuse unchanged document term frequencies instead of tokenizing the entire catalog again. Changed bodies are retokenized, input bounds are revalidated, and scores, exclusions and ranking order remain query-specific.
• Local safe-context-window rejections during tool turns now enter bounded overflow compaction recovery instead of being classified as invalid provider responses. Auto-compaction opt-out and the hard input ceiling remain unchanged.
• A per-call bash timeout now also bounds the outer tool timer, so a requested timeout longer than the fixed 300 second limit is no longer cut short. Extension tools and session wrappers receive the same bound.
• Lock ownership no longer depends on the wall clock alone. The durable goal journal lock uses a 30 second stale window and a lost lock fails the write instead of crashing the process; the sync auth.json lock uses the same 30 second window as OAuth refresh, so a live refresh lock is no longer taken over; the trust store lock is reclaimed by owner pid and released only by its owner; and omk session doctor repair takes the session owner lease and refuses a live session with session_in_use.
• Goal evidence is pinned to its generation and a complete workspace scope, stale autocomplete acceptance is rejected, and next-suggestion cost ceilings, stream identity and request lifetimes are aligned.
• The status sidebar reads the current session's shared usage reader after /new or resume instead of the first session's.
• omk run cancel reads the run journal in reader mode, so an owner appending at the same time no longer makes it fail with integrity; persistent concurrent change reports concurrent_change.
• Durations, throttles, in-memory caches and deadlines now use a monotonic clock, so a wall-clock step (seen on WSL2) no longer makes them fire early, late or never. This covers the double Ctrl+C and Esc windows, the working timer, the bash output throttle, the subscription usage, diagnostics and workspace scope caches, edit diagnostic budgets, OAuth device-code polling and the TUI input drain. npm run check now rejects new wall-clock durations and proper-lockfile locks without an explicit stale window.

Security

• Goal-recall evidence deletion refuses to run when .omk/goals/recall or one of its parents is a symlink.
• npm audit --omit=dev is clean again. undici is updated to 8.12.3 (EventSource memory, SRI token and content-encoding advisories), and a root override moves zod to 4.6.7 for every SDK and the sandbox example (oversized constrained collection advisory; no fixed 3.x release exists).
• The optional Gondolin example now uses Gondolin 0.14.0 with undici 6.29.1. Gondolin no longer depends on node-forge, so the temporary CVE-2026-85393 runtime guard is removed; a regression suite replays the malformed signatures against Gondolin's real cached-leaf verification. The example now requires Node.js 22.19.0 or later. Replace previously copied example directories. See Gondolin signature security.

Release notes live in RELEASE_NOTES_v1.5.9.md.

Release v1.5.8

Added

• Goal autonomy behind OMK_GOAL_AUTONOMY=1 (flag, default off). /goal budget <usd|-> [<deadline ISO>|-] sets a user-only cost and deadline budget that includes subagent lane cost; the goal stops with budget-limit, deadline, outcome-unknown or scope-changed, steering pauses it, and only /goal resume restarts it. Stop reasons are custom entries; the omk.goal.v1 schema is unchanged (#266, #268).
• Strong-only skill auto-load behind OMK_SKILL_AUTO_LOAD (flag, default off), with an observe-only skill-autoload.jsonl log (#262).
• Evidence recall delete-after-use behind OMK_EVIDENCE_LIFECYCLE=delete (flag, default off; observe only records) (#263).

With all new flags off, behavior is the same as 1.5.7.

Fixed

• Evidence recall delete recovery can no longer fail session_start (#264).
• session_info JSON test no longer flakes (#265).

Changed

• Research count scripts for spec 117 and 119 on synthetic fixtures (#267), NaN/Infinity tolerance (#269), header comment fix (#271).
• Spec 118 D3 measurement addendum, design only (#272).
• AGENTS.md lists the goal autonomy flag.

Release notes live in RELEASE_NOTES_v1.5.8.md.