[taciturnaxolotl]

Adds the honcho memory integration with full oauth support

[porkloin]

@taciturnaxolotl I've been running this patch on a locally built crush with my self-hosted Honcho v3. One bug I encountered was Service.lookup() sending peer_perspective with an empty peer_target. The session context endpoint has no "self" default like the dialectic chat path does, so Honcho returns 422 (peer_target must be provided if peer_perspective is provided). The symptom is that memory recall silently never injects anything. The failure only shows up in the failure log, so nothing looks wrong from the UI.

I've been running a local patch on top of yours that sets PeerTarget to the user peer in the lookup, plus a case in the fake Honcho in service_test.go mirroring Honcho's validation so it stays fixed. Happy to PR it, if it's helpful! Thanks for putting this together, it's super useful.

[taciturnaxolotl]

I'm so glad its been working well for you! I added your patch to the pr so let me know if that works for you

[vshulcz]

While wiring a local agent.Memory backend on top of this branch, I ran into two small issues in the prompt/skill wiring:

1. prompt.WithFeatures(c.liveMemoryFeatures) is only evaluated when prompt.Build runs inside buildAgent at startup. When memory is connected or disconnected mid-session (UpdateModels -> updateAgentModels), SetMemory and SetTools run on the active agent, but SetSystemPrompt is never rebuilt (and the inactive agent in c.agents keeps its old Memory until a mode switch). Connecting mid-session attaches the Honcho tools while leaving honcho-memory out of the system prompt until restart, and disconnecting leaves honcho-memory advertised in the prompt after the tools are removed.
2. agentTool (internal/agent/agent_tool.go:33) passes prompt.WithFeatures(c.liveMemoryFeatures) to taskPrompt, even though buildTools skips attaching honcho_* tools when isSubAgent is true (coordinator.go:1007), so the task sub-agent gets the honcho-memory skill in its prompt without the tools it documents.

Fix for both is in vshulcz@ac0fc11, and the read-only local deja backend (Snapshot via deja orient, Recall via deja recall, no-op Record* like readOnlyMemory) is on top of it at vshulcz@2a54d59 if useful.