TailClaude Puts Claude Code in the Browser

Running Claude Code from a phone usually means juggling a terminal, keyboard shortcuts, and connection management. TailClaude replaces all that with a browser-based interface you can open on any device.

It can publish access through Tailscale Funnel, so the interface is reachable outside your tailnet too.

What Happened

TailClaude is a new layer for Claude Code that runs an iii engine, a TailClaude worker, and a Node.js proxy. The proxy spawns Claude Code requests, streams chat events, records operational data, and can expose the whole thing through Tailscale.

The feature set covers the workflows you would normally expect from a desktop terminal:

• Real-time SSE chat streaming shows generated tokens, tool-use badges, input/output token counts, and per-message cost.
• Session discovery indexes and browses Claude Code sessions from terminal and web use, loads conversation history, and restores the last browser session.
• Claude Code controls include Opus, Sonnet, and Haiku selection; permission modes; effort levels; per-message budget limits; system prompts; and MCP-server settings.
• The usage dashboard aggregates daily and seven-day cost, request, and token data, including historical session-cost backfill from Claude Code JSONL files.
• System and request observability includes CPU, memory, event-loop-lag timelines, overload alerts, and request traces with model, duration, cost, tokens, and exit status.

Why It Matters

For anyone who uses Claude Code on the go, this removes the need for a heavy terminal setup. The browser interface plus Tailscale Funnel means your session can be waiting for you on any device, and the dashboard gives you the same cost and token visibility you would have on a desktop.