| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Allow clients to keep MCP App views enabled while making form-backed write tools execute directly when explicitly configured. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Adds a user-controlled feature flag to bypass MCP App form deferral while preserving UI metadata and result views.
Changes:
| File | Description |
|---|---|
| pkg/http/server_test.go | Tests HTTP-header and insiders behavior. |
| pkg/github/ui_capability.go | Adds the form-deferral opt-out check. |
| pkg/github/ui_capability_test.go | Tests deferral flag combinations. |
| pkg/github/feature_flags.go | Defines and allows the new flag. |
| pkg/github/feature_flags_test.go | Tests feature resolution behavior. |
| docs/server-configuration.md | Documents remote and local configuration. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
MCP Apps in the GitHub MCP Server are useful, but having issue and pull request tools open a form instead of performing the requested operation can be disruptive, especially in autopilot workflows where autonomous task completion is expected.
This adds the user-controllable mcp_apps_disable_form_deferral feature flag. When enabled alongside remote_mcp_ui_apps, form-backed write tools execute directly while MCP App result views and UI metadata remain enabled. HTTP clients can opt in per request through X-MCP-Features.
Testing