Skip to content

feat(status): restore state across restarts + sidebar workflow-state grouping - #421

Draft
dkattan wants to merge 2 commits into
eneskirca:mainfrom
dkattan:feat/restore-agent-status
Draft

feat(status): restore state across restarts + sidebar workflow-state grouping#421
dkattan wants to merge 2 commits into
eneskirca:mainfrom
dkattan:feat/restore-agent-status

Conversation

@dkattan

@dkattan dkattan commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Two related changes to agent-status / sessions-sidebar behavior:

fix(sidebar): group by workflow state

Keep unread as a row-level notification affordance instead of a workflow bucket. Finished unread sessions remain under Done, and unknown unread sessions remain under Unknown — rather thanunread pulling rows into a separate bucket.

feat(status): restore state across restarts

Keep a lifecycle-bound display snapshot while operational evidence still expires. Reconcile Claude/Gemini transcripts and Codex app-server status without letting restored state drive notifications or process control.


Draft — opening for early visibility. Builds on the current main (6476c894).

🤖 Generated with Claude Code

Keep unread as a row-level notification affordance instead of a workflow bucket. Finished unread sessions remain under Done, and unknown unread sessions remain under Unknown.
Keep a lifecycle-bound display snapshot while operational evidence still expires. Reconcile Claude/Gemini transcripts and Codex app-server status without letting restored state drive notifications or process control.
@eneskirca

Copy link
Copy Markdown
Owner

Checking in on this draft — a quick status of where main has moved since your base, so effort doesn't go where it's already spent:

  • The grouping half is now main's model. The sidebar settled on three workflow-state sections (Waiting for your response / Running / Unknown), with unread as a row-level affordance that NEVER changes the bucket — CLAUDE.md pins it in exactly your framing ("a click may clear the glow but cannot move the row"). So that half of the draft describes behavior main already ships.
  • The restore-state-across-restarts half is still open and still interesting — nothing on main persists a display snapshot across app restarts (live state is deliberately transient), and the constraint you set (restored state must never drive notifications or process control) is the right one. It also touches a documented gap: Eco hibernation is structurally inert for sessions with no turn in the current app run, and a reconciled snapshot is one of the plausible fixes.

Are you planning to carry this forward? If so, trimming it to just the restore/reconcile half and rebasing onto current main would make it reviewable — happy to give it a full pass then. If it's parked, no problem, just say so and we'll treat it as a design note.

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.

2 participants