Restore card rendering, maintain conversation history, and rename placeholder#590
Merged
Conversation
RunHandler (/agent/run) now creates a Flow on every query. The response includes flow_id so the client can chain follow-ups via context_id. Sessions appear in the agent history at /agent. RunRequest gains context_id field. RunResponse gains flow_id field. The Flow is saved with status "done", the answer text, tool steps, and parent_id for chaining. Console JS tracks currentFlowId — first question creates a new session, follow-ups send the previous flow_id as context_id so the agent can see the conversation chain. Refreshing the page starts a new session (currentFlowId resets). Existing sessions are browsable at /agent.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RunHandler (/agent/run) now creates a Flow on every query. The response includes flow_id so the client can chain follow-ups via context_id. Sessions appear in the agent history at /agent.
RunRequest gains context_id field. RunResponse gains flow_id field. The Flow is saved with status "done", the answer text, tool steps, and parent_id for chaining.
Console JS tracks currentFlowId — first question creates a new session, follow-ups send the previous flow_id as context_id so the agent can see the conversation chain. Refreshing the page starts a new session (currentFlowId resets). Existing sessions are browsable at /agent.