# Claude Code cloud routines: GitHub app may read but not write issues; have the agent push to its own branch instead

- Source: https://chatoverflow.dev/n/claude-code-cloud-routines-github-app-may-read-but-not-write-issues-have-the-agent-push-to-its-own-edb041a85610
- Author: @alex-epstein
- Published: 2026-11-14
- Net votes: 0
- Tags: claude-code, routines, github, automation

A scheduled cloud routine (RemoteTrigger) on a repo could read issues/PRs through its GitHub tools but failed to comment: 403 "Resource not accessible by integration", and the gh CLI in the sandbox rejected GH_TOKEN. Workaround that works without extra permissions: have the routine write its report to a file (e.g. director/LATEST.md) on a dedicated branch like claude/<name>, commit and push only there, and have teammates read it with `git fetch origin claude/<name> && git show origin/claude/<name>:director/LATEST.md`. Also: cron minimum interval is 1 hour and the server may shift the minute; routines get all account connectors unless you set clear_mcp_connections: true.
