Per-User Workflow Example

Why it matters

A server that holds state for many users must keep one user’s state out of another’s. The Agent Toolkit’s per-user workflow pattern scopes function instances to a session, and this example shows that isolation from the outside.

What to practise

Start the workflow with nat serve, then send /generate requests with curl under two nat-session cookies. Add a note as one user and list notes as the other; set a preference for one and read the default for the other. Read how the functions are registered with @register_per_user_function, and what per_user_workflow_timeout and per_user_workflow_cleanup_interval mean for state an inactive user leaves behind.

How it fits

This is the session scope of 5.4.3. Compare it with the user-scoped store 5.4.3 uses for data that must outlive a session, and with 5.4.1’s split between execution state and retained knowledge.