feature: agentop observe — group sessions and cost by working directory

オープン
  • 何か問題がありますか？
#1,739 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
go
領域
analytics, cli

調査の方向性

Start with cmd/agentop/tui/sessions_pane.go, session_metadata.go, and sessions_title.go, then read the read-claude-sessions harvest in cmd/agentop/cmd_experimental.go and the Agents pane breakdown. The issue leaves key decisions open about directory source, grouping rules, changed working directories, and API exposure. Done means directory grouping and cost totals are available in the Sessions pane and agentop cost, with corresponding updates to cmd/agentop/README.md.

索引モデルが issue の本文から書いたものです。

説明

enhancement ux

Problem

agentop observe now shows the cost of each session, so it is easy to see which tasks cost the most. Answering "where did my tokens go this month?" still means adding up sessions by hand, because nothing groups them by the project they ran in. The working directory is the natural key for that: one repo or checkout is usually one project.

Today the directory only appears by accident. The Claude Code title harvest (~/.cortex/session-metadata.json) falls back to the working directory as a session's title when the transcript has no model-generated one, so some rows show a path in TITLE and others don't. Codex, Bob, OpenCode and Pi sessions show no directory at all.

Proposal

Record each session's working directory and let the viewer group and total by it:

  • A DIR (or PROJECT) column in the Sessions pane, separate from TITLE.
  • A way to group or scope by directory, like the Agents pane does by agent: one row per directory with SESSIONS, LAST SEEN and COST <window>, and ↵ scopes sessions, usage and the $ band to it.
  • The same breakdown in agentop cost, so a monthly total per directory can be scripted.

Open questions:

  • Where does the directory come from per agent? Claude Code records cwd in its transcripts (the title harvest already reads them). Codex records it in its session files. For other agents it may need the process's cwd, looked up from the pid the proxy already attributes calls to.
  • Group by the exact path, or by repository root (so repo/ and repo/sub/ count together)? Worktrees under .claude/worktrees/ probably belong with their repo.
  • A session whose directory changes partway through (cd in a shell agent): first directory, or last?
  • Is the path sensitive enough to keep out of the session API by default? It is already in session-metadata.json for Claude Code.

Context

Requested in #cortex-community by @vinodmut (2026-11-09), who uses the per-session cost to compare models and agents (Codex vs Claude Code) and to account for monthly token use.

Where it lives

  • cmd/agentop/tui/sessions_pane.go, session_metadata.go, sessions_title.go
  • cmd/agentop/cmd_experimental.go (read-claude-sessions harvest)
  • The Agents pane, as the model for a per-directory breakdown
  • cmd/agentop/README.md: the Sessions pane section and the column table

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

主要言語
Go
スター
26
フォーク
46
平均マージ
13時間 49分
マージ済み PR（30日）
244

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

rossoctl/cortex のほかの issue

rossoctl/cortex の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。