Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] Cowork Dispatch should expose available host connectors and mounted directories to the orchestrator [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48187•Fetched 2026-04-15 06:30:42
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
pganapathy80pganapathy80
Participants
pganapathy80pganapathy80
Timeline (top)
labeled ×3

Fix Action

Fix / Workaround

When orchestrating tasks from Cowork Dispatch, the Dispatch agent (orchestrator) has no way to discover what connectors, mounted directories, or cloud storage integrations are already available on the host Mac.

For example, if the user has Google Drive mounted via CloudStorage (~/Library/CloudStorage/GoogleDrive-*/Shared drives/), Cowork can access it via request_cowork_directory. But the Dispatch orchestrator doesn't know this is available — it wastes time searching the MCP registry for a Google Drive connector or suggesting the user set one up, when the access is already there.

  1. User asks Dispatch to save a file to Google Shared Drive
  2. Dispatch searches search_mcp_registry for Google Drive connectors — finds nothing
  3. Dispatch tells the user it can't access Google Drive and suggests connecting one
  4. User has to tell Dispatch that Cowork already has access
  5. Dispatch then uses request_cowork_directory with the correct path — works fine
RAW_BUFFERClick to expand / collapse

Problem

When orchestrating tasks from Cowork Dispatch, the Dispatch agent (orchestrator) has no way to discover what connectors, mounted directories, or cloud storage integrations are already available on the host Mac.

For example, if the user has Google Drive mounted via CloudStorage (~/Library/CloudStorage/GoogleDrive-*/Shared drives/), Cowork can access it via request_cowork_directory. But the Dispatch orchestrator doesn't know this is available — it wastes time searching the MCP registry for a Google Drive connector or suggesting the user set one up, when the access is already there.

Current Behavior

  1. User asks Dispatch to save a file to Google Shared Drive
  2. Dispatch searches search_mcp_registry for Google Drive connectors — finds nothing
  3. Dispatch tells the user it can't access Google Drive and suggests connecting one
  4. User has to tell Dispatch that Cowork already has access
  5. Dispatch then uses request_cowork_directory with the correct path — works fine

Expected Behavior

  1. User asks Dispatch to save a file to Google Shared Drive
  2. Dispatch checks available host connectors/mounts and sees Google Drive is accessible
  3. Dispatch uses request_cowork_directory directly — no wasted round-trip

Suggested Solution

Provide a tool like list_available_directories or list_host_connectors that returns:

  • Currently mounted directories in the Cowork VM
  • Available CloudStorage mounts on the host (Google Drive, OneDrive, iCloud, Dropbox, etc.)
  • Connected MCP servers/connectors
  • Any other integrations the Cowork session has access to

This way the orchestrator can make informed routing decisions without guessing or asking the user.

Impact

This affects every Cowork Dispatch session where the user expects Dispatch to know about their existing integrations. The current behavior feels broken — the user already connected these services, but Dispatch acts like they don't exist.

Environment

  • macOS (Apple Silicon)
  • Claude Desktop with Cowork
  • Google Drive for Desktop (CloudStorage mount)

extent analysis

TL;DR

Implement a discovery mechanism, such as list_available_directories or list_host_connectors, to inform the Dispatch orchestrator about available host connectors, mounted directories, and cloud storage integrations.

Guidance

  • Develop a tool or API that returns a list of currently mounted directories in the Cowork VM, available CloudStorage mounts on the host, and connected MCP servers/connectors.
  • Integrate this discovery mechanism into the Dispatch orchestrator to enable informed routing decisions.
  • Consider caching the results of the discovery process to minimize overhead and improve performance.
  • Verify the effectiveness of the discovery mechanism by testing it with various cloud storage integrations and mounted directories.

Example

# Example implementation of list_available_directories
import os

def list_available_directories():
    available_directories = []
    # Check for CloudStorage mounts
    cloud_storage_path = '~/Library/CloudStorage/'
    if os.path.exists(cloud_storage_path):
        available_directories.extend(os.listdir(cloud_storage_path))
    # Check for connected MCP servers/connectors
    # ...
    return available_directories

Notes

The implementation details of the discovery mechanism will depend on the specific requirements and constraints of the Cowork Dispatch system. This example provides a starting point, but additional development and testing will be necessary to ensure a robust and reliable solution.

Recommendation

Apply a workaround by implementing the suggested list_available_directories or list_host_connectors tool to improve the Dispatch orchestrator's awareness of available host connectors and mounted directories. This will enable more efficient and informed routing decisions, reducing the need for user intervention and improving the overall user experience.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#authentication setup#request error#file not found#serialization error#model compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [FEATURE] Cowork Dispatch should expose available host connectors and mounted directories to the orchestrator [1 participants]