Testing Grok Bot: agent demands full-device GitHub PAT despite existing repo access
vincent_koc · x · 2026-10-27
- The author tested several agent tools including Grok Bot and found that even after granting GitHub access, it wanted a full device PAT token as the user on its cloud runners
- Screenshot shows the bot explaining the existing GitHub link suffices for reading repos, planning and reviewing PRs, while CLI login would enable cloning, running tests and pushing multi-file commits — but requests broad repo/workflow access; the bot then cancelled the login itself
- The author declines to hand all repo permissions to a cloud agent, raising the least-privilege question for cloud-hosted coding agents
More from coding & agent
- The 17-skill AI engineer checklist for 2026 — obsolete half by the time you finish — JafarNajafov · 2026-10-27
- The AI engineer job in 2023 vs 2026: one viral blank line — JafarNajafov · 2026-10-27
- DeepSeek Flash impresses dev: let it build its own tools, cheap enough to experiment — victormustar · 2026-10-27
- Solo dev builds a remote MCP server that runs a small business's website and socials — Ok_Cucumber_131 · 2026-10-27
- Agent loop on OpenClaw stays stable for over a week straight — vincent_koc · 2026-10-27
- Teaching Grok Bot to take your work: five ways to hand off tasks, from drafting to cross-app workflows — Scobleizer · 2026-10-27