Hycli README

项目的 README,来自 github.com/Hybirdss/Hycli。合并为一个 markdown 文件:README.md。

Hycli — Websites, ready for AI.

Turn any website into a typed CLI and MCP server for your AI agent.
Read, search, create, edit, and automate—using your real browser login, with zero cookie leaks to LLMs and built-in anti-bot resilience.

Release 0.1.1 Apache-2.0 license CLI and MCP 20 languages

Download (Windows · macOS · Linux) · Help and feedback · 30-second quickstart · What your AI can do · Common concerns · Use with your AI · 한국어 · 日本語

Read in your language · 20 languages

English · 한국어 · 日本語 · 简体中文 · 繁體中文 · Español · Français · Deutsch · Português (Brasil) · Bahasa Indonesia · Italiano · Nederlands · Polski · Türkçe · Русский · Українська · Tiếng Việt · ไทย · العربية · हिन्दी

Give Hycli any website URL and what you want to do. Three AI workers inspect its docs, frontend bundles, and live browser network traffic to build a typed CLI and MCP toolset—covering both reads and writes—without ever mutating your account during setup.

Hycli example workspace with Discord, GitHub, Notion, Naver Blog, Netflix and Slack.

One local dashboard and CLI for your websites, accounts, and AI agents.

Try it in 30 seconds

# 1. Point Hycli at any website and describe your goal (prepares reads & writes; zero live mutations)
hycli prepare https://your-website.example --intent "Search posts, save drafts, and publish articles"

# 2. See every prepared read, write, and multi-step workflow
hycli describe your-website

# 3. Run read actions immediately
hycli your-website search-posts --query "release notes"

# 4. Enable writes once for this CLI when you're ready to create, edit, or delete
hycli writes your-website allow
hycli your-website create-draft --title "Hello from Hycli" --body "Automated from my terminal."

Or connect Hycli to Claude Code, Cursor, Codex, or Windsurf once with "command": "hycli", "args": ["mcp"] and ask your agent in plain language:

"Use Hycli to prepare https://..., show me what actions are available, and draft a new post."

Get started

