English · 简体中文

Use the AI providers you already have—through the browser, without provider API keys.
Tokenless gives agents one local interface for visible AI workflows while reducing agent-side token use.

Quick start · CLI · Capabilities · Privacy

_{Captured from a real local browser session; token totals and job states are actual local dashboard data, not a benchmark.}

10 providers. One local interface.

Four providers are supported today; seven more are experimental and fail closed when a workflow is not verified.

ChatGPT Supported	Claude Supported	Gemini Supported	Grok Supported	Qwen / 千问 Experimental
DeepSeek Experimental	Perplexity Experimental	Z.ai / GLM Experimental	Doubao / 豆包 Experimental	Kimi Experimental
Dola Experimental

See the Capability Matrix for the verified workflows behind each provider.

Start in three commands

Browser features require Node.js 22.13+ and a current Google Chrome or Brave Browser release that exposes its browser-managed remote debugging endpoint. Apple Silicon macOS is the current target, and Windows x64 remains prerelease.

Chrome and Brave are user-supplied browsers: Tokenless does not bundle or download either one. If setup cannot find the selected browser, it still saves configuration, skips provider checks, and ends with instructions for adding an executable path. The first browser action validates that path or retries standard discovery. During setup, CloakBrowser is the only browser runtime Tokenless downloads and prepares.

Before setup, open chrome://inspect/#remote-debugging in your everyday Google Chrome or brave://inspect/#remote-debugging in Brave, enable remote debugging, and approve the browser's connection prompt. The browser manages the underlying CDP endpoint and Tokenless discovers it automatically, so you do not launch it with --remote-debugging-port or configure a fixed port. Tokenless tests capability by connecting; it does not copy your profile or launch another browser.

npm install --global tokenless@latest
tokenless setup
tokenless run --provider chatgpt --prompt "Review this proposal."

Setup asks about Anti-Detect mode first. If you decline, choose Google Chrome or Brave; Tokenless then creates a logical profile, connects to that running headed browser, checks enabled providers, and opens the local dashboard. Reopen it later with tokenless dashboard.

Native mode is headed-only for now. Stopping or restarting the Tokenless daemon disconnects automation but does not close the selected browser.

Explicit Anti-Detect setup can instead install a checksum-pinned CloakBrowser from its official GitHub release on macOS arm64/x64, Linux arm64/x64, or Windows x64. These catalog paths do not imply real-provider acceptance on every host; Tokenless does not bundle or redistribute CloakBrowser.

What agents get

• Prompts, visible responses, and citations through real provider websites.
• File uploads plus verified model, reasoning, and provider-specific controls.
• Stable provider tabs, task continuity, and supported native Projects.
• Browser state and credentials remain in your Chrome; job history and token-savings estimates remain local.

Optional Codex integration

Install delegation guidance and exact invocation continuity without wrapping or replacing Codex:

tokenless setup --install-codex
# Or install it separately after setup:
tokenless agents install codex

Setup never installs the integration by default; --codex-home <dir> is available only with --install-codex. Restart Codex, open /hooks, and trust the Tokenless hook definition.

Go deeper

• CLI commands
• Capability Matrix
• Privacy boundaries
• Architecture
• Documentation index

Tokenless is in early access: it reduces agent-side token use, but does not eliminate token use or bypass provider account requirements.