# Post Cortex: Hermes Agent plugin

> Self-hosted long-term memory through a post-cortex daemon (https://github.com/julymetodiev/post-cortex): typed records (decisions, fixed problems, code changes) in an entity graph with local semantic search.

Canonical: https://hermeswatcher.com/plugins/post-cortex  
Tier: Community  
Official page (Nous Research): https://hermes-agent.nousresearch.com/docs/plugins/post-cortex  
Last updated in catalog: 2026-10-20

Self-hosted long-term memory through a post-cortex daemon (https://github.com/julymetodiev/post-cortex): typed records (decisions, fixed problems, code changes) in an entity graph with local semantic search. Recalls related records from the profile's workspace before each turn, puts the user card and the workspace's project card in the system prompt, mirrors built-in memory writes as records, and adds post_cortex_search, post_cortex_record and post_cortex_context (graph neighbours and reverse dependencies of named components) plus the post-cortex:memory skill. Records and captured turns carry the author hermes:<profile>. Profiles are mapped to shared workspaces by name glob, so a team of profiles recalls each other's records.

## Good to know before installing

Talks only to the post-cortex daemon at the configured URL (default http://127.0.0.1:3737; a remote daemon over plain HTTP should sit on a private network or behind TLS): each non-trivial user prompt (up to 2,000 characters) is sent as a search query, and built-in memory writes and post_cortex_record calls are sent as records; with the opt-in capture setting (off by default) each completed turn of the primary agent is sent too: the user's message (with the sender's display name when Hermes knows it), the final reply, tool names and file paths, never tool output; nothing goes to third parties. Disclosure — the daemon stores records (and captured turns, deleted after its message_retention_days) in its own database and redacts credentials, e-mail addresses, phone numbers and public IPv4 addresses on write. Disclosure — PCX_TOKEN (and optionally PCX_URL) is read through the Hermes secret scope; the only local state is $HERMES_HOME/post-cortex.json (0600, never holds the token). No threads or processes of its own (capture runs on Hermes' sync worker), no shell commands, no deletes in post-cortex; cron and subagent runs never write automatically.

From the plugin's catalog listing.

## How to install

1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.

```bash
hermes plugins install post-cortex
```

2. Said no? Turn it on later:

```bash
hermes plugins enable post-cortex
```

3. Restart Hermes so it loads the plugin.

Some plugins also need a sign-in or settings: see the official page. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide: https://hermes-agent.nousresearch.com/docs/user-guide/features/plugins

## Facts

- Category: Memory & notes
- Maintained by: julymetodiev (Community)
- Needs: No API keys declared
- Requires Hermes: `>=0.22.2`
- Version: 0.2.0
- In the catalog since: 2026-10-18, updated 2026-10-20

## Links

- [Full setup and settings (official page)](https://hermes-agent.nousresearch.com/docs/plugins/post-cortex)
- [Source code](https://github.com/julymetodiev/hermes-plugin-post-cortex#readme)
- [All plugins](https://hermeswatcher.com/plugins.md)

---

HermesWatcher is an independent guide. It is not affiliated with or endorsed by Nous Research. The [official Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs) and [repository](https://github.com/NousResearch/hermes-agent) from Nous Research are the authority; each page here lists the official sources it was written from. If this site and the official docs disagree, trust the official docs. Index for agents: https://hermeswatcher.com/llms.txt