What's new in 0.5.0

0.5.0 gives AI apps and integrations their own section, shares private hostnames with WARP users and makes an agent's changes wait for a person. This page groups what changed, with a link to each guide; 0.4.0, 0.3.0 and 0.2.0 follow below.

0.5.0

• AI & Integrations. AI apps, agents, shared MCP servers, the browser extension and other programs in their own sidebar section. AI apps are found by the installed app and say whether they're connected, need updating or are left over; Test Connection lists the tools they'll see. New: GitHub Copilot CLI, opencode, Kiro, LM Studio and Junie. AI agents · Browser extension
• Private hostnames. Share a name such as wiki.internal with WARP users, next to private IP ranges. Share a private hostname
• Approvals that need a person. In ask mode a change waits for your answer in Teitunnel or your AI tool (approveInApp); MCP protocol 2026-07-28; outside content marked as untrusted. Approvals
• Harder OAuth for shared MCP servers: safe refresh token rotation, disconnecting ends a connection at once, 90-day lifetime, rate-limited sign-ins.
• Fixes: teitunnel share --on finds the app's connector instead of starting a second one; teitunnel mcp status says when an entry's teitunnel is gone.

0.4.0

• GitHub and Google sign-in. Let in the members of a GitHub organization or team (github:teispace/Developers), and limit the login to the account's GitHub or Google login method with Log in with. Require a login
• Bypass the cache. Stop Cloudflare caching one hostname, so a dev server's changes show at once. Edge protection · Dev servers
• Faster imports. Several routes' DNS records are created in one call per domain, applied all or nothing.
• Fixes: the Linux AppImage includes the tray library; permission messages say how to add a permission when you signed in with Cloudflare.

0.3.0

Reliability

• Tunnels recover by themselves. After a wake, a new network or coming back online, connectors reconnect within seconds instead of waiting out a retry, and one that kept failing while you were offline is tried again every 10 minutes and as soon as the network returns. "Down" notifications wait 90 seconds after a wake or network change. Observability
• Pages that load but are broken. After you share, the check reads the page and names links visitors can't follow, to localhost or over plain http://, with the setting to change for your framework. Dev servers

Inspect and debug

• A live Overview: traffic, errors, uptime and the latest requests.
• Breakpoints: hold a request or its answer, change it, answer it yourself or drop it. Inspector
• WebSocket messages: filter by direction, search, and open one to read it whole.
• Traffic Numbers for any share or route, Quick Shares included: requests per second, status codes, countries, browsers and bots. Analytics

Sharing and protection

• Pause and resume a Quick Share from its card; pause and schedule routes from the Routes view. Sharing
• Protect a Quick Share with a password, a secret link or a token from its card. Protect a Quick Share
• Webhooks skip a route's login: keep a login on the site while /webhooks stays open for Stripe or GitHub. Require a login
• The browser extension: share the local page you're on from Chrome, Edge, Brave, Arc, Vivaldi or Firefox. The store listings follow. Browser extension

AI agents

• claude.ai and ChatGPT sign in to MCP servers you share, each connection approved in Teitunnel. Put an MCP server online
• New tools: test how an app copes with slow networks and failures, a route's health, local HTTPS addresses for dev servers, offline pages and webhook inboxes. AI agents

Fixes

• Settings opens on Windows; on macOS the app, the command and agents share keychain items.
• Removing a hostname's last route, or a tunnel, removes everything attached to it, and the Doctor cleans up what earlier versions left.
• Undoing a change restores a signature-checking webhook inbox with its secret.

0.2.0

0.2.0 is the biggest release since the first beta: Teitunnel now inspects traffic, publishes static copies of sites, protects hostnames at Cloudflare's edge, serves local HTTPS domains and works with AI agents. This page groups what changed since 0.1.1, with a link to each guide.

Accounts

