[GitHub integration]

Status Open
Maintainer reply None cached
Activity 2 comments · opened Oct 9, 2026

Screenshot

Una conversación de Claude dice que no tiene add_repo.

What were you trying to do?

I have two scheduled tasks (routines) that run unattended in the cloud and must push HTML files to my private repo Interpretaorg/pulso-web after each run:

  • "Pulso España madrugada" (trig_018W2gBYsABJvBhaGPXoygtX), daily 02:20 America/Santiago
  • "Pulso diario" (trig_01792HVLVbHTHyAhmTkTZJQt), daily 07:15 America/Santiago

Both routines include the Claude_Code_Remote connector, and their instructions say to call mcp__claude-code-remote__add_repo (owner Interpretaorg, repo pulso-web, access push), then git clone and push to main.

The GitHub integration is set up correctly: the Claude GitHub App is installed on Interpretaorg, and "Check repository status" is green ("Claude Code cloud sessions can work on Interpretaorg/pulso-web").

What happened instead?

In the scheduled run on 2026-10-09 (session cse_01SLzg3Yj9iGVRw8VECQ4Ht8), the tool mcp__claude-code-remote__add_repo was not available. The claude-code-remote server only exposed 6 trigger tools (create/update/delete/list/fire triggers, send_later). Because of that, git had no credentials ("could not read Username for 'https://github.com'"), and nothing could be pushed.

In an interactive conversation in the same project, add_repo IS available and works. On 2026-10-08 an interactive session pushed to this same repo successfully.

So it looks like scheduled/routine sessions do not receive add_repo or git access to the repo, even though the GitHub App and the repository check are green.

Expected: scheduled sessions should be able to use add_repo (or get git push access to the selected repo) so the daily routines can publish without manual steps.

Diagnostics

Filed from: GitHub settings for Claude Code on claude.ai
Report code: GH-9W63FX
Page: claude.ai/customize/connectors/integration-github
Client: web

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