hermes-agent

Files

T

Erosika 21180ae7e8 feat(honcho): rework the setup wizard's gateway mapping step around Honcho's peer model

The step declares its scope up front: human mapping only, with each
Hermes profile bringing its own AI peer. A note explains aliases as
the join between platform accounts and named peers. Each shape now
says when it fits. Fresh configs default the choice to [1] single
peer — the common personal setup — instead of [3], which silently
fragmented a solo operator's gateway account away from their
peerName history. Configured setups keep their detected shape as
the default.

2026-09-13 19:05:39 +05:30

byterover

refactor(memory-plugins): background threads inherit the profile context; JSON sidecar reads and the holographic config.yaml write use core primitives

2026-09-13 05:19:48 -07:00

hindsight

fix(hindsight): corrupt config.json falls through to the legacy file and env, as before

2026-09-13 05:19:48 -07:00

holographic

refactor(memory-plugins): background threads inherit the profile context; JSON sidecar reads and the holographic config.yaml write use core primitives

2026-09-13 05:19:48 -07:00

honcho

feat(honcho): rework the setup wizard's gateway mapping step around Honcho's peer model