Conversation state
Each time an agent completes successfully, the conversation state is encrypted and stored in Search2o Cloud. A follow-up query in the same conversation restores the state and runs the selected agent with that context.
What the state holds
- The runs so far: which agent ran, with which inputs, what the agent output, and where the agent paused when the run paused on
ask. - The prompts: for each named prompt, the system text and the full history of user turns, assistant answers and tool results. This history is why an LLM in a follow-up remembers the earlier exchange.
- The conversation variables (
conv.), shared by every agent in the conversation. - The agent variables (
agent.) of every agent that has run in the conversation.
Agents see the state only through these variables and prompts. Local variables are not kept.
When state is saved
State is saved when a run ends with end, with return from main, or by pausing on ask. State is not saved when the run ends with fail or with an error. A follow-up therefore sees the state as it was before the failed run.
Encryption
State is encrypted before the state leaves the agent server, and the cloud never decrypts the state. By default Search2o manages the key for your account. An administrator can switch to keys held entirely in your organization. See Security.
Retention
A conversation is deleted after a period without use: 7 days on the Free plan, 90 days on the Paid plan, counted from the last time an agent ran in the conversation or the conversation was read, whichever is later. A user can pin a conversation to keep the conversation, and can delete a conversation at any time.

