agent-harness · Dual-agent continuity layer

AChange sessions without losing tasks

BreakAndMemory + ImBack solidifies the taskbar, environment fingerprints, key files and excluded routes into snapshots; when restoring a new session, it first performs environment control and drift detection. If the fingerprints are inconsistent, mark STALE, and it is forbidden to directly regard "completed" in the old snapshot as the current fact.

BAutomatic compression does not rewrite the target

CompactAnchor curates goals, authorization boundaries, rejection routes and real stuck points before compression; automatic compression without warning generates mechanical anchors from hooks. A canary back-injection block must appear after compression. If it is missing, the link will be interrupted, and further advancement based on the summary alone is not allowed.

CCorrection can reflow, but cannot contaminate

Hermes Incremental Hook continuously consumes session signals according to the successful cursor, giving priority to updating existing memory, rebuilding the index and running retrieval regression; the cursor will be advanced only if the complete submission is successful. When the source continues to grow during processing, new tails are added and left for the next round to avoid missing reading or mistakenly recording unaccepted content as long-term facts.

DDo not mix sources of internal and external knowledge

Shared memory holds verified engineering facts and user corrections, and Obsidian RAG holds external data and topical research. Internal memory is injected according to tasks through the Top-3 route-card, and external knowledge is retrieved on demand; the two layers each retain the source, update and acceptance boundaries, and do not directly upgrade the web page summary to the engineering truth.

ADual engine native entrance

Claude Code and Codex CLI share the project directory and vault truth source, which are entered through CLAUDE.md / AGENTS.md respectively. Share rule text, retain respective tool events and permission semantics, and do not duplicate two sets of long-term documents that will drift.

BInject memory by task

Structured memory is bucketed by topic and routed by full indexing. Only up to 3 related route-cards are returned in each round, and specific articles are read as needed; the entire knowledge base is not resident in the context, and no bounded full-text search is relied on to try its luck.

CRelay and drift detection

Task snapshots record goals, progress, file pointers, and environment fingerprints; during recovery, the current status is compared item by item. CompactAnchor handles same-session compression, BreakAndMemory / ImBack handles cross-window relay, and the two links have a clear division of labor.

Dcurrent verification

The current item-by-item compatibility status of contracts, skills, hooks, memory, commands, plugins and MCP is maintained by CODEX_PARITY.md; the Codex side only enables adapted and real-machine verified entries, without using quantity alignment to cover up tool semantic differences.

ACross-end parity automatic audit

Continuously put contract routing, skill visibility, hook trust and memory retrieval boundaries into one-click acceptance to prevent silent drift after either end is upgraded.

BRetrieval regression and boundary verification

Maintain a fixed query set, and check whether relevant inputs can hit, whether irrelevant inputs remain silent, and whether the routing results fall at the correct level; rerun after each index, hook, or descriptor change to prevent silent recall degradation.