Hycli ships as a single native binary containing both the website engine and the local dashboard (http://127.0.0.1:4318). Neither Rust nor Node.js is needed to run a release package.

Download and run (Windows, macOS, Linux)

Download the native installer or portable archive for your platform from Releases (v0.1.1):

Platform Architecture Native Installer Portable Archive How to start
Windows 10/11 x64 & ARM64 hycli-0.1.1-win32-*-setup.exe hycli-0.1.1-win32-*.tar.gz Run *-setup.exe (adds hycli to your user PATH and Start Menu), then launch Hycli or run hycli open in PowerShell.
macOS 13+ Apple Silicon (arm64) & Intel (x64) hycli-0.1.1-darwin-*.dmg hycli-0.1.1-darwin-*.tar.gz Open the .dmg, drag Hycli.app to Applications, and open it (automatically links hycli into ~/.local/bin).
Linux x64 & ARM64 hycli-0.1.1-linux-*.deb hycli-0.1.1-linux-*.tar.gz Install the .deb (sudo apt install ./hycli-*.deb) or extract the .tar.gz and run ./install.sh, then run hycli open.

Published v0.1.0: Windows and macOS portable archives do not include installation scripts. Use the Windows *-setup.exe or macOS .dmg installer from the release above instead.

Quick terminal install & build from source

The archive commands below require a package containing install.sh (Linux/macOS) or install.ps1 (Windows), such as a package built from current source.

Linux / macOS portable archive:

sha256sum -c hycli-0.1.1-*.tar.gz.sha256   # or: shasum -a 256 -c on macOS
tar -xzf hycli-0.1.1-*.tar.gz
cd hycli-0.1.1-*
./install.sh
hycli open

Windows PowerShell portable archive:

tar -xzf hycli-0.1.1-win32-x64.tar.gz
cd hycli-0.1.1-win32-x64
powershell -ExecutionPolicy Bypass -File .\install.ps1
hycli open

Build from source (Linux, macOS, Windows):

Install the build prerequisites and run:

node scripts/build.mjs
./dist/hycli open

Run node scripts/package-desktop.mjs to produce the native .exe, .dmg, or .deb installer for your OS. See building and packaging and release verification.

Connect your first website

  1. Run hycli open (or click the Hycli app icon) to open the local dashboard at http://127.0.0.1:4318.
  2. Open AI connections and connect OpenAI, Anthropic Claude, xAI, Z.ai, or your local ChatGPT Codex login.
  3. For logged-in sites, click Accounts → Find my sign-in to import your browser session into the local vault.
  4. Enter a website URL and optional goal, or copy the MCP config from Coding agents into your AI assistant.

What your AI can do

Hycli turns real website interfaces into self-documented CLI subcommands and MCP tools:

Website interface Prepared capability
REST and OpenAPI Typed read and write actions grounded in JSON/YAML schemas and API docs.
GraphQL Parsed query and mutation documents with typed JSON variables.
HTML & JS-rendered pages Structured records, links, pagination, and rendered GET reads via a local Chromium engine.
JSON and URL-encoded forms Documented inputs, defaults, and account-scoped form submissions (POST, PUT, PATCH, DELETE).
Real Hycli AI connection screen using demonstration data.A completed action in the real Hycli dashboard using a synthetic local service.
Choose the AI that prepares your websites.Inspect actions and structured results locally.

Three workers. One very busy little bird.

Three workers. One very busy little bird.

Action type Execution behavior
Read or search Runs immediately when grounded in evidence and classified as a safe read.
Create, send, edit, or delete Discovered and synthesized into the CLI without ever running during preparation. Off by default (writes: false). Your AI agent asks you once per CLI whether to enable writes (hycli writes SITE allow or MCP hycli_writes). Once enabled, write actions execute directly when you ask for them.
Unclear effect Held for review before sending.
Auth challenge or rate limit Switches transport strategy (HTTP → in-page window.fetch → stealth Chromium) or pauses cleanly.

See the operation reference for supported request shapes and extraction rules.

Common concerns and how Hycli solves them

Connecting an AI agent to real websites and logged-in accounts raises serious questions. Here is how Hycli handles each one by design:

1. "Will the AI accidentally post, edit, or delete data on my account?"

2. "Does Hycli send my cookies, login tokens, or API keys to the AI model?"

3. "Will scraping trigger CAPTCHAs or get my account banned?"

4. "Can a redirect leak my session, or can a shared spec expose my computer's paths?"

5. "Will the AI waste tokens retrying when my login expires?"

AI connections

Provider Authentication
ChatGPT · API key OpenAI API key
Claude Anthropic API key
xAI xAI API key
Z.ai / Z.ai Coding Plan Z.ai API key
ChatGPT · login Local ChatGPT sign-in via the official Codex app-server protocol

The Codex login connection runs in an ephemeral thread with file, shell, browser, and external MCP execution disabled; Hycli never reads or copies Codex OAuth tokens.

Use Hycli with your AI

MCP lets an AI app call Hycli tools. It does not connect that app's subscription to Hycli's AI connections. Hycli's Claude provider uses an Anthropic API key. Its ChatGPT login provider uses the Codex app-server protocol described above.

Open Coding agents → View connection settings in Hycli. For manual setup, preserve the generated executable path, arguments, and HYCLI_DATA_DIR so the client uses the same installed sites and accounts.

For clients that accept mcpServers JSON, this is a minimal example. Use the generated settings rather than replacing their path, arguments, or data directory with this example:

{
  "mcpServers": {
    "hycli": {
      "command": "hycli",
      "args": ["mcp"]
    }
  }
}

Use hycli mcp --sites-only to expose only installed website tools, or add --only-site SITE to scope to a single site. The MCP server provides hycli_prepare, hycli_writes (enables writes once per CLI after asking you), hycli_run, hycli_check, hycli_result, and hycli_activity—and never exposes a tool for reading credentials.

From the terminal, every workflow works the same way:

hycli prepare https://your-website.example --intent "Find saved references"
hycli request SITE "Add draft editing and publishing with full post content"
hycli describe SITE
hycli SITE ACTION --help
hycli writes SITE allow
hycli SITE ACTION --query "design systems"
hycli check SITE

See the Hycli skill and agent guide (CLAUDE.md) for how coding agents discover capabilities, summarize available read/write actions for you, ask once per CLI before enabling writes, and recover from failures.

Browser sign-in

Hycli discovers local Chrome, Chromium, Edge, Brave, Vivaldi, Arc, Whale, and Firefox profiles (plus local stealth Chromium binaries when installed) on Windows, macOS, and Linux, importing only the requested website's session into the local vault. Profiles sharing the same verified website account are deduplicated automatically.

Native discovery is optional. In Settings, choose whether Hycli may scan local browser sessions. It defaults off on macOS, including upgrades without a saved choice; Windows and Linux retain the enabled default. The choice applies to the dashboard, CLI and MCP using the same data directory (HYCLI_DATA_DIR when configured), including already-running processes. Enabling it does not start a scan: use Find/Recheck explicitly. Native access may request OS keychain approval.

Turning it off preserves imported accounts and the browser companion connection. If a native attempt does not complete, automatic retries pause. Finish or dismiss any existing OS prompts before choosing Find/Recheck again; a still-running scan must finish first. Cancellation prevents further work cooperatively but cannot dismiss dialogs the OS already displayed. See recovery guidance.

If a session is locked by Windows App-Bound encryption, private containers, or an unimported browser, use Accounts → Connect an account to sign in via your browser, connect the browser companion extension, or import a JSON/Netscape cookie file in the dashboard (never paste cookies into an AI chat).

Languages

The dashboard and AI-generated action descriptions support the 20 languages linked at the top of this README, including right-to-left Arabic.

Local data and request limits

Website definitions, encrypted credentials, and activity logs live in your OS data directory (%LOCALAPPDATA%\hycli on Windows, ~/Library/Application Support/hycli on macOS, ~/.local/share/hycli on Linux, or HYCLI_DATA_DIR). Inspect active vault protection anytime under Settings.

Development and verification

See CONTRIBUTING.md and CHANGELOG.md. Run the full verification suite locally with:

npm --prefix dashboard ci
npm --prefix dashboard run check
npm --prefix dashboard run build
cargo test --all-targets --locked
cargo test --locked --features dashboard-test-support --test codex_launch
cargo build --locked --bin hycli
cargo build --locked --features dashboard-test-support --example dashboard_fixture
node scripts/test-e2e.mjs --full

All tests run against synthetic local websites and fixtures—never test write operations against a real third-party account.

Community

For setup questions and ideas, open an issue. Use the issue templates to report a reproducible bug or request an improvement.

hycli feedback requests a browser to open a generic issue editor with the Hycli version and platform in the title and body. It always returns JSON containing url and launch_requested; the latter only says whether the browser launcher started, not whether a page opened. If no page opens, open the returned URL yourself. The command exits successfully even without a launcher.

No issue is submitted automatically. Opening the URL contacts GitHub and sends the version and platform in the URL, along with ordinary browser request metadata. Review the public issue before submitting and remove credentials, cookies, account details and private website data.

License and intended use

Hycli is licensed under Apache-2.0. Use it only with websites and accounts you are authorized to access. Provided "as is" without warranty; the authors and contributors are not liable for any losses, account restrictions, or bans resulting from its use.

Star History

Star History Chart

For a known JSON or GraphQL endpoint before a website action exists, see bounded verified-account reads: hycli accounts read ACCOUNT --request REQUEST.json.

Hycli (Hybirdss/Hycli)

正在搜索数据库…

473 ·GitHub
这是什么?Hycli 可以把任意网站变成带类型的 CLI 和 MCP 服务器,让 AI 智能体使用你真实的浏览器登录状态,读取、搜索、创建、编辑网站内容并实现自动化操作,并内置反机器人检测应对机制。
这是命令行工具、桌面应用,还是 MCP 服务器?这三者都包含在一个原生二进制文件中:本地控制面板、带类型的 CLI,以及可供 AI 编程智能体直接调用的 MCP 服务器。
怎样让它运行起来?从 v0.1.1 的 GitHub Release 下载适合你操作系统的原生安装包或便携压缩包,安装后运行 'hycli open',即可启动本地控制面板并连接你的第一个网站。
使用它需要安装 Rust 或 Node.js 吗?不需要,发布的二进制文件是自包含的;只有在从源码构建 Hycli 时才需要 Rust 和 Node.js。
AI 会不会意外地在我的账号上发帖或删除内容?写入类操作(创建、编辑、删除)在设置过程中只会被发现,不会被执行;而且每个新的网站 CLI 都默认禁用写入,直到你明确批准一次为止。
Hycli 会把我的 Cookie 或登录令牌发送给 AI 模型吗?不会,Cookie、令牌和 API 密钥都保存在本地加密保险库中;AI 模型只能看到账号标签和经过脱敏处理的结构信息,永远看不到真实的敏感凭据。
哪些 AI 编程智能体和聊天应用可以连接 Hycli?Hycli 通过 MCP 连接 Claude Code、Cursor、Codex、Windsurf、Claude Desktop 和 ChatGPT;它自身的 AI 连接则支持 OpenAI、Anthropic Claude、xAI、Z.ai,或本地的 ChatGPT Codex 登录。
Hycli 如何避免账号被封或触发验证码?它从不对接口进行模糊测试,会按网站和账号对请求进行串行处理并限制频率;遇到机器人验证时,会从普通 HTTP 请求切换到页面内 fetch,或切换到本地隐身 Chromium 引擎。
控制面板支持多少种语言?控制面板和文档提供 20 种语言,包括英语、日语、韩语、中文、西班牙语、法语、德语、阿拉伯语和印地语等。
Hycli 如何登录网站?它会把本地 Chrome、Chromium、Edge、Brave、Vivaldi、Arc、Whale 或 Firefox 配置文件中已有的会话导入到其本地保险库中,且仅限于目标网站的域名范围。
作者
Hybirdss
大小
11 MB
星标
473
时长
1个月
提交 · 90 天