← ClaudeAtlas

t3-app-linklisted

Monitor Codex and Claude work threads inside T3 through a read-only CLI, with formal questions, RESULT detection, settling, stalls and resumable multi-thread watches. Use when managing T3 threads; use native T3 tools to dispatch or answer them.
transcendr/slopware-skills · ★ 40 · AI & Automation · score 73
Install: claude install-skill transcendr/slopware-skills
# T3 App Link Coming from codex-app-link: | Existing command | In T3 | | --- | --- | | `send`, `send --queue`, `send --steer` | `t3_thread_send`, mode `auto`, `queue`, `steer` | | `new`, `queue`, `interrupt`, `access` | `t3_thread_launch`, `t3_queue`, `t3_thread_interrupt`, `t3_thread_configure` | | Answer a formal question | `t3_pending_request`, action `respond` | | `status`, `read`, `list`, `wait`, `questions`, `result`, `track`, `rules`, `version` | Same verbs in `scripts/t3-thread.mjs` | | `watch`, progress script | `watch`, `watch --progress` | The CLI only monitors. Its dispatch verbs print a native tool call and exit 2. No token with write access is needed. T3 is the only thread-data source. Resolve `TT` from this installed skill's directory each session: ```bash TT=<skill-base-dir>/scripts/t3-thread.mjs node "$TT" setup node "$TT" version ``` Setup reuses the private read-only token, or issues one through T3's bundled CLI. It reads the current origin from T3's runtime file. Requirements and installation are in the plugin README; commands and exits are in [references/operational.md](references/operational.md). ## Dispatch and track Use `t3_thread_launch` for a new thread, or `t3_thread_send` for an authorized existing thread. New work for a busy thread uses mode `queue`; mode `steer` supplies answers or corrections for its current work. Formal questions use `t3_pending_request respond`, not an inferred shared reply. Approvals need the user in T3; the monitor c