docs: optimize deployment guides and expand AI Agent examples

README.md

@@ -54,9 +54,13 @@ The public demo resets every Monday at 1:00 AM (China Standard Time) and restore
 
 ## Deployment
 
+EdgeEver uses a pure Serverless architecture that runs entirely within Cloudflare's free tiers. **No VPS or server rental is required, and there is no need to configure Docker or SSL certificates.**
+
+You can deploy online using either of the following two options:
+
 ### Option A: Deploy with an AI Agent (Recommended)
 
-Copy this prompt into an AI Agent configured with GitHub and Cloudflare MCP servers, plugins, or other integrations:
+Copy this prompt into an AI Agent configured with GitHub and Cloudflare MCP servers, plugins, or other integrations (such as Codex, Claude, Cursor, Antigravity, OpenClaw, Hermes Agent, etc.):
 
 ```text
 Deploy EdgeEver online:
@@ -67,11 +71,18 @@ Deploy EdgeEver online:
 5. Enable and run `Update deployed EdgeEver` once.
 ```
 
-Detailed requirements: [AI Agent Cloudflare Deployment](docs/agent-deploy-cloudflare.md).
+> Detailed requirements: [AI Agent Cloudflare Deployment](docs/agent-deploy-cloudflare.md).
 
-### Option B: Deploy online from a Fork
+### Option B: Manual Online Deployment
 
-Complete deployment in 4 steps: Fork EdgeEver on GitHub, import it into Cloudflare Workers & Pages, configure the required resources, then run and verify the first build. See the [online deployment guide](docs/deploy-cloudflare-button.md) for details.
+No command line needed—complete setup in 4 simple web steps:
+
+1. **Fork the Repository**: Click **Fork** at the top right of GitHub to copy EdgeEver to your personal account.
+2. **Import into Cloudflare**: Log into the Cloudflare Dashboard, navigate to **Workers & Pages**, and choose to import your Fork repository.
+3. **Bind Resources & Password**: Bind the D1 database (`DB`), R2 bucket (`RESOURCES`), and set the Worker Secret `EDGE_EVER_AUTH_PASSWORD` as your admin password.
+4. **Build & Verify**: Start the first build with default settings. Once complete, visit `/api/health` to verify a `200` response before logging in.
+
+> 📖 For full step-by-step instructions and configuration details, see the [Online Deployment Guide](docs/deploy-cloudflare-button.md).
 
 ## Multi-Account Login
 

README.zh-CN.md

@@ -52,9 +52,13 @@ EdgeEver 是一个开源、自托管、Cloudflare-native 的现代笔记工作
 
 ## 部署
 
-### 方案一：AI Agent 部署（推荐）
+EdgeEver 采用纯 Serverless 架构，完全运行在 Cloudflare 免费配额内，**无需购买服务器/VPS，也无需配置 Docker 或 SSL 证书**。
 
-将下方提示词复制给已配置 GitHub、Cloudflare MCP、插件或其他可用集成的 AI Agent：
+您可以选择以下两种方式之一在线部署：
+
+### 方案一：AI Agent 一键部署（推荐）
+
+将下方提示词直接复制发送给已配置 GitHub、Cloudflare MCP/插件或其他可用集成的 AI Agent（如 Codex, Claude, Cursor, Antigravity, OpenClaw, Hermes Agent 等）：
 
 ```text
 请在线完成 EdgeEver 部署：
@@ -65,11 +69,18 @@ EdgeEver 是一个开源、自托管、Cloudflare-native 的现代笔记工作
 5. 启用并手动运行一次 `Update deployed EdgeEver`。
 ```
 
-详细要求见：[AI Agent 在线部署约定](docs/agent-deploy-cloudflare.zh-CN.md)。
+> 详细约定与要求请查看：[AI Agent 在线部署约定](docs/agent-deploy-cloudflare.zh-CN.md)。
 
-### 方案二：Fork 后在线部署
+### 方案二：手动在线部署
 
