You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m implementing a Gemini/Claude-style multi-session chat UI with CopilotKit on the frontend and FastAPI +
pydantic-ai on the backend. Current endpoints:
GET /api/sessions returns the list of recent sessions (id + title).
GET /api/sessions/:sessionId loads persisted key-value blobs for a given session (messages, agent state, etc.).
Questions
When the user navigates to /chat/:threadId, what is the recommended way to hydrate CopilotKit with the saved
agent state and messages returned by /api/sessions/:sessionId?
For a brand-new session (/chat without a threadId), how should the frontend obtain the thread id that
CopilotKit generates after the first message reaches the backend?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I’m implementing a Gemini/Claude-style multi-session chat UI with CopilotKit on the frontend and FastAPI +
pydantic-ai on the backend. Current endpoints:
GET /api/sessionsreturns the list of recent sessions (id + title).GET /api/sessions/:sessionIdloads persisted key-value blobs for a given session (messages, agent state, etc.).Questions
/chat/:threadId, what is the recommended way to hydrate CopilotKit with the savedagent state and messages returned by
/api/sessions/:sessionId?/chatwithout athreadId), how should the frontend obtain the thread id thatCopilotKit generates after the first message reaches the backend?
Beta Was this translation helpful? Give feedback.
All reactions