Fix WebMCP repository-first workflow - #62
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6de7c32fd1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| repositorySelect?.addEventListener('change', () => { | ||
| if (currentHandoff) clearPublishedHandoff('Repository selection changed. Press Send again before the agent receives a new handoff.'); | ||
| const skillWasCleared = clearSelectedSkill(); |
There was a problem hiding this comment.
Clear stale output when changing repositories
After a skill has been selected or a handoff has been sent, changing the repository clears selectedName and invalidates the tool but leaves [data-webmcp-output] displaying the previous repository, skill, or full handoff. The page can therefore show the new repository alongside an obsolete SELECTED REPOSITORY → SKILL or HUMAN → AGENT HANDOFF record; reset or replace that output as part of this invalidation.
Useful? React with 👍 / 👎.
What changed
Verification
git diff --checknode --check src/assets/js/webmcp.jsnode --check tests/site.spec.mjsnode --test tests/webmcp.test.mjs— 7/7 passedUsage
Open
/webmcp/, choose the target repository, then choose how the agent should work, state the outcome, and press Send. Changing the repository requires choosing the skill again.hmmm
The new browser-path test is committed for the repository's authoritative CI/browser gate; focused local checks pass.