Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] In Desktop SSH sessions, allow WebFetch to run on the local host instead of the remote SSH target [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#54895•Fetched 2026-05-01 05:51:37
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
iorin0217iorin0217
Participants
iorin0217iorin0217
Timeline (top)
labeled ×3
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 Code Desktop over SSH, I want WebFetch to run on the local desktop host, while shell/file/code operations continue to run on the remote machine.

In remote compute environments, outbound network access is often restricted or routed differently. That is fine for code execution, but it makes doc/web retrieval unnecessarily hard. Since Claude Code Desktop itself is running locally, it would be very useful to let WebFetch use the local machine's network path.

Proposed Solution

Please add an option for Desktop SSH sessions to route WebFetch through the local host only.

  • Remote: Bash, file edits, git, tests
  • Local: WebFetch

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

No response

Additional Context

This seems related, but distinct from:

#53511 (WebFetch permissions vs sandbox network allowlist coupling) #31296 and #38735 (current coupling between WebFetch rules and sandbox network behavior)

This request is specifically about Desktop SSH sessions and allowing WebFetch to execute on the local host instead of the remote SSH target.

extent analysis

TL;DR

Implement an option to route WebFetch requests through the local host for Desktop SSH sessions.

Guidance

  • Identify the current network routing configuration for WebFetch in Desktop SSH sessions to understand how it's currently being handled.
  • Consider adding a flag or configuration option to specify whether WebFetch should use the local or remote network path.
  • Investigate how the existing WebFetch implementation can be modified to support this new routing option, potentially involving changes to the network request handling code.
  • Evaluate the potential security implications of allowing WebFetch to use the local network path, considering the restrictions and routing differences in remote compute environments.

Notes

The solution will depend on the specific implementation details of WebFetch and the Desktop SSH session handling, which are not provided in the issue. Additionally, careful consideration of security implications is necessary to avoid introducing vulnerabilities.

Recommendation

Apply workaround: Implement the proposed option to route WebFetch through the local host for Desktop SSH sessions, as it addresses the specific use case and provides a clear solution to the problem.

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…
#model compatibility#GPU setup#container setup#orchestration issue#cache issue

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] In Desktop SSH sessions, allow WebFetch to run on the local host instead of the remote SSH target [1 participants]