feature: agentop observe — search user prompts and agent responses across a session's events

Abierto
  • ¿Algo no está bien?
#1,680 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@huang195 ya está trabajando en esto.

Desde el 7/11/2026.

  • #1713 de @huang195 — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement ux

Problem

In agentop observe, / searches only what a pane displays. On the events pane that's the table columns (host, method, plugin, and so on), not what the user typed or what the agent answered. Message text is searched only inside an event's detail, after you open it. There's no way to find the turn that contained a given prompt or reply without opening events one by one.

This was deliberate (#1339, and the README note on ?view=summary): the events list fetches summaries without conversation bodies, which makes sessions open about 163x faster.

Proposal

Add a way to search the conversation text of a session (user prompts and agent responses, maybe tool inputs/outputs) and land on the matching event.

Possible shapes:

  • A separate key on the events pane that searches message bodies. The proxy could answer it server-side, for example GET /v1/sessions/{id}/events?q=… returning matching seqs, so the list keeps fetching summaries.
  • The same search across sessions on the sessions pane ("which session did I ask X in?").

Open questions:

  • Server-side search over in-memory and archived (on-disk) sessions, or client-side after fetching full events on demand?
  • What text counts: only the newest user message and the completion, or the whole request payload? Matching the whole history would hit every later turn.
  • How to mark matches in the table, since it doesn't render bodies.

Context

Requested in #cortex-community by @vinodmut (2026-11-06).

Where it lives

  • cmd/agentop/tui/search.go, search_surfaces.go, events_pane.go
  • the session events API (/v1/sessions/{id}/events) if the search runs in the proxy
  • cmd/agentop/README.md: the / row in Keybindings and the summary-view note

Assisted-By: Claude (Anthropic AI) [email protected]

Lenguaje dominante
Go
Estrellas
23
Forks
44
Merge medio
14 h 38 min
PR fusionados (30 d)
254

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de rossoctl/cortex

Todos los issues de rossoctl/cortex

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.