-共 4 步完成部署：在 GitHub Fork EdgeEver、导入 Cloudflare Workers & Pages、配置所需资源、启动并验证首次构建。详细操作请查看[在线部署文档](docs/deploy-cloudflare-button.zh-CN.md)。
+无需命令行，仅需在网页端完成 4 步极简配置：
+
+1. **Fork 仓库**：在 GitHub 点击右上角 **Fork**，将 EdgeEver 复制到您的个人账户。
+2. **导入 Cloudflare**：登录 Cloudflare 控制台，进入 **Workers & Pages**，选择导入该 Fork 仓库。
+3. **绑定资源与密码**：绑定 D1 数据库（`DB`）、R2 存储桶（`RESOURCES`），并添加 Worker Secret `EDGE_EVER_AUTH_PASSWORD` 作为登录密码。
+4. **启动构建与验证**：使用默认构建配置启动首次构建，部署完成后访问 `/api/health` 确认返回 `200` 即可开始使用。
+
+> 📖 包含具体参数与构建命令的详细步骤，请查看 [在线部署完整文档](docs/deploy-cloudflare-button.zh-CN.md)。
 
 ## 多账号登录
 

docs/agent-deploy-cloudflare.md

@@ -1,17 +1,41 @@
-# AI Agent Cloudflare Deployment
+# AI Agent Cloudflare Deployment Guide
 
-## Steps
+This document defines the standard operating specifications and conventions for AI Agents (and automated deployment scripts) deploying EdgeEver on Cloudflare.
 
-1. Fork `tianma-if/edgeever`.
-2. Enable the Fork's **Update deployed EdgeEver** workflow.
-3. In Cloudflare **Workers & Pages**, import the Fork using the repository root, `main` branch, and existing `wrangler.toml`.
-4. Configure D1 `DB`, R2 `RESOURCES`, and the Worker Secret `EDGE_EVER_AUTH_PASSWORD`.
-5. Configure Workers Builds:
+> 💡 **Core Principle**: Pure Serverless architecture running entirely within Cloudflare free limits—no VPS or server purchasing, no Docker or SSL certificate configuration required.
 
-   ```text
-   Build command: bun install --frozen-lockfile && EDGE_EVER_DEPLOYMENT_TRIGGER=main_push EDGE_EVER_DEPLOYMENT_METHOD=cloudflare_workers_builds bun run build:cloudflare
-   Deploy command: bun run deploy:cloudflare-builds
-   ```
+---
 
-6. Start the first build and verify `/api/health`, `/api/openapi.json`, and login.
-7. Run **Update deployed EdgeEver** once and confirm that upstream updates work.
+## Standard Automated Deployment Steps
+
+1. **Fork Repository**
+   - Fork `tianma-if/edgeever` to the target GitHub account.
+
+2. **Enable Workflow**
+   - In the **Actions** tab of the Forked repository, enable the **Update deployed EdgeEver** automatic update workflow.
+
+3. **Cloudflare Project Import**
+   - Log into the Cloudflare **Workers & Pages** console and import the Fork repository.
+   - Configure the project to use the repository root, the production `main` branch, and read the root `wrangler.toml`.
+
+4. **Resource Bindings & Secrets**
+   - **D1 Database Binding**: Binding name `DB`, associated with database `edgeever`.
+   - **R2 Bucket Binding**: Binding name `RESOURCES`, associated with a globally unique R2 Bucket.
+   - **Worker Secret**: Add secret `EDGE_EVER_AUTH_PASSWORD` for initial admin password.
+
+5. **Configure Workers Builds Commands**
+   - In the Cloudflare project build settings, set the standard commands:
+
+     ```text
+     Build command: bun install --frozen-lockfile && EDGE_EVER_DEPLOYMENT_TRIGGER=main_push EDGE_EVER_DEPLOYMENT_METHOD=cloudflare_workers_builds bun run build:cloudflare
+     Deploy command: bun run deploy:cloudflare-builds
+     ```
+
+6. **Start Initial Build & Verify Service**
+   - Trigger the initial build. Once deployed, run the following automated verifications:
+     - Check `https://<your-worker-domain>/api/health` returns HTTP `200` with JSON `{"ok": true}`.
+     - Check `https://<your-worker-domain>/api/openapi.json` loads the OpenAPI schema properly.
+     - Verify login API using the configured `EDGE_EVER_AUTH_PASSWORD`.
+
+7. **Verify Upstream Update Channel**
+   - Manually trigger **Update deployed EdgeEver** once in the Fork's **Actions** tab to confirm upstream synchronization and automated builds work properly.

