Conversation
The active-agents view already showed sessions and repo changes, but it hid file-lock ownership and offered no conflict signal when repo-root edits were claimed by another branch. This change caches the lock registry per repo, appends lock counts to session rows, warns on foreign-branch locks in repo-root changes, refreshes that cache from lock-file watcher events, and keeps the lock registry file itself out of the CHANGES tree. Constraint: Repo-root change warnings compare against the repo worktree's current branch, because CHANGES rows belong to that checkout rather than an arbitrary active session Rejected: Re-read the lock file inside every getChildren() call | repeated IO on tree expansion with no freshness benefit over watcher events Confidence: high Scope-risk: narrow Directive: Keep runtime and template VS Code extension copies in sync whenever the tree-provider data model changes Tested: node --test test/vscode-active-agents-session-state.test.js; openspec validate agent-codex-vscode-tree-lock-decorations-clean-2026-04-22-11-09 --type change --strict Not-tested: Interactive rendering in a real VS Code window
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.
Automated by gx branch finish (PR flow).