Insiders Feedback:
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Start by tracing the action tool call and its confirmation flow in the GitHub MCP Server; the issue does not name source files or tests. Reproduce PR creation in Copilot chat and follow what happens after Allow, including the second confirmation and whether the agent continues. Done means one approval creates the PR and the agent continues automatically.
Written by the indexing model from the issue text.
Description
Version: 1.140.0
Commit: 07f806f999227108933c2e30515b26eecc1fda74
Date: 2026-09-30T10:38:38+02:00
Electron: 43.7.3
ElectronBuildId: 15386805
Chromium: 150.0.7871.250
Node.js: 24.21.0
V8: 15.0.245.31-electron.0
@github/copilot: 1.0.89-7
@github/copilot-sdk: 1.0.15-preview.4
OS: Linux x64 7.0.0-38-generic
Feature: The UI component shown for action tool calls like PR create
Feedback:
I like the idea of an in-chat UI for action tool calls, but right now it conflicts with the normal flow. Here's what I see in Copilot chat:
-
Tool calls aren't auto-approved, so the PR details are already visible in the confirmation prompt. The UI isn't great, but it's enough for a quick review of the PR create request. When I click Allow, the original tool call appears to be cancelled and shows an ✗ mark.
-
A new UI then appears, asking me to confirm all the same details again. I have to approve a second time by clicking the Create PR button.
-
Once that's done, the chat stops, and I have to ask the AI to continue. Previously, a single Allow was all it took and everything just worked.
Expected behavior: a single approval step, with the agent continuing automatically afterward.
Thanks for looking into this. I hope it gets resolved soon.
- Dominant language
- Go
- Stars
- 34.2k
- Forks
- 5.3k
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/github-mcp-server
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3760 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/github-mcp-server#3758 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3729 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3722 ·
Maintainers usually reply within 2 days
-
Insiders Feedback: PR created UI doesn't link to the PRPossibly taken @genius-0963 claimed this 5 days ago. Openbug insiders user-experience
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3658 ·
Maintainers usually reply within 2 days
All issues in github/github-mcp-server
Similar issues
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hexlet-basics/hexlet-basics#962 ·
Maintainers usually reply within 1 day
-
imapproxy closeForMaintenance grace timer calls clientConn.Close() before closeMaintenanceTransportPossibly taken @dejanstrbac claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
renovate-health
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Netcracker/qubership-network-latency-exporter#267 ·
Maintainers usually reply within 1 day
-
Network capture does not workPossibly taken @KSpaceer claimed this today. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aquasecurity/tracee#5395 ·