[BUG] Claude Slack app returns "No repositories found" for non-coding queries without GitHub connected

Status Closed — not planned
Maintainer reply None cached
Activity 8 comments · opened May 1, 2026 · closed Jun 13, 2026

Description

The Claude app for Slack consistently returns a GitHub / Claude Code repository error even when the user asks a purely non-coding Slack question and has no GitHub account connected.

Error message:

"No repositories found. Please connect your GitHub account at claude.ai and try again."

The key issue is that this error is triggered for general Slack assistant requests with no coding intent, such as checking today's mentions or summarizing important Slack conversations. This suggests that Slack requests may be incorrectly routed into the Claude Code / GitHub repository flow before, or instead of, normal chat / Slack connector handling.

Steps to Reproduce

  1. Install the Claude app from the Slack Marketplace.
  2. Connect / authenticate the Slack app to a Claude account.
  3. Do not connect any GitHub account in Claude / Claude Code.
  4. Re-authenticate and/or reinstall the Slack app multiple times to rule out a stale auth state.
  5. Open Claude inside Slack via one of the following surfaces:
  • Slack DM with Claude
  • Claude side panel in Slack
  • @Claude mention in a Slack channel
  1. Ask a Slack-related, non-coding question, for example:
  • "What mentions did I receive today?"
  • "Summarize today's important conversations."
  • "Summarize this Slack channel."
  1. Observe that Claude returns the GitHub repository error instead of handling the Slack request or returning a Slack-specific access error.

Expected Behavior

For non-coding Slack questions, Claude should not require GitHub repository access.

Expected behavior should be one of the following:

  • If the Slack connector / Slack app permissions are available, Claude should answer using accessible Slack data.
  • If Slack data is unavailable, Claude should return a Slack-specific permissions or access message, such as "I do not have access to that Slack information."
  • The response should not mention GitHub or repositories unless the user explicitly asks for a coding / repository task.

Actual Behavior

Claude returns this GitHub-specific error for non-coding Slack questions:

"No repositories found. Please connect your GitHub account at claude.ai and try again."

This happens even though:

  • The prompt does not mention code, repositories, GitHub, pull requests, branches, or Claude Code.
  • The account has no GitHub integration connected at all.
  • The same Slack connector works correctly from the Claude web app at claude.ai.
  • The failure occurs only inside Slack.

This makes the Slack app unusable for general Claude / Slack assistant workflows unless GitHub is connected, even when the request has no coding intent.

Environment

  • Plan: Claude Team
  • Account type: Organization account
  • GitHub connection: No GitHub account connected at all
  • Slack app: Claude app installed from the Slack Marketplace
  • Affected surfaces:
  • Slack DM with Claude
  • Claude side panel in Slack
  • @Claude mentions in Slack
  • Web app behavior:
  • Slack connector works correctly via claude.ai
  • The issue occurs only inside the Slack app
  • Re-authentication attempts:
  • Slack app re-authenticated multiple times
  • Slack app reinstalled multiple times
  • The behavior remains reproducible

Additional Context

Official Claude Code in Slack documentation describes Claude Code in Slack as a coding-task workflow that routes coding requests to Claude Code on the web, and also documents a routing mode intended to distinguish coding tasks from general chat:

https://code.claude.com/docs/en/slack

This report is specifically about the routing behavior for non-coding Slack questions. Even if GitHub is required for Claude Code in Slack, general Slack assistant questions should not fail with a GitHub repository error.

A similar user report is visible on Reddit:

https://www.reddit.com/r/ClaudeAI/comments/1sgo7zh/claude_app_for_slack_not_working/

There is also a related, but distinct, GitHub issue about Slack and GitHub connector access:

https://github.com/anthropics/claude-code/issues/15884

That issue appears to describe GitHub being unavailable from Slack when GitHub should be available. This report is the inverse failure mode: GitHub / repository lookup is triggered even when the request is explicitly non-coding and no GitHub account is connected.

Screenshots can be provided showing the Slack prompt and the returned repository error. Organization/workspace identifiers can be shared privately if needed.

View original on GitHub ↗

8 Comments

github-actions[bot] · 5 months ago

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/49891
  2. https://github.com/anthropics/claude-code/issues/44805

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

