Run any Skill in Manus with one click

sot-fe-session-start

Stars2

Forks0

UpdatedJuly 11, 2026 at 02:17

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kalidke

kalidke/ship-of-tools

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	sot-fe-session-start
description	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.

sot-fe-session-start

Run this on the frontend machine. The FE machine usually has its own filesystem and registry, so do not expect a local comm-join.sh to create a backend-host registry row.

Handle

Match the native frontend handle:

PowerShell:

$hostName = if ($env:HOSTNAME) { $env:HOSTNAME } elseif ($env:COMPUTERNAME) { $env:COMPUTERNAME } else { "unknown" }
$env:SOT_COMM_NAME = "win-fe-$($hostName.ToLowerInvariant())"

Bash:

export SOT_COMM_NAME="win-fe-$( (hostname -s 2>/dev/null || hostname || printf unknown) | tr '[:upper:]' '[:lower:]' )"

If ~/.sot-comm/bin is installed locally, join with that name so outbound relay messages have the right from::

~/.sot-comm/bin/comm-join.sh --name "$SOT_COMM_NAME"

Endpoint

The backend is socket-only by default. The frontend sends through a local TCP tunnel that forwards to the remote Unix socket:

PowerShell:

$port = if ($env:SOT_PORT) { $env:SOT_PORT } else { "18743" }
$env:SOT_RELAY_ENDPOINT = "tcp:127.0.0.1:$port"

Bash:

export SOT_RELAY_ENDPOINT="tcp:127.0.0.1:${SOT_PORT:-18743}"

Do not probe remote 127.0.0.1:18743. Query the remote socket with sotd session-socket-path sot and forward local 18743 to that socket.

Inbox

The native frontend appends daemon agent.message events to:

Windows: %LOCALAPPDATA%\sot\fe-inbox.jsonl
Linux/macOS FE: ${XDG_STATE_HOME:-$HOME/.local/state}/sot/fe-inbox.jsonl

Codex FE sessions do not automatically get a tmux codex-watch.sh wake unless they are running inside tmux. At turn start, or when told there is FE backlog, read the local FE inbox and answer via comm-relay.sh.

The daemon broadcasts every agent.message to ALL connected FEs; the to field is an advisory label, not enforced routing. Treat as addressed to you: to:<your handle> or the bare to:win-fe family label ("any FE"). Lines aimed at another handle (a sibling win-fe-<otherhost>, backend-dev) and true broadcasts (to:"") are FYIs — anything broadcast that matters is also on the durable git-bus (/bus-sync).

PowerShell backlog check:

$inbox = Join-Path $env:LOCALAPPDATA "sot\fe-inbox.jsonl"
if (Test-Path $inbox) { Get-Content $inbox -Tail 40 }

Bash backlog check:

state="${XDG_STATE_HOME:-$HOME/.local/state}/sot"
[ -n "${LOCALAPPDATA:-}" ] && state="$LOCALAPPDATA/sot"
[ -f "$state/fe-inbox.jsonl" ] && tail -40 "$state/fe-inbox.jsonl"

Ping BE

If the backend handle is known:

~/.sot-comm/bin/comm-relay.sh send @<be-handle> "[$SOT_COMM_NAME] FE relay path armed; please ack."

If no direct route exists yet, use the human-provided temporary dropbox only for that live incident; never commit private machine paths or secrets to the repo.

More from this repository

same repository

sot-fe-session-start

kalidke/ship-of-tools

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".

2026-07-112

show-result

kalidke/ship-of-tools

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.

2026-07-102

sot-comm

kalidke/ship-of-tools

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".

2026-07-102

release

kalidke/ship-of-tools

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.

2026-07-092

sot-be-session-start

kalidke/ship-of-tools

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".

2026-07-082

sot-install

kalidke/ship-of-tools

Install or update Ship of Tools agent resources (Claude Code skills, Codex skills/hooks, and sot-comm scripts) from the package into ~/.claude, ~/.codex, ~/.local/bin, and ~/.sot-comm. Idempotent. Run after pulling the Ship of Tools repo on a machine to close version skew. Activates for "install sot", "update sot comm", "sync sot", "sot install", "reinstall comm".

2026-07-082

name	sot-fe-session-start
description	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.

sot-fe-session-start

Run this on the frontend machine. The FE machine usually has its own filesystem and registry, so do not expect a local comm-join.sh to create a backend-host registry row.

Handle

Match the native frontend handle:

PowerShell:

$hostName = if ($env:HOSTNAME) { $env:HOSTNAME } elseif ($env:COMPUTERNAME) { $env:COMPUTERNAME } else { "unknown" }
$env:SOT_COMM_NAME = "win-fe-$($hostName.ToLowerInvariant())"

Bash:

export SOT_COMM_NAME="win-fe-$( (hostname -s 2>/dev/null || hostname || printf unknown) | tr '[:upper:]' '[:lower:]' )"

If ~/.sot-comm/bin is installed locally, join with that name so outbound relay messages have the right from::

~/.sot-comm/bin/comm-join.sh --name "$SOT_COMM_NAME"

Endpoint

The backend is socket-only by default. The frontend sends through a local TCP tunnel that forwards to the remote Unix socket:

PowerShell:

$port = if ($env:SOT_PORT) { $env:SOT_PORT } else { "18743" }
$env:SOT_RELAY_ENDPOINT = "tcp:127.0.0.1:$port"

Bash:

export SOT_RELAY_ENDPOINT="tcp:127.0.0.1:${SOT_PORT:-18743}"

Do not probe remote 127.0.0.1:18743. Query the remote socket with sotd session-socket-path sot and forward local 18743 to that socket.

Inbox

The native frontend appends daemon agent.message events to:

Windows: %LOCALAPPDATA%\sot\fe-inbox.jsonl
Linux/macOS FE: ${XDG_STATE_HOME:-$HOME/.local/state}/sot/fe-inbox.jsonl

PowerShell backlog check:

$inbox = Join-Path $env:LOCALAPPDATA "sot\fe-inbox.jsonl"
if (Test-Path $inbox) { Get-Content $inbox -Tail 40 }

Bash backlog check:

state="${XDG_STATE_HOME:-$HOME/.local/state}/sot"
[ -n "${LOCALAPPDATA:-}" ] && state="$LOCALAPPDATA/sot"
[ -f "$state/fe-inbox.jsonl" ] && tail -40 "$state/fe-inbox.jsonl"

Ping BE

If the backend handle is known:

~/.sot-comm/bin/comm-relay.sh send @<be-handle> "[$SOT_COMM_NAME] FE relay path armed; please ack."

If no direct route exists yet, use the human-provided temporary dropbox only for that live incident; never commit private machine paths or secrets to the repo.