Complete external agent harness workflow#68
Merged
Conversation
epowell40
marked this pull request as ready for review
July 13, 2026 16:24
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.
What changed
doctorand real child-process stdiosmokeworkflowonceandsessionwrite grants with no YOLO optionWhy
The public bridge and MCP tools already existed, but external agent harnesses lacked a complete operational path: configuration was fragile, write approval depended on the Operator pane, and no reusable live stdio acceptance command existed.
Validation
npm --prefix apps/mcp-server test— 21/21 passeddotnet build RevitBridge/RevitBridge.csproj -c Release -f net48— passed, 0 errors (existing warnings)external-agent doctoragainst Revit 2024 — readyexternal-agent smoke— 113 tools, ping/search/context/grant status passed through an independent stdio child