Skip to content

fix(tui): move KV-persisted toggles from Session to System category#167

Open
ariane-emory wants to merge 5 commits intodevfrom
feat/command-palette-consistecy
Open

fix(tui): move KV-persisted toggles from Session to System category#167
ariane-emory wants to merge 5 commits intodevfrom
feat/command-palette-consistecy

Conversation

@ariane-emory
Copy link
Owner

@ariane-emory ariane-emory commented Feb 13, 2026

What does this PR do?

Move four command palette items that persist via KV store and that last through changes in sessuin to the System category for consistency:

  • Show/Hide timestamps
  • Show/Hide thinking
  • Show/Hide tool details
  • Show/Hide header

These toggles persist across sessions, so they belong in System rather than Session group and should be available for use before a session has been started by sending a message.

Resolves #158

How did you verify your code works?

Manual A/B testing, bun typecheck, bun test.

Move four command palette items that persist via KV store from the
session route to the app level so they are available at all times:

- Show/Hide timestamps
- Show/Hide thinking
- Show/Hide tool details
- Show/Hide header

These toggles persist across sessions via kv.json, so they belong in
the System category and should be accessible even before a session starts.

Resolves #158
@ariane-emory ariane-emory force-pushed the feat/command-palette-consistecy branch from 62cfb68 to b02e276 Compare February 13, 2026 02:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve consistency/clarity by moving the remaining session-agnostic KV-persisted toggles to the System category

1 participant