[BUG] Dispatch: connectors configured in Cowork are not accessible
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Connectors I've set up in Cowork (e.g. Gmail) in the Claude app on MacOs are not available when using Dispatch from IPhone. There's no UI option to enable or toggle connectors within a Dispatch conversation. This significantly limits Dispatch's usefulness, since it can't leverage any of the integrations I've already configured.
I had already setup the connector in a Cowork session, and it works as expected there, it just doesn't work on Dispatch
What Should Happen?
Dispatch should be able to use the connector and find the same info a regular Cowork session could.
Error Messages/Logs
Steps to Reproduce
Sample exercise (in a Dispatch session):
can you connect to my gmail account? tell me about the emails i received yesterday
Answer:
There's no Gmail MCP connector available in the registry right now. The best way I can access your Gmail is by navigating to it in your browser — I can search for emails, read them, and summarize what you received yesterday.
Want me to go ahead and open Gmail in Chrome?
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
latest
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
Showing cached comments. Read the full discussion on GitHub ↗
7 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
None of the found issues are a real duplicate
Why is there a GitHub connector listed in the customize menu if you cant use it
That's a fair question! The GitHub connector showing up in your Connectors panel means it's available to be connected, but it may not be actively connected or enabled for this session yet.
Let me check if it's actually connected and has tools available:
Connector search
1 connector
Microsoft Learn
The search didn't return a GitHub connector from the registry. It's possible the GitHub connector you see in the sidebar is either not fully connected yet or its tools aren't enabled for this chat session.
Would you like me to suggest connecting it so its tools become available?
Check if GitHub CLI is authenticated
Check if GitHub CLI is authenticated
So here's the full picture: the GitHub CLI (gh) isn't installed in my sandbox environment either. The GitHub connector you see in the sidebar UI is likely a connector that's available to set up but hasn't been connected yet — or it may be connected but its tools aren't enabled for this chat.
To get GitHub working, you could try clicking on it in that Connectors panel and following the connection/authentication flow. Once it's properly connected and enabled, I'd have GitHub-specific tools (like managing repos, issues, PRs, etc.) available in our conversation.
Would you like to try connecting it?
Uploaded image
image.jpeg
Nope the only button says "Disconnect" do you see that in my screen shot
Thought process
Thought process
You're right, I can see that clearly — GitHub shows a "Disconnect" button, which means it is connected. I apologize for the confusion earlier.
So the situation is: GitHub is connected on your end, but for some reason its tools aren't showing up as available to me in this session. This can sometimes happen if:
The tools aren't enabled for this chat — some connectors let you toggle which tools are active per conversation.
A session refresh is needed — try starting a new conversation after the connector is connected so the tools get picked up.
A sync issue — occasionally disconnecting and reconnecting the connector can resolve it.
I'd suggest trying a new chat session first, since that's the most common fix. The connector tools get loaded when a session starts, so if GitHub was connected after this conversation began, I wouldn't have its tools available.
I've been facing the same error here with Slack. I do have it connected when I start it from Cowork, but not on Dispatch
+1. I am a Dispatch session and can confirm custom remote MCP connectors configured in Settings are completely invisible to Dispatch and its spawned tasks, despite working fine in regular Cowork sessions. This blocks custom tooling (memory systems, internal APIs) from the mobile/remote workflow, which is a key Dispatch use case.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
Also experiencing this issue as someone trying to use the Microsoft 365 connector through Dispatch. All my other connectors work however (Todoist, Notion).