Skip to content

feat(cmd): ux feedback - #1051

Merged
rektdeckard merged 10 commits into
mainfrom
tobiasfried/ocd-3469-cli-ux-feedback
Oct 20, 2026
Merged

rektdeckard merged 10 commits into
mainfrom
tobiasfried/ocd-3469-cli-ux-feedback

Conversation

@rektdeckard

@rektdeckard rektdeckard commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

Implement some UX feedback on CLI commands:

  • Support natural language query ranges with the --since flag (--since 2w as an alternative to --start 2026-10-02)
  • Sets default query window for analytics commands to 14 days instead of 24 hours
  • Increases default page size for observability objects from 50 -> 1000 Remove client-side default page size; server currently uses a default of 1000 when unset.
  • Makes the output of lk analytics session transcript match the live transcript output when running lk agent console, lk agent debugger
  • Standardize the --json output of some experimental commands (consistent way of showing pagination, prefer raw response shapes to something made-up)
  • Sets default --type=audio for lk analytics session recording and handles file name collisions
  • By default, lk analytics session recording only prints the presigned URL. With --output it saves the file.
  • Updates charm.land/bubbletea package to fix issue with form output not being cleared from the terminal

@JackNDwyer

Copy link
Copy Markdown
Contributor

Me and claude went through

Two things:
(1) With --quiet, recording prints nothing, and now that filenames get numbered, scripts can’t tell where the file went. Is it reasonable for the path to go to stdout?
(2) I know we discussed max query return lengths. Is 1000 per page safe for aggregator, given the 64 MB cap and Kuba’s get-traces OOM? If not, maybe a lower default with a 1000 max?

@Topherhindman

Copy link
Copy Markdown
Contributor

Me and claude went through

Two things: (1) With --quiet, recording prints nothing, and now that filenames get numbered, scripts can’t tell where the file went. Is it reasonable for the path to go to stdout? (2) I know we discussed max query return lengths. Is 1000 per page safe for aggregator, given the 64 MB cap and Kuba’s get-traces OOM? If not, maybe a lower default with a 1000 max?

yeah 1000 is safe. https://live-kit.slack.com/archives/C02RXL72MQA/p1792097914902789

Comment thread pkg/public/render/analytics.go Outdated
Comment thread cmd/lk/analytics.go Outdated
@rektdeckard
rektdeckard force-pushed the tobiasfried/ocd-3469-cli-ux-feedback branch from 0f6680e to efbd56e Compare October 19, 2026 23:52
@rektdeckard
rektdeckard merged commit 49dca2e into main Oct 20, 2026
26 checks passed
@rektdeckard
rektdeckard deleted the tobiasfried/ocd-3469-cli-ux-feedback branch October 20, 2026 00:07
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.

3 participants