claude-code - 💡(How to fix) Fix Feature request: Enable Terminal panel in remote/SSH sessions (desktop app) [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#49644Fetched 2026-04-17 08:35:20
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×2cross-referenced ×1

The Terminal panel in the Claude Code desktop app is disabled in remote sessions with the tooltip "로컬 세션에서만 사용 가능합니다" ("Only available in local sessions"). Requesting that the Terminal panel also be usable when connected to a remote host (SSH / dev container / WSL).

Root Cause

The Terminal panel in the Claude Code desktop app is disabled in remote sessions with the tooltip "로컬 세션에서만 사용 가능합니다" ("Only available in local sessions"). Requesting that the Terminal panel also be usable when connected to a remote host (SSH / dev container / WSL).

RAW_BUFFERClick to expand / collapse

Summary

The Terminal panel in the Claude Code desktop app is disabled in remote sessions with the tooltip "로컬 세션에서만 사용 가능합니다" ("Only available in local sessions"). Requesting that the Terminal panel also be usable when connected to a remote host (SSH / dev container / WSL).

Motivation

Many development workflows run entirely on a remote dev server via SSH:

  • Large monorepos, HDL/EDA toolchains, GPU machines, corp-policy servers
  • Local machine is only a thin client

In these setups the embedded Terminal panel is arguably more useful than on local, since the user is already operating against a remote filesystem. Today they must keep a separate SSH terminal app open alongside the Claude Code desktop app.

Current behavior

  • Connected via remote/SSH to a Linux host (CentOS 7 in my case)
  • In the desktop app sidebar, the Terminal item is greyed out
  • Hover shows: "로컬 세션에서만 사용 가능합니다" / "Only available in local sessions"
  • "미리보기", "작업", "계획" tabs remain usable

Requested behavior

Allow the Terminal panel to attach to the remote shell (the same shell that Bash tool calls execute in), so users can interact with the remote environment without leaving the app.

Notes

  • If there is a security rationale (e.g. TTY piping over the transport), an opt-in setting or per-workspace toggle would be acceptable.
  • Related: the `/skills` command is also unavailable in some remote modes — there may be a shared "remote-gated features" list worth reviewing together.

Environment

  • Claude Code desktop app (latest)
  • Remote host: Linux (CentOS 7), connected via SSH

extent analysis

TL;DR

Enable the Terminal panel in remote sessions by modifying the Claude Code desktop app to attach to the remote shell, potentially with an opt-in setting for security concerns.

Guidance

  • Review the remote-gated features list to identify potential security rationales for disabling the Terminal panel in remote sessions.
  • Investigate modifying the app to attach to the remote shell, similar to how Bash tool calls execute in the remote environment.
  • Consider adding an opt-in setting or per-workspace toggle to allow users to enable the Terminal panel in remote sessions, addressing potential security concerns.
  • Examine the /skills command's unavailability in some remote modes to identify potential shared limitations or restrictions.

Example

No code snippet is provided as the issue lacks specific technical details about the app's implementation.

Notes

The solution may require modifications to the Claude Code desktop app's architecture and security settings. The opt-in setting or per-workspace toggle would need to balance security concerns with user convenience.

Recommendation

Apply a workaround by modifying the app to attach to the remote shell, with an opt-in setting for security concerns, as this would provide the requested functionality while addressing potential security limitations.

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