Repository navigation
Description
Note
GPT-6 Astra on behalf of PsychedelicShayna
Contract
Use the chat frame for information-efficient native session status. Keep project/global context above and session-specific information near the docked composer. Move infrequent Full access/supervised controls into the header/configuration area instead of occupying the composer.
Acceptance
- Show model, reasoning effort, tokens per second, cache hit rate, context utilization and total thread cost from authoritative native observations; label unavailable/stale values honestly.
- Model/effort status controls open the native-equivalent selectors.
- Preserve useful context-window information rather than hiding it as a legacy feature.
- A bounded/truncated title leaves room for useful information; the full title remains accessible through existing sidebar detail/hover behavior.
- Permissions remain visible and reachable in the header without pretending to switch native ownership policy locally.
Coordinate with native session synchronization and the docked composer; do not create one extra button per native command.
Owner's words (verbatim)
2026-10-22 owner dictation — contiguous excerpt
Dock that thing and that model selector and that effort level. Those are status line components, now that I think about it. If I look at my current status line, which is built for information efficiency, more than anything else, not aesthetics. There's the session title, there's the branch, the hosting, blah blah blah, but then I have the thing, I have a section for the model, not the project. The project information and like, you know, global info I have above, and then the, the session specific info I have I have at the bottom. That's how I have it set up. GPT-6 Astra, extra high, so that's basically model, reasoning level. I have the tokens per second, a cash rate, a cash hit rate indicator, a context, context window percentage like visualization bar, and a total thread cost. Would that fit, and, and, and the UI, the GUI has this full access thing, like supervised. This should not be there because you're not gonna change your mind constantly about that. It should be like above. You should hide that in the top section somewhere. Like, you already created a button there for, called NeoPy session configuration, where you, you, you hid follow model changes. yeah, instead of adding a bunch of new buttons for every single thing that NeoPy has, the, the, the session title is up there. Huh. It kind of follows what I already have. The composer that I have, the status line that I have inside of NeoPy is kind of how it's structured inside of, inside of NeoCode. It's just that it has the thread in between the top and the bottom. I, okay, that's interesting. But it's basically true. And it would work. If you repeated the same thing, it would work. And the thread name is not so important that the thread, like, appears, that the full title appear at the very top. It can be truncated, it's fine, because you have the sidebar. The sidebar allows you to switch between threads, and when you hover over a thread, it shows you, like, a card, and that shows you the whole name, and it shows you, you know, the, the, the repository, it shows you the host, it shows you the model, it shows you all this information. All the additional information that you could put at the top of the bar, but you can't because it's being hidden by the title, maybe
Complete unedited message: #125 . The owner's words take precedence over this summary.
Activity
perf(rpc): omit prompt and tool dumps from status-only reads
feat(rpc): notify observers when native approval mode changes
fix(rpc): declare native session telemetry on the wire
merge(rpc): verify native usage and permission notifications
merge(rpc): retain telemetry with model configuration updates