Re-run takes you to the script's form pre-filled with that run's variable values, rather than re-executing immediately - this is necessary, not just cautious: stored run.variables already have secret fields redacted to "***" (see the run detail command/variables view), so a true one-click re-run would either fail validation or, worse, silently pass the literal string "***" to the script as a real secret. Pre-filling instead lets the user review/tweak values and forces secret fields to be re-entered, both of which are new safe defaults now that required fields are actually enforced. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
TriggerShell web app
This is the Next.js app that TriggerShell's Python CLI (triggershell dev / triggershell start)
launches — it's not meant to be run standalone with next dev/next start since it needs a
custom server (server.ts) for the WebSocket endpoint.
See the repo root README for how to run TriggerShell end-to-end, and
../docs/ARCHITECTURE.md for how this app is put together.
pnpm install
pnpm dev # tsx watch server.ts - reads TRIGGERSHELL_CONFIG_PATH from the environment
pnpm lint
pnpm typecheck
pnpm db:studio # browse the SQLite database