RewindStore

OMNI’s archive layer — every piece of raw output distilled by OMNI is stored here with a SHA-256 hash, ensuring zero information loss despite aggressive distillation.

How It Works

When omni distills a command’s output, the original raw content is:

1. Stored in a local SQLite database
2. Indexed by a SHA-256 hash of the content
3. Made available for retrieval by both humans and agents

Access Methods

Via MCP (agent access):

omni_retrieve("sha256hash")

The agent calls this tool when it needs the full original output behind a distilled signal.

Via CLI (human access):

omni rewind list          # list archived entries
omni rewind show <hash>   # show a specific entry

Why It Matters

Without RewindStore, distillation would be a lossy, irreversible operation. With it, OMNI can be aggressive about reducing tokens sent to the agent while still guaranteeing that nothing is permanently discarded. The agent can always “rewind” to the original if the distilled signal wasn’t enough.

See Also

• omni — the tool that uses RewindStore
• context-distillation — the distillation process that makes RewindStore necessary