← ClaudeAtlas

throughlinelisted

Use when the user asks to use Throughline from Codex, continue or restore Throughline memory, prepare a new Codex thread handoff, summarize a captured Codex session, or check whether the Throughline Codex Stop hook captured the current session. Hide long Throughline command details behind this workflow.
kitepon-rgb/Throughline · ★ 4 · AI & Automation · score 77
Install: claude install-skill kitepon-rgb/Throughline
# Throughline Use this skill to operate Throughline from Codex without making the user type long commands. If the user invokes `$throughline` by itself, treat that as a request to prepare a fresh Codex thread handoff from the current Throughline memory. The normal path is not a current-thread trim/rollback path: it starts a new Codex thread through app-server, injects the handoff memory as a developer item, and opens that thread in the selected host. ## Core Rule Do not ask the user for a Codex thread id when the current environment can provide it. Prefer the current `CODEX_THREAD_ID` / `THROUGHLINE_CODEX_THREAD_ID` identity. For bare `$throughline`, do not run doctor / dry-run / preflight first and do not ask for confirmation. Execute the handoff-start command directly. If it fails, report the error plainly instead of silently falling back to another memory source or current-thread rollback. Choose the open host from the current Codex application surface, not from environment variables inherited by the shell or a persistent PTY. Pass it explicitly whenever the surface is known: - Codex Desktop: `--open-host desktop` - Codex in VS Code: `--open-host vscode` - Codex CLI: `--open-host cli` Use `--open-host auto` only when the Codex surface is genuinely unknown. In that case, report both the requested and resolved hosts from the CLI result. ## Common Requests ### Bare "$throughline" / "use Throughline" Run: ```bash throughline codex-handoff-start --execute --open-hos