agenthub · memory.write
Memory Write
Persist this turn — the user's message and the assistant's reply — back to the memory service. It acts rather than computes, so it is triggered by a flow edge.
Why the node earns its place
The write half. It has nothing to hand onward, so it has no output ports at all; what it needs is to run after the reply exists. That is what the flow edge is for — wire it from the LLM's flow port, then wire the two texts in as data.
How it works at run time
- 1Wait for the flow trigger.
- 2Take the user text and the assistant text from their wired inputs.
- 3Append the turn. On failure, log and do nothing — memory must never block the chat path.
What you wire
Inputs
- trigger *flow
- user_textstring
- assistant_textstring
Outputs
Nothing handed onward.
Configuration
Nothing to configure — this node has no settings of its own.
What usually goes wrong
Watch for this
Forgetting the flow edge is the classic error: the node has no data dependency forcing it to run last, so without the trigger it may run before there is a reply to store, or not at all. If you want this wiring without the wiring, use LLM with Memory.
Behaviour & provenance