claude-code - 💡(How to fix) Fix [BUG] "Send to Claude Code Web" from Claude Design opens a session with no way to connect a GitHub repo [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#51980Fetched 2026-04-23 07:39:46
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

This forces users into a two-step workaround: download the bundle via "Send to local coding agent", commit it manually to their repo, then start a separate web session pointed at that repo.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When using "Send to Claude Code Web" from a Claude Design project, the resulting claude.ai/code session has the design bundle attached at the working directory but no way to connect a GitHub repo — not at session start, and not from inside the session.

The composer's + menu only offers "Add image" and "Slash commands". There's no repo picker on the session page, and the Claude Design dialog doesn't expose one either. The only way to connect a GitHub repo is to abandon the session and start a fresh one from claude.ai/code directly, which loses the attached design bundle.

This forces users into a two-step workaround: download the bundle via "Send to local coding agent", commit it manually to their repo, then start a separate web session pointed at that repo.

What Should Happen?

Either (a) the "Send to Claude Code Web" dialog in Claude Design should include a repo picker, or (b) the resulting session should expose one so the design bundle can be committed to an existing repo without leaving the session.

Environment

Claude Code on the web (claude.ai/code) Session started via Claude Design handoff Model: Opus 4.7

Error Messages/Logs

Steps to Reproduce

Open a project in Claude Design (claude.ai/design) Click the hand-off button → "Send to Claude Code Web" tab Click "Open in Claude Code Web" In the resulting session, try to connect a GitHub repo — there's no repo picker in the composer + menu, the session-title dropdown, or anywhere else I could find

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

web

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue can be mitigated by modifying the "Send to Claude Code Web" workflow to include a GitHub repository connection step, either by adding a repo picker to the dialog or by exposing a repo picker in the resulting session.

Guidance

  • Review the Claude Design handoff functionality to determine why the GitHub repository connection is not being passed through to the Claude Code Web session.
  • Investigate adding a repository picker to the "Send to Claude Code Web" dialog in Claude Design to allow users to select a GitHub repository before opening the session.
  • Consider modifying the Claude Code Web session to include a repository picker, allowing users to connect a GitHub repository after the session has started.
  • Verify that the design bundle is correctly attached to the working directory in the Claude Code Web session and that the expected repository connection functionality is available.

Example

No code snippet is provided as the issue is related to the functionality of the Claude Design and Claude Code Web applications, and no specific code is mentioned.

Notes

The issue may be related to the specific version of the Claude Code Web application or the Opus model being used, but without further information, it is difficult to determine the root cause.

Recommendation

Apply workaround: Modify the "Send to Claude Code Web" workflow to include a GitHub repository connection step, either by adding a repo picker to the dialog or by exposing a repo picker in the resulting session, as this will allow users to connect a GitHub repository without having to abandon the session and start a new one.

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