tunelito

Run a Tunelito live review room for a local HTML/Markdown file or folder, then process the comments it collects. Use whenever a user wants to share, serve, or preview a local .html page, .md memo, or static site/mini-site from their machine so a designer, client, teammate, or PM can leave feedback on a call; wants a temporary public link to a local page; says "review my HTML", "annotate this page", "review this Markdown draft", "let people comment on my site", "get feedback on index.html", "spin up a review room", or "review this page locally without exposing it"; OR points you at a `*.comments.md` / `site.comments.md` inbox and asks you to apply, process, or act on the comments inside it. Covers starting and sharing a session (Cloudflare Tunnel, keyed bearer URLs), local-only review of sensitive pages, active-agent `tunelito inbox` commands, the opt-in `--agent` worker that edits files from comments, and the comment Markdown schema (scope, page, path, id, status). Do NOT use for reviewing a pull request, IDE

Update or review Tunelito documentation. Use when README, changelog, release docs, examples, security docs, or agent playbooks need to stay in sync with behavior.

Run a live local Tunelito smoke test against an HTML page. Use before declaring browser/client/server/package changes ready.

Prepare Tunelito changes for a PR-ready commit and push, including verification and handoff summary.

Maintain Tunelito npm package quality. Use for package.json, package-lock, npm pack, npm install smoke tests, CI workflows, release docs, or distribution changes.

Prepare a Tunelito package or npm release using the release playbook and package verification.

Maintain Tunelito's agent operating system. Use when editing AGENTS.md, CLAUDE.md, .claude hooks, .claude skills, .claude agents, or docs/agents playbooks.

Reproduce and fix Tunelito bugs. Use when behavior is broken, tests fail, comments do not sync, tunnels fail, mobile selection fails, or the CLI does something surprising.

Implement a Tunelito feature or bug fix following repo playbooks, tests, docs, and release-safe habits.

Prepare a GitHub PR or PR-ready summary for Tunelito changes. Use when opening a PR, updating PR notes, or summarizing commits for review.

Review the current Tunelito diff for bugs, regressions, security issues, missing tests, and docs drift.

Audit or implement Tunelito security-sensitive changes. Use for tunnel sharing, review keys, cookies, WebSocket auth, file serving, hooks, secrets, or package publishing.

Orient a new agent in Tunelito. Use at the start of any Tunelito session, after compaction, when resuming work, or when the user says to keep going.