fix(chat): route incident Ask AI through the tool-calling engine - #40
Merged
Merged
Conversation
The incident detail 'Ask AI' panel hit POST /api/v1/llm/ask — a single-shot completion with zero cluster context. 'How many pods are affected?' could only be answered with a request for kubectl output because the LLM had no pod data to ground on. Wire the panel onto the agentic POST /api/v1/chat engine (get_pods, query_prometheus, list_incidents, ...). The backend now accepts incidentId: the incident prompt + prior RCA summary are injected into the system context (identical to handleAsk's grounding) and the namespace defaults from the incident, so get_pods targets the right place. The panel renders tool chips and citations, persists the server-side conversation id alongside history, and aborts in-flight streams on unmount. Closes #39
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
1 participant
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.
The incident detail 'Ask AI' panel hit POST /api/v1/llm/ask — a single-shot
completion with zero cluster context. 'How many pods are affected?' could
only be answered with a request for kubectl output because the LLM had no
pod data to ground on.
Wire the panel onto the agentic POST /api/v1/chat engine (get_pods,
query_prometheus, list_incidents, ...). The backend now accepts incidentId:
the incident prompt + prior RCA summary are injected into the system context
(identical to handleAsk's grounding) and the namespace defaults from the
incident, so get_pods targets the right place. The panel renders tool chips
and citations, persists the server-side conversation id alongside history,
and aborts in-flight streams on unmount.
Closes #39