跳过界面。把任何网站变成快速、可靠的API， 特工。
超越Claw。调用底层API。
跳过电脑代理

---

🚀 什么是NoUI？

NoUI将任何网站都变成你的代理可以调用的API。

NoUI不再自动点击和抓取界面，而是：

1. 记录你如何使用网站（通过Tabby浏览器会话）
2. 提取底层API
3. 将它们转换为可调用的 Python 函数
4. 通过MCP或作为特工可安装技能来暴露它们

没有点击声。没有DOM解析。没有脆弱的自动化。

NoUI 作为单一、与代理无关的技能包（skills/noui/）发布。该 只有外部依赖是可达的 Tabby——没有独立的后端 服务运行，且不需要LLM API密钥。

---

⚡ 为什么是NoUI？

计算机使用代理模拟人类：

• 🐢 慢速（UI循环，页面加载）
• 💸 昂贵（token-heavy for tokens， heavy step-heavy）
• 🧱 脆弱（UI变更时中断）

NoUI 直接执行软件：

• ⚡ Fast — 直接 API 调用
• 💸 便宜 步骤更少，标记数更少—

NoUI

Skip the UI. Turn any website into fast, reliable APIs for agents.
Go beyond Claw. Call the underlying APIs.
Skip Computer-use Agents.

---

🚀 What is NoUI?

NoUI turns any website into an API your agents can call.

Instead of automating clicks and scraping the UI, NoUI:

1. Records how you use a website (through a Tabby browser session)
2. Extracts the underlying APIs
3. Converts them into callable Python functions
4. Exposes them via MCP or as an installable Skill for agents

No clicks. No DOM parsing. No brittle automation.

NoUI ships as a single, agent-agnostic skill bundle (skills/noui/). The only external dependency is a reachable Tabby — there is no separate backend service to run and no LLM API key required.

---

⚡ Why NoUI?

Computer-use agents simulate humans:

• 🐢 Slow (UI loops, page loads)
• 💸 Expensive (token-heavy, step-heavy)
• 🧱 Fragile (break on UI changes)

NoUI executes software directly:

• ⚡ Fast — direct API calls
• 💸 Cheap — fewer steps, fewer tokens
• 🎯 Reliable — uses the same APIs the app uses internally

Stop automating clicks. Execute software.

---

🧠 How it works

1. Record a session in a Tabby browser — manually in a VNC viewer, or with Autopilot (the agent drives POST /execute/browser)
2. Tabby captures HAR traces + interaction events server-side
3. Compile the capture into Python API functions (a FastMCP server and/or a Skill)
4. Execute tools from inside the authenticated Tabby browser session
5. Install the Skill / run the MCP server in any agent
6. Agents call APIs instead of clicking UI

Execution

Generated tools run from inside the authenticated Tabby browser, not from a Python HTTP client. By default (the tabby execution mode) each operation calls Tabby’s POST /execute/fetch endpoint over plain HTTP; the Tabby worker runs fetch(url, {credentials: 'include'}) inside the real authenticated browser, so the browser’s TLS fingerprint and cookies are used — no credential extraction, and no Akamai/Cloudflare false positives. There is no WebSocket or CDP-port access from the NoUI side.

The legacy Python-side path (httpx + resolved credentials) is still available for server-to-server APIs that aren’t reachable from the browser origin; opt in explicitly when compiling with --execution-mode http.

---

🏗️ Architecture

Tabby browser session
    → VNC (human drives) | Autopilot (agent drives POST /execute/browser)
    ↓ (HAR + click/url events — captured server-side by Tabby)
noui_core  (the skill bundle, skills/noui/)
    → capture/   — drain/synthesize the recording bundle