You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TypeScript client already implements updateSession metadata and deleteSession, but the UI can only create, select, recover, and run Sessions. Users need bounded organization and cleanup without introducing product organizations or claiming physical data erasure.
Observable outcome: users can rename/update metadata and request deletion with deterministic behavior for current, inactive, missing, and active Sessions.
Acceptance criteria
Add an accessible Session details/action surface that supports title and string metadata editing.
Retrieve or reconcile the latest Session before submitting an update.
Preserve form input and current durable data when update fails.
Require explicit confirmation before delete and remove the Session from UI only after Core success.
On successful deletion of the selected Session, close/abort its SSE and pending reads, clear its Items/Turns/actions, and select the next deterministic Session or empty state.
Deleting a non-selected Session must not disturb the active stream.
Surface Core behavior accurately for active Session conflicts, missing Sessions, network errors, and repeated deletion.
Explain that Parsar deletion follows server lifecycle semantics and is not a promise of physical history erasure.
Never place credentials or secrets in Session metadata.
Add update/delete request, stale response, active stream, 404/409/503/network failure, confirmation, focus, and narrow-layout tests.
Keep feature code local and minimize App.tsx/style.css changes.
Validation
Run focused metadata and delete tests, including deleting selected/non-selected Sessions while SSE is connecting or active.
Context
The TypeScript client already implements updateSession metadata and deleteSession, but the UI can only create, select, recover, and run Sessions. Users need bounded organization and cleanup without introducing product organizations or claiming physical data erasure.
Observable outcome: users can rename/update metadata and request deletion with deterministic behavior for current, inactive, missing, and active Sessions.
Acceptance criteria
Validation
Non-goals
Dependencies
Start from current main after #3 is merged because both tasks touch stream/read cleanup in App.tsx.