URL parameters on claude.ai/code: open a cloud session already filled

TL;DR Build https://claude.ai/code?prompt=…&repositories=owner/repo (URL-encode the values), drop it on a ticket or a doc, and one click opens the cloud form ready to send.

This is not another way to open Claude Code on the web. It is how you wire it into the tools you already use: Linear, GitHub Issues, Notion, an internal dashboard. The page accepts query parameters and fills the new-session form before you type a word.

Result:

https://claude.ai/code?prompt=Fix%20the%20login%20bug&repositories=acme/webapp

Open that link while signed in with GitHub connected, and you see the prompt and the repo already selected. You only hit send.

How to use it

1. Build the URL with the minimum you need

Four parameters. All optional; combine them for what you want pre-filled.

Every value must be URL-encoded. In the browser:

const base = 'https://claude.ai/code'
const params = new URLSearchParams({
  prompt: 'Fix the flaky test in auth.spec.ts',
  repositories: 'acme/webapp',
  environment: 'Default',
})
const url = `${base}?${params.toString()}`
// https://claude.ai/code?prompt=Fix+the+flaky+test...&repositories=acme%2Fwebapp&environment=Default

In a shell:

python3 - <<'PY'
from urllib.parse import urlencode
print('https://claude.ai/code?' + urlencode({
    'prompt': 'Fix the flaky test in auth.spec.ts',
    'repositories': 'acme/webapp',
}))
PY

2. Turn it into a "Fix with Claude" button

In an issue tracker, a PR template, or a runbook:

[Fix with Claude](https://claude.ai/code?prompt=Reproduce%20and%20fix%20AUTH-204&repositories=acme/webapp)

In a script that receives the ticket body:

# ISSUE_BODY and REPO come from the webhook or your tracker's CLI
ENC=$(python3 -c "from urllib.parse import quote; import sys; print(quote(sys.argv[1]))" "$ISSUE_BODY")
echo "https://claude.ai/code?prompt=${ENC}&repositories=${REPO}"

If the prompt is too long for a query string, host it at a public URL (raw gist, internal asset with CORS) and use prompt_url instead of prompt. That URL must allow cross-origin requests; otherwise the browser cannot read it.

Now read it the other way round, for the links you receive. The prompt was written by whoever built the URL, not by you. Nothing is sent on your behalf, so the gap between opening the link and pressing send belongs to you. Read what is in the box first, especially when the link came from a public issue or from someone outside your team.

3. What this link does NOT do

• It does not auto-start the session. It fills the form; you press send (or you do not).
• It does not replace claude --cloud. From the terminal, that flag is still the short path (cloud sessions from browser or terminal).
• It is not the claude-cli:// protocol. That one is the local twin: claude-cli://open?repo=owner/repo&q=… opens a fresh terminal window with Claude Code in your clone and the prompt already typed, unsent (deep links).

Both links solve the same gesture, and you pick one by destination. The https:// link on this page opens the cloud session, runs on Anthropic's machine, and survives anywhere a link gets rendered. The claude-cli:// link opens your terminal, with your config, your tools, and your clone, and the session carries a Prompt from an external link warning under the input until you send or clear it. The practical catch: GitHub strips the claude-cli:// scheme when it renders READMEs, issues, pull requests, and wikis, so the link dies as plain text there. For a button inside a GitHub issue, the one that survives is the one on this page.

When the session is done and you want the work on your machine, teleport is still the bridge.

Reference

Official docs: Pre-fill sessions (web quickstart)

Requirements

• Pro, Max, Team, or Enterprise account (same base as Claude Code on the web)
• GitHub connected at claude.ai/code (or /web-setup in the CLI)
• Browser signed into Anthropic; otherwise you hit login first