Repository navigation
Replies: 4 comments 3 replies
|
Yes! I also opened a discord thread for this. |
|
If I'm right, this was merged in #3603, should it be labelled somehow or closed? |
|
Mark as unread shipped in v0.8.0. Open the workspace menu in the sidebar on a finished workspace and choose Mark as unread, and its green attention dot comes back so the workspace stays in your queue. Leaving the workspace keeps the mark. Reopening it or interacting with the chat clears it, the same way ordinary completion attention clears today. The action needs the app and the daemon both on 0.8.0. Against an older daemon the menu item is hidden. @evankford you read it right, #3603 is the change. Thanks @edihasaj for describing the workflow here and then building it. |
|
Returning to a workspace you marked unread gets a fix in #7608. After you close and reopen the app, that workspace will load its chat and current history instead of getting stuck loading with extra Files and Changes tabs. Until then, reselecting the agent tab restores the chat in this case. Thanks for describing the save-for-later workflow. The fix is merged and will be in the next release. The current stable, v0.12.0, and latest beta, v0.13.0-beta.1, do not contain it; the next version number is not decided yet. Watch Releases if you want it sooner, since changes often appear in a beta before the stable release. |
Uh oh!
There was an error while loading. Please reload this page.
What am I trying to do
I sometimes open a finished workspace to quickly check what the agent did, then realize I cannot review or act on it yet. I want to put it back into my attention queue so I remember to return to it later.
How I do it today
I leave the workspace open, pin it, or create a reminder elsewhere. None of those restores the unread signal that originally told me the agent was ready for review.
Where Paseo gets in the way
Opening the workspace clears its unread attention state. Once I have glanced at it, there is no way to restore that state, so the workspace can blend into the rest of the finished work and be forgotten.
What would the flow look like if it worked for me
A read, finished workspace has a Mark as unread action in the same context menu that currently shows Mark as read for unread workspaces. Selecting it restores the normal finished/unread attention state and puts the workspace back where unread finished work appears. Opening it again marks it read through the existing flow.
This is the inverse of the existing Mark as read action and complements the acknowledgement workflow discussed in #2807.
All reactions