← ClaudeAtlas

open-guilisted

Use when the user wants a browser-based GUI for a Claude Code session — "open a GUI", "browser terminal", "web version of claude", or a live decision-tree panel alongside the conversation. Also the dependency other skills reach for when they need a session running in a browser (e.g. grill-with-web) — invoke it with a seed prompt and topic rather than reimplementing PTY/browser plumbing.
wayne930242/grillboard · ★ 1 · Web & Frontend · score 72
Install: claude install-skill wayne930242/grillboard
# open-gui Spin up a fresh, independent `claude` session driven through the Agent SDK, with a card-based conversation pane and a live typed-node tree panel beside it (see DESIGN.md's D11). `AskUserQuestion` calls render as live interactive cards and are answered structurally — no terminal, no keystroke emulation. **Passive by default.** Once launched, do not poll it, do not wait for it, do not close it. The session runs until the user or a calling skill stops it. This is the one rule every step below exists to protect — read [Passive lifecycle](#passive-lifecycle) before you do anything that looks like waiting. ## 1. First-run setup Run `${CLAUDE_PLUGIN_ROOT}/skills/open-gui/init.sh` (macOS/Linux) or `${CLAUDE_PLUGIN_ROOT}/skills/open-gui/init.ps1` (Windows — best-effort, unverified on a real Windows machine). It's idempotent: installs Deno if missing, checks for Node.js (needed only for the frontend's own build tooling — the backend itself is pure Deno, including the Agent SDK via an `npm:` specifier), and builds the frontend — each step skipped if already done. ## 2. Determine session parameters - `cwd`: the target project root. Default to the current working directory unless told otherwise. - `topic`: a short label for the session (shown in the browser). Derive from what the user asked for; default to `"open-gui session"` if nothing specific was said. - `seed prompt` (optional): only construct one if there's real content to seed the new session with — a topic, backgr