State Management

State management tracks the context and progress of a conversation across multiple turns. It maintains information about what has been discussed, what decisions have been made, and where the user is in a multi-step process. This allows the AI to provide coherent, context-aware responses.

Interlocute uses threads to manage state. Each thread maintains the full conversation history and context. The platform automatically tracks message history, user inputs, and conversation flow, so your node always has access to the current state without manual state management.

Yes. Interlocute's thread-based state management is ideal for multi-step workflows. You can guide users through complex processes like onboarding, data collection, or troubleshooting, with the node remembering each step and adapting based on previous responses.

State management tracks the current conversation flow and immediate context within a thread. Memory stores information across threads and sessions for long-term recall. State is about workflow position; memory is about user history. Both work together.

Yes. Each thread is isolated with its own state. Different users or even the same user in different contexts can have multiple concurrent threads, each maintaining independent state and conversation history.

State is maintained automatically by Interlocute as part of the thread object. Each message in a thread is stored with its context, and the node has access to the full thread history when processing new messages. There's no manual state serialization required.

Yes. You can create new threads to branch conversations or fork existing threads to explore different paths. This is useful for scenarios like A/B testing conversation flows or letting users explore multiple options simultaneously.

State storage is included in the platform's thread management. There are no separate charges for maintaining conversation state. You only pay for token usage when the node processes messages.