• Sign in with Cloudflare. Connect an account with one consent screen instead of creating an API token. Four scopes are required; the rest are optional, and anything you decline is offered again, in place, when you use the feature that needs it. Accounts and permissions
• Fix it where you are. A missing permission shows which dashboard permission to add and why, and Teitunnel checks again when you come back. An account that has never used Cloudflare Zero Trust gets a Set up Cloudflare Zero Trust card instead of an error. When a permission is missing
• One sign-in for the app, the command and agents. They share one access token through the keychain, so one of them refreshing can't sign the others out.
• Account-owned API tokens (Cloudflare's recommendation for servers and CI) work.
• The token link asks for the permissions of every new feature (Workers, D1, WAF, Transform Rules, service tokens, analytics). Every permission

The teitunnel command

• It's teitunnel now, not teitunnel-cli, everywhere: the archives, Homebrew, the Linux packages and the Docker image. Update scripts that call the old name.
• It comes with the app. The Windows installer and the Linux packages put it on your PATH; the macOS disk image and the AppImage offer it once, and Settings ▸ General ▸ Command line manages it. The teitunnel command
• It uses the running app for share, shares and routes, so a share started in a terminal shows up in the app and keeps running there. --here keeps it in the terminal.
• teitunnel top, a live dashboard of shares, routes and requests, and teitunnel status. Shell completions now complete your hostnames, tunnels, domains and accounts. Command line

Sharing

• Dev servers just work. Vite, webpack, Angular, Next.js, Rails and Django refusing an unknown host is recognised, with a one-click fix. Dev servers
• Pause and resume a share or route on your domain: the address stays and visitors see a paused page. Schedules keep one online only during set hours. Pause, schedule, name and share folders
• Stable and branch names such as {branch}.dev.yourhost.com, filled from your project.
• Share a folder of files, with a listing or as a single-page app, without a server.
• The exposure check looks for .env files, .git, debug pages and open admin tools before anything goes public. Exposure check
• One-click sharing from the menu bar or tray, and an optional global shortcut. The menu bar and tray
• Quick Shares ignore a leftover ~/.cloudflared/config.yml that used to break them.

Inspect and debug

• The inspector shows every request to a share or route: headers, bodies, timing. Replay, edit, compare and export them (cURL, HAR and more), with credentials masked. Quick Shares are inspected by default; a route when you choose to. Inspector
• OpenAPI from traffic: an API description inferred from what the inspector saw. OpenAPI from traffic
• Analytics, uptime and alerts: traffic per hostname from Cloudflare's edge, uptime checked every minute, and alerts when a route goes down or slows. Analytics, uptime and alerts
• Share an MCP server or a local AI server behind a bearer token (teitunnel share --mcp, --ai). Inspector

Publish

• Snapshots: a static copy of a folder, a build or a running site, published to your own Cloudflare account, online while your computer sleeps. Versions, rollback, passwords and logins. Snapshots
• Comments: reviewers pin comments to a share or Snapshot; you answer from the app, the terminal or an agent. Comments
• Offline page: your own page instead of Cloudflare's error 1033 while your computer is off. Offline page
• Webhook inbox: webhooks sent while your computer is off are kept and delivered in order when it's back. Webhook inbox

Protect

• Edge protection for one hostname: challenge or block bots and AI crawlers, rate limit visitors, set or remove headers. Never applied to a whole domain. Edge protection
• Service tokens let CI, scripts and servers through a login. The secret is shown once and never stored. Service tokens

On your computer

• Local HTTPS domains: https://shop.test, app.localhost or name.local for a local service, with a certificate browsers trust, no Cloudflare account needed. Local domains
• Move to a new computer with an encrypted backup of your setup (never a token or password). Move to a new computer
• Import finds every cloudflared setup, including Windows service configs and files not named config.yml. Import

Automate and work as a team

• Project files: a teitunnel.yml in your repository describes routes, shares, Snapshots and local domains; teitunnel up applies it. Project files
• Pull request previews with a GitHub Action or GitLab CI template, and hostname reservations so teammates sharing one account see who holds a name. Previews in CI and teams
• Links and integrations: teitunnel:// links, a local control connection, and extensions for VS Code, Raycast and JetBrains IDEs. Links and integrations

AI agents

• An MCP server gives Claude Code, Cursor, VS Code, Codex and other agents Teitunnel's abilities: share, add routes through reviewed plans, run the Doctor, read traffic. Settings ▸ AI Tools connects them in one click, and teitunnel mcp install does it from a terminal.
• You approve every change in a native dialog when the app runs, and every agent change is in Activity. Secrets never reach the agent. AI agents

Under the hood

• Current Cloudflare API throughout: tunnel connections from their own endpoint, record type changes through Cloudflare's batch endpoint (pointing an existing A record at a tunnel failed before), and Access applications with reusable policies.
• Actions stay busy until their result is on screen, and every view shows a placeholder while it loads, so a click never looks like it did nothing.
• Disconnecting an account leaves nothing behind: its temporary shares end and everything Teitunnel remembered about it is deleted.
• The window opens drawn, and slow Cloudflare waits say what they're waiting for.

The full list of changes for each version is in the release notes on GitHub.

Related