菜单
Bootstrap or repair a Ship of Tools backend Codex session, including generic Codex comm setup, socket-only relay awareness, frontend reachability ping, and backlog handling. Use for BE session start, backend comm repair, or after restarting a backend Codex pane.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Bootstrap a (re)started Ship of Tools FE session — set the win-fe handle, point relay sends at the local SSH tunnel to the backend Unix socket, re-arm the fast-comm wake (fe-inbox Monitor), and catch up on anything missed during the down-window. Fires automatically as the first turn after an ADR-0017 FE relaunch (via the [terminal] resume_command, i.e. claude --continue "/sot-fe-session-start"); also runnable manually. Activates for "fe session start", "frontend session start", "session start", "bootstrap session", "rearm fe comm", "rearm comm", "fe bootstrap session", "resume bootstrap".
Bootstrap a frontend-side Codex session for Ship of Tools. Use in a local FE terminal/Codex session to set the win-fe handle, send through the local SSH tunnel to the backend Unix socket, read the frontend-local fe-inbox, and coordinate with backend sessions without relying on old remote TCP.
Surface a result you just produced (saved plot/figure, rendered image, screenshot, PDF, HTML report, built doc, output file) in the user's Ship of Tools nav/preview pane — badge it (shown completely, nav + preview, when the user looks; their session is never stolen), never merely name it in text. Fire whenever your work creates something the user should SEE.
Session-to-session messaging for Ship of Tools sessions (fork of agent-comm, cross-tmux-session and cross-machine on shared $HOME). Use when sending messages between Claude sessions, joining/leaving the sot-comm network, checking for messages, listing who is online, or starting/stopping other sessions (durable peers via ccb/ccbe, ephemeral task agents via comm-spawn). Also activates on receiving a message in "[name:repo] ..." format. Activates for "sot send", "sot comm", "comm send", "comm join", "comm poll", "broadcast to sessions", "@<session>", "comm spawn", "spawn a session", "spawn an agent", "start a session on <repo>", "despawn".
Cut a Ship of Tools release — stamp the product version everywhere, tag, and let CI build+publish the GitHub Release (ADR 0030 Phase B). Activates for "cut a release", "release vX.Y.Z", "tag a release", "publish a release", "new release" in the ship-of-tools repo.
Bootstrap a (re)started Ship of Tools BE (backend / tmux) session so it RECEIVES instant fast-comm — run the generic /sot-session-start receive-bootstrap, then add sot-specific checks: confirm a frontend is reachable, report how many FEs are attached, and pull the .claude-bus git fallback. The BE counterpart of /sot-fe-session-start (which is FE-only). Runnable manually or as a `claude --continue` resume turn. Activates for "be session start", "backend session start", "rearm be comm", "be bootstrap session".
| name | sot-be-session-start |
| description | Bootstrap or repair a Ship of Tools backend Codex session, including generic Codex comm setup, socket-only relay awareness, frontend reachability ping, and backlog handling. Use for BE session start, backend comm repair, or after restarting a backend Codex pane. |
Run sot-session-start first. For Codex launched by ccx, that setup should
already be done; still run comm-poll.sh if there was downtime.
Attached FEs receive daemon relay broadcasts even if no win-fe-* handle exists
in this backend host's ~/.sot-comm/registry.json. Use @win-fe as an advisory
broadcast label:
~/.sot-comm/bin/comm-relay.sh send @win-fe "[$SOT_COMM_NAME] BE receive path armed; any FE please ack."
Do not block on ask during bootstrap. A later FE reply should arrive as a
directed [relay] from win-fe-<host>: line if your Codex wake path is armed.
The backend normally listens on the private Unix socket from:
sotd session-socket-path ${SOT_BACKEND_LABEL:-sot}
The remote backend does not need to bind 127.0.0.1:18743. That port exists only
on a frontend machine when its launcher opens an SSH tunnel to the remote Unix
socket. Browser helper ports 1234-1240 must also be forwarded for docs,
Pluto, and static page previews.
Best-effort report:
comm-listen.sh --selftest passedcomm-poll.sh