claude-code - 💡(How to fix) Fix [FEATURE] Allow enabling connectors when using `claude --remote` [1 comments, 2 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#56245Fetched 2026-05-06 06:33:17
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×2commented ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

When using claude --remote, all connectors are disabled by default. If your task depends on a connector, that interface to start a Claude Code web session is not usable.

Proposed Solution

Add a flag to enable specific or all connectors when using claude --remote

Alternative Solutions

Don't use that interface to start Claude Code web session. Use the web UI, or create a routine instead.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

  1. claude --remote "/start-task <task-id>" --connectors <connector> with a custom skill designed to fetch the task details from the connector.

Additional Context

No response

extent analysis

TL;DR

Add a flag to the claude --remote command to enable specific or all connectors.

Guidance

  • Review the current implementation of claude --remote to understand how connectors are disabled by default.
  • Consider adding a new flag, such as --connectors or --enable-connectors, to allow users to specify which connectors to enable.
  • Evaluate the proposed solution and alternative solutions to determine the best approach for the use case.
  • Test the new flag with the example use case, claude --remote "/start-task <task-id>" --connectors <connector>, to ensure it works as expected.

Example

claude --remote "/start-task my-task" --connectors my-connector

Notes

The solution may require modifications to the CLI command parsing and the underlying connector management logic.

Recommendation

Apply workaround: Add a new flag to the claude --remote command to enable specific or all connectors, as it provides a flexible solution for users who need to use connectors with the remote interface.

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…

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] Allow enabling connectors when using `claude --remote` [1 comments, 2 participants]