feature: agentop observe — search user prompts and agent responses across a session's events
维护者通常 1 天内回复
评估
这个 Issue 还没有评估数据。
描述
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]
- 主要语言
- Go
- 星标
- 23
- 派生
- 44
- 平均合并
- 14 小时 38 分钟
- 30 天内合并 PR
- 254
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
rossoctl/cortex 的其他 Issue
-
feature: let `session.archive` set where it writes, so a second Cortex can keep its own sessions未关闭enhancement
难度 4/5 3-5 天 新手友好度 54/100
维护者通常 1 天内回复
-
feature: agentop observe — show a request and its response as one row可能已有人在做 @huang195 今天认领。 未关闭enhancement ux
rossoctl/cortex#1681 · 已指派 1 人 ·
维护者通常 1 天内回复
-
feedback laptop
难度 5/5 一周以上 新手友好度 28/100
维护者通常 1 天内回复
-
chore: Remove the decline_responses_websockets translation after a deprecation release可能已有人在做 @Alan-Cha 于 4 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 55/100
rossoctl/cortex#1625 · 已指派 1 人 ·
维护者通常 1 天内回复
-
agentop configure codex/opencode can wait on itself when an agent runs it可能已有人在做 @Alan-Cha 于 10 天前认领。 未关闭
rossoctl/cortex#1530 · 已指派 1 人 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 78/100
router-for-me/CLIProxyAPI#7330 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
bug os:ios
难度 2/5 1-3 小时 新手友好度 72/100
hajimehoshi/ebiten#4039 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 9 天内回复