supacode-deeplinks

Control Supacode worktrees, tabs, and repositories via supacode:// deeplink URLs.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Chia1104/agent-air --skill supacode-deeplinks-chia1104
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supacode-deeplinks
Source: https://github.com/Chia1104/agent-air/tree/main/skills/shared/supacode-deeplinks
Command: npx skills add https://github.com/Chia1104/agent-air --skill supacode-deeplinks-chia1104

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working outside a Supacode terminal session, such as in scripts or other applications, there is no direct way to programmatically control Supacode worktrees, tabs, surfaces, and repositories. This Skill provides the complete supacode:// URL scheme reference so you can dispatch actions with the open command wherever the supacode CLI is not installed. ## Core Features & Use Cases - Worktree Management: Select, run, stop, archive, unarchive, delete, pin, and restyle worktrees, including running specific scripts by UUID. - Tab & Surface Control: Create, focus, rename, split, and destroy tabs and terminal surfaces, with optional command input and background mode. - Repository & Settings Access: Open repositories, create new worktrees with branch and upstream configuration, and jump directly to specific settings sections. - Use Case: From a CI script running outside Supacode, dispatch open "supacode://worktree/$SUPACODE_WORKTREE_ID/run" to trigger the primary run script for a worktree without needing the CLI. ## Quick Start Ask the AI to run the primary script for the current Supacode worktree using a supacode:// deeplink from your terminal.

Frequently Asked Questions about supacode-deeplinks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control Supacode from a script or terminal?▼

Dispatch supacode:// deeplinks with the open command, for example open "supacode://worktree/$SUPACODE_WORKTREE_ID/run". Prefer the supacode CLI when available; use deeplinks only where the CLI is not installed.

How do I find my Supacode worktree and tab IDs?▼

Each Supacode terminal session exposes SUPACODE_REPO_ID, SUPACODE_WORKTREE_ID, SUPACODE_TAB_ID, and SUPACODE_SURFACE_ID as environment variables. Run env | grep SUPACODE_ to discover the IDs for the current session.

When should I use supacode deeplinks instead of the supacode CLI?▼

Use deeplinks only from scripts, other apps, or terminals where the supacode CLI is not installed. The CLI is available in every Supacode terminal session and is always the preferred option.

Why do my commands stop running after archiving a Supacode worktree?▼

Archiving or deleting the worktree you are working in closes your own terminal surface, so subsequent commands never execute. Make archive or delete your final operation after all edits, commits, and reporting are complete.

Do Supacode deeplinks require confirmation for destructive actions?▼

Yes, deeplinks that run commands or perform destructive actions require confirmation unless Allow dangerous actions is enabled in Developer settings. IDs must also be percent-encoded, though SUPACODE_REPO_ID and SUPACODE_WORKTREE_ID already are.