claude-code - 💡(How to fix) Fix claude-cli:// URL scheme: add session-id param to jump to a specific session [1 comments, 2 participants]

Use case

I maintain a Todoist-based kanban that tracks long-running projects across many Claude Code sessions. Each card's description lists related session UUIDs as Markdown links so I can jump back into the right session when I pick up the card.

Today the only deep-link option is claude-cli://open?cwd=<path>. That opens Code at the right working directory but always starts a fresh session — the user still has to manually run /resume <uuid> or claude --resume <uuid> in a terminal. Every link is effectively a two-click operation.

What I'd like

Extend the URL scheme to accept a session-id (or resume) param:

claude-cli://open?cwd=/Users/me/proj&session-id=92f722d6-4ffa-4f0f-badb-d58f5e105e97

When present, the handler would pass it through to the CLI as --resume <uuid> (which already exists per claude --help), opening Code directly into that session.

Why it matters

• Workflow tools (Todoist, Linear, Obsidian, Notion, project trackers) can render these as clickable links — true one-click resume.
• The CLI flag (-r, --resume) already supports the behavior; this is purely a URL-handler change.
• The deep-link handler already passes --deep-link-cwd-b64, --deep-link-origin, --deep-link-repo, --deep-link-last-fetch — one more is consistent precedent.

Workaround today

Two-step pattern: deep link opens the cwd, separate code block contains the resume command for copy/paste. Functional but adds friction every time you want to jump back into a session.

Environment

• Claude Code v2.1.144
• macOS (Darwin 25.5.0)