rossoctl / rossoctl/cortex

Feedback: [Sessions] Pipeline picker ID column confusing

Open
#1,008 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feedback laptop
Dominant language
Go
Stars
13
Forks
40
Avg merge
12h 17m
Merged PRs (30d)
156

Description

What kind of feedback is this?

Something was confusing

What happened, and what did you expect?

The [Sessions] Pipeline screen is confusing:

abctl · http://127.0.0.1:47601 · [Sessions] Pipeline                                             
 ID                                        UPDATED         EVENTS    TOKENS      ACTIVE          
 bcc20b29-cbf1-48d7-b213-8556971f00ca      just now        45        319,508     ●               
 6b8d5530-9af2-44c3-9d3e-02ddbaa352c6      26s ago         500       12,687,236                  
 b65456a9-aa02-46a2-b25b-1b9e9d69f9cd      13h ago         500       —                           
 391b3d09-ff48-4cda-acd6-c8fc5a2c2d6d      Sep 15 11:01    40        86,431                      
 5148ef58-027f-49ff-8c7c-aa50ff9e4821      Sep 15 09:21    500       —                           
 6ffd43c2-b91a-479b-9be2-2526dbe4dc42      Sep 15 07:29    479       175,615                     
 default                                   Sep 14 19:11    21        —                           

I know this screen only refers to one authbridge-proxy, but I don't understand what the IDs refer to. I first thought it was Authbridge-Proxy IDs. Then I suspected Claude harnesses.

Although the column is titled ID it would be better if it indicated what kind of ID it was.

The ID is also very long. It is a globally unique UUID. It might be better as six hex digits, or even a randomly generated two-word name.

It would be good to include COST, if it can be calculated, in addition to TOKENS.

I don't understand what ACTIVE means. One of these Sessions/Pipelines is only 26 seconds old, but it is not active.

Operating system and architecture

Darwin arm64

Agent and model

Claude code, sonnet I guess

Cortex version

dev

Service status and logs

Did anything else on your machine change?
  • git, gh, ssh or curl stopped working after I installed Cortex

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start from the [Sessions] Pipeline screen shown in the report and determine what the ID and ACTIVE columns represent. Review the requested shorter identifier, clearer labeling, and optional COST value as one coherent UI change; done means the screen's session information is unambiguous and the requested display improvements are addressed.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.