Skip to content

Audit app performance and terminal usability; prioritize an evidence-backed roadmap #1180

Closed

Description

@currentbits

Requested audit of current Solenta performance bottlenecks and view usability, with particular attention to the Terminal pane. Scope: inspect current implementation, reproduce concrete defects or measure hot paths, check existing GitHub issues for duplicates, and publish prioritized implementation issues with acceptance criteria. This issue tracks the audit only; resulting implementation issues stay plan:todo until work begins.

Audit baseline: checkout 9fc8645, 2026-09-10. No product implementation is included in this audit.

Activity

  1. added and removed on Sep 10, 2026
  2. currentbits commented on Sep 10, 2026

    @currentbits
    OwnerAuthor

    Audit complete. Published six implementation issues through the host coder-threads issue_create tool; all remain plan:todo.

    Recommended order

    1. P1: Compute transcript provenance in one pass to avoid streaming UI stalls #1181: P1 transcript provenance CPU work. Synthetic near-cap benchmark: 78.2 ms for 1,001 messages; smaller fixtures show quadratic scaling.
    2. P1: Isolate terminal replies, drafts and command history when switching threads #1182 and P1: Bind terminal sessions to the current worktree and clean up removed threads #1183: P1 terminal thread/session ownership and lifecycle. Fix these foundations before expanding terminal behavior.
    3. P1: Upgrade Terminal from a piped command box to an interactive worktree terminal #1184: P1 interactive PTY terminal: normal keyboard input, completion, Ctrl-C, colors, resize, bounded streaming and packaged-build validation.
    4. P2: Search terminal output and send selected failures into the composer #1185: P2 terminal Find/Clear/selection-to-composer. Coordinate with P1: Upgrade Terminal from a piped command box to an interactive worktree terminal #1184's renderer to avoid implementing the same UI twice.
    5. P2: Load the full active Planboard backlog without fetching all completed history #1187: P2 Planboard fetch volume and first-content latency. Current snapshot fetched 950 issues, including 756 Done candidates for 25 visible Done cards.

    Evidence and verification

    • Read current renderer, terminal backend, IPC, session cleanup, store, streaming and Planboard paths. Fetched origin/main bf6fb02; relevant implementations match checkout 9fc8645.
    • Actual TerminalPane DOM-harness checks reproduced late A write contaminating B output and A command history appearing in B.
    • Actual terminal module with fake child reproduced retaining the original root after opening the same thread with a different root.
    • Provenance timing called the actual function with synthetic 251/501/1,001-message fixtures. This is not an end-to-end desktop profile; no live user transcript or other project's data was published.
    • Existing store sharding, lazy hydration, throttled streaming and DOM windowing are present; did not recreate their older issues.
    • Overlapping terminal reads duplicate scrollback on slow connections #934 already tracks same-session duplicate terminal deltas and is closed with a merge comment. The audited baseline still contains the old polling implementation, so confirm its integration before changing that path. No duplicate issue was filed.
    • Existing Find in the current transcript (Cmd+F), not just the sidebar #486 (find in transcript) and Copy this turn / last reply, like CLI /copy #493 (copy turn/reply) remain useful view improvements; reused their references rather than recreating them.

    This closes the audit only. No app code was changed and no implementation issue is marked complete. Each new issue contains source links, scope, acceptance checks and relevant dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions