sublime-rs/sessions
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 86 Wiki Activity

Phase 3: agent window prototype (session list, activity log, editor split) #8

New Issue
Closed
opened 2026-04-11 18:15:52 +09:00 by mschoi · 1 comment
mschoi commented 2026-04-11 18:15:52 +09:00
Owner
Copy Link

Goal

Prototype the long-term Sessions UI: multiple remote sessions, activity/chat-style summaries, and an editor area in one workflow.

Implementation Checklist

  • Define the first agent window layout
  • Build a session list sourced from recent metadata
  • Build an activity timeline / chat-like panel for one selected session
  • Show structured summaries of helper / CLI actions instead of raw terminal spam
  • Provide an editor split or fast jump into the relevant file
  • Show proposed changes as diff when possible
  • Define how directory browsing is exposed next to editor content
  • Define what happens when a selected session is offline or stale

Edge Cases and Test Scope

  • Very long activity histories
  • Session selected but no cache exists yet
  • Session selected from a different local host with shared cache
  • Diff proposal available but source file changed since proposal generation
  • Two sessions point to the same remote root with different profiles

Manual UI / Product Decisions

  • Left pane: sessions
  • Center pane: activity/chat summary
  • Right pane: editor and file tree
  • Prefer summary-first over terminal-first presentation
  • Avoid trying to rebuild the full VS Code workbench in the first prototype

Current Status

  • Completed in commit: 6286f14
  • Done: UI-free agent window layout models, recent-session list state, structured timeline/chat entries, helper/CLI action summaries, editor jump targets, diff proposal references, directory pane descriptors, and offline/stale-session state handling
  • Edge/test coverage now includes long-history trimming, missing-cache session selection, shared-cache sessions from another local host, stale diff proposals after source changes, and same-remote-root sessions with distinct profiles
  • Remaining: actual Sublime pane/widget wiring, persisted activity logs, live connection presence detection, and rendered diff/editor integration
## Goal Prototype the long-term `Sessions` UI: multiple remote sessions, activity/chat-style summaries, and an editor area in one workflow. ## Implementation Checklist - [x] Define the first `agent window` layout - [x] Build a session list sourced from recent metadata - [x] Build an activity timeline / chat-like panel for one selected session - [x] Show structured summaries of helper / CLI actions instead of raw terminal spam - [x] Provide an editor split or fast jump into the relevant file - [x] Show proposed changes as diff when possible - [x] Define how directory browsing is exposed next to editor content - [x] Define what happens when a selected session is offline or stale ## Edge Cases and Test Scope - [x] Very long activity histories - [x] Session selected but no cache exists yet - [x] Session selected from a different local host with shared cache - [x] Diff proposal available but source file changed since proposal generation - [x] Two sessions point to the same remote root with different profiles ## Manual UI / Product Decisions - [x] Left pane: sessions - [x] Center pane: activity/chat summary - [x] Right pane: editor and file tree - [x] Prefer summary-first over terminal-first presentation - [x] Avoid trying to rebuild the full VS Code workbench in the first prototype ## Current Status - Completed in commit: `6286f14` - Done: UI-free agent window layout models, recent-session list state, structured timeline/chat entries, helper/CLI action summaries, editor jump targets, diff proposal references, directory pane descriptors, and offline/stale-session state handling - Edge/test coverage now includes long-history trimming, missing-cache session selection, shared-cache sessions from another local host, stale diff proposals after source changes, and same-remote-root sessions with distinct profiles - Remaining: actual Sublime pane/widget wiring, persisted activity logs, live connection presence detection, and rendered diff/editor integration
mschoi added this to the Phase 3 - Agent Window Prototype milestone 2026-04-11 18:15:52 +09:00
mschoi commented 2026-04-11 21:52:16 +09:00
Author
Owner
Copy Link

Completed the Issue #8 prototype model layer in commit 6286f14.

Added the first agent-window layout, session list and selection state, activity/chat timeline models, structured helper/CLI action summaries, editor jump targets, diff proposal references, directory-pane descriptors, and offline/stale-session handling. Added tests for long-history trimming, no-cache sessions, shared-cache sessions from another local host, stale diff proposals, and same-remote-root sessions with different profiles. Closing this issue with concrete Sublime UI wiring left as follow-up work.

Completed the Issue #8 prototype model layer in commit `6286f14`. Added the first agent-window layout, session list and selection state, activity/chat timeline models, structured helper/CLI action summaries, editor jump targets, diff proposal references, directory-pane descriptors, and offline/stale-session handling. Added tests for long-history trimming, no-cache sessions, shared-cache sessions from another local host, stale diff proposals, and same-remote-root sessions with different profiles. Closing this issue with concrete Sublime UI wiring left as follow-up work.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone Phase 3 - Agent Window Prototype
Projects
Clear projects
No project
Assignees
Clear assignees
mschoi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sublime-rs/sessions#8
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?