Daily upstream check run — 2026-06-19
The scheduled daily-upstream-check routine ran successfully but could not push its results to the repository because the GitHub integration token has no write access (403 Resource not accessible by integration on both git push via the local proxy and mcp__github__push_files).
What was collected
8 sources fetched successfully (first-run baselines):
| Key |
Version |
claude-code-cli |
2.1.183 |
claude-agent-sdk |
0.3.183 |
claude-agent-sdk-py |
0.2.105 |
codex-cli |
0.141.0 |
aider |
0.86.2 |
goose |
0.1.0 |
mcp-python |
1.28.0 |
mcp-ts |
1.29.0 |
7 sources failed to fetch:
| Key |
Reason |
cursor |
403 Forbidden (cursor.com/changelog) |
cline |
403 Forbidden (VS Code Marketplace) |
continue |
403 Forbidden (VS Code Marketplace) |
windsurf |
403 Forbidden (windsurf.com/changelog) |
zed |
GitHub API rate limit exceeded (unauthenticated) |
mcp-spec |
GitHub API rate limit exceeded (unauthenticated) |
claude-plugins-official |
GitHub API rate limit exceeded (unauthenticated) |
Action required
- Grant write access to the Claude Code remote agent integration for
OpenCircuitDev/codetalker so the routine can push docs/upstream-log/state.json and docs/upstream-log/YYYY-MM.md on future runs.
- Add a
GITHUB_TOKEN env variable to the routine's environment to avoid the GitHub API unauthenticated rate limit on Zed, mcp-spec, and claude-plugins-official.
- Consider an alternative to VS Code Marketplace HTML scraping (which returns 403) — the Marketplace REST API at
https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery may be more permissive.
Open questions (from the spec)
goose-ai on PyPI (v0.1.0) appears to be the GooseAI LLM API client, not the Block/Square "Goose" CLI coding assistant. The spec should be verified to confirm the correct PyPI package name for Goose.
Auto-generated by daily-upstream-check routine.
Daily upstream check run — 2026-06-19
The scheduled
daily-upstream-checkroutine ran successfully but could not push its results to the repository because the GitHub integration token has no write access (403 Resource not accessible by integrationon bothgit pushvia the local proxy andmcp__github__push_files).What was collected
8 sources fetched successfully (first-run baselines):
claude-code-cliclaude-agent-sdkclaude-agent-sdk-pycodex-cliaidergoosemcp-pythonmcp-ts7 sources failed to fetch:
cursorclinecontinuewindsurfzedmcp-specclaude-plugins-officialAction required
OpenCircuitDev/codetalkerso the routine can pushdocs/upstream-log/state.jsonanddocs/upstream-log/YYYY-MM.mdon future runs.GITHUB_TOKENenv variable to the routine's environment to avoid the GitHub API unauthenticated rate limit on Zed, mcp-spec, and claude-plugins-official.https://marketplace.visualstudio.com/_apis/public/gallery/extensionquerymay be more permissive.Open questions (from the spec)
goose-aion PyPI (v0.1.0) appears to be the GooseAI LLM API client, not the Block/Square "Goose" CLI coding assistant. The spec should be verified to confirm the correct PyPI package name for Goose.Auto-generated by daily-upstream-check routine.