GitHub Copilot is hard to run and test locally

Dev tooling4 posts from 4 people4d active+22 posts in the last 7 days, 2 the 7 days before (steady)

Posts per day4 posts, Oct 8 to Oct 21

The posts behind it

4, newest first

GitHub issuesOct 16 Copilot SDK Agent Host pauses for 60 seconds after each completed tool callType: Bug Environment: Windows x64; VS Code 1.142.0, commit 6d62b1d5dace93a33b3a6d3eca1317bd5e15bcb1; bundled Copilot runtime 1.0.95-0.unstable.r38345923974.g3754b70. Observed: During an approximately 60-minute task, 48 tool-completion-to-turn-end gaps measured 60.021-60.067...microsoft/vscode · Ralph-Nijpels2 reactionsOpen ↗GitHub issuesOct 15 Copilot chat Type: Bug Copilot Chat in VS Code (WSL2) is intermittently delayed by 3-4 minutes even for simple prompts ("hello"), while Codex works normally in the same environment. Network diagnostics are healthy (HTTP 200 to GitHub/Copilot endpoints, ~150-400ms). Logs show successful model...microsoft/vscode · chef88val4 reactions, 2 repliesOpen ↗GitHub issuesOct 9 Copilot chat feedbackType: Feature Request Hi There, how are you going. Happy Friday Recently switched to the Agent SDK within VSCode from using local. It would be really great to be able to possibly have these two things from Local come across to Agent. 1. Code Changes within VSCode editor so you...microsoft/vscode · ProxayFox1 reactions, 1 repliesOpen ↗GitHub issuesOct 8 Memory tool's repo-scope storage (/memories/repo/) is placed outside the workspace, so it's lost in devcontainers on "Rebuild Container"### Description The Copilot Chat `memory` tool documents its "repo" scope as: > stored locally in the workspace In practice, repo-scope memory files are written to: `~/.vscode-server/data/User/workspaceStorage/ /GitHub.copilot-chat/memory-tool/memories/repo/` This path is...microsoft/vscode · lacs23871 reactionsOpen ↗

Companies and products named

Named4 posts

GitHub Copilot Named4 posts

VS Code Named2 posts

NVIDIA Named1 post

Model Context Protocol Named1 post

GitHub Actions Named1 post

Microsoft Azure

About this problem

Evidence

4 posts from 4 people in 1 place, about 2 a week over 9 days. Mostly on microsoft/vscode. Tools named alongside: VS Code, NVIDIA, Model Context Protocol, GitHub Actions.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts that state a pain and match the "local-dev" rule about GitHub Copilot. First post Oct 8, 2026, latest Oct 16, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

The same problem elsewhere

Elsewhere7 postsLocal development setups are hard to get right Elsewhere2 postsGitHub is hard to run and test locally Elsewhere2 postsClaude Code is hard to run and test locally Elsewhere2 postsSupabase is hard to run and test locally

Other GitHub Copilot problems

Same product14 postsGitHub Copilot upgrades break working setups Same product7 postsGitHub Copilot feels slow and laggy Same product8 postsTrouble with GitHub Copilot harness Same product10 postsTrouble with GitHub Copilot agent Same product2 postsTrouble with GitHub Copilot sessions Same product7 postsGitHub Copilot outages and slowdowns disrupt work Same product5 postsTrouble with GitHub Copilot chat Same product4 postsTrouble with GitHub Copilot loop Same product3 postsTrouble with GitHub Copilot custom Same product3 postsGitHub Copilot gives confidently wrong answers Same product2 postsTrouble with GitHub Copilot allow Same product2 postsMigrating to or off GitHub Copilot is slow and risky

History

CorroborationOct 21, 2026unverified to corroborated

MomentumOct 21, 2026fading to steady

MomentumOct 16, 2026steady to fading

MomentumOct 15, 2026new to steady

AddedOct 13, 2026GitHub Copilot is hard to run and test locally (2 posts)