ryofukutani · 5 months ago

This is related but not a duplicate of #49891 or #44805.

Those issues involve Claude routines / Remote Control flows. This issue is
specifically about the Claude Slack app routing non-coding Slack questions,
such as mentions or channel summaries, into a GitHub / Claude Code
repository lookup path.

The key distinction is that the prompt has no coding intent and does not
involve repositories, yet Slack returns “No repositories found.” The same
Slack connector works from claude.ai, and the failure occurs only inside
Slack.

2026年5月1日(金) 22:25 github-actions[bot] @.***>:

github-actions[bot] left a comment (anthropics/claude-code#55315) <https://github.com/anthropics/claude-code/issues/55315#issuecomment-4359484120> Found 2 possible duplicate issues: 1. #49891 <https://github.com/anthropics/claude-code/issues/49891> 2. #44805 <https://github.com/anthropics/claude-code/issues/44805> This issue will be automatically closed as a duplicate in 3 days. - If your issue is a duplicate, please close it and 👍 the existing issue instead - To prevent auto-closure, add a comment or 👎 this comment 🤖 Generated with Claude Code <https://claude.ai/code> — Reply to this email directly, view it on GitHub <https://github.com/anthropics/claude-code/issues/55315#issuecomment-4359484120>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFROIFCNT4MWMGNXBXNLEDT4YSQVXAVCNFSM6AAAAACYNNHEDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNJZGQ4DIMJSGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: @.***>

--
福谷 亮 / Ryo FUKUTANI
@.***
Mobile 080-1743-5786

jeremyCWD · 5 months ago

I'm experiencing the same issue. The Claude Slack integration currently seems non-functional for non-coding intent requests.

For all requests, it will respond: "No repositories found. Please connect your GitHub account at claude.ai and try again."

I connected a Github account and received: "No repositories found. Please connect your GitHub account at claude.ai and try again."

I created a new repository and tried again, this time receiving: "Claude Code is not enabled for your account — contact your workspace admin to enable it."

After restarting Slack again, I asked Claude to try again, and it asked me to select a repository and then started a coding session immediately. I asked it to stop and it stopped successfully with this message: "Stopping! Let me know what you'd like help with when you're ready."

Now it responds to all requests with this message: ":computer: I wasn't sure which repository you meant — pick one to start a code session:", even for explicitly no coding intent messages.

It seems like it's unable to escape this loop

jason-ehawk · 5 months ago

I was running into this issue and opened the Select Repository and used the "Switch to chat" button.

<img width="520" height="398" alt="Image" src="https://github.com/user-attachments/assets/885af55b-d257-492d-b3ba-9e1ac0ba009d" />

It replied to my original question (non code related) correctly but then when I asked another non code related questions it responded with "I wasn't sure which repository you meant — pick one to start a code session:" again.

jason-ehawk · 5 months ago

Just found the setting under Home to switch from "Code only" to "Code + Chat". This resolved it for me.

<img width="845" height="458" alt="Image" src="https://github.com/user-attachments/assets/071e0459-eb1e-44fe-9270-2dfa168905cd" />

github-actions[bot] · 4 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

yvol-ah · 3 months ago
Just found the setting under Home to switch from "Code only" to "Code + Chat". This resolved it for me. <img alt="Image" width="845" height="458" src="https://private-user-images.githubusercontent.com/134300769/588474840-071e0459-eb1e-44fe-9270-2dfa168905cd.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODIwMjQ5NzAsIm5iZiI6MTc4MjAyNDY3MCwicGF0aCI6Ii8xMzQzMDA3NjkvNTg4NDc0ODQwLTA3MWUwNDU5LWViMWUtNDRmZS05MjcwLTJkZmExNjg5MDVjZC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwNjIxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDYyMVQwNjUxMTBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01OWI3YTQxMTM2YzZhNGIwNTUxNDU0NjMyYTQ4ZmIyYmQwMDgyYmNhNjE4OGJjODNmZjNlMDlmYTZkY2VlYjQ0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.MR3fty69qen6Q9e1N5Pn21RP-rD6e0nJqA7Svqrk26g">

where to find this?

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.