Halofy plugin
A Claude Code plugin that connects the agent to shared organizational memory with access control, audit and signed erasure
- 319 ★ on the repository
- Last commit
- AGPL-3.0
Broad access
Why this level
- The stop hook sends the session transcript to the server, and it may contain code, data and secrets
- The agent key in an environment variable opens read and write access to organizational memory
- The plugin installs an MCP server and hooks that fire at the start and stop of every session
Install
- Works in
Manual install
git clone https://github.com/halofyai/halofy.git && cd halofy/kernel && npm ci && npm run serveStarts the server locally; the console opens at http://localhost:8787/console/login. For durable use with Postgres follow the self-hosting guide.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The stop hook sends the session transcript to the server, and it may contain code, data and secrets
- The agent key in an environment variable opens read and write access to organizational memory
- The plugin installs an MCP server and hooks that fire at the start and stop of every session
This is third-party code. Review the repository files before installing.
What it does
The Claude Code plugin in Halofy's integrations folder connects the agent to a shared memory server. At session start a hook searches memory for the project's conventions and decisions and injects the best hits into context. When the session stops, a second hook sends the transcript to the server, which extracts durable facts, verifies them and removes duplicates. The server closes a corrected fact and links the new version. History is kept. Inside the session the MCP tools `mem_search`, `mem_write` and `mem_read` are available. Halofy itself is a server that sits between organizational knowledge and agents. It resolves identity, role and namespace from the access key on its own side and writes every action to audit. The server confirms erasure of a person's data with a signed certificate. The default storage is embedded PGlite, and Postgres with pgvector suits long-running use. Codex has an installer that writes the server into its config. Other clients need an MCP config snippet.
Who it is for. Teams that run several agents over shared knowledge and want to control access, change history and deletion on their own server.
Good fit when
- Several agents on a team must see shared conventions and decisions of a project and nothing extra
- You need change history for facts: a correction closes the old record and links to the new one
- You need to demonstrably erase a customer's data and get a signed certificate
- You want Claude Code to receive project rules from memory automatically at session start
- Different clients need separate access keys with roles and namespace separation
Not a fit when
- You need a personal note for one agent on one machine: the server, keys and policies are overkill
- You need two-way sync with Obsidian: the integration only sends notes to the server
- You cannot run and maintain a Node.js server
Example request
Start a local Halofy, issue an agent key and connect the halomem plugin to Claude Code in this projectLimitations
The plugin works only with a deployed Halofy server: it needs the variables HALOMEM_URL and HALOMEM_API_KEY with an agent key. If the variables are missing or the server is unreachable, the hooks exit silently and the agent keeps working without memory. The repository is licensed under AGPL-3.0, and the integrations folder has its own license file. By default the server uses embedded PGlite and a deterministic stub in place of a model. Real Anthropic, OpenAI-compatible and Azure OpenAI models are configured separately. The Obsidian integration is one-way.
How to disable. Remove the halomem plugin through the Claude Code plugin manager (/plugin). For Codex run the installer with the --remove flag, which takes the block out of config.toml. The access key can be revoked in the Halofy console.
FAQ
How do I connect Halofy to Claude Code?
Start the server, set HALOMEM_URL and HALOMEM_API_KEY, then run claude plugin marketplace add with the path to kernel/integrations and claude plugin install halomem@halomem-integrations.
What does the plugin send to the server?
The stop hook reads the session transcript and passes it to /v1/mem/write. The server extracts durable facts itself. The session start hook does the opposite and queries memory for the project's conventions and decisions.
What happens if the server is unreachable?
Both hooks exit without output and the agent keeps working as usual. The plugin is built so a connection failure never blocks the session.
Does Halofy work with Cursor and Codex?
Yes. Codex has the codex/install.mjs installer. For Cursor, VS Code, Cline, Gemini CLI, Claude Desktop and other clients, the Halofy console generates the right config snippet on its Integrations screen.
How is Halofy different from Hindsight?
Hindsight stores an agent's experience and facts as a long-term memory system. Halofy adds an organizational layer to memory: roles, namespaces, policies, an audit of every call and signed erasure.
Discussion
No questions or reviews yet.
Related
PluginsKnowledge-graph memory for agents: Claude Code and Codex plugins, an MCP server and a Python library
An operating layer for Claude Code and Codex: one /do entry point, project memory across sessions, safety hooks, cost telemetry and parallel agents
Local memory for agents: stores conversations and project files verbatim and retrieves them with semantic search over MCP
A long-term memory plugin that keeps decisions, preferences and task state across sessions and injects only what a query needs
A self-improvement plugin for Claude Code, Codex and OpenCode: turns corrections into rules the agent follows in later sessions
Shared cloud memory for a team's agents: stores session traces and turns repeated patterns into skills
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Halofy (this entry) | yes | 319 | ||
| Hindsight | yes | API key | 55,871 | a long-term agent memory system without roles, namespaces or signed erasure |
| agent-memory | no | 4,374 | agent memory in Markdown files with a SQLite index on one machine, with no server or access policies |
README in short
Halofy gives an organization's agents, applications and operators one set of identity and policy rules over MCP and HTTP. The repository holds a TypeScript kernel, a web console and four connectors: filesystem, Postgres, Obsidian and CSV.