ade-deeplinks

name	ade-deeplinks
description	Use this skill when an agent needs to mint, share, or open ADE deeplinks (lane, work session, file, commit, artifact, branch, PR, Linear issue) so users — or the agent itself — can jump straight to a specific ADE surface from anywhere (GitHub PR description, Linear issue, Slack, email, terminal, mobile).

ADE deeplinks

What a deeplink is

ADE deeplinks are URLs that route directly to a specific ADE entity. Two forms, identical semantics:

ade://lane/<uuid>                                # local-only — focuses an existing lane
ade://session/<id>[?lane=<lane-uuid>&event=<n>&offset=<bytes>]  # Work session + anchors
ade://file/<repo-relative-path>[?line=<n>&lane=<lane-uuid>]      # Files tab
ade://commit/<sha>[?lane=<lane-uuid>]            # Lanes git detail, or GitHub fallback with envelope
ade://artifact/<artifact-id>                     # local proof/history artifact
ade://repo/<owner>/<repo>/branch/<branch>        # cross-machine — find or offer-to-create lane
ade://pr/<owner>/<repo>/<number>                 # PR detail view
ade://linear-issue/<ADE-123>[?branch=<branch>]   # Linear handoff — opens the Linear pane

https://ade-app.dev/open?type=lane&id=<uuid>
https://ade-app.dev/open?type=session&id=<id>[&lane=<lane-uuid>]
https://ade-app.dev/open?type=file&path=<path>[&line=<n>&lane=<lane-uuid>]
https://ade-app.dev/open?type=commit&sha=<sha>[&lane=<lane-uuid>]
https://ade-app.dev/open?type=artifact&id=<artifact-id>
https://ade-app.dev/open?type=branch&repo=<owner/repo>&branch=<branch>[&pr=<n>]
https://ade-app.dev/open?type=pr&repo=<owner/repo>&number=<n>
https://ade-app.dev/open?type=linear-issue&issue=<ADE-123>[&branch=<branch>]

The HTTPS form is the share-friendly variant (it gets a Vercel-rendered OpenGraph card in Slack/Discord/iMessage/Gmail/Linear). The web landing page tries the ade:// upgrade and falls back to an install card. Both forms parse to the same target shape.

Lane, session, commit, and artifact ids are local — the UUID/id is meaningful only on the machine that created it. ADE can attach an envelope to local links as query params:

repo=<owner>/<repo>&branch=<branch>&pr=<number>&linear=<ADE-123>

The envelope does not change the primary target; it gives receivers a portable fallback chain. If the local id is unknown, ADE can offer to switch to the matching project, create/open the branch or PR, open the Linear issue, or open a commit on GitHub. Branch links are portable — they fetch/import the remote branch as a lane if the receiver does not have it yet. Linear-issue links are portable — they open ADE's Linear pane for the issue and show setup if the active project has not connected Linear.

When to use which form

Need	Use
Jump back to MY lane from another terminal on the same Mac	ade://lane/<uuid>
Jump back to a Work session on this Mac	ade://session/<id>
Jump to a chat event or terminal scrollback byte offset	ade://session/<id>?event=<n> / ?offset=<bytes>
Open a file and reveal a line	ade://file/src/app.ts?line=42
Open a commit from a local lane or GitHub fallback	ade://commit/<sha>?lane=<uuid>&repo=owner/repo
Open a local proof artifact/history entry	ade://artifact/<artifact-id>
Share a branch with a teammate or your other devices	https://ade-app.dev/open?type=branch&…
Drop into a PR's detail tab	https://ade-app.dev/open?type=pr&…
Linear "Open in coding tool" hand-off (opens Linear pane)	https://ade-app.dev/open?type=linear-issue&…

Minting a deeplink — ade link

ade link lane <lane-uuid>                                  # local lane link
ade link session <session-id> [--lane <lane-uuid>]          # local Work session link
ade link file <path> [--line N] [--lane <lane-uuid>]        # file link
ade link commit <sha> [--lane <lane-uuid>]                  # commit link
ade link artifact <id>                                      # proof/history artifact
ade link branch <owner/repo> <branch> [--pr <number>]      # cross-machine branch
ade link pr <owner/repo> <number>                          # PR detail
ade link linear-issue <ADE-123> [--branch <branch>]        # Linear hand-off
ade link <url>                                             # round-trip an existing link

# Flags
--ade            # emit ade:// instead of https:// (default: https)
--no-envelope    # skip best-effort repo/branch/PR envelope lookup
--web            # emit the hosted web client URL (https://app.ade-app.dev/...)
--no-clipboard   # print without copying

Every form copies to the clipboard by default and prints the URL to stdout. When a live ADE runtime is bound, ade link lane, session --lane, and commit --lane attach repo/branch/PR envelope params best-effort. Use --no-envelope to skip that lookup and --no-clipboard in scripts.

Concrete examples:

ade link file apps/desktop/src/shared/deeplinks.ts --line 12 --ade --no-clipboard
ade link commit abc1234 --lane 550e8400-e29b-41d4-a716-446655440000 --no-clipboard

Pairing a browser — ade sync web

Run ade sync web --text on, or pointed at, an ADE machine to print the web-client pairing link and 6-digit code. Open the link in any browser, enter the code, and the ADE web client (Work, Lanes, Files, PRs) pairs to that machine — the browser analogue of scanning the phone pairing QR.

Use --open to launch the pairing link in the default browser. Human output copies the link by default; add --no-clipboard for scripts. The same link from desktop Settings > Sync > Web client or the iOS "Pair a browser" screen does the same thing.

