Hermes – full automata part 2

Another day, another problems to solve, probably I will put everything under that one topic. So far issues:

Supermemory

Self-hosted memory server on the host, Hermes in a container reaching it over the bridge gateway. Connection is green, but zero memories – embeddings run locally, while fact extraction needs an LLM provider key that never reached the process. The systemd unit was missing an EnvironmentFile directive.

Along the way: config had to go into the container’s Hermes home, not the host path that looked equivalent; doctor run as the wrong account gave misleading output; 404 from /health turned out to mean success. Auto-capture flushes only on clean session end, so sessions killed by budget exhaustion silently drop everything – explicit saves are the reliable test. Documents ingested before the key works are never reprocessed.

Still open: bridge IP → host.docker.internal, SDK persistence via pylibs + PYTHONPATH, and a real end-to-end recall test.

RTK

Important to add because Kanban eaten my weekly GLM tokens in 2 days :). Just recap from my notes:

Command-output filter that rewrites git status → rtk git status through a pre_tool_call hook. Now working on all profiles.

Three failures stacked. The distro’s /etc/profile wiped PATH in login shells, so the binary and the Hermes venv vanished for agent subprocesses. HOME turned out to differ per context — each profile has its own, and interactive shells use another. And the plugin registration is per profile, so the initial init covered only the default while everything else silently ran unrewritten commands.

Symptoms worth recognising: exit 127 means the hook fired but the binary isn’t on PATH; a plain unrewritten command means the profile lacks the config entry; empty stats usually means you’re reading a different home.

Side discovery: profiles were using system Python, not the Hermes venv — worth auditing for silent ImportErrors.

Register on every profile:

rtk init -g --agent hermes                        # default profile
for p in /opt/data/profiles/*/; do
  HERMES_HOME="$p" rtk init --agent hermes
done
grep -l rtk-rewrite /opt/data/profiles/*/config.yaml | wc -l   # expect number of profiles!!!

Re-run after every RTK upgrade.

Stats are per profile — “Global Scope” means all projects, not all homes:

for h in /opt/data/home /opt/data/profiles/*/home; do
  echo "== $h"
  HOME="$h" rtk gain
done

Open question: whether RTK adds anything over mvn -B -q plus an [ERROR] grep, since its filters target git, pytest, pip, ruff and docker.