Stop leaving your Agent stateless. Give it Threads in one hook. Resumable conversations that capture everything: messages, generative UI, shared state, human-in-the-loop workflows. Built on AG-UI, so it works with any compatible agent framework. docs:

CopilotKit threads enable persistent, resumable multi-turn conversations. The useThreads hook lists, creates, renames, archives, and deletes threads with realtime synchronization via WebSocket. Threads work with any agent framework — and we store conversation history server-side, so users can close their browser and pick up where they left off. Thread metadata updates (renames, archives, new threads) are pushed to all connected clients in realtime without polling. With the open source, thread retention is up to 3 days. For more, check out our other plans for 5, 14, custom number of days! As always, our open source is number one 👇

stateful threads are the right primitive. the next missing layer is knowing which workflow or skill quietly degraded after the thread got long. building for that.

I know what Im doing this weekend...!

Stateless agents are not always the problem. Many Base agent loops stay reliable without forcing threads into every workflow.

I had the same idea yesterday about this, crazy

What was your idea?

i will not tell you because mine is better and im building it haha