AI 에이전트 생체모방형 메모리 Hippo 공개

🦛 Hippo The secret to good memory isn't remembering more. It's knowing what to forget. Works with: Claude Code, Codex, Cursor, OpenClaw, any CLI agent Imports from: ChatGPT, Claude (CLAUDE.md), Cursor (.cursorrules), any markdown Storage: SQLite backbone + markdown/YAML mirrors. Git-trackable and human-readable. Dependencies: Zero runtime deps. Requires Node.js 22.5+. Optional embeddings via @xenova/transformers. The Problem AI agents forget everything between sessions. Existing solutions just save everything and search later. That's a filing cabinet, not a brain. Your memories are also trapped. ChatGPT knows things Claude doesn't. Cursor rules don't travel to Codex. Switch tools and you start from zero. Who Is This For Multi-tool developers. You use Claude Code on Monday, Cursor on Tuesday, Codex on Wednesday. Context doesn't carry over. Hippo is the shared memory layer across all of them. Teams where agents repeat mistakes. The agent hit the same deployment bug last week. And the week before. Hippo's error memories and decay mechanics mean hard lessons stick and noise fades. Anyone whose CLAUDE.md is a mess. Your instruction file grew to 400 lines of mixed rules, preferences, and stale workarounds. Hippo gives that structure: tags, confidence levels, automatic decay of outdated info. People who want portable AI memory. No vendor lock-in. Markdown files in your repo. Import from ChatGPT, Claude, Cursor. Export by copying a folder. Quick Start npm install -g hippo-memory hippo init hippo remember " FRED cache silently dropped the tips_10y series " --tag error hippo recall " data pipeline issues " --budget 2000 That's it. You have a memory system. What's new in v0.9.1 Auto-sleep on session exit. hippo hook install claude-code now installs a Stop hook in ~/.claude/settings.json so hippo sleep runs automatically when Claude Code exits. hippo init does this too when Claude Code is detected. No cron needed, no manual sleep. What's new in v0.9.0 Working memory layer ( hippo wm push/read/clear/flush ). Bounded buffer (max 20 per scope) with importance-based eviction. Current-state notes live separately from long-term memory. Session handoffs ( hippo handoff create/latest/show ). Persist session summaries, next actions, and artifacts so successor sessions can resume without transcript archaeology. Session lifecycle with explicit start/end events, fallback session IDs, and hippo session resume for continuity. Explainable recall ( hippo recall --why ). See which terms matched, whether BM25 or embedding contributed, and the source bucket (layer, confidence, local/global). hippo current show for compact current-state display (active task + recent session events), ready for agent injection. SQLite lock hardening : busy_timeout=5000 , synchronous=NORMAL , wal_autocheckpoint=100 . Concurrent plugin calls no longer hit SQLITE_BUSY . Consolidation batching : all writes/deletes happen in a single transaction instead of N open/close cycles. --limit flag on hippo recall and hippo context to cap result count independently of token budget. Plugin injection dedup guard prevents double context injection on reconnect. What's new in v0.8.0 Hybrid search blends BM25 keywords with cosine embedding similarity. Install @xenova/transformers , run hippo embed , recall quality jumps. Falls back to BM25 otherwise. Schema acceleration auto-computes how well new memories fit existing patterns. Familiar memories consolidate faster; novel ones decay faster if unused. Multi-agent shared memory with hippo share , hippo peers , and transfer scoring. Universal lessons travel between projects; project-specific config stays local. Conflict resolution via hippo resolve <id> --keep <mem_id> . Closes the detect-inspect-resolve loop. Agent eval benchmark validates the learning hypothesis: hippo agents drop from 78% trap rate to 14% over a 50-task sequence. Zero-config agent integration hippo init auto-detects your agent framework and wires itself in: cd my-project hippo init # Initialized Hippo at /my-project # Directories: buffer/ episodic/ semantic/ conflicts/ # Auto-installed claude-code hook in CLAUDE.md If you have a CLAUDE.md , it patches it. AGENTS.md for Codex/OpenClaw. .cursorrules for Cursor. No manual hook install needed. Your agent starts using Hippo on its next session. It also sets up a daily cron job (6:15am) that runs hippo learn --git and hippo sleep automatically. Memories get captured from your commits and consolidated every day without you thinking about it. To skip: hippo init --no-hooks --no-schedule Cross-Tool Import Your memories shouldn't be locked inside one tool. Hippo pulls them in from anywhere. # ChatGPT memory export hippo import --chatgpt memories.json # Claude's CLAUDE.md (skips existing hippo hook blocks) hippo import --claude CLAUDE.md # Cursor rules hippo import --cursor .cursorrules # Any markdown file (headings become tags) hippo import --markdown MEMORY.md # Any text file hippo import --file notes.txt All import commands support --dry-run (preview without writing), --global (write to ~/.hippo/ ), and --tag (add extra tags). Duplicates are detected and skipped automatically. Conversation Capture Extract memories from raw conversation text. No LLM needed: pattern-based heuristics find decisions, rules, errors, and preferences. # Pipe a conversation in cat session.log | hippo capture --stdin # Or point at a file hippo capture --file conversation.md # Preview first hippo capture --file conversation.md --dry-run Active task snapshots Long-running work needs short-term continuity, not just long-term memory. Hippo can persist the current in-flight task so a later continue has something concrete to recover. hippo snapshot save \ --task " Ship SQLite backbone " \ --summary " Tests/build/smoke are green, next slice is active-session recovery " \ --next-step " Implement active snapshot retrieval in context output " hippo snapshot show hippo context --auto --budget 1500 hippo snapshot clear hippo context --auto includes the active task snapshot before long-term memories, so agents get both the immediate thread and the deeper lessons. Session event trails Manual snapshots are useful, but real work also needs a breadcrumb trail. Hippo can now store short session events and link them to the active snapshot so context output shows the latest steps, not just the last summary. hippo session log \ --id sess_20260326 \ --task " Ship continuity " \ --type progress \ --content " Schema migration is done, next step is CLI wiring " hippo snapshot save \ --task " Ship continuity " \ --summary " Structured session events are flowing " \ --next-step " Surface them in framework hooks " \ --session sess_20260326 hippo session show --id sess_20260326 hippo context --auto --budget 1500 Hippo mirrors the latest trail to .hippo/buffer/recent-session.md so you can inspect the short-term thread without opening SQLite. Session handoffs When you're done for the day (or switching to another agent), create a handoff so the next session knows exactly where to pick up: hippo handoff create \ --summary " Finished schema migration, tests green " \ --next " Wire handoff injection into context output " \ --session sess_20260403 \ --artifact src/db.ts hippo handoff latest # show the most recent handoff hippo handoff show 3 # show a specific handoff by ID hippo session resume # re-inject latest handoff as context Working memory Working memory is a bounded scratchpad for current-state notes. It's separate from long-term memory and gets cleared between sessions. hippo wm push --scope repo \ --content " Investigating flaky test in store.test.ts, line 42 " \ --importance 0.9 hippo wm read --scope repo # show current working notes hippo wm clear --scope repo # wipe the scratchpad hippo wm flush --scope repo # flush on session end The buffer holds a maximum of 20 entries per scope. When full, the lowest-importance entry is evicted. Explainable recall See why a memory was returned: hippo recall " data pipelin