chore(seer): Start sending category key over with investigations - #123364
chore(seer): Start sending category key over with investigations#123364wedamija wants to merge 1 commit into
Conversation
This should stop investigation runs showing up as chat sessions.
github-actions
Bot
added
the
Scope: Backend
vaind
left a comment
vaind
left a comment
There was a problem hiding this comment.
The category key is the right thing to send to Seer, but I don't think it fixes the sidebar on its own.
The Explorer session list is served from our local mirror, not from Seer: it queries /seer/runs/ with is:mine type:explorer (seerExplorerSessionContext.tsx). start_run mirrors every run as type=explorer and the category key only goes into the Seer request body, nothing on our side stores it.
Fixed the description, I've got a separate pr to help with the frontend: #123384 |
2 participants
Investigation runs currently start with no
category_key, so Seer treats every block run and title run as plain Explorer chat. Tag themcategory_key="investigation"(paired with the investigation id) so they drop out of the chat evals and are separable in chat-session agent monitoring.