Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
max(updated, viewed)), and always keep the session in view listedopenor the last-used age (5m,3h,2d) beside each idle session, with the spinner for running onessession.created,session.renamed,session.deletedandsession.idleValidation
npm ci --ignore-scriptsnpm test(tsc, against@opencode/plugin2.0.14)npm run buildproducesdist/tui.jsdist/tui.js: the plugin id resolves andorderSessionsorders open tabs ahead of recent sessionsNot yet checked: a live sidebar run in OpenCode 2.0.14 on this branch.
Possible improvements
orderSessionsandageare pure but have no unit tests;npm testonly typechecks.session.idleevent refetches the list. A debounce, or patching the one changed session fromdata, would cut requests in busy workspaces.agelabel only updates when the list re-renders for another reason, so it can go stale.RECENT_LIMIT(8) and the 26-character title cut-off are hard-coded.running, so the oldretryindicator is gone. It can come back if the API exposes that state again.