Skip to content

Blog: Give Every Agent You Run in Omnigent a Persistent Memory#2709

Merged
benfrank241 merged 6 commits into
mainfrom
blog/omnigent-persistent-memory
Jul 15, 2026
Merged

Blog: Give Every Agent You Run in Omnigent a Persistent Memory#2709
benfrank241 merged 6 commits into
mainfrom
blog/omnigent-persistent-memory

Conversation

@benfrank241

Copy link
Copy Markdown
Member

Summary

Tutorial-style post on integrating Hindsight into Omnigent, a meta-harness that wraps multiple AI agents (Claude Code, Codex, Cursor, Hermes, Pi, and more).

Key angle — the universal memory bridge: Omnigent intercepts hindsight_recall, hindsight_retain, and hindsight_reflect at the runner level and executes them locally, so every wrapped harness gets persistent memory through one setup, even harnesses with no native Hindsight support (Codex, Pi, OpenCode, custom).

What it covers

  • Install: pip install "omnigent[memory]" (adds hindsight-client>=0.4.0)
  • YAML spec config with all tool fields (api_key, bank_id, budget, max_tokens, recall_tags)
  • System instruction pattern (explicit tool calls, not automatic lifecycle hooks)
  • Bank scoping: config bank_idagent_idconversation_id
  • Working Remy example (examples/remy/config.yaml)
  • Cloud vs self-hosted
  • Harness coverage table (which have native Hindsight, which get it only via Omnigent)

Grounding

Every technical claim verified against the omnigent-ai/omnigent repo:

  • Tool classes in omnigent/tools/builtins/hindsight.py
  • Runner-local dispatch in omnigent/runner/tool_dispatch.py
  • hindsight-client>=0.4.0 optional dep in pyproject.toml
  • Bank resolution chain in HindsightRetainTool._bank()
  • Remy example at examples/remy/config.yaml

~1,220 words, 0 em-dashes.

Changes

  • hindsight-docs/blog/2026-07-14-omnigent-persistent-memory.md
  • hindsight-docs/static/img/blog/omnigent-persistent-memory.png — harness-fan bridge diagram (harnesses → Omnigent → ONE BANK)

🤖 Generated with Claude Code

benfrank241 and others added 2 commits July 14, 2026 10:26
Tutorial-style post on adding persistent memory to Omnigent. Key angle:
Omnigent intercepts hindsight_recall/retain/reflect at the runner level, so
every wrapped harness (Claude Code, Codex, Cursor, Hermes, Pi) gets memory
through one setup, even those with no native Hindsight support. Covers
install, YAML spec, bank scoping, the Remy example, and cloud/self-hosted.
Grounded in omnigent-ai/omnigent source. Bridge-diagram cover.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Fact-check against omnigent-ai/omnigent revealed CRITICAL error: tools are
named memory_recall/retain/reflect (not hindsight_*). Fixed all 15 occurrences.
Also added: reflect structured-output note, recall_tags filtering FAQ.
Cover tagline updated to match. 0 em-dashes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
benfrank241 and others added 4 commits July 14, 2026 11:27
Reviewer was right: Codex and OpenCode have official Hindsight integrations,
and Pi has a community one (epimetheus). Corrected the table (all marked Yes
with the right type). Reframed the differentiator from 'only path to memory'
to 'one central setup across every orchestrated harness'. Added a new section
on when to use Omnigent's memory tools vs a tool's native integration, and the
warning not to enable both against the same bank (double-write).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
An earlier fact-check read a stale unmerged branch (integration/hindsight-
memory-tool) that renames the tools to memory_*. The RELEASED omnigent v0.5.1
(what 'pip install omnigent[memory]' gets) and main both use hindsight_recall/
retain/reflect (file omnigent/tools/builtins/hindsight.py, and examples/remy).
Verified against the locally-installed 0.5.1 registry. Cover tagline reverted too.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@benfrank241
benfrank241 merged commit b0e5d10 into main Jul 15, 2026
86 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant