Add support for new vscode "steer" message#769
Open
mubaidr wants to merge 13 commits intogithub:stagedfrom
Open
Add support for new vscode "steer" message#769mubaidr wants to merge 13 commits intogithub:stagedfrom
mubaidr wants to merge 13 commits intogithub:stagedfrom
Conversation
- Remove redundant `<mission>` section from gem-browser-tester - Add "Reflect" step to gem-documentation-writer for self-review on high-priority or failed tasks - Refactor gem-orchestrator completion phase to generate a walkthrough markdown file instead of a review - Update orchestrator rules to allow direct execution for creating walkthrough files
github-actions
bot
force-pushed
the
main
branch
from
98501a5 to
dc8b0cc
Compare
Introduce explicit sections for input, output, and verification criteria. Define structured JSON output including detailed evidence paths and error counts. Update workflow to reference new guides and move Observation-First loop to operating rules. Clarify verification steps with specific pass/fail conditions for console, network, and accessibility checks.
- Refined `gem-browser-tester` workflow to separate initialization from
execution and enforce an Observation-First loop.
- Added retry logic for transient failures (e.g., timeouts, network issues)
in browser automation tasks.
- Standardized artifact generation paths to `docs/plan/{plan_id}/`
across multiple agents.
- Updated failure actions to specify evidence capture locations
(logs, network) for improved debugging and traceability.
Remove redundant `<operating_rules>`, agent-specific parameters, and `<delegation_validation>` sections. This removes duplicate content to ensure a single source of truth for the agent's behavior protocols and configuration.
Updated agent guidelines to specify the use of accessibility_snapshot over visual screenshots for element identification. Accessibility snapshots provide structured DOM/ARIA data, which is more reliable for browser automation than pixel-based visual analysis.
github-actions
bot
force-pushed
the
main
branch
9 times, most recently
from
b32fe27 to
97043a1
Compare
github-actions
bot
force-pushed
the
main
branch
from
97043a1 to
ccc6997
Compare
aaronpowell
requested changes
Feb 24, 2026
Contributor
aaronpowell
left a comment
aaronpowell
left a comment
There was a problem hiding this comment.
Can you repoint this branch to be staged as the contributing docs. Here's how to do that with the GitHub CLI:
gh pr edit 769 --base staged
Contributor
Author
|
Thanks for pointing this out, missed the newly updated requirements: Fixed now. |
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
2 participants
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.
Pull Request Checklist
npm startand verified thatREADME.mdis up to date.Description
Type of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.