Opening a deeplink — ade open

ade open <url>                                             # any ade:// or https://ade-app.dev/open URL
ade open --linear-issue <ADE-123> --branch <branch>        # Linear coding-tool entry point

The CLI hands the URL to the OS, which routes through the registered ade:// protocol back to a running ADE desktop window (or launches ADE cold). If the focused window's project doesn't match the deeplink's repo, the cross-repo banner appears with a "Switch to " button.

Wiring Linear hand-off — ade linear install

ade linear install               # writes ~/.linear/coding-tools.json
ade linear install --dry-run     # show what would be written

Adds an entry so Linear's "Open issue in coding tool" picker can launch ADE. The template uses Linear's documented placeholders ({{issue.identifier}}, {{issue.branchName}}) — Linear does NOT expose the GitHub repo, so the desktop renderer opens the active project's Linear pane to the issue. If the project is not connected to Linear yet, ADE shows a setup modal that routes to Settings > Integrations > Linear.

RPC for programmatic dispatch

For agents working through the ADE RPC layer, deeplinks dispatch via the existing app/navigate method:

// JSON-RPC over the ADE socket (`ade serve` / desktop RPC port)
{ "method": "app/navigate", "params": {
    "target": { "kind": "lane", "laneId": "<uuid>" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "work", "sessionId": "<session-id>", "laneId": "<uuid>" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "file", "path": "src/app.ts", "line": 42, "laneId": "<uuid>" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "commit", "sha": "<sha>", "laneId": "<uuid>", "envelope": { "repoOwner": "anthropics", "repoName": "claude-code", "branch": "feat-x" } }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "artifact", "artifactId": "<artifact-id>" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "branch", "repoOwner": "anthropics", "repoName": "claude-code", "branch": "feat-x" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "pr", "repoOwner": "anthropics", "repoName": "claude-code", "prNumber": 1234 }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "linear-issue", "issueIdentifier": "ADE-123", "branch": "arul/ade-123-feat" }
}}

Use app/navigate (not deeplinks.open) when you have structured fields. Use ade open <url> when you already have a stringified deeplink (e.g. something a user pasted).

Auto-attached deeplinks

ADE automatically appends an "Open in ADE" footer to PR descriptions it creates or adopts (idempotent via an HTML marker), and pushes ADE lane/chat links with repo envelopes to any Linear issue linked to the lane (Linear attachment + one-time comment). Agents do not need to call ade link for those flows — they fire on PR creation / Linear-link events.

Linear card/comment matrix:

Linear-related action	Who adds the ADE link
ade lanes create --linear-issue-json / ade lanes create-from-linear	ADE posts the lane attachment/comment
ade lanes link-linear-issue / ade chat attach-linear-issue / ade linear attach --this-session	ADE posts lane/chat attachments when a lane/session is known
ade chat create --from-linear-issue or ade lanes create-from-linear --start-chat	ADE posts the chat attachment after the issue is attached
ade prs create on a linked lane	ADE posts the PR attachment/footer
ade linear comment, set-state, assign, label, or graphql	The agent should include the relevant ADE link in any Linear comment it writes

If you create new Linear state directly (for example with ade linear graphql), mint the Linear-pane link yourself and comment it back to the issue:

ade link linear-issue ADE-123 --no-clipboard
ade linear comment ADE-123 "Created via ADE. Open in ADE: <paste link>"

Agents should still include a user-facing ADE PR link when handing off a newly created or adopted PR. Use the GitHub PR URL for the browser link and the adeUrl printed by ade prs create. If the PR came from another path, mint the ADE link with:

ade link pr <owner/repo> <number> --no-clipboard

Use that output for the ADE link. Prefer the default HTTPS form in chat and terminal output because it is clickable, shareable, and upgrades into the ADE PRs tab.

When you copy a deeplink from the desktop UI, the lane right-click menu offers Copy lane link, Copy branch link (cross-machine), Copy PR link, and Copy Linear-issue link. The Work session context menu also offers Copy session deep link for returning to the selected terminal/chat session on the same desktop.

What deeplinks NEVER do silently

• Clone a repository you don't have — the user always confirms via the inbound modal that reuses the PRs-tab "Create lane from PR branch" preflight (with its existing safety blocks).
• Mutate state for pure navigation — opening an existing lane is silent; creating one is not.
• Trust the URL params blindly — the parser rejects bad UUIDs, traversal segments, malformed Linear identifiers, and non-https hosts on the mirror form.

Quick command palette for the CTO

# Mint links the user can paste anywhere
ade link branch anthropics/claude-code feat-deeplinks               # share with teammates
ade link pr anthropics/claude-code 1234                             # PR detail
ade link linear-issue ADE-512 --branch arul/ade-512-feat            # Linear hand-off
ade link file apps/desktop/src/shared/deeplinks.ts --line 12         # source location
ade link commit abc1234 --lane <lane-uuid>                           # commit detail
ade link artifact proof-123                                          # proof/history artifact
ade link session <session-id> --lane <lane-uuid>                    # Work session
ade link lane "$(ade lanes list --text | head -2 | tail -1 | awk '{print $1}')"  # current lane

# Open a link locally (any of these reach a running ADE)
ade open ade://lane/<uuid>
ade open ade://session/<session-id>
ade open "https://ade-app.dev/open?type=branch&repo=a/b&branch=feat"
ade open --linear-issue ADE-123 --branch feat-x

# One-time setup so Linear's "Open in coding tool" calls into ADE
ade linear install