I Put GitHub Copilot Behind a MITM Proxy. Here's What I Found
- ID: 220d5105
- Original: https://www.lighthousenewsletter.com/p/i-put-github-copilot-behind-a-mitm
- Added: 2026-08-12
- Source: newsletter / Lighthouse Newsletter
- Original Date: 2026-08-12
- AAIF Category: agents
- Quality Score: 4
- Status: active
- Source Type: article
- Language: en
- Tags: copilot, mitm, agent-harness, oauth, mcp-registry
中文摘要
用 mitmproxy 在 VS Code 启动阶段抓出 Copilot 完整的 OAuth 换短令牌模型与 SWE-agent 能力发现intent 路由器MCP registry 拉取和 repo context 收集的请求矩阵，是观察 agent harness 在你打字前做了什么的第一手样本在 Auto 模式下每次输入先发到 models session intent 端点，把 prompt 按 code-gendebuggingreasoningtool-use 打分再选模型；bootstrap 阶段已经发出 authconfigpolicyMCP registryrepo context模型发现最近仓库六类请求；VS Code 的 Extension Host 进程陈旧会导致扩展流量不进代理，需要 Developer: Restart Extension Host文章给出完整序列图扩展主机重启脚本和 mitmweb 操作步骤，并把上下文正在成为产品作为对 harness 工程的判断
English Summary
Uses mitmproxy during VS Code launch to capture Copilot's full request matrix: OAuth token exchange, model + SWE-agent capability discovery, intent router, MCP registry fetches, and repo-context collection. In Auto mode every keystroke first hits a models session intent endpoint that scores prompts across code-gen / debugging / reasoning / tool-use before picking a model. Bootstrap already issues six request families: auth, config, policy, MCP registry, repo context, model discovery, recent repos. Stale Extension Host processes skip the proxy entirely and require Developer: Restart Extension Host. Article ships the full sequence diagram, an Extension Host restart script, and mitmweb walkthrough, and frames context-as-product as the harness-engineering takeaway.
来源 / Obsidian 引用
- 本机 Obsidian 同日 digest 落地（ClawFeed 24h / AK-RSS-Digest 89 源 / X-Hot-Brief / 内容选题编排）
- 评分依据：原文正文（不靠标题/摘要/源声誉）