with one click
happytrails-stop
Stop the active HappyTrails session and shut down the server
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.
Menu
Stop the active HappyTrails session and shut down the server
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.
Based on SOC occupation classification
| name | happytrails-stop |
| description | Stop the active HappyTrails session and shut down the server |
| invocable_by | ["user"] |
Read <CWD>/.happytrails/.active to get the log file path.
If the file does not exist, tell the user there is no active HappyTrails session.
Derive the session directory as the parent of the log file path
(e.g., if .active contains /project/.happytrails/12345/log.jsonl,
the session directory is /project/.happytrails/12345).
Read <SESSION_DIR>/.server.pid to get the server process ID.
If the file does not exist, or the PID is not running (kill -0 <PID> fails),
tell the user the server is already stopped and remove the stale .active file:
rm -f <CWD>/.happytrails/.active
Send SIGTERM to stop the server (it handles cleanup automatically):
kill <PID>
Do NOT remove the hook — it is managed by the plugin and reused across sessions.
Confirm to the user that capture has stopped.