omk-context-broker

What problem does it solve?

It prevents long-running multi-file Kimi Code work from losing critical context by organizing project-local memory and run-local checkpoints across turns and workers.

Core Features & Use Cases

• Context Broker Policy for Long Sessions: Keeps memory coherent when tasks span many files, turns, agents, or repeated project runs.
• Local Graph Memory as Default Source of Truth: Leverages omk-project memory tools to read/write stable project facts and temporary run/session facts, with a local mirror at .omk/memory/.
• Okabe / D-Mail Checkpoints for Context Recovery: Uses Kimi Code Okabe plus SendDMail to trigger smart recovery before risky changes, multi-agent handoffs, or compaction.
• Durable Memory File Conventions: Standardizes where project facts, decisions, commands, risks, and run events/plans/final reports are stored.

Quick Start

Use omk-context-broker whenever your coding task is likely to span multiple files and turns so the agent can maintain durable project memory and run checkpoints.