docs/agent-deploy-cloudflare.zh-CN.md

@@ -1,17 +1,41 @@
-# AI Agent 在线部署 EdgeEver
+# AI Agent 在线部署 EdgeEver 约定
 
-## 步骤
+本文档为 AI Agent（以及自动化部署工具）在 Cloudflare 上在线部署 EdgeEver 的标准操作规范与约定。
 
-1. Fork `tianma-if/edgeever`。
-2. 启用 Fork 中的 **Update deployed EdgeEver** 工作流。
-3. 在 Cloudflare **Workers & Pages** 导入 Fork，使用仓库根目录、`main` 分支和现有 `wrangler.toml`。
-4. 配置 D1 `DB`、R2 `RESOURCES` 和 Worker Secret `EDGE_EVER_AUTH_PASSWORD`。
-5. 配置 Workers Builds：
+> 💡 **核心原则**：纯 Serverless 架构部署，基于 Cloudflare 免费配额运行，无需购买 VPS 或配置 Docker/SSL 证书。
 
-   ```text
-   Build command: bun install --frozen-lockfile && EDGE_EVER_DEPLOYMENT_TRIGGER=main_push EDGE_EVER_DEPLOYMENT_METHOD=cloudflare_workers_builds bun run build:cloudflare
-   Deploy command: bun run deploy:cloudflare-builds
-   ```
+---
 
-6. 启动首次构建，验证 `/api/health`、`/api/openapi.json` 和登录。
-7. 手动运行一次 **Update deployed EdgeEver**，确认上游更新正常。
+## 自动化部署标准步骤
+
+1. **Fork 仓库**
+   - Fork `tianma-if/edgeever` 到目标 GitHub 账户。
+
+2. **启用工作流**
+   - 在 Fork 仓库的 **Actions** 标签页中，启用 **Update deployed EdgeEver** 自动更新工作流。
+
+3. **Cloudflare 项目导入**
+   - 登录 Cloudflare **Workers & Pages** 控制台，导入该 Fork 仓库。
+   - 配置项目使用仓库根目录、生产环境 `main` 分支，并读取仓库根目录下的 `wrangler.toml`。
+
+4. **绑定资源与凭据 (Bindings & Secrets)**
+   - **D1 数据库绑定**：Binding 名称填 `DB`，关联数据库名称为 `edgeever`。
+   - **R2 存储桶绑定**：Binding 名称填 `RESOURCES`，关联全局唯一的 R2 Bucket。
+   - **Worker Secret**：添加密钥 `EDGE_EVER_AUTH_PASSWORD`，值为初始管理员登录密码。
+
+5. **配置 Workers Builds 命令**
+   - 在 Cloudflare 项目的构建设置中，填入以下标准命令：
+
+     ```text
+     Build command: bun install --frozen-lockfile && EDGE_EVER_DEPLOYMENT_TRIGGER=main_push EDGE_EVER_DEPLOYMENT_METHOD=cloudflare_workers_builds bun run build:cloudflare
+     Deploy command: bun run deploy:cloudflare-builds
+     ```
+
+6. **启动首次构建与服务验证**
+   - 触发启动首次构建，待构建部署完成后，进行如下自动化验证：
+     - 检查 `https://<你的 Worker 域名>/api/health` 返回 `200` 状态码且 JSON 内容为 `{"ok": true}`。
+     - 检查 `https://<你的 Worker 域名>/api/openapi.json` 能够正常加载 OpenAPI 规范。
+     - 使用之前配置的 `EDGE_EVER_AUTH_PASSWORD` 验证登录 API 是否可用。
+
+7. **验证上游更新通道**
+   - 在 Fork 的 **Actions** 中手动运行一次 **Update deployed EdgeEver**，确认上游同步与构建更新流程畅通。

docs/deploy-cloudflare-button.md

@@ -1,34 +1,95 @@
-# Deploy EdgeEver online from a Fork
+# Deploy EdgeEver Online from a Fork
 
-## First installation
+This document provides a detailed step-by-step guide for deploying EdgeEver online via GitHub and Cloudflare. The entire setup is performed in your browser—**no local code installation or environment setup is required**.
 
-1. Fork EdgeEver on GitHub.
-2. In Cloudflare **Workers & Pages**, import the Fork.
-3. Use the repository root and `main` branch. Keep the repository's `wrangler.toml`.
-4. Configure:
-   - D1 binding: `DB`, database name: `edgeever`
-   - R2 binding: `RESOURCES`, with a unique bucket name
-   - Worker Secret: `EDGE_EVER_AUTH_PASSWORD`
-5. Set the build commands:
+> 💡 **Zero-Cost Self-Hosting**: Built completely on Cloudflare's free tiers—**no VPS or server rentals needed, and no Docker or SSL certificate setup required**.
 
-   ```text
-   Build command: bun install --frozen-lockfile && EDGE_EVER_DEPLOYMENT_TRIGGER=main_push EDGE_EVER_DEPLOYMENT_METHOD=cloudflare_workers_builds bun run build:cloudflare
-   Deploy command: bun run deploy:cloudflare-builds
+---
+
+## Prerequisites
+
+- **GitHub Account** (for Forking the repository and enabling automated updates)
+- **Cloudflare Account** (for hosting Worker logic, SQLite D1 database, and R2 storage)
+
+---
+
+## Step-by-Step Deployment Guide
+
+### Step 1: Fork the Repository & Enable Actions
+
+1. Visit the official EdgeEver repository: `https://github.com/tianma-if/edgeever`.
+2. Click the **Fork** button at the top right to copy the repository to your GitHub account.
+3. Go to your Forked repository, navigate to the **Actions** tab, and click **"I understand my workflows, go ahead and enable them"** to activate automated workflows.
+
+---
+
+### Step 2: Create Storage & Database Resources in Cloudflare
+
+Log into your [Cloudflare Dashboard](https://dash.cloudflare.com/):
+
+1. **Create a D1 Database**:
+   - Navigate to **Workers & Pages** -> **D1**, then click **Create database**.
+   - Database name: `edgeever`, then click **Create**.
+2. **Create an R2 Bucket** (for note attachments & images):
+   - Navigate to **Workers & Pages** -> **R2**, then click **Create bucket**.
+   - Enter a globally unique bucket name (e.g., `my-edgeever-resources`), then click **Create bucket**.
+
+---
+
+### Step 3: Import Project & Configure Resources (Bindings & Secrets)
+
+1. In Cloudflare Dashboard, navigate to **Workers & Pages** -> **Overview**, click **Create application** -> **Pages** / **Workers** (Import Git Repository).
+2. Click **Connect to Git**, authorize Cloudflare, and select your Forked `edgeever` repository.
+3. Project settings:
+   - **Production branch**: `main`
+   - **Root directory**: Leave blank or default `/`
+4. **Configure Bindings & Variables** (under **Settings** -> **Variables and Bindings**):
+
+| Type | Binding / Variable Name | Value / Bound Resource | Purpose |
+| :--- | :--- | :--- | :--- |
+| **D1 Database Binding** | `DB` | Select `edgeever` database | Stores notes & structured data |
+| **R2 Bucket Binding** | `RESOURCES` | Select your created R2 bucket | Stores images & file attachments |
+| **Environment Variable (Secret)** | `EDGE_EVER_AUTH_PASSWORD` | Set your admin password | Initial login credential |
+
+---
+
+### Step 4: Set Build Commands & Start Build
+
+In the Cloudflare project **Build settings**, configure:
+
+```text
+Build command:  bun install --frozen-lockfile && EDGE_EVER_DEPLOYMENT_TRIGGER=main_push EDGE_EVER_DEPLOYMENT_METHOD=cloudflare_workers_builds bun run build:cloudflare
+Deploy command: bun run deploy:cloudflare-builds
+```
+
+Click **Save and Deploy** to trigger the initial build.
+
+---
+
+### Step 5: Verify Deployment & Login
+
+1. After deployment completes, Cloudflare will assign a default domain (e.g., `https://edgeever.your-subdomain.workers.dev`).
+2. Visit the health check endpoint in your browser: `https://<your-domain>/api/health`, and confirm it returns HTTP `200` with:
+   ```json
+   { "ok": true }
    ```
+3. Open the homepage, log in with your configured `EDGE_EVER_AUTH_PASSWORD`, and start using EdgeEver!
+4. Go back to your Fork's **Actions** tab on GitHub and manually trigger **Update deployed EdgeEver** once to ensure upstream updates will sync properly in the future.
 
-6. Start the build. Confirm that `/api/health` returns `200` with `"ok": true`, then test login.
-7. In the Fork's **Actions**, enable and run **Update deployed EdgeEver** once.
+---
 
-## Update channel
+## Advanced Configuration: Update Channels
 
-The default follows formal Releases. To follow upstream `main`, create:
+By default, deployments follow official stable Release tags. If you want to follow the latest `main` branch (Edge preview builds), add the following environment variable in Cloudflare under **Settings** -> **Variables and Bindings**:
 
 ```text
 EDGE_EVER_UPDATE_CHANNEL=edge
 ```
 
+---
+
 ## Troubleshooting
 
-- Build failure: inspect the Worker **Deployments** log.
-- No updates: open the Fork's **Actions**, enable **Update deployed EdgeEver**, and run it manually.
-- Recovery: [Cloudflare Manual Deployment](manual-deploy.md).
+- **Initial build failed**: Check the Worker **Deployments** log in Cloudflare to verify that D1 (`DB`) and R2 (`RESOURCES`) binding names match the exact case required.
+- **Updates not syncing**: Navigate to your Fork's **Actions** tab, verify **Update deployed EdgeEver** is enabled, and try clicking **Run workflow** manually.
+- **Reset or Manual Recovery**: See the [Cloudflare Manual Deployment Guide](manual-deploy.md).

docs/deploy-cloudflare-button.zh-CN.md

@@ -1,34 +1,95 @@
 # 从 Fork 在线部署 EdgeEver
 
-## 首次部署
+本文档为在线部署 EdgeEver 的详细图文操作指南。整个部署流程在浏览器中即可完成，**不需要本地安装任何代码或配置本地环境**。
 
-1. 在 GitHub Fork EdgeEver。
-2. 在 Cloudflare **Workers & Pages** 导入这个 Fork。
-3. 使用仓库根目录和 `main` 分支，读取仓库中的 `wrangler.toml`。
-4. 配置：
-   - D1 binding：`DB`，数据库名：`edgeever`
-   - R2 binding：`RESOURCES`，bucket 名称自定义且唯一
-   - Worker Secret：`EDGE_EVER_AUTH_PASSWORD`
-5. 设置构建命令：
+> 💡 **零成本自托管**：部署完全使用 Cloudflare 免费配额，**无需购买 VPS / 云服务器，也不需要折腾域名证书或 Docker**。
 
-   ```text
-   Build command: bun install --frozen-lockfile && EDGE_EVER_DEPLOYMENT_TRIGGER=main_push EDGE_EVER_DEPLOYMENT_METHOD=cloudflare_workers_builds bun run build:cloudflare
-   Deploy command: bun run deploy:cloudflare-builds
+---
+
+## 前置准备
+
+- **GitHub 账户**（用于 Fork 仓库及配置自动更新）
+- **Cloudflare 账户**（用于托管 Worker 逻辑、SQLite 数据库及文件存储）
+
+---
+
+## 首次部署图文指南
+
+### 步骤 1：Fork 仓库并开启 Actions
+
+1. 访问 EdgeEver 官方仓库：`https://github.com/tianma-if/edgeever`。
+2. 点击右上角 **Fork** 按钮，将仓库复制到您的个人 GitHub 账户下。
+3. 进入您 Fork 后的仓库，切换到 **Actions** 标签页，点击 **"I understand my workflows, go ahead and enable them"** 启用自动化工作流。
+
+---
+
+### 步骤 2：在 Cloudflare 创建存储与数据库资源
+
+登录 [Cloudflare Dashboard](https://dash.cloudflare.com/) 控制台：
+
+1. **创建 D1 数据库**：
+   - 导航至 **Workers & Pages** -> **D1**，点击 **Create database**。
+   - 数据库名称填入：`edgeever`，点击 **Create**。
+2. **创建 R2 存储桶**（用于存储笔记附件与图片）：
+   - 导航至 **Workers & Pages** -> **R2**，点击 **Create bucket**。
+   - 填入自定义存储桶名称（全局唯一，如 `my-edgeever-resources`），点击 **Create bucket**。
+
+---
+
+### 步骤 3：导入项目并配置资源绑定 (Bindings & Secrets)
+
+1. 在 Cloudflare 控制台中，进入 **Workers & Pages** -> **Overview**，点击 **Create application** -> **Pages** / **Workers** (选择导入 Git 仓库)。
+2. 选择 **Connect to Git**，授权并选中您刚才 Fork 的 `edgeever` 仓库。
+3. 在项目设置中：
+   - **Production branch**：选择 `main`
+   - **Root directory**：保持留空或默认 `/`
+4. **配置环境变量与资源绑定**（在 **Settings** -> **Variables and Bindings**）：
+
+| 类型 (Type) | 名称 (Binding / Variable Name) | 值 / 绑定的资源 (Value / Resource) | 说明 |
+| :--- | :--- | :--- | :--- |
+| **D1 Database Binding** | `DB` | 选择 `edgeever` 数据库 | 存放笔记与结构化数据 |
+| **R2 Bucket Binding** | `RESOURCES` | 选择您创建的 R2 Bucket | 存放图片与图片附件 |
+| **Environment Variable (Secret)** | `EDGE_EVER_AUTH_PASSWORD` | 设置您的管理员登录密码 | 初始登录凭据 |
+
+---
+
+### 步骤 4：设置构建命令并启动构建
+
+在 Cloudflare 项目的 **Build settings**（构建设置）中配置：
+
+```text
+Build command:  bun install --frozen-lockfile && EDGE_EVER_DEPLOYMENT_TRIGGER=main_push EDGE_EVER_DEPLOYMENT_METHOD=cloudflare_workers_builds bun run build:cloudflare
+Deploy command: bun run deploy:cloudflare-builds
+```
+
+点击 **Save and Deploy** 启动首次构建部署。
+
+---
+
+### 步骤 5：验证部署与登录
+
+1. 构建完成后，Cloudflare 会为您生成一个二级域名（如 `https://edgeever.your-subdomain.workers.dev`）。
+2. 在浏览器打开该域名下的健康检查接口：`https://你的域名/api/health`，确认返回 `200` 及 JSON：
+   ```json
+   { "ok": true }
    ```
+3. 打开主站首页，输入您配置的密码（`EDGE_EVER_AUTH_PASSWORD`）测试登录并开始使用。
+4. 返回 Fork 的 GitHub 仓库 **Actions** 页面，手动触发运行一次 **Update deployed EdgeEver** 工作流，确保未来可自动跟进上游更新。
 
-6. 启动构建。部署完成后确认 `/api/health` 返回 `200` 和 `"ok": true`，再测试登录。
-7. 在 Fork 的 **Actions** 中启用并运行一次 **Update deployed EdgeEver**。
+---
 
-## 更新通道
+## 高级配置：更新通道设置
 
-默认跟随正式 Release。跟随上游 `main` 时创建：
+部署默认自动跟随官方正式 Releases（稳定版）。若希望跟进最前沿的 `main` 分支（Edge 预览版），可前往 Cloudflare 的 **Settings** -> **Variables and Bindings** 添加如下环境变量：
 
 ```text
 EDGE_EVER_UPDATE_CHANNEL=edge
 ```
 
-## 排错
+---
 
-- 构建失败：查看 Cloudflare Worker 的 **Deployments** 日志。
-- 更新没有运行：打开 Fork 的 **Actions**，启用 **Update deployed EdgeEver** 并手动运行。
-- 恢复部署：[手动部署指南](manual-deploy.zh-CN.md)。
+## 常见问题与排错
+
+- **首次构建失败**：请检查 Cloudflare 控制台中 Worker 的 **Deployments** 构建日志，确认 D1 (`DB`) 和 R2 (`RESOURCES`) Binding 名称大小写是否正确。
+- **无法同步上游更新**：打开您 Fork 仓库的 **Actions** 标签页，确认 **Update deployed EdgeEver** 工作流是否处于已启用状态，并尝试手动点击 **Run workflow**。
+- **需要重置或手动恢复部署**：请参阅 [手动部署指南](manual-deploy.zh-CN.md)。

docs/evernote-migration-guide.en-US.md

@@ -2,7 +2,7 @@
 
 [简体中文](evernote-migration-guide.md) | [English](evernote-migration-guide.en-US.md)
 
-We strongly recommend using an AI coding assistant, such as Antigravity, Claude Code, or Cursor, to run the migration automatically. The current migration flow is optimized for streaming large archives and preprocessing empty text, and can handle multi-GB note libraries while preserving created/updated timestamps and nested notebook hierarchy.
+We strongly recommend using an AI coding assistant, such as Codex, Antigravity, Claude Code, Cursor, OpenClaw, or Hermes Agent, to run the migration automatically. The current migration flow is optimized for streaming large archives and preprocessing empty text, and can handle multi-GB note libraries while preserving created/updated timestamps and nested notebook hierarchy.
 
 ---
 
@@ -13,7 +13,7 @@ We strongly recommend using an AI coding assistant, such as Antigravity, Claude
 3. Paste the copied JSON into your AI coding assistant and ask it to install the MCP service in your current AI client:
 
 ```sh
-You are an AI coding assistant. This is my EdgeEver MCP service configuration JSON. Please configure this MCP service directly in the MCP server configuration file for my current AI editor/client, such as Claude Code, Cursor, or Cline:
+You are an AI coding assistant. This is my EdgeEver MCP service configuration JSON. Please configure this MCP service directly in the MCP server configuration file for my current AI editor/client, such as Codex, Claude Code, Cursor, or Cline:
 
 <paste the copied JSON configuration here>
 ```

docs/evernote-migration-guide.md

@@ -2,7 +2,7 @@
 
 [简体中文](evernote-migration-guide.md) | [English](evernote-migration-guide.en-US.md)
 
-我们强烈推荐使用 AI 编程助手（如 Antigravity、Claude Code、Cursor 等）自动执行迁移。该方案已完成内存流式优化与空文本预处理，能安全应对数 GB 级别超大笔记库，完整保留创建/修改时间与嵌套笔记本目录层级。
+我们强烈推荐使用 AI 编程助手（如 Codex、Antigravity、Claude Code、Cursor、OpenClaw、Hermes Agent 等）自动执行迁移。该方案已完成内存流式优化与空文本预处理，能安全应对数 GB 级别超大笔记库，完整保留创建/修改时间与嵌套笔记本目录层级。
 
 ---
 
@@ -10,10 +10,10 @@
 
 1. 点击网页端左下角的 **设置（Settings）** 图标。
 2. 在 **API & MCP 授权** 卡片生成 Token 后，点击 **复制完整 MCP 配置** 按钮。
-3. 把复制的 JSON 配置直接粘贴发送给你的 AI 编程助手（如 Antigravity, Claude Code, Cursor 等），让它帮你自动在当前的 AI 客户端中安装配置好该 MCP 服务：
+3. 把复制的 JSON 配置直接粘贴发送给你的 AI 编程助手（如 Codex, Antigravity, Claude Code, Cursor, OpenClaw, Hermes Agent 等），让它帮你自动在当前的 AI 客户端中安装配置好该 MCP 服务：
 
 ```sh
-你是 AI 编程助手。这是我的 EdgeEver MCP 服务配置 JSON。请帮我把这个 MCP 服务直接配置到我当前使用的 AI 编辑器/客户端（如 Claude Code, Cursor, Cline 等）的 MCP 服务器配置文件中：
+你是 AI 编程助手。这是我的 EdgeEver MCP 服务配置 JSON。请帮我把这个 MCP 服务直接配置到我当前使用的 AI 编辑器/客户端（如 Codex, Claude Code, Cursor, Cline 等）的 MCP 服务器配置文件中：
 
 <在此处粘贴刚才复制 of JSON 配置内容>
 ```