A local-first multi-agent app development platform, built on PenguinHarness
docs: 文档改称 Adelie,并且与代码真正读到的名字对上
lmliheng74fdaa144ca6
diff --git a/changelog/unreleased/2026-10-17-docs-naming.md b/changelog/unreleased/2026-10-17-docs-naming.mdnew file mode 100644index 00000000..5b6f8b80--- /dev/null+++ b/changelog/unreleased/2026-10-17-docs-naming.md@@ -0,0 +1,47 @@+# The documentation says Adelie, and matches what the code actually reads++- **Date:** 2026-10-17+- **Type:** process+- **Scope:** `docs`++[中文版](2026-10-17-docs-naming.zh.md)++The documentation site described this product by upstream's name and pointed at paths and variables+that Adelie stopped using. Every page now names Adelie, and every path, data root and environment+variable it prints is one the code on this branch actually reads.++## Renamed++- The product name: `PenguinHarness` → `Adelie`, in 30 page pairs (English and Chinese) plus the+ docs site's own title, `og:` tags, description and sidebar name.+- Desktop paths: the macOS, Windows and Linux log and data directories now read `Adelie`, which is+ what `productName` in the desktop build produces, and the dev profile is `Adelie-Dev`.+- The data root and its variable: `~/.penguin/data` → `~/.adelie/data`,+ `%USERPROFILE%\.penguin\data` → `%USERPROFILE%\.adelie\data`, and `PENGUIN_HOME` → `ADELIE_HOME`+ (the old spelling is still read — the configuration page says so where it matters).+- The install directory in the quickstart tables: `~/.penguin` → `~/.adelie`, which is the default+ `install.sh` and `penguin update` use.+- Control-plane variables: `ADELIE_AGENT_ID`, `ADELIE_SESSION_ID`, `ADELIE_PROJECT_ID`,+ `ADELIE_API_URL`, `ADELIE_API_TOKEN`, `ADELIE_AGENT_KEY`, `ADELIE_ORG_ID`, `ADELIE_LANG`,+ `ADELIE_PASSWORD`, `ADELIE_SHELL`, `ADELIE_UPDATE_CHECK`, `ADELIE_TRUST_PROXY`,+ `ADELIE_PREVIEW_ORIGIN`, `ADELIE_SEED_ADMIN_PASSWORD`, `ADELIE_SERVE_CHILD`, `ADELIE_SUPERVISED`,+ and the deployment names `ADELIE_WEB_DIST`, `ADELIE_WEB_DB`, `ADELIE_CLI_ENTRY`,+ `ADELIE_PORT_FILE`, `ADELIE_DESKTOP_TOKEN`.+- The promotional name for the message format: `Penguin Message` → `Adelie Message`.++## What deliberately keeps the old spelling++The installer and release protocol (`PENGUIN_INSTALL_DIR`, `PENGUIN_VERSION`, `PENGUIN_ARCHIVE`,+`PENGUIN_DOWNLOAD_*`): a running CLI downloads `install.sh` from a release, so both ends move with+the release chain, not with a rename. The upstream gateway (`PENGUIN_GO_ORIGIN`,+`PENGUIN_GO_API_KEY`, `token.penguin.ooo`, `go.penguin.ooo/modelscope`): their service, and the+values have to match what the code sends. `PENGUIN_NO_LOGIN_SHELL_ENV`, which belongs to the+desktop shell. The dev data root `~/.penguin/dev-data`, which the dev scripts really do use.++## Corrected, not renamed++The quickstart and CLI pages described the installer's download sources as upstream's: an OSS+release directory, a speed probe, `PENGUIN_DOWNLOAD_SOURCE=auto|oss|github`. Adelie's installer+downloads from this repository's GitHub Releases, accepts `auto` and `github` (which mean the same+thing here) and rejects anything else, and takes a mirror through `PENGUIN_DOWNLOAD_BASE_URL` with+one optional fallback. The pages now say that.diff --git a/changelog/unreleased/2026-10-17-docs-naming.zh.md b/changelog/unreleased/2026-10-17-docs-naming.zh.mdnew file mode 100644index 00000000..0195c702--- /dev/null+++ b/changelog/unreleased/2026-10-17-docs-naming.zh.md@@ -0,0 +1,44 @@+# 文档改称 Adelie,并且与代码真正读到的名字对上++- **Date:** 2026-10-17+- **Type:** process+- **Scope:** `docs`++[English](2026-10-17-docs-naming.md)++文档站此前用上游的名字称呼这个产品,路径与变量名也停在这条分支早就不再使用的一套上。现在每一页+都叫 Adelie,页面里写出来的路径、数据根与环境变量,都是这条分支的代码真正读的那一个。++## 改掉的++- 产品名:30 对页面(中英各一份)里的 `PenguinHarness` → `Adelie`,以及文档站自己的标题、`og:`+ 标签、描述与侧栏名。+- 桌面端路径:macOS、Windows、Linux 下的日志与数据目录都改成 `Adelie` —— 桌面构建的+ `productName` 就是它;开发态的应用名是 `Adelie-Dev`。+- 数据根与它的变量:`~/.penguin/data` → `~/.adelie/data`,+ `%USERPROFILE%\.penguin\data` → `%USERPROFILE%\.adelie\data`,`PENGUIN_HOME` → `ADELIE_HOME`+ (旧拼写仍被读取,配置参考在要说清的地方写了这一点)。+- 快速开始表格里的安装目录:`~/.penguin` → `~/.adelie`,也就是 `install.sh` 与 `penguin update`+ 真正用的默认值。+- 控制面变量:`ADELIE_AGENT_ID`、`ADELIE_SESSION_ID`、`ADELIE_PROJECT_ID`、`ADELIE_API_URL`、+ `ADELIE_API_TOKEN`、`ADELIE_AGENT_KEY`、`ADELIE_ORG_ID`、`ADELIE_LANG`、`ADELIE_PASSWORD`、+ `ADELIE_SHELL`、`ADELIE_UPDATE_CHECK`、`ADELIE_TRUST_PROXY`、`ADELIE_PREVIEW_ORIGIN`、+ `ADELIE_SEED_ADMIN_PASSWORD`、`ADELIE_SERVE_CHILD`、`ADELIE_SUPERVISED`,以及部署接线用的+ `ADELIE_WEB_DIST`、`ADELIE_WEB_DB`、`ADELIE_CLI_ENTRY`、`ADELIE_PORT_FILE`、+ `ADELIE_DESKTOP_TOKEN`。+- 消息格式的宣传名:`Penguin Message` → `Adelie Message`。++## 有意保留旧拼写的地方++安装器与发布协议(`PENGUIN_INSTALL_DIR`、`PENGUIN_VERSION`、`PENGUIN_ARCHIVE`、+`PENGUIN_DOWNLOAD_*`):正在运行的 CLI 会从某个 Release 下载 `install.sh`,两端只能随发布链一起走,+不跟改名走。上游网关(`PENGUIN_GO_ORIGIN`、`PENGUIN_GO_API_KEY`、`token.penguin.ooo`、+`go.penguin.ooo/modelscope`):那是他们的服务,值必须与代码发出去的一致。+`PENGUIN_NO_LOGIN_SHELL_ENV` 属于桌面壳。开发态的数据根 `~/.penguin/dev-data`,开发脚本用的就是它。++## 顺带改对的,不是改名++快速开始与 CLI 页面把安装器的下载来源写成了上游的样子:OSS 上的不可变目录、测速探针、+`PENGUIN_DOWNLOAD_SOURCE=auto|oss|github`。Adelie 的安装器从这个仓库的 GitHub Release 下载,只接受+`auto` 与 `github`(在这里两者是一回事),写别的会直接拒绝;要用镜像就设+`PENGUIN_DOWNLOAD_BASE_URL`,另有一个可选的回退地址。页面现在如实这么写。diff --git a/packages/docs/README.md b/packages/docs/README.mdindex 3e0a09c0..a44ab4d6 100644--- a/packages/docs/README.md+++ b/packages/docs/README.md@@ -1,6 +1,6 @@# @adelie/docs-The PenguinHarness documentation site (React + Vite + Tailwind CSS 4). Its own package, sharing the landing page's visual language: bilingual pages (zh/en), light/dark themes, a sidebar + per-page table of contents, and a "Copy Markdown" button on every page.+The Adelie documentation site (React + Vite + Tailwind CSS 4). Its own package, keeping the visual language the landing page introduced: bilingual pages (zh/en), light/dark themes, a sidebar + per-page table of contents, and a "Copy Markdown" button on every page.Live at <https://lmliheng.github.io/Adelie/docs/>.diff --git a/packages/docs/content/agent-api.en.md b/packages/docs/content/agent-api.en.mdindex d412333f..3dad0592 100644--- a/packages/docs/content/agent-api.en.md+++ b/packages/docs/content/agent-api.en.md@@ -3,7 +3,7 @@ title: Agent APIdescription: Let a program talk to one agent over HTTP — turn on the agent's API, mint keys, and run it with curl or the @adelie/amsp client.----The Agent API lets a program outside PenguinHarness — a script, a service, a page in a browser — talk to one agent over HTTP. The program sends its input, reads the run as it happens as an [AMSP](/amsp) event stream, and continues the conversation by its Session id. A run uses the Project's models and credentials, is recorded like any other conversation, and appears in the sidebar's **Background** folder.+The Agent API lets a program outside Adelie — a script, a service, a page in a browser — talk to one agent over HTTP. The program sends its input, reads the run as it happens as an [AMSP](/amsp) event stream, and continues the conversation by its Session id. A run uses the Project's models and credentials, is recorded like any other conversation, and appears in the sidebar's **Background** folder.Where to go:@@ -27,7 +27,7 @@ Where to go:2. Turn on **Enable API access**.3. Choose the **Approval mode for API conversations**. See [Approval mode](#approval-mode).4. Under **Keys**, select **New key**, name it and copy the key. It is shown once.-5. Copy the **Base URL** and the **Agent ID** under **Connection**. **Examples** holds a curl command and a TypeScript snippet with both filled in and `$PENGUIN_AGENT_KEY` in place of the key.+5. Copy the **Base URL** and the **Agent ID** under **Connection**. **Examples** holds a curl command and a TypeScript snippet with both filled in and `$ADELIE_AGENT_KEY` in place of the key.On the **Agents** page, an agent whose API is on carries an API icon after its name, with the tooltip **API access on**.@@ -79,7 +79,7 @@ The **API** tab ends, for the Project's owner, with **Try it**: an input holding```bashcurl -N http://localhost:7364/api/amsp/v1/agents/demo/coder/runs \- -H "Authorization: Bearer $PENGUIN_AGENT_KEY" -H "Content-Type: application/json" \+ -H "Authorization: Bearer $ADELIE_AGENT_KEY" -H "Content-Type: application/json" \-d '{"input":"Summarize README.md"}'```@@ -98,7 +98,7 @@ To continue the conversation, send the Session id with the next input:```bashcurl -N http://localhost:7364/api/amsp/v1/agents/demo/coder/runs \- -H "Authorization: Bearer $PENGUIN_AGENT_KEY" -H "Content-Type: application/json" \+ -H "Authorization: Bearer $ADELIE_AGENT_KEY" -H "Content-Type: application/json" \-d '{"session_id":"session-2026-10-07-10-00-00-3f9a1c2e","input":"Now list its headings"}'```@@ -174,7 +174,7 @@ import { AgentClient } from "@adelie/amsp";const client = new AgentClient({baseUrl: "http://localhost:7364/api/amsp/v1",agent: "demo/coder",- apiKey: process.env.PENGUIN_AGENT_KEY,+ apiKey: process.env.ADELIE_AGENT_KEY,});const run = client.run({ input: "Summarize README.md" });diff --git a/packages/docs/content/agent-api.zh.md b/packages/docs/content/agent-api.zh.mdindex 185f4ada..7299bdb2 100644--- a/packages/docs/content/agent-api.zh.md+++ b/packages/docs/content/agent-api.zh.md@@ -3,7 +3,7 @@ title: Agent APIdescription: 让外部程序经 HTTP 与某个 Agent 对话:开启 Agent 的 API、签发密钥,再用 curl 或 @adelie/amsp 客户端运行它。----Agent API 让 PenguinHarness 之外的程序(脚本、服务、浏览器里的页面)经 HTTP 与某一个 Agent 对话。程序发送输入,以 [AMSP](/amsp) 事件流实时读取这次运行,再凭 Session id 延续对话。运行使用 Project 的模型与凭据,像其他对话一样被记录,并出现在侧边栏的**后台会话**折叠夹中。+Agent API 让 Adelie 之外的程序(脚本、服务、浏览器里的页面)经 HTTP 与某一个 Agent 对话。程序发送输入,以 [AMSP](/amsp) 事件流实时读取这次运行,再凭 Session id 延续对话。运行使用 Project 的模型与凭据,像其他对话一样被记录,并出现在侧边栏的**后台会话**折叠夹中。从哪里开始:@@ -27,7 +27,7 @@ Agent API 让 PenguinHarness 之外的程序(脚本、服务、浏览器里的2. 打开**开启 API 访问**。3. 选择 **API 会话的审批模式**,见[审批模式](#审批模式)。4. 在**密钥**下选择**新建密钥**,起个名字,然后复制密钥。密钥只显示这一次。-5. 在**连接**下复制 **Base URL** 和 **Agent ID**。**示例**里有一条 curl 命令和一段 TypeScript 代码,两者都已填好,密钥处写作 `$PENGUIN_AGENT_KEY`。+5. 在**连接**下复制 **Base URL** 和 **Agent ID**。**示例**里有一条 curl 命令和一段 TypeScript 代码,两者都已填好,密钥处写作 `$ADELIE_AGENT_KEY`。在**智能体**页面上,已开启 API 的 Agent 名称后带有 API 图标,悬停提示为**已开启 API 访问**。@@ -79,7 +79,7 @@ API 会话的沙箱取自服务器的新对话默认值,与其他新对话相```bashcurl -N http://localhost:7364/api/amsp/v1/agents/demo/coder/runs \- -H "Authorization: Bearer $PENGUIN_AGENT_KEY" -H "Content-Type: application/json" \+ -H "Authorization: Bearer $ADELIE_AGENT_KEY" -H "Content-Type: application/json" \-d '{"input":"Summarize README.md"}'```@@ -98,7 +98,7 @@ data: [DONE]```bashcurl -N http://localhost:7364/api/amsp/v1/agents/demo/coder/runs \- -H "Authorization: Bearer $PENGUIN_AGENT_KEY" -H "Content-Type: application/json" \+ -H "Authorization: Bearer $ADELIE_AGENT_KEY" -H "Content-Type: application/json" \-d '{"session_id":"session-2026-10-07-10-00-00-3f9a1c2e","input":"Now list its headings"}'```@@ -174,7 +174,7 @@ import { AgentClient } from "@adelie/amsp";const client = new AgentClient({baseUrl: "http://localhost:7364/api/amsp/v1",agent: "demo/coder",- apiKey: process.env.PENGUIN_AGENT_KEY,+ apiKey: process.env.ADELIE_AGENT_KEY,});const run = client.run({ input: "Summarize README.md" });diff --git a/packages/docs/content/agents.en.md b/packages/docs/content/agents.en.mdindex 47c2ae6f..8ccbbdc5 100644--- a/packages/docs/content/agents.en.md+++ b/packages/docs/content/agents.en.md@@ -56,7 +56,7 @@ The **Report-writing agent** example creates an agent with the id `report-writer3. In **Agent id**, enter an id, or select **Generate with AI** beside the field to have the Project's default model derive one from the name, or from the description while the name is empty. An id is 2–64 characters long, starts with a lowercase letter, and uses only lowercase letters, digits and underscores. A proposal replaces what is in the box and stays editable. You cannot change the id later.4. Optional: fill in **Description**.5. Optional: in **Plugins**, select plugins from the plugin library to install on the new agent. Their Skills and hook packages are installed when the agent is created.-6. Optional: in **Import Skills from a project directory**, select a directory. PenguinHarness reads the Skills under its `.agents/skills` and `.claude/skills` folders; select the ones to install. If a Skill from the directory has the same name as a Skill from a selected plugin, the directory's Skill is installed.+6. Optional: in **Import Skills from a project directory**, select a directory. Adelie reads the Skills under its `.agents/skills` and `.claude/skills` folders; select the ones to install. If a Skill from the directory has the same name as a Skill from a selected plugin, the directory's Skill is installed.7. Select **Create**. The new agent's settings open.Any Project member can create an agent.@@ -143,7 +143,7 @@ For how versions and snapshots work, see [Self-Improvement](/self-improvement#sn### Update the kernel-An agent's kernel version records which generation of the built-in default settings its configuration is based on. An existing agent never picks up newer defaults on its own. When PenguinHarness ships newer defaults, the **Kernel** section shows the current and the latest kernel version, and the Overview tab shows a red dot.+An agent's kernel version records which generation of the built-in default settings its configuration is based on. An existing agent never picks up newer defaults on its own. When Adelie ships newer defaults, the **Kernel** section shows the current and the latest kernel version, and the Overview tab shows a red dot.1. In the **Kernel** section, select **Update kernel**.2. Confirm.@@ -181,7 +181,7 @@ Under **Available placeholders (click to insert)**, select a placeholder to inse| `{{OS_VERSION}}` | The operating system version || `{{SHELL}}` | The shell used to run commands || `{{DATE}}` | The current date |-| `{{PROJECT_DIR}}` | The PenguinHarness app data root, which holds all agents' data and Project data; not the task's working directory |+| `{{PROJECT_DIR}}` | The Adelie app data root, which holds all agents' data and Project data; not the task's working directory || `{{AGENT_ID}}` | The agent's id || `{{CWD}}` | The absolute Workspace path || `{{PROVIDER}}` | The model's provider group |@@ -227,7 +227,7 @@ MCP servers add external tools to the agent. Their tools are named `mcp__<name>_1. On the **Tools** tab, select **Add MCP Server**.2. Choose the transport:- `http`, the default: Streamable HTTP, the current remote transport.- - `stdio`: a local process that PenguinHarness starts and talks to over stdin and stdout.+ - `stdio`: a local process that Adelie starts and talks to over stdin and stdout.- `sse`: the legacy HTTP+SSE transport, for servers that have not migrated.3. In **name**, enter the tool-name prefix. Use letters, digits, `_` and `-`, starting with a letter or digit.4. Fill in the connection fields:@@ -251,7 +251,7 @@ To change a server, select **Edit** on its row. To remove it, select **Remove**1. In the **MCP Servers** section, select **Test connection**.2. Select **Start test**.-PenguinHarness connects to each server in turn and discovers its tools. Nothing is saved. Each row shows the number of tools and the time taken, or **Connection failed** with the reason.+Adelie connects to each server in turn and discovers its tools. Nothing is saved. Each row shows the number of tools and the time taken, or **Connection failed** with the reason.## Skills tab@@ -314,7 +314,7 @@ The memory count on the agent's card opens this tab.## Vault tab-The vault holds environment variables for the agent, such as API keys. PenguinHarness passes them to the agent's shell commands. The model sees the variable names, never their values. Subagents use their own vaults and do not inherit this one. Changes take effect from the next Task; a Task that is already running is not affected.+The vault holds environment variables for the agent, such as API keys. Adelie passes them to the agent's shell commands. The model sees the variable names, never their values. Subagents use their own vaults and do not inherit this one. Changes take effect from the next Task; a Task that is already running is not affected.Only the Project owner can change the vault. Members see the variable names with masked values.@@ -344,7 +344,7 @@ To delete a variable, select **Remove** on its row and confirm. The value cannotA scheduled task sends a prompt to the agent on a schedule: once, or every period. Changes made on this tab take effect immediately.> [!NOTE]-> Scheduled tasks fire only while the PenguinHarness service is running.+> Scheduled tasks fire only while the Adelie service is running.You can also create and manage scheduled tasks from a conversation; see [Scheduled tasks](/schedules).@@ -377,7 +377,7 @@ On each row, the owner can select **Disable** or **Enable**, **Edit**, or **Dele## API tab-The **API** tab lets programs outside PenguinHarness talk to the agent over HTTP: **Enable API access**, the **Approval mode for API conversations**, the **Base URL** and **Agent ID** under **Connection**, the **Keys**, **Allow keyless access**, **Examples** of a call, and, for the Project's owner, **Try it**, which runs the agent once through the API and shows the stream a program would receive. There is no **Save** button: the switches and the approval mode apply when you change them, and turning the API off or deleting a key asks first. To set it up and call the agent, see [Agent API](/agent-api).+The **API** tab lets programs outside Adelie talk to the agent over HTTP: **Enable API access**, the **Approval mode for API conversations**, the **Base URL** and **Agent ID** under **Connection**, the **Keys**, **Allow keyless access**, **Examples** of a call, and, for the Project's owner, **Try it**, which runs the agent once through the API and shows the stream a program would receive. There is no **Save** button: the switches and the approval mode apply when you change them, and turning the API off or deleting a key asks first. To set it up and call the agent, see [Agent API](/agent-api).## How it worksdiff --git a/packages/docs/content/agents.zh.md b/packages/docs/content/agents.zh.mdindex 35b6f513..bf2df079 100644--- a/packages/docs/content/agents.zh.md+++ b/packages/docs/content/agents.zh.md@@ -56,7 +56,7 @@ Agent 是 Project 里配置好的助手。每个 Agent 都有自己的指令、3. 在 **Agent id** 中输入 id,也可以点击输入框旁边的**用 AI 生成**,由 Project 的默认模型根据名称生成一个;名称为空时则根据描述生成。id 长度为 2–64 个字符,以小写字母开头,只能用小写字母、数字和下划线。生成的 id 会覆盖框里原有的内容,之后仍可以手动修改。创建后 id 不能再改。4. 可选:填写**描述**。5. 可选:在**插件**中从插件库选择要装到新 Agent 上的插件。Agent 创建时会一并装上这些插件的 Skill 和钩子包。-6. 可选:在**从项目目录导入技能**中选择一个目录。PenguinHarness 会读取这个目录下 `.agents/skills` 和 `.claude/skills` 文件夹里的 Skill,从中勾选要安装的。目录里的 Skill 与所选插件里的 Skill 同名时,装的是目录里的那个。+6. 可选:在**从项目目录导入技能**中选择一个目录。Adelie 会读取这个目录下 `.agents/skills` 和 `.claude/skills` 文件夹里的 Skill,从中勾选要安装的。目录里的 Skill 与所选插件里的 Skill 同名时,装的是目录里的那个。7. 选择**创建**,打开新 Agent 的设置。任何 Project 成员都能创建 Agent。@@ -143,7 +143,7 @@ Agent 是 Project 里配置好的助手。每个 Agent 都有自己的指令、### 更新内核-Agent 的内核版本记录它的配置基于哪一代内置默认设置。已有的 Agent 永远不会自动采用更新的默认值。PenguinHarness 发布新默认值后,**内核**区块会显示当前内核版本和最新内核版本,概览标签页上出现红点。+Agent 的内核版本记录它的配置基于哪一代内置默认设置。已有的 Agent 永远不会自动采用更新的默认值。Adelie 发布新默认值后,**内核**区块会显示当前内核版本和最新内核版本,概览标签页上出现红点。1. 在**内核**区块选择**更新内核**。2. 确认。@@ -181,7 +181,7 @@ Agent 的内核版本记录它的配置基于哪一代内置默认设置。已| `{{OS_VERSION}}` | 操作系统版本 || `{{SHELL}}` | 执行命令所用的 shell || `{{DATE}}` | 当前日期 |-| `{{PROJECT_DIR}}` | PenguinHarness 应用数据根目录,存放所有 Agent 数据和 Project 数据;不是 Task 的工作目录 |+| `{{PROJECT_DIR}}` | Adelie 应用数据根目录,存放所有 Agent 数据和 Project 数据;不是 Task 的工作目录 || `{{AGENT_ID}}` | Agent 的 id || `{{CWD}}` | Workspace 的绝对路径 || `{{PROVIDER}}` | 模型的供应商分组 |@@ -227,7 +227,7 @@ MCP Server 给 Agent 增加外部工具,工具名形如 `mcp__<name>__<tool>`1. 在**工具**标签页选择**添加 MCP Server**。2. 选择传输方式:- `http`(默认):Streamable HTTP,当前的远程传输方式。- - `stdio`:本地进程,由 PenguinHarness 启动,通过 stdin 和 stdout 通信。+ - `stdio`:本地进程,由 Adelie 启动,通过 stdin 和 stdout 通信。- `sse`:旧的 HTTP+SSE 传输方式,供尚未迁移的 Server 使用。3. 在 **name** 中输入工具名前缀,可以用字母、数字、`_` 和 `-`,以字母或数字开头。4. 填写连接字段:@@ -251,7 +251,7 @@ MCP Server 给 Agent 增加外部工具,工具名形如 `mcp__<name>__<tool>`1. 在 **MCP Server** 区块选择**测试连接**。2. 选择**开始测试**。-PenguinHarness 依次连接每个 Server 并发现它的工具,不会保存任何内容。每行显示工具数量和耗时;失败则显示**连接失败**和原因。+Adelie 依次连接每个 Server 并发现它的工具,不会保存任何内容。每行显示工具数量和耗时;失败则显示**连接失败**和原因。## 技能标签页@@ -314,7 +314,7 @@ PenguinHarness 依次连接每个 Server 并发现它的工具,不会保存任## 密钥保险柜标签页-密钥保险柜存放 Agent 用的环境变量,比如 API key。PenguinHarness 把它们传给 Agent 的 shell 命令。模型只能看到变量名,永远看不到值。子 Agent 用各自的密钥保险柜,不继承这里的变量。修改从下一个 Task 起生效;正在运行的 Task 不受影响。+密钥保险柜存放 Agent 用的环境变量,比如 API key。Adelie 把它们传给 Agent 的 shell 命令。模型只能看到变量名,永远看不到值。子 Agent 用各自的密钥保险柜,不继承这里的变量。修改从下一个 Task 起生效;正在运行的 Task 不受影响。只有 Project owner 能修改密钥保险柜。成员能看到变量名,值以掩码显示。@@ -344,7 +344,7 @@ PenguinHarness 依次连接每个 Server 并发现它的工具,不会保存任定时任务按计划给 Agent 发送提示词:发一次,或按周期反复发。这个标签页上的修改立即生效。> [!NOTE]-> 定时任务只在 PenguinHarness 服务运行时触发。+> 定时任务只在 Adelie 服务运行时触发。也可以在对话里创建和管理定时任务,见[定时任务](/schedules)。@@ -377,7 +377,7 @@ owner 可以在每一行选择**停用**或**启用**、**编辑**、**删除**## API 标签页-**API** 标签页让 PenguinHarness 之外的程序经 HTTP 与这个 Agent 对话:**开启 API 访问**、**API 会话的审批模式**、**连接**下的 **Base URL** 和 **Agent ID**、**密钥**、**允许无密钥访问**、调用**示例**,以及只对 Project 所有者显示的**试一试**:经 API 运行一次这个 Agent,按程序会收到的样子显示事件流。这个标签页没有**保存**按钮:开关和审批模式改动即生效,关闭 API 访问和删除密钥前会先确认。如何设置、如何调用,见 [Agent API](/agent-api)。+**API** 标签页让 Adelie 之外的程序经 HTTP 与这个 Agent 对话:**开启 API 访问**、**API 会话的审批模式**、**连接**下的 **Base URL** 和 **Agent ID**、**密钥**、**允许无密钥访问**、调用**示例**,以及只对 Project 所有者显示的**试一试**:经 API 运行一次这个 Agent,按程序会收到的样子显示事件流。这个标签页没有**保存**按钮:开关和审批模式改动即生效,关闭 API 访问和删除密钥前会先确认。如何设置、如何调用,见 [Agent API](/agent-api)。## 工作原理diff --git a/packages/docs/content/amsp.en.md b/packages/docs/content/amsp.en.mdindex 4e4a339a..b786ea1b 100644--- a/packages/docs/content/amsp.en.md+++ b/packages/docs/content/amsp.en.md@@ -226,7 +226,7 @@ Fields that serve only the Trace, such as provider `fidelity` and `session_meta.- The version is in the path, `/api/amsp/v1`; events carry none.- Within `/v1`, changes only add: new event types and new optional fields. A client that ignores what it does not know keeps working.- A change to what an existing field means is a new version, `/v2`, served beside `/v1`.-- Event names are `<subject>.<phase>`; items are `K.delta` and `K.done`, as in MMSP. A "run" on the wire is one Task in PenguinHarness's terms.+- Event names are `<subject>.<phase>`; items are `K.delta` and `K.done`, as in MMSP. A "run" on the wire is one Task in Adelie's terms.## Reading the stream yourselfdiff --git a/packages/docs/content/amsp.zh.md b/packages/docs/content/amsp.zh.mdindex b80e482e..39f60f91 100644--- a/packages/docs/content/amsp.zh.md+++ b/packages/docs/content/amsp.zh.md@@ -226,7 +226,7 @@ data: [DONE]- 版本写在路径里:`/api/amsp/v1`;事件本身不带版本。- 在 `/v1` 之内只做增加:新的事件类型和新的可选字段。忽略未知内容的客户端可以继续工作。- 改变已有字段含义的变更属于新版本 `/v2`,与 `/v1` 并存。-- 事件名形如 `<subject>.<phase>`;内容项为 `K.delta` 与 `K.done`,与 MMSP 一致。传输中的一次 run 即 PenguinHarness 术语中的一个 Task。+- 事件名形如 `<subject>.<phase>`;内容项为 `K.delta` 与 `K.done`,与 MMSP 一致。传输中的一次 run 即 Adelie 术语中的一个 Task。## 自行读取流diff --git a/packages/docs/content/architecture.en.md b/packages/docs/content/architecture.en.mdindex 248b30f9..d2e8862c 100644--- a/packages/docs/content/architecture.en.md+++ b/packages/docs/content/architecture.en.md@@ -3,7 +3,7 @@ title: Architecturedescription: How the SDK, Server, CLI and Web App divide responsibilities, and how the three-interface boundary and OmniMessage organize the system.----PenguinHarness is a pnpm monorepo. Its center is the execution engine in `@adelie/core`. The Server ships with the product as the Human implementation of that engine: it runs every Task. SDK embedders can also drive the engine directly.+Adelie is a pnpm monorepo. Its center is the execution engine in `@adelie/core`. The Server ships with the product as the Human implementation of that engine: it runs every Task. SDK embedders can also drive the engine directly.The Web App and the CLI are clients of the Server over HTTP and SSE, and the desktop app wraps the Server and the Web App in one window. This page covers the layers, the engine's three-interface boundary, the [data flow of one Task](#data-flow-of-one-task), where each responsibility lives, and the source layout.@@ -71,7 +71,7 @@ To place a design in a layer, ask where its **source of truth** lives. One rule| --- | --- | --- || SDK (`core`) | Protocol and execution: everything that makes messages flow | persisted user state, multi-user, any rendering || Server | The resident process and the multi-user runtime | engine logic, fully delegated to the SDK |-| File layer (`~/.penguin/data`) | Everything editable and everything recorded | any computation |+| File layer (`~/.adelie/data`) | Everything editable and everything recorded | any computation || CLI / Web | Rendering and interaction | business state |Item by item, each design maps to an owner and to the file or module that carries it:@@ -104,7 +104,7 @@ Item by item, each design maps to an owner and to the file or module that carrie## The state layer-Below the engine sits a purely file-based state layer. Its root is `~/.penguin/data` (override it with `PENGUIN_HOME`), organized as `<project>/agents/<agent>/`:+Below the engine sits a purely file-based state layer. Its root is `~/.adelie/data` (override it with `ADELIE_HOME`), organized as `<project>/agents/<agent>/`:| Component | Location | Contents || --- | --- | --- |diff --git a/packages/docs/content/architecture.zh.md b/packages/docs/content/architecture.zh.mdindex 31774e27..212a5fd9 100644--- a/packages/docs/content/architecture.zh.md+++ b/packages/docs/content/architecture.zh.md@@ -3,7 +3,7 @@ title: 架构总览description: SDK、Server、CLI 和 Web App 如何分工,以及三接口边界与 OmniMessage 如何组织整个系统。----PenguinHarness 是一个 pnpm monorepo,核心是 `@adelie/core` 里的执行引擎。Server 是随产品交付的 Human 实现,所有 Task 都由它运行;SDK 嵌入方也可以直接驱动引擎。+Adelie 是一个 pnpm monorepo,核心是 `@adelie/core` 里的执行引擎。Server 是随产品交付的 Human 实现,所有 Task 都由它运行;SDK 嵌入方也可以直接驱动引擎。Web App 和 CLI 经 HTTP 与 SSE 访问 Server,桌面应用则把 Server 和 Web App 装进同一个窗口。本页依次介绍分层结构、引擎的三接口边界、[一个 Task 的数据流](#一个-task-的数据流)、各项职责的归属和源码结构。@@ -71,7 +71,7 @@ CLI 和 Web App 经 HTTP 与 SSE 同 Server 通信。随产品交付的各个应| --- | --- | --- || SDK(`core`) | 协议与执行:让消息流动的一切 | 持久化用户状态、多用户、任何渲染 || Server | 常驻进程与多用户运行时 | 引擎逻辑,完全委托给 SDK |-| 文件层(`~/.penguin/data`) | 一切可编辑的定义与一切被记录的历史 | 任何计算 |+| 文件层(`~/.adelie/data`) | 一切可编辑的定义与一切被记录的历史 | 任何计算 || CLI / Web | 渲染与交互 | 业务状态 |逐项对应(设计 → 归属 → 承载文件或模块):@@ -104,7 +104,7 @@ CLI 和 Web App 经 HTTP 与 SSE 同 Server 通信。随产品交付的各个应## 状态层-引擎之下是纯文件的状态层。数据根目录为 `~/.penguin/data`(可用 `PENGUIN_HOME` 修改),按 `<project>/agents/<agent>/` 组织:+引擎之下是纯文件的状态层。数据根目录为 `~/.adelie/data`(可用 `ADELIE_HOME` 修改),按 `<project>/agents/<agent>/` 组织:| 组件 | 位置 | 内容 || --- | --- | --- |diff --git a/packages/docs/content/builtin-browser.en.md b/packages/docs/content/builtin-browser.en.mdindex d9ad65c0..8b60b513 100644--- a/packages/docs/content/builtin-browser.en.md+++ b/packages/docs/content/builtin-browser.en.md@@ -85,7 +85,7 @@ Import copies the cookies (which hold your sign-ins) and the history of one profWhat to expect on each platform:-- **macOS**: Chromium-based browsers encrypt cookies with a key kept in your Keychain, so macOS asks whether PenguinHarness may use the Keychain item named after the browser, such as "Chrome Safe Storage". Allow it; if you deny it, the encrypted cookies are skipped and the result says so.+- **macOS**: Chromium-based browsers encrypt cookies with a key kept in your Keychain, so macOS asks whether Adelie may use the Keychain item named after the browser, such as "Chrome Safe Storage". Allow it; if you deny it, the encrypted cookies are skipped and the result says so.- **Windows**: Chrome 127 and later protect most cookies with app-bound encryption, which only Chrome itself can read. Those cookies are skipped with a warning; sign in in the panel instead. A browser that is running may also hold its cookie file open; close it and import again.- **Linux**: newer cookies are encrypted with a password kept in the desktop keyring, read through `secret-tool` (from the `libsecret-tools` package on Debian and Ubuntu). Without it those cookies are skipped with a warning.- **Firefox** stores cookies unencrypted. Cookies kept for a container or partitioned to another site are left out.@@ -128,9 +128,9 @@ Every tab is a whole web page with memory of its own: a busy shopping or news si| System | Log file || --- | --- |-| macOS | `~/Library/Application Support/PenguinHarness/logs/desktop.log` |-| Windows | `%APPDATA%\PenguinHarness\logs\desktop.log` |-| Linux | `~/.config/PenguinHarness/logs/desktop.log` |+| macOS | `~/Library/Application Support/Adelie/logs/desktop.log` |+| Windows | `%APPDATA%\Adelie\logs\desktop.log` |+| Linux | `~/.config/Adelie/logs/desktop.log` |## How it worksdiff --git a/packages/docs/content/builtin-browser.zh.md b/packages/docs/content/builtin-browser.zh.mdindex 86052ed3..f3c53cc1 100644--- a/packages/docs/content/builtin-browser.zh.md+++ b/packages/docs/content/builtin-browser.zh.md@@ -85,7 +85,7 @@ Agent 从不输入你的密码。Agent 需要的页面要求登录时,`browser各平台的注意事项:-- **macOS**:基于 Chromium 的浏览器用保存在钥匙串里的密钥加密 Cookie,因此 macOS 会询问是否允许 PenguinHarness 使用以浏览器命名的钥匙串项目,例如「Chrome Safe Storage」。请选择允许;拒绝的话,加密的 Cookie 会被跳过,导入结果中会说明。+- **macOS**:基于 Chromium 的浏览器用保存在钥匙串里的密钥加密 Cookie,因此 macOS 会询问是否允许 Adelie 使用以浏览器命名的钥匙串项目,例如「Chrome Safe Storage」。请选择允许;拒绝的话,加密的 Cookie 会被跳过,导入结果中会说明。- **Windows**:Chrome 127 及以后的版本用应用绑定加密保护大部分 Cookie,只有 Chrome 自己能读取。这些 Cookie 会被跳过并给出警告,请改为在面板里登录。正在运行的浏览器也可能占用它的 Cookie 文件,关闭浏览器后再导入即可。- **Linux**:较新的 Cookie 用保存在桌面密钥环里的密码加密,通过 `secret-tool` 读取(Debian 和 Ubuntu 上由 `libsecret-tools` 软件包提供)。没有它时,这些 Cookie 会被跳过并给出警告。- **Firefox** 的 Cookie 不加密。容器专用的 Cookie 和按其他网站分区的 Cookie 不会导入。@@ -128,9 +128,9 @@ EOF| 系统 | 日志文件 || --- | --- |-| macOS | `~/Library/Application Support/PenguinHarness/logs/desktop.log` |-| Windows | `%APPDATA%\PenguinHarness\logs\desktop.log` |-| Linux | `~/.config/PenguinHarness/logs/desktop.log` |+| macOS | `~/Library/Application Support/Adelie/logs/desktop.log` |+| Windows | `%APPDATA%\Adelie\logs\desktop.log` |+| Linux | `~/.config/Adelie/logs/desktop.log` |## 工作原理diff --git a/packages/docs/content/cli.en.md b/packages/docs/content/cli.en.mdindex d9182cc2..876cbe10 100644--- a/packages/docs/content/cli.en.md+++ b/packages/docs/content/cli.en.md@@ -7,33 +7,33 @@ This page documents every `penguin` command. It opens with how the CLI reaches aThe CLI ships as the npm package `@adelie/cli`, and the command is `penguin`. Bare `penguin` prints help. `-v, --version` prints the running build's one-line identity, and `penguin version --json` prints all of it. On startup the CLI loads a `.env` file from the working directory.-The CLI is a thin client of the server. Every session-facing command (`run`, `chat`, `ls`, `input`, `logs`, `agent`, `project`, `cost`, `schedule`, `org`, `browser`) sends HTTP requests to a PenguinHarness server and renders the replies. Tasks run on the server, Sessions live in its index, and the Web App sees everything the CLI creates, and the other way round. Only `config` still edits the Project's files directly, and `server` / `web` start the service itself.+The CLI is a thin client of the server. Every session-facing command (`run`, `chat`, `ls`, `input`, `logs`, `agent`, `project`, `cost`, `schedule`, `org`, `browser`) sends HTTP requests to an Adelie server and renders the replies. Tasks run on the server, Sessions live in its index, and the Web App sees everything the CLI creates, and the other way round. Only `config` still edits the Project's files directly, and `server` / `web` start the service itself.## Server connectionA CLI that talks to the server on the local machine needs no login, except to change an agent's exposure (see [penguin agent api](#penguin-agent-api)). The CLI picks its server in this order, and the first match wins:1. `--server <url>`: an explicit target.-2. `PENGUIN_API_URL`: the same, from the environment. Server-driven sessions inject it into every tool subprocess, together with `PENGUIN_API_TOKEN`, `PENGUIN_PROJECT_ID`, `PENGUIN_AGENT_ID` and `PENGUIN_SESSION_ID`, so an agent's own `penguin` calls reach the server that runs them.-3. A live `server.lock` at the data root (`PENGUIN_HOME`, else `~/.penguin/data`): the CLI attaches to the running local server.+2. `ADELIE_API_URL`: the same, from the environment. Server-driven sessions inject it into every tool subprocess, together with `ADELIE_API_TOKEN`, `ADELIE_PROJECT_ID`, `ADELIE_AGENT_ID` and `ADELIE_SESSION_ID`, so an agent's own `penguin` calls reach the server that runs them.+3. A live `server.lock` at the data root (`ADELIE_HOME`, else `~/.adelie/data`): the CLI attaches to the running local server.4. Auto-start: the CLI spawns a detached local server on an ephemeral port, waits for it and attaches. The server's output goes to `<root>/logs/server-auto-<date>.log`. If two CLIs race, the losing spawn exits and both attach to the winner.-The CLI authenticates with the local API token. The server writes a fresh token to `<root>/api-token` on every boot (owner-only), and the CLI sends it as `Authorization: Bearer`. `PENGUIN_API_TOKEN` overrides the file. The CLI reads the file only for loopback targets, so a remote `--server` needs `PENGUIN_API_TOKEN` set explicitly. Holding the file grants admin authority by design, because local filesystem access to the data root already does. `penguin server reset-admin-password` relies on the same rule.+The CLI authenticates with the local API token. The server writes a fresh token to `<root>/api-token` on every boot (owner-only), and the CLI sends it as `Authorization: Bearer`. `ADELIE_API_TOKEN` overrides the file. The CLI reads the file only for loopback targets, so a remote `--server` needs `ADELIE_API_TOKEN` set explicitly. Holding the file grants admin authority by design, because local filesystem access to the data root already does. `penguin server reset-admin-password` relies on the same rule.A few writes take a person's sign-in instead, such as those that change an agent's exposure (see [penguin agent api](#penguin-agent-api)). The server refuses the token on them with `403` `human_required`, and the CLI then sends that request once more with your sign-in from [`penguin auth login`](#penguin-auth-login) or [`penguin auth token`](#penguin-auth-token), stored in `<root>/cli-session.json` and sent as the session cookie. It does so only for a server on this machine, only when the sign-in itself is to a server on this machine, and never from inside a Session, where the command is an agent's. Every other request carries the token alone.## Global conventions- Model references: a model's identity is always the `(provider, model_id)` pair. `--model-id` takes the upstream model id and `--provider` the group it belongs to. The CLI never infers, guesses or defaults the provider. On `run` and `chat` the pair as a whole is optional: pass both to pick a model, or neither to use the Project's default model. Passing only one is an error.-- Project and agent defaults: `--project-id` falls back to `PENGUIN_PROJECT_ID`, then `default_project`. `--agent-id` falls back to `PENGUIN_AGENT_ID`, then `default_agent`. Inside a server-driven session, those variables name the session's own Project and agent.+- Project and agent defaults: `--project-id` falls back to `ADELIE_PROJECT_ID`, then `default_project`. `--agent-id` falls back to `ADELIE_AGENT_ID`, then `default_agent`. Inside a server-driven session, those variables name the session's own Project and agent.- Session references: wherever a command takes a session id (`input`, `logs`, `run --session`, `chat --resume`), the full id or any unique fragment works. The 8-hex tail that `penguin ls` prints is the intended shorthand. An ambiguous fragment is an error that lists the candidates.- Latest-session default: where the session id is optional (`input [session_id]`, `logs [session_id]`, `chat --resume`), omitting it means the agent's most recent Session, and `--agent-id` picks the agent. `input` and `logs` name the Session they picked in a dim `[latest]` line on stderr, so the target is always clear and `--json` output on stdout stays parseable. When the agent has no Session at all, they print one line pointing at `penguin run` / `penguin chat` and exit non-zero.- JSON output: `--json` prints raw JSON instead of rendered or tabular output.- Target server: `--server <url>` targets a specific server. See [Server connection](#server-connection).-- Caller-context defaults: inside a harness agent (`PENGUIN_SESSION_ID` is set), a Session created by `run` or `chat` takes each unspecified field from the calling Session's live values: the Workspace, the model pair, the approval mode and the thinking level. `run_subagent` applies the same inheritance to the children it spawns, so both surfaces follow one convention. For each field, an explicit flag wins over the caller's value, which wins over the plain fallback. A failed lookup prints a dim warning and uses the plain fallback. Outside an agent nothing changes, and `--project-id` / `--agent-id` keep their environment-variable defaults.+- Caller-context defaults: inside a harness agent (`ADELIE_SESSION_ID` is set), a Session created by `run` or `chat` takes each unspecified field from the calling Session's live values: the Workspace, the model pair, the approval mode and the thinking level. `run_subagent` applies the same inheritance to the children it spawns, so both surfaces follow one convention. For each field, an explicit flag wins over the caller's value, which wins over the plain fallback. A failed lookup prints a dim warning and uses the plain fallback. Outside an agent nothing changes, and `--project-id` / `--agent-id` keep their environment-variable defaults.- Timeouts: `--timeout <duration>` on `run`, `input` and `logs -f` bounds the wait with soft-yield semantics, the `exec_command` yield-window model applied to the CLI. At expiry the command detaches cleanly and exits 0. The Task keeps running on the server, and a later `penguin input` or `penguin logs` can pick it up. Accepted values are `30s`, `5m`, `2h`, or a bare integer meaning seconds; anything else is rejected. `--timeout 0` returns immediately after delivery (`{sessionId, status: "running"}` under `--json`), so the same option also covers "don't wait". Without the option, the command waits indefinitely. For new Tasks, `run --background` remains the usual fire-and-forget: it prints the bare session id for scripts and detaches as soon as the Task is created.- Argument errors: a missing argument, a missing required option, an unknown option or a mistyped command prints one line in the interface language, the command's own usage and a pointer to its `--help`, then exits non-zero.-- Data root: `--root <dir>` sets the data root for the commands that read it directly: `config`, `auth`, `version`, `server status` and `server stop`. A relative path resolves against the working directory. Priority: `--root`, then the `PENGUIN_HOME` environment variable, then `~/.penguin/data`.+- Data root: `--root <dir>` sets the data root for the commands that read it directly: `config`, `auth`, `version`, `server status` and `server stop`. A relative path resolves against the working directory. Priority: `--root`, then the `ADELIE_HOME` environment variable, then `~/.adelie/data`.## penguin run@@ -46,8 +46,8 @@ penguin run -m <message> [options]| Option | Description | Default || --- | --- | --- || `-m, --message <message>` | The message to send. Required. | — |-| `--project-id <id>` | Project to use. | `PENGUIN_PROJECT_ID`, else `default_project` |-| `--agent-id <id>` | Agent to use. | `PENGUIN_AGENT_ID`, else `default_agent` |+| `--project-id <id>` | Project to use. | `ADELIE_PROJECT_ID`, else `default_project` |+| `--agent-id <id>` | Agent to use. | `ADELIE_AGENT_ID`, else `default_agent` || `--workspace <path>` | Workspace directory. A relative path resolves against the CLI's working directory. The directory must exist on the server's machine, which in the default local setup is this machine. | The working directory || `--model-id <id>` | Upstream id of the model to use. Requires `--provider`. | The Project's default model || `--provider <group>` | Provider group of the model. Required with `--model-id`. | — |@@ -162,8 +162,8 @@ penguin input [session_id] [options]| --- | --- | --- || `-m, --message <text>` | The message text. Omit it to poll the last assistant reply instead. | — || `--timeout <duration>` | Soft-yield wait budget. With `-m`, the command detaches at expiry as `run` does, and `--timeout 0` returns right after delivery. Without `-m`, the command takes the snapshot at expiry (`0` means immediately) and notes that the Session is still running. | Wait indefinitely |-| `--project-id <id>` | Scope of the fragment search. A full session id needs none. | `PENGUIN_PROJECT_ID`, else `default_project` |-| `--agent-id <id>` | The agent whose most recent Session an omitted session id means. | `PENGUIN_AGENT_ID`, else `default_agent` |+| `--project-id <id>` | Scope of the fragment search. A full session id needs none. | `ADELIE_PROJECT_ID`, else `default_project` |+| `--agent-id <id>` | The agent whose most recent Session an omitted session id means. | `ADELIE_AGENT_ID`, else `default_agent` || `--json` / `--server <url>` | See [Global conventions](#global-conventions) and the JSON shapes below. | — |With `-m`, a running Session receives the text as steering, delivered between turns, and an idle Session starts a new Task. By default the command waits and renders until the turn completes.@@ -196,8 +196,8 @@ penguin logs [session_id] [options]| `--tail <n>` | Shows only the last n entries. | All entries || `-f, --follow` | Keeps following the live stream after the history. Read-only: Ctrl-C detaches without touching the Session. | — || `--timeout <duration>` | Stops following after this long (soft yield, exit 0). Only meaningful with `-f`. | — |-| `--project-id <id>` | Scope of the fragment search. | `PENGUIN_PROJECT_ID`, else `default_project` |-| `--agent-id <id>` | The agent whose most recent Session an omitted session id means. | `PENGUIN_AGENT_ID`, else `default_agent` |+| `--project-id <id>` | Scope of the fragment search. | `ADELIE_PROJECT_ID`, else `default_project` |+| `--agent-id <id>` | The agent whose most recent Session an omitted session id means. | `ADELIE_AGENT_ID`, else `default_agent` || `--json` / `--server <url>` | `--json` prints the raw message array, and with `-f` one JSON message per line as messages arrive. | — |```bash@@ -261,7 +261,7 @@ Options:| Option | Description | Default || --- | --- | --- |-| `--agent-id <id>` | The agent. Required: unlike other commands, it never falls back to `PENGUIN_AGENT_ID` or `default_agent`, so no agent is exposed by default. | — |+| `--agent-id <id>` | The agent. Required: unlike other commands, it never falls back to `ADELIE_AGENT_ID` or `default_agent`, so no agent is exposed by default. | — || `--open` / `--no-open` | Allows keyless access / requires a key (`enable`, `set`). | Unchanged || `--approve <mode>` | The approval mode new API conversations start with; see [Approval modes (--approve)](#approval-modes---approve). A mode that asks sends the question to the calling program (`enable`, `set`). An unknown mode fails before any request. | Unchanged || `--name <name>` | The key's name, 1–64 characters (`keys create`, required). | — |@@ -453,7 +453,7 @@ penguin org finance [--period <YYYY-MM>] [--json]Every subcommand takes `--org-id <id>`, `--project-id`, `--json` and `--server`.-`--org-id` defaults to `PENGUIN_ORG_ID`, the one variable company mode adds to the environment described under [Server connection](#server-connection). The server injects it into every tool subprocess of a desk or ticket session, so an employee's own `penguin org` calls reach its organization without naming it, while a person in a shell passes the flag. There is no default organization: with neither the flag nor the variable, the command fails before contacting any server. `create` is the exception, because its `--org-id` is the id to create and never comes from the environment.+`--org-id` defaults to `ADELIE_ORG_ID`, the one variable company mode adds to the environment described under [Server connection](#server-connection). The server injects it into every tool subprocess of a desk or ticket session, so an employee's own `penguin org` calls reach its organization without naming it, while a person in a shell passes the flag. There is no default organization: with neither the flag nor the variable, the command fails before contacting any server. `create` is the exception, because its `--org-id` is the id to create and never comes from the environment.`--json` prints the response as one line of JSON. Without it, the write commands print a one-line confirmation.@@ -461,9 +461,9 @@ Every subcommand takes `--org-id <id>`, `--project-id`, `--json` and `--server`.Inside a session, the same environment identifies the caller:-- `--agent-id` on the `calendar` commands and the `<agent_id>` argument of `desk` default to `PENGUIN_AGENT_ID`, so an employee schedules its own events and renews its own desk. `calendar ls` without the flag lists every employee's events.-- `ticket start` runs the ticket session as `--agent-id` when given, else as `PENGUIN_AGENT_ID` when it is set, else as the ticket's owner, whom the server picks. The command also sends `PENGUIN_SESSION_ID`, which lets the server enforce its rule: only the ticket's owner, or a person, starts the ticket's sessions. An employee that asks for someone else's ticket, or for a ticket with no employee owner, gets `403 not_ticket_owner`, printed verbatim. The error tells it to assign the ticket instead (`penguin org ticket assign <id> --owner agent:<employee>`) and let that employee's desk pick it up in its next sweep. The owner uses `--agent-id` to bring a colleague onto its own ticket.-- The ticket writes (`create`, `assign`, `move`, `block`, `unblock`, `progress`) and the channel writes (`create`, `invite`, `join`, `archive`, `unarchive`, `send`) send `PENGUIN_SESSION_ID` in their request body, so the file records the session's employee rather than the token's user. `ticket attach` attaches that session when `--session` is omitted; `--session` takes a full id or a unique fragment, as everywhere.+- `--agent-id` on the `calendar` commands and the `<agent_id>` argument of `desk` default to `ADELIE_AGENT_ID`, so an employee schedules its own events and renews its own desk. `calendar ls` without the flag lists every employee's events.+- `ticket start` runs the ticket session as `--agent-id` when given, else as `ADELIE_AGENT_ID` when it is set, else as the ticket's owner, whom the server picks. The command also sends `ADELIE_SESSION_ID`, which lets the server enforce its rule: only the ticket's owner, or a person, starts the ticket's sessions. An employee that asks for someone else's ticket, or for a ticket with no employee owner, gets `403 not_ticket_owner`, printed verbatim. The error tells it to assign the ticket instead (`penguin org ticket assign <id> --owner agent:<employee>`) and let that employee's desk pick it up in its next sweep. The owner uses `--agent-id` to bring a colleague onto its own ticket.+- The ticket writes (`create`, `assign`, `move`, `block`, `unblock`, `progress`) and the channel writes (`create`, `invite`, `join`, `archive`, `unarchive`, `send`) send `ADELIE_SESSION_ID` in their request body, so the file records the session's employee rather than the token's user. `ticket attach` attaches that session when `--session` is omitted; `--session` takes a full id or a unique fragment, as everywhere.- The channel reads (`ls`, `show`, `tail`) and the member DELETE behind `leave` and `remove` have no request body, so they send the same session as `?sessionId=`. Without it, the server would answer an employee as the signed-in person, and `channel ls` would list every channel instead of the employee's own.### ls, show and chart@@ -560,9 +560,9 @@ penguin browser history [<query>] [-n <count>]- `--tab <id>` names the tab that `open`, `scan`, `exec`, `click`, `type`, `screenshot` and `cdp` act on: a tab id from `tabs`, or `active`, the default.- `--json` prints the response as one line of JSON, and `--server` works as everywhere.-- Inside a session, `open`, `exec`, `click` and `type` send `PENGUIN_SESSION_ID`, so the app opens the Browser panel in the conversation that is driving it.+- Inside a session, `open`, `exec`, `click` and `type` send `ADELIE_SESSION_ID`, so the app opens the Browser panel in the conversation that is driving it.- These commands never auto-start a server, because a server started that way would have no desktop app to host the browser. With no server running they fail with `browser_unavailable`.-- The labels and messages follow the CLI's language. The examples here are the English output; with `PENGUIN_LANG=zh` they are in Chinese.+- The labels and messages follow the CLI's language. The examples here are the English output; with `ADELIE_LANG=zh` they are in Chinese.`status` prints `status: available` and the tab list, or `status: unavailable (<reason>)` followed by a note, and then exits 1. The reason is `not_desktop` (the server is not the desktop app's), `shell_unsupported` (the desktop app is too old for the browser) or `no_window` (the app has no window open).@@ -634,7 +634,7 @@ The result names the source, then prints `cookies: <n> imported, <n> skipped, <n### Errors-An error is one line on stderr, `error: <code>: <message>`, and the command exits 1. The server's codes are `browser_unavailable`, `no_tab` (no tab is open), `no_such_tab`, `tab_crashed` (the tab's page crashed: close it and open the page in a new tab), `too_many_tabs` (the browser holds 20 tabs), `script_error`, `timeout`, `invalid_url`, `source_not_found` and `import_failed`; the CLI adds `invalid_argument` for a command typed wrong, `io_error` for a file it cannot read or write, and `request_failed` when the server cannot be reached. For `browser_unavailable` the message explains that the built-in browser needs the PenguinHarness desktop app, and that the app must be open.+An error is one line on stderr, `error: <code>: <message>`, and the command exits 1. The server's codes are `browser_unavailable`, `no_tab` (no tab is open), `no_such_tab`, `tab_crashed` (the tab's page crashed: close it and open the page in a new tab), `too_many_tabs` (the browser holds 20 tabs), `script_error`, `timeout`, `invalid_url`, `source_not_found` and `import_failed`; the CLI adds `invalid_argument` for a command typed wrong, `io_error` for a file it cannot read or write, and `request_failed` when the server cannot be reached. For `browser_unavailable` the message explains that the built-in browser needs the Adelie desktop app, and that the app must be open.## Approval modes (--approve)@@ -717,7 +717,7 @@ penguin config vault remove --key GITHUB_TOKENpenguin config lang en```-Sets the CLI's interface language (`en` or `zh`) by writing `PENGUIN_LANG` into your shell's startup file. In an interactive terminal the command then offers to open a new shell so the setting takes effect; otherwise it prints how to apply it. On Windows the command is refused, because there is no POSIX shell startup file to write.+Sets the CLI's interface language (`en` or `zh`) by writing `ADELIE_LANG` into your shell's startup file. In an interactive terminal the command then offers to open a new shell so the setting takes effect; otherwise it prints how to apply it. On Windows the command is refused, because there is no POSIX shell startup file to write.## penguin server / penguin web@@ -753,7 +753,7 @@ penguin server status [--root <dir>]# {"running":true,"port":7364,"pid":41233,"machineId":"LNrJdHAZJ91G58i0"}```-`running` is true only when the recorded pid is alive and its port accepts a connection, so a recycled pid does not look like a live server. `port` and `pid` are `null` when no server is running. `machineId` is `null` until a server has started on this machine at least once: the id is minted on first boot and never changes afterwards. The data root comes from `--root` or `PENGUIN_HOME` as usual.+`running` is true only when the recorded pid is alive and its port accepts a connection, so a recycled pid does not look like a live server. `port` and `pid` are `null` when no server is running. `machineId` is `null` until a server has started on this machine at least once: the id is minted on first boot and never changes afterwards. The data root comes from `--root` or `ADELIE_HOME` as usual.The **Machines** page runs this command over ssh to ask a machine what it is doing, which is why the output is JSON rather than prose.@@ -765,7 +765,7 @@ An offline rescue for a forgotten Web admin password. Run it with the server stopenguin server reset-admin-password```-The built-in `admin` returns to the unclaimed state: its password becomes a random one nobody has seen, and all of its sessions are revoked. Start the server again and open the first-login link it prints to set a new password; nothing needs to be written down in between. The admin resets other accounts on the **Users** page, and this command only touches `admin`. The data root comes from `PENGUIN_HOME` as usual.+The built-in `admin` returns to the unclaimed state: its password becomes a random one nobody has seen, and all of its sessions are revoked. Start the server again and open the first-login link it prints to set a new password; nothing needs to be written down in between. The admin resets other accounts on the **Users** page, and this command only touches `admin`. The data root comes from `ADELIE_HOME` as usual.### penguin server stop@@ -795,7 +795,7 @@ penguin version --json # the full build info| Option | Description | Default || --- | --- | --- || `--json` | Prints the full version report instead of one line: `{version, describe, channel, buildDate, commit, branch, dirty, runtime, harness}`. | — |-| `--root <dir>` | The data root whose HMR store is reported as `harness`. Only used with `--json`. | `PENGUIN_HOME`, else `~/.penguin/data` |+| `--root <dir>` | The data root whose HMR store is reported as `harness`. Only used with `--json`. | `ADELIE_HOME`, else `~/.adelie/data` |The bare form prints one line. For a source build, that line is the output of `git describe --tags --dirty`: `v0.2.3-14-g9e8f7d6-dirty` means fourteen commits after `v0.2.3`, at commit `9e8f7d6`, with uncommitted changes. `-v, --version` prints the same line.@@ -813,7 +813,7 @@ The JSON is the same record that `GET /api/version` returns, so a bug report can```json"harness": {- "source": { "repo": "…/penguin-harness", "revision": "v0.2.3-7-gabc1234-dirty" },+ "source": { "repo": "…/Adelie", "revision": "v0.2.3-7-gabc1234-dirty" },"pushedAt": "2026-08-20T10:15:00.000Z","bundles": { "platform": "store/platform/…", "cli": "store/cli/…", "web": "store/web/…" }}@@ -827,7 +827,7 @@ An installed `penguin` never runs git: it reads constants stamped into the build## penguin auth-Signs in to a running PenguinHarness server from the terminal. There are two ways in, and the right one depends on where you are.+Signs in to a running Adelie server from the terminal. There are two ways in, and the right one depends on where you are.```bashpenguin auth login # password, against the server on this data root@@ -843,17 +843,17 @@ Every `auth` subcommand takes `--root <dir>` to pick the data root; see [Global`login` takes a password and asks a running server for a session, exactly as the browser's login page does. The target defaults to the server running on this data root, read from its lock file, so signing in to your own server needs no URL.-When run interactively, `login` asks for the account first and then the password, and the password prompt names the account, so you never type one account's password for another. If you supply the password non-interactively (`--password` or `PENGUIN_PASSWORD`), neither question is asked, because a script cannot answer them.+When run interactively, `login` asks for the account first and then the password, and the password prompt names the account, so you never type one account's password for another. If you supply the password non-interactively (`--password` or `ADELIE_PASSWORD`), neither question is asked, because a script cannot answer them.| Option | Description | Default || --- | --- | --- || `--server <url>` | The server to sign in to. | The server running on this data root || `--user-id <id>` | The account. Asked for when omitted; a bare Enter means `admin`. | `admin` |-| `--password <pw>` | The password. Also read from `PENGUIN_PASSWORD`; otherwise prompted for without echo. | — |+| `--password <pw>` | The password. Also read from `ADELIE_PASSWORD`; otherwise prompted for without echo. | — || `--print` | Also prints the session token to stdout, for piping. | — |> [!WARNING]-> Prefer `PENGUIN_PASSWORD` or the prompt over `--password`: anyone on the machine can read a command line through `ps`.+> Prefer `ADELIE_PASSWORD` or the prompt over `--password`: anyone on the machine can read a command line through `ps`.### penguin auth token@@ -892,7 +892,7 @@ The flag is `--release`, not `--version`, because `-v, --version` is the CLI's o| Install kind | How it upgrades || --- | --- |-| Tarball (`install.sh`, default `~/.penguin`) | Re-runs the official installer, keeping the install directory and whether the package bundles a Node runtime |+| Tarball (`install.sh`, default `~/.adelie`) | Re-runs the official installer, keeping the install directory and whether the package bundles a Node runtime || Global npm, pnpm, yarn or bun install | Runs that package manager's global install of `@adelie/cli@<target>`. If the manager cannot be identified, prints the command instead of guessing || Source checkout | Refused: update it with `git pull` and a rebuild || The desktop app's bundled CLI | Refused: it is replaced when the app updates, so check for updates from the app menu |@@ -900,11 +900,10 @@ The flag is `--release`, not `--version`, because `-v, --version` is the CLI's oWithout `-y`, the command prints exactly what it will do (the mechanism, the target version and the install directory) and asks for confirmation. When stdin is not a terminal, it requires `--yes` instead of waiting on a prompt nobody can answer. **The data root is never touched**: an upgrade replaces only `bin`, `lib`, `web` and `node`. On Windows neither upgrade path runs in place. The installer is a POSIX shell script, and a global install cannot be driven from here because Node does not execute an `npm` or `pnpm` `.cmd` shim without a shell, so the command prints the exact command for you to run yourself.-Release discovery and downloads follow `PENGUIN_DOWNLOAD_SOURCE=auto|oss|github`, the same policy as the stable installer entry point:+Release discovery and downloads follow `PENGUIN_DOWNLOAD_SOURCE=auto|github`, the same policy as the stable installer entry point. Adelie publishes to one source — this repository's GitHub Releases — so the two values mean the same thing, and upstream's `oss` mirror is refused rather than ignored:-- `auto`, the default, reads the OSS `latest.json`, prefers that immutable release, and falls back to the matching GitHub tag. The package itself then comes from whichever source the installer's speed probe picks.-- `oss` and `github` are strict: the command uses only that source.-- `--release <tag>` skips latest-version discovery but still follows the selected source policy.+- `auto`, the default, and `github` both resolve the newest Release through this repository's GitHub Releases.+- `--release <tag>` skips newest-version discovery but keeps the same source.- An explicit HTTPS `PENGUIN_DOWNLOAD_BASE_URL` takes precedence over everything for the installer and package downloads, and `PENGUIN_DOWNLOAD_FALLBACK_BASE_URL` optionally adds a fallback for the package.See also: [Configuration Reference](/configuration), [Models & Providers](/models).diff --git a/packages/docs/content/cli.zh.md b/packages/docs/content/cli.zh.mdindex ae6fce0e..a2ab8431 100644--- a/packages/docs/content/cli.zh.md+++ b/packages/docs/content/cli.zh.md@@ -7,33 +7,33 @@ description: 所有 penguin 命令和子命令的选项、默认值、输出结CLI 以 npm 包 `@adelie/cli` 发布,命令名为 `penguin`。直接运行 `penguin` 会打印帮助。`-v, --version` 打印当前构建的一行标识信息,`penguin version --json` 则打印完整信息。启动时,CLI 会从工作目录加载 `.env` 文件。-CLI 是服务器的瘦客户端。所有面向会话的命令(`run`、`chat`、`ls`、`input`、`logs`、`agent`、`project`、`cost`、`schedule`、`org`、`browser`)都向 PenguinHarness 服务器发送 HTTP 请求,并渲染返回结果。Task 在服务器上运行,Session 存放在服务器的索引里;CLI 创建的一切 Web App 都能看到,反过来也一样。只有 `config` 仍直接编辑 Project 的文件,`server` / `web` 则负责启动服务本身。+CLI 是服务器的瘦客户端。所有面向会话的命令(`run`、`chat`、`ls`、`input`、`logs`、`agent`、`project`、`cost`、`schedule`、`org`、`browser`)都向 Adelie 服务器发送 HTTP 请求,并渲染返回结果。Task 在服务器上运行,Session 存放在服务器的索引里;CLI 创建的一切 Web App 都能看到,反过来也一样。只有 `config` 仍直接编辑 Project 的文件,`server` / `web` 则负责启动服务本身。## 服务器连接与本机服务器通信的 CLI 无需登录,只有改变 Agent 的对外暴露时例外(见 [penguin agent api](#penguin-agent-api))。CLI 按以下顺序确定要连接的服务器,命中第一项即停止:1. `--server <url>`:显式指定的目标。-2. `PENGUIN_API_URL`:同样指定目标,但取自环境变量。服务器驱动的会话会把它注入每个工具子进程,同时注入的还有 `PENGUIN_API_TOKEN`、`PENGUIN_PROJECT_ID`、`PENGUIN_AGENT_ID` 和 `PENGUIN_SESSION_ID`,这样 Agent 自己调用 `penguin` 时,请求就能到达运行它的那台服务器。-3. 数据根目录下存在活跃的 `server.lock`(数据根目录取 `PENGUIN_HOME`,否则为 `~/.penguin/data`):CLI 接入正在运行的本地服务器。+2. `ADELIE_API_URL`:同样指定目标,但取自环境变量。服务器驱动的会话会把它注入每个工具子进程,同时注入的还有 `ADELIE_API_TOKEN`、`ADELIE_PROJECT_ID`、`ADELIE_AGENT_ID` 和 `ADELIE_SESSION_ID`,这样 Agent 自己调用 `penguin` 时,请求就能到达运行它的那台服务器。+3. 数据根目录下存在活跃的 `server.lock`(数据根目录取 `ADELIE_HOME`,否则为 `~/.adelie/data`):CLI 接入正在运行的本地服务器。4. 自动启动:CLI 在临时端口上拉起一个独立运行的本地服务器,等它就绪后接入。服务器输出写入 `<root>/logs/server-auto-<date>.log`。如果两个 CLI 同时抢着启动,落败一方的启动进程会退出,双方都接入先成功的那台。-CLI 使用本地 API token 认证。服务器每次启动都会把一个新 token 写入 `<root>/api-token`(仅所有者可读),CLI 以 `Authorization: Bearer` 的形式发送它。`PENGUIN_API_TOKEN` 优先于这个文件。CLI 只对回环地址目标读取这个文件,因此远程 `--server` 需要显式设置 `PENGUIN_API_TOKEN`。按设计,持有这个文件就等于持有管理员权限——能直接访问数据根目录的本地文件系统,本来就拥有同样的权限。`penguin server reset-admin-password` 依据的也是同一条规则。+CLI 使用本地 API token 认证。服务器每次启动都会把一个新 token 写入 `<root>/api-token`(仅所有者可读),CLI 以 `Authorization: Bearer` 的形式发送它。`ADELIE_API_TOKEN` 优先于这个文件。CLI 只对回环地址目标读取这个文件,因此远程 `--server` 需要显式设置 `ADELIE_API_TOKEN`。按设计,持有这个文件就等于持有管理员权限——能直接访问数据根目录的本地文件系统,本来就拥有同样的权限。`penguin server reset-admin-password` 依据的也是同一条规则。少数修改只接受人的登录,例如改变 Agent 对外暴露的修改(见 [penguin agent api](#penguin-agent-api))。服务器以 `403` `human_required` 拒绝携带 token 的这类请求,CLI 随即改用你通过 [`penguin auth login`](#penguin-auth-login) 或 [`penguin auth token`](#penguin-auth-token) 保存的登录把同一请求再发一次:登录存放在 `<root>/cli-session.json`,以会话 Cookie 发送。CLI 只对本机上的服务器这样做,只在登录的对象本身就是本机服务器时使用,且从不在 Session 内使用——那里的命令属于 Agent。其余请求一律只带 token。## 全局约定- 模型引用:模型的标识始终是 `(provider, model_id)` 这一对。`--model-id` 接收上游模型 id,`--provider` 接收模型所属的分组。CLI 从不推断、猜测或默认指定供应商。在 `run` 和 `chat` 上,这一对参数整体可选:两个都传即可选择模型,两个都不传则使用 Project 的默认模型;只传一个是错误。-- Project 与 Agent 默认值:`--project-id` 依次回退到 `PENGUIN_PROJECT_ID`,再回退到 `default_project`;`--agent-id` 依次回退到 `PENGUIN_AGENT_ID`,再回退到 `default_agent`。在服务器驱动的会话里,这些环境变量指向会话所属的 Project 和 Agent。+- Project 与 Agent 默认值:`--project-id` 依次回退到 `ADELIE_PROJECT_ID`,再回退到 `default_project`;`--agent-id` 依次回退到 `ADELIE_AGENT_ID`,再回退到 `default_agent`。在服务器驱动的会话里,这些环境变量指向会话所属的 Project 和 Agent。- Session 引用:凡是接受 session id 的命令(`input`、`logs`、`run --session`、`chat --resume`),完整 id 或任何唯一的片段都有效。`penguin ls` 打印的 8 位十六进制尾部就是为此准备的简写。片段有歧义时报错,并列出所有候选。- 默认使用最近的 Session:session id 可选的命令(`input [session_id]`、`logs [session_id]`、`chat --resume`)在省略 id 时,指向 Agent 最近的一个 Session,由 `--agent-id` 指定是哪个 Agent。`input` 和 `logs` 会在 stderr 上用一行暗色的 `[latest]` 标注选中的 Session,目标始终明确,stdout 上的 `--json` 输出也保持可解析。如果这个 Agent 一个 Session 都没有,命令会打印一行提示指向 `penguin run` / `penguin chat`,然后以非零码退出。- JSON 输出:`--json` 打印原始 JSON,取代渲染后的或表格形式的输出。- 目标服务器:`--server <url>` 指定要连接的服务器。参见[服务器连接](#服务器连接)。-- 调用方上下文默认值:在 harness Agent 内部(`PENGUIN_SESSION_ID` 已设置)时,`run` 或 `chat` 创建的 Session 会从调用方 Session 的实时取值继承每一个未指定的字段:Workspace、模型对、审批模式和思考等级。`run_subagent` 对它派生的子 Agent 采用同样的继承,两个入口遵循同一条约定。对每个字段,显式传入的选项优先于调用方的值,调用方的值又优先于普通回退值。查找失败时打印一条暗色警告,并改用普通回退值。在 Agent 之外,行为不变:`--project-id` / `--agent-id` 仍按环境变量取默认值。+- 调用方上下文默认值:在 harness Agent 内部(`ADELIE_SESSION_ID` 已设置)时,`run` 或 `chat` 创建的 Session 会从调用方 Session 的实时取值继承每一个未指定的字段:Workspace、模型对、审批模式和思考等级。`run_subagent` 对它派生的子 Agent 采用同样的继承,两个入口遵循同一条约定。对每个字段,显式传入的选项优先于调用方的值,调用方的值又优先于普通回退值。查找失败时打印一条暗色警告,并改用普通回退值。在 Agent 之外,行为不变:`--project-id` / `--agent-id` 仍按环境变量取默认值。- 超时:`run`、`input` 和 `logs -f` 上的 `--timeout <duration>` 限制等待时长,语义为软让出——相当于把 `exec_command` 的让出窗口模型搬到 CLI 上。到时后命令干净地脱离并退出,退出码为 0。Task 在服务器上继续运行,之后可以用 `penguin input` 或 `penguin logs` 接上。可接受的值有 `30s`、`5m`、`2h`,或一个表示秒数的纯整数;其他值一律拒绝。`--timeout 0` 在消息送达后立即返回(`--json` 下为 `{sessionId, status: "running"}`),所以这个选项也覆盖「不等」的场景。不带此选项时,命令无限等待。对新建 Task 而言,惯常做法仍是 `run --background`:提交后不再等待,打印裸 session id 供脚本使用,Task 一创建就脱离。- 参数错误:缺少参数、缺少必填选项、选项未知或命令拼错时,CLI 用界面语言打印一行错误、命令自身的用法,并提示查看 `--help`,然后以非零码退出。-- 数据根目录:`--root <dir>` 为直接读取数据根目录的命令指定根目录,涉及 `config`、`auth`、`version`、`server status` 和 `server stop`。相对路径相对工作目录解析。优先级:`--root`,然后是 `PENGUIN_HOME` 环境变量,最后是 `~/.penguin/data`。+- 数据根目录:`--root <dir>` 为直接读取数据根目录的命令指定根目录,涉及 `config`、`auth`、`version`、`server status` 和 `server stop`。相对路径相对工作目录解析。优先级:`--root`,然后是 `ADELIE_HOME` 环境变量,最后是 `~/.adelie/data`。## penguin run@@ -46,8 +46,8 @@ penguin run -m <message> [options]| 选项 | 说明 | 默认值 || --- | --- | --- || `-m, --message <message>` | 要发送的消息。必填。 | — |-| `--project-id <id>` | 要使用的 Project。 | `PENGUIN_PROJECT_ID`,否则 `default_project` |-| `--agent-id <id>` | 要使用的 Agent。 | `PENGUIN_AGENT_ID`,否则 `default_agent` |+| `--project-id <id>` | 要使用的 Project。 | `ADELIE_PROJECT_ID`,否则 `default_project` |+| `--agent-id <id>` | 要使用的 Agent。 | `ADELIE_AGENT_ID`,否则 `default_agent` || `--workspace <path>` | Workspace 目录。相对路径相对 CLI 的工作目录解析。目录必须存在于服务器所在的机器上;默认的本地部署中,服务器就在本机。 | 工作目录 || `--model-id <id>` | 要使用的模型的上游 id。需要配合 `--provider`。 | Project 的默认模型 || `--provider <group>` | 模型所属的供应商分组。与 `--model-id` 搭配时必填。 | — |@@ -162,8 +162,8 @@ penguin input [session_id] [options]| --- | --- | --- || `-m, --message <text>` | 消息文本。省略它则改为轮询最后一次 助手回复。 | — || `--timeout <duration>` | 软让出的等待预算。带 `-m` 时,到时后命令像 `run` 一样脱离,`--timeout 0` 在送达后立即返回。不带 `-m` 时,命令在到时点拍快照(`0` 表示立即拍),并注明 Session 仍在运行。 | 无限等待 |-| `--project-id <id>` | 片段搜索的范围。完整 session id 无需此选项。 | `PENGUIN_PROJECT_ID`,否则 `default_project` |-| `--agent-id <id>` | 省略 session id 时,取这个 Agent 最近的 Session。 | `PENGUIN_AGENT_ID`,否则 `default_agent` |+| `--project-id <id>` | 片段搜索的范围。完整 session id 无需此选项。 | `ADELIE_PROJECT_ID`,否则 `default_project` |+| `--agent-id <id>` | 省略 session id 时,取这个 Agent 最近的 Session。 | `ADELIE_AGENT_ID`,否则 `default_agent` || `--json` / `--server <url>` | 见[全局约定](#全局约定)和下文的 JSON 结构。 | — |带 `-m` 时,运行中的 Session 收到的文本会作为插话处理,在两轮之间送达;空闲的 Session 则启动一个新 Task。默认情况下,命令会等待并渲染,直到这一轮完成。@@ -196,8 +196,8 @@ penguin logs [session_id] [options]| `--tail <n>` | 只显示最后 n 条记录。 | 全部记录 || `-f, --follow` | 历史播完后继续跟踪实时流。只读:Ctrl-C 脱离,不改动 Session。 | — || `--timeout <duration>` | 跟踪这么长时间后停止(软让出,退出 0)。只在配合 `-f` 时有意义。 | — |-| `--project-id <id>` | 片段搜索的范围。 | `PENGUIN_PROJECT_ID`,否则 `default_project` |-| `--agent-id <id>` | 省略 session id 时,取这个 Agent 最近的 Session。 | `PENGUIN_AGENT_ID`,否则 `default_agent` |+| `--project-id <id>` | 片段搜索的范围。 | `ADELIE_PROJECT_ID`,否则 `default_project` |+| `--agent-id <id>` | 省略 session id 时,取这个 Agent 最近的 Session。 | `ADELIE_AGENT_ID`,否则 `default_agent` || `--json` / `--server <url>` | `--json` 打印原始消息数组;配合 `-f` 时,消息一到就以每行一条 JSON 打印。 | — |```bash@@ -261,7 +261,7 @@ penguin agent api server on|off [--json] [--server <url>]| 选项 | 说明 | 默认值 || --- | --- | --- |-| `--agent-id <id>` | 目标 Agent。必填:与其他命令不同,它不会回退到 `PENGUIN_AGENT_ID` 或 `default_agent`,任何 Agent 都不会因默认值而被对外开放。 | — |+| `--agent-id <id>` | 目标 Agent。必填:与其他命令不同,它不会回退到 `ADELIE_AGENT_ID` 或 `default_agent`,任何 Agent 都不会因默认值而被对外开放。 | — || `--open` / `--no-open` | 允许无密钥访问 / 要求密钥(`enable`、`set`)。 | 不变 || `--approve <mode>` | 新建 API 会话起始的审批模式,见[审批模式(--approve)](#审批模式--approve)。需要确认时,确认请求发给调用方程序(`enable`、`set`)。模式未知时,在发出任何请求之前失败。 | 不变 || `--name <name>` | 密钥名称,1–64 个字符(`keys create`,必填)。 | — |@@ -453,7 +453,7 @@ penguin org finance [--period <YYYY-MM>] [--json]每个子命令都接受 `--org-id <id>`、`--project-id`、`--json` 和 `--server`。-`--org-id` 默认取 `PENGUIN_ORG_ID`——公司模式加入[服务器连接](#服务器连接)所述环境的唯一一个变量。服务器把它注入工位会话和工单会话的每个工具子进程,员工自己调用 `penguin org` 时无需指名,请求就能到达自己所在的组织;人在 shell 里则显式传入这个选项。没有默认组织:选项和变量都不提供时,命令在联系任何服务器之前就会失败。`create` 是例外,因为它的 `--org-id` 就是要创建的 id,从不取自环境。+`--org-id` 默认取 `ADELIE_ORG_ID`——公司模式加入[服务器连接](#服务器连接)所述环境的唯一一个变量。服务器把它注入工位会话和工单会话的每个工具子进程,员工自己调用 `penguin org` 时无需指名,请求就能到达自己所在的组织;人在 shell 里则显式传入这个选项。没有默认组织:选项和变量都不提供时,命令在联系任何服务器之前就会失败。`create` 是例外,因为它的 `--org-id` 就是要创建的 id,从不取自环境。`--json` 把响应打印为一行 JSON。不加时,写命令打印一行确认信息。@@ -461,9 +461,9 @@ penguin org finance [--period <YYYY-MM>] [--json]在会话内部,同一套环境变量标识调用方:-- `calendar` 系列命令的 `--agent-id` 和 `desk` 的 `<agent_id>` 参数默认取 `PENGUIN_AGENT_ID`,员工借此安排自己的日程、换新自己的工位会话。不带选项的 `calendar ls` 列出所有员工的事件。-- `ticket start` 启动工单会话:给了 `--agent-id` 就以它运行;否则在设置了 `PENGUIN_AGENT_ID` 时以它运行;再否则以工单负责人的身份运行,由服务器确定。命令还会发送 `PENGUIN_SESSION_ID`,服务器借此执行自己的规则:只有工单负责人或人才能启动工单会话。员工请求别人的工单,或请求没有员工负责人的工单时,会得到 `403 not_ticket_owner`,原样打印。错误信息会提示改为指派工单(`penguin org ticket assign <id> --owner agent:<employee>`),让那位员工的工位在下一轮巡检时接手。负责人也可以用 `--agent-id` 把同事拉到自己负责的工单上。-- 工单写操作(`create`、`assign`、`move`、`block`、`unblock`、`progress`)和频道写操作(`create`、`invite`、`join`、`archive`、`unarchive`、`send`)在请求体里带上 `PENGUIN_SESSION_ID`,文件里记录的因此是会话对应的员工,而不是 token 的用户。`ticket attach` 在省略 `--session` 时挂接的就是这个会话;`--session` 与其他地方一样,接受完整 id 或唯一片段。+- `calendar` 系列命令的 `--agent-id` 和 `desk` 的 `<agent_id>` 参数默认取 `ADELIE_AGENT_ID`,员工借此安排自己的日程、换新自己的工位会话。不带选项的 `calendar ls` 列出所有员工的事件。+- `ticket start` 启动工单会话:给了 `--agent-id` 就以它运行;否则在设置了 `ADELIE_AGENT_ID` 时以它运行;再否则以工单负责人的身份运行,由服务器确定。命令还会发送 `ADELIE_SESSION_ID`,服务器借此执行自己的规则:只有工单负责人或人才能启动工单会话。员工请求别人的工单,或请求没有员工负责人的工单时,会得到 `403 not_ticket_owner`,原样打印。错误信息会提示改为指派工单(`penguin org ticket assign <id> --owner agent:<employee>`),让那位员工的工位在下一轮巡检时接手。负责人也可以用 `--agent-id` 把同事拉到自己负责的工单上。+- 工单写操作(`create`、`assign`、`move`、`block`、`unblock`、`progress`)和频道写操作(`create`、`invite`、`join`、`archive`、`unarchive`、`send`)在请求体里带上 `ADELIE_SESSION_ID`,文件里记录的因此是会话对应的员工,而不是 token 的用户。`ticket attach` 在省略 `--session` 时挂接的就是这个会话;`--session` 与其他地方一样,接受完整 id 或唯一片段。- 频道读操作(`ls`、`show`、`tail`)以及 `leave` 和 `remove` 背后的成员 DELETE 没有请求体,改为通过 `?sessionId=` 发送同一个会话。不传的话,服务器会把员工当作登录的那个人来应答,`channel ls` 列出的会是所有频道而不是员工自己的频道。### ls、show 和 chart@@ -560,9 +560,9 @@ penguin browser history [<query>] [-n <count>]- `--tab <id>` 指定 `open`、`scan`、`exec`、`click`、`type`、`screenshot` 和 `cdp` 作用的标签页:取 `tabs` 列出的标签页 id,或 `active`(默认值)。- `--json` 把响应打印为一行 JSON;`--server` 与其他命令相同。-- 在会话内部,`open`、`exec`、`click` 和 `type` 会发送 `PENGUIN_SESSION_ID`,应用据此在正在驱动浏览器的那个对话里打开浏览器面板。+- 在会话内部,`open`、`exec`、`click` 和 `type` 会发送 `ADELIE_SESSION_ID`,应用据此在正在驱动浏览器的那个对话里打开浏览器面板。- 这些命令从不自动启动服务器,因为这样启动的服务器没有桌面应用来承载浏览器。没有服务器在运行时,命令以 `browser_unavailable` 失败。-- 输出的标签与提示跟随 CLI 的语言。本节示例是英文输出;`PENGUIN_LANG=zh` 时改用中文,例如 `状态:success 标签页:12`。+- 输出的标签与提示跟随 CLI 的语言。本节示例是英文输出;`ADELIE_LANG=zh` 时改用中文,例如 `状态:success 标签页:12`。`status` 打印 `status: available` 和标签页列表;不可用时打印 `status: unavailable (<reason>)` 和一行说明,并以退出码 1 结束。原因有三种:`not_desktop`(服务器不属于桌面应用)、`shell_unsupported`(桌面应用版本过旧,无法承载浏览器)和 `no_window`(应用没有打开的窗口)。@@ -634,7 +634,7 @@ note: No visible change on the page.### 错误-出错时在 stderr 打印一行 `error: <code>: <message>`,命令以退出码 1 结束。服务器的错误码有 `browser_unavailable`、`no_tab`(没有打开的标签页)、`no_such_tab`、`tab_crashed`(该标签页的页面已崩溃:关闭它,在新标签页中重新打开页面)、`too_many_tabs`(浏览器已有 20 个标签页)、`script_error`、`timeout`、`invalid_url`、`source_not_found` 和 `import_failed`;CLI 自己还有三种:命令写错时的 `invalid_argument`、文件读写失败时的 `io_error`,以及连不上服务器时的 `request_failed`。对于 `browser_unavailable`,错误信息会说明内置浏览器需要 PenguinHarness 桌面应用,并且应用必须处于打开状态。+出错时在 stderr 打印一行 `error: <code>: <message>`,命令以退出码 1 结束。服务器的错误码有 `browser_unavailable`、`no_tab`(没有打开的标签页)、`no_such_tab`、`tab_crashed`(该标签页的页面已崩溃:关闭它,在新标签页中重新打开页面)、`too_many_tabs`(浏览器已有 20 个标签页)、`script_error`、`timeout`、`invalid_url`、`source_not_found` 和 `import_failed`;CLI 自己还有三种:命令写错时的 `invalid_argument`、文件读写失败时的 `io_error`,以及连不上服务器时的 `request_failed`。对于 `browser_unavailable`,错误信息会说明内置浏览器需要 Adelie 桌面应用,并且应用必须处于打开状态。## 审批模式(--approve)@@ -717,7 +717,7 @@ penguin config vault remove --key GITHUB_TOKENpenguin config lang en```-设置 CLI 的界面语言(`en` 或 `zh`),方式是把 `PENGUIN_LANG` 写入你的 shell 启动文件。在交互式终端里,命令随后会提议打开一个新 shell 让设置生效;否则会打印让设置生效的方法。Windows 上命令会拒绝执行,因为没有 POSIX shell 启动文件可写。+设置 CLI 的界面语言(`en` 或 `zh`),方式是把 `ADELIE_LANG` 写入你的 shell 启动文件。在交互式终端里,命令随后会提议打开一个新 shell 让设置生效;否则会打印让设置生效的方法。Windows 上命令会拒绝执行,因为没有 POSIX shell 启动文件可写。## penguin server / penguin web@@ -753,7 +753,7 @@ penguin server status [--root <dir>]# {"running":true,"port":7364,"pid":41233,"machineId":"LNrJdHAZJ91G58i0"}```-只有当记录的 pid 还活着、端口也能建立连接时,`running` 才是 true,所以复用的 pid 不会冒充存活的服务器。没有服务器在运行时,`port` 和 `pid` 为 `null`。`machineId` 在本机至少启动过一次服务器之前为 `null`:id 在首次启动时生成,此后永不改变。数据根目录照常取自 `--root` 或 `PENGUIN_HOME`。+只有当记录的 pid 还活着、端口也能建立连接时,`running` 才是 true,所以复用的 pid 不会冒充存活的服务器。没有服务器在运行时,`port` 和 `pid` 为 `null`。`machineId` 在本机至少启动过一次服务器之前为 `null`:id 在首次启动时生成,此后永不改变。数据根目录照常取自 `--root` 或 `ADELIE_HOME`。**机器管理**页面通过 ssh 运行这条命令,询问一台机器正在做什么,这也是输出采用 JSON 而不是文字说明的原因。@@ -765,7 +765,7 @@ penguin server status [--root <dir>]penguin server reset-admin-password```-内置的 `admin` 账号回到未认领状态:密码换成一个没人见过的随机值,它的所有会话全部吊销。重新启动服务器,打开它打印的首次登录链接设置新密码即可,中间不需要记下任何东西。其他账号由管理员在**用户管理**页面重置,这条命令只处理 `admin`。数据根目录照常取自 `PENGUIN_HOME`。+内置的 `admin` 账号回到未认领状态:密码换成一个没人见过的随机值,它的所有会话全部吊销。重新启动服务器,打开它打印的首次登录链接设置新密码即可,中间不需要记下任何东西。其他账号由管理员在**用户管理**页面重置,这条命令只处理 `admin`。数据根目录照常取自 `ADELIE_HOME`。### penguin server stop@@ -795,7 +795,7 @@ penguin version --json # the full build info| 选项 | 说明 | 默认值 || --- | --- | --- || `--json` | 打印完整的版本报告,而不是一行:`{version, describe, channel, buildDate, commit, branch, dirty, runtime, harness}`。 | — |-| `--root <dir>` | 指定把哪个数据根目录的 HMR 存储报告为 `harness`。仅在指定 `--json` 时使用。 | `PENGUIN_HOME`,否则 `~/.penguin/data` |+| `--root <dir>` | 指定把哪个数据根目录的 HMR 存储报告为 `harness`。仅在指定 `--json` 时使用。 | `ADELIE_HOME`,否则 `~/.adelie/data` |不带选项时打印一行。对源码构建版来说,这一行就是 `git describe --tags --dirty` 的输出:`v0.2.3-14-g9e8f7d6-dirty` 表示在 `v0.2.3` 之后第十四个提交(`9e8f7d6`),且带有未提交的改动。`-v, --version` 打印同样的一行。@@ -813,7 +813,7 @@ penguin version --json # the full build info```json"harness": {- "source": { "repo": "…/penguin-harness", "revision": "v0.2.3-7-gabc1234-dirty" },+ "source": { "repo": "…/Adelie", "revision": "v0.2.3-7-gabc1234-dirty" },"pushedAt": "2026-08-20T10:15:00.000Z","bundles": { "platform": "store/platform/…", "cli": "store/cli/…", "web": "store/web/…" }}@@ -827,7 +827,7 @@ penguin version --json # the full build info## penguin auth-从终端登录一台正在运行的 PenguinHarness 服务器。登录方式有两种,选哪种取决于你所处的位置。+从终端登录一台正在运行的 Adelie 服务器。登录方式有两种,选哪种取决于你所处的位置。```bashpenguin auth login # password, against the server on this data root@@ -843,17 +843,17 @@ penguin auth token # no password: minted from this data roo`login` 使用密码向正在运行的服务器请求会话,和浏览器的登录页完全一样。目标默认是这个数据根目录上运行的服务器,从它的锁文件读出,所以登录你自己的服务器不需要 URL。-交互式运行时,`login` 先问账号、再问密码,密码提示中会显示账号名,因此不会把一个账号的密码误输入给另一个账号。如果以非交互方式提供密码(`--password` 或 `PENGUIN_PASSWORD`),这两个问题都不会出现,因为脚本无法回答。+交互式运行时,`login` 先问账号、再问密码,密码提示中会显示账号名,因此不会把一个账号的密码误输入给另一个账号。如果以非交互方式提供密码(`--password` 或 `ADELIE_PASSWORD`),这两个问题都不会出现,因为脚本无法回答。| 选项 | 说明 | 默认值 || --- | --- | --- || `--server <url>` | 要登录的服务器。 | 这个数据根目录上运行的服务器 || `--user-id <id>` | 账号。省略时会询问;直接回车表示 `admin`。 | `admin` |-| `--password <pw>` | 密码。也可以从 `PENGUIN_PASSWORD` 读取;否则会提示输入且不回显。 | — |+| `--password <pw>` | 密码。也可以从 `ADELIE_PASSWORD` 读取;否则会提示输入且不回显。 | — || `--print` | 同时把 session token 打印到 stdout,供管道使用。 | — |> [!WARNING]-> 优先用 `PENGUIN_PASSWORD` 或交互提示,而不是 `--password`:机器上的任何人都能通过 `ps` 读到命令行。+> 优先用 `ADELIE_PASSWORD` 或交互提示,而不是 `--password`:机器上的任何人都能通过 `ps` 读到命令行。### penguin auth token@@ -892,7 +892,7 @@ penguin update # upgrade to the latest release, after confirming| 安装类型 | 升级方式 || --- | --- |-| 压缩包(`install.sh`,默认 `~/.penguin`) | 重新运行官方安装器,保留原安装目录以及安装包是否自带 Node 运行时 |+| 压缩包(`install.sh`,默认 `~/.adelie`) | 重新运行官方安装器,保留原安装目录以及安装包是否自带 Node 运行时 || npm、pnpm、yarn 或 bun 全局安装 | 用对应的包管理器全局安装 `@adelie/cli@<target>`。无法识别包管理器时,打印命令而不是猜测 || 源码检出 | 拒绝:请用 `git pull` 加重新构建来更新 || 桌面应用内置的 CLI | 拒绝:应用更新时会随之替换,请从应用菜单检查更新 |@@ -900,11 +900,10 @@ penguin update # upgrade to the latest release, after confirming不带 `-y` 时,命令会打印它将要做的事(升级机制、目标版本和安装目录),并要求确认。stdin 不是终端时,命令要求提供 `--yes`,而不是等一个没人能回答的提示。**数据根目录完全不受影响**:升级只替换 `bin`、`lib`、`web` 和 `node`。Windows 上两种升级路径都无法原地执行。安装器是 POSIX shell 脚本;全局安装也无法从这里驱动,因为 Node 离开 shell 就无法执行 `npm` 或 `pnpm` 的 `.cmd` shim,所以命令会把完整命令打印出来,由你自己运行。-发布版本的发现和下载遵循 `PENGUIN_DOWNLOAD_SOURCE=auto|oss|github`,与稳定版安装入口使用相同的策略:+发布版本的发现和下载遵循 `PENGUIN_DOWNLOAD_SOURCE=auto|github`,与稳定版安装入口使用相同的策略。Adelie 只发布到一个来源 —— 这个仓库的 GitHub Release —— 所以这两个取值是一回事,而上游的 `oss` 镜像会被明确拒绝,而不是被忽略:-- `auto` 是默认值:读取 OSS 的 `latest.json`,优先使用那个不可变的发布版本,失败时退回匹配的 GitHub 标签。安装包本身则来自安装器测速后选定的源。-- `oss` 和 `github` 是严格模式:命令只使用指定的源。-- `--release <tag>` 跳过最新版本探测,但仍遵循所选的源策略。+- `auto`(默认)与 `github` 都通过这个仓库的 GitHub Release 解析最新版本。+- `--release <tag>` 跳过最新版本探测,但来源不变。- 显式设置的 HTTPS `PENGUIN_DOWNLOAD_BASE_URL` 拥有最高优先级,安装器和安装包下载都遵循它;`PENGUIN_DOWNLOAD_FALLBACK_BASE_URL` 可选,为安装包提供回退地址。另请参阅:[配置参考](/configuration)、[模型与供应商](/models)。diff --git a/packages/docs/content/company-mode.en.md b/packages/docs/content/company-mode.en.mdindex b8ebac4e..8adf8a81 100644--- a/packages/docs/content/company-mode.en.md+++ b/packages/docs/content/company-mode.en.md@@ -250,7 +250,7 @@ Know the limits before you rely on a mirror organization:## Commands-Inside a desk or ticket session, the `penguin org` commands already know the organization, Project, agent and Session from the environment (`PENGUIN_ORG_ID` joins the other control variables). From a shell, pass `--org-id`. The essentials are below; see [the CLI reference](/cli#penguin-org) for every subcommand.+Inside a desk or ticket session, the `penguin org` commands already know the organization, Project, agent and Session from the environment (`ADELIE_ORG_ID` joins the other control variables). From a shell, pass `--org-id`. The essentials are below; see [the CLI reference](/cli#penguin-org) for every subcommand.```textpenguin org show # employees, board counts, spend vs budgetdiff --git a/packages/docs/content/company-mode.zh.md b/packages/docs/content/company-mode.zh.mdindex b7fcf993..e0ec7d4c 100644--- a/packages/docs/content/company-mode.zh.md+++ b/packages/docs/content/company-mode.zh.md@@ -250,7 +250,7 @@ id 使用小写 snake_case,长 2 到 64 个字符,以字母开头。按惯## 命令-在工位会话或工单会话里,`penguin org` 命令已经从环境中知道组织、Project、Agent 和当前 Session(`PENGUIN_ORG_ID` 与其他控制变量一起注入);在 shell 里则要传 `--org-id`。下面是常用的几条,全部子命令见 [CLI 参考](/cli#penguin-org)。+在工位会话或工单会话里,`penguin org` 命令已经从环境中知道组织、Project、Agent 和当前 Session(`ADELIE_ORG_ID` 与其他控制变量一起注入);在 shell 里则要传 `--org-id`。下面是常用的几条,全部子命令见 [CLI 参考](/cli#penguin-org)。```textpenguin org show # employees, board counts, spend vs budgetdiff --git a/packages/docs/content/concepts.en.md b/packages/docs/content/concepts.en.mdindex f7431041..890ffd97 100644--- a/packages/docs/content/concepts.en.md+++ b/packages/docs/content/concepts.en.md@@ -1,9 +1,9 @@---title: Key concepts-description: The terms PenguinHarness uses, grouped by topic, each with a link to the page that covers it in depth.+description: The terms Adelie uses, grouped by topic, each with a link to the page that covers it in depth.----PenguinHarness uses a small set of terms with specific meanings. This page defines them, grouped by topic, and each entry links to the page that covers the term in depth.+Adelie uses a small set of terms with specific meanings. This page defines them, grouped by topic, and each entry links to the page that covers the term in depth.- [How work is organized](#how-work-is-organized): Project, agent, Agent State, Workspace, data root- [How work runs](#how-work-runs): Session, Task, Trace, OmniMessage, approval mode, subagent@@ -34,13 +34,13 @@ See [Configuration Reference](/configuration).### Workspace-A Workspace is the directory an agent works in during a Session: the files it reads, creates and changes. You choose the Workspace when you start a Session. If you don't, PenguinHarness creates a temporary Workspace inside the agent's directory.+A Workspace is the directory an agent works in during a Session: the files it reads, creates and changes. You choose the Workspace when you start a Session. If you don't, Adelie creates a temporary Workspace inside the agent's directory.See [Sessions & Traces](/sessions-and-traces#run-model).### Data root-The data root is the directory where PenguinHarness keeps Projects, agents, model settings and Traces. It is `~/.penguin/data` by default (`%USERPROFILE%\.penguin\data` on Windows), and the desktop app, the CLI and the SDK on one machine all use it. Set `PENGUIN_HOME` to use another directory.+The data root is the directory where Adelie keeps Projects, agents, model settings and Traces. It is `~/.adelie/data` by default (`%USERPROFILE%\.adelie\data` on Windows), and the desktop app, the CLI and the SDK on one machine all use it. Set `ADELIE_HOME` to use another directory.See [Quickstart](/quickstart).@@ -60,13 +60,13 @@ See [The Agent Loop](/agent-loop).### Trace-A Trace is the record of a Session: every message, tool call, approval decision and Token usage, appended in order to JSON Lines files. PenguinHarness restores a Session from its Trace, and the usage and cost figures come from the same records.+A Trace is the record of a Session: every message, tool call, approval decision and Token usage, appended in order to JSON Lines files. Adelie restores a Session from its Trace, and the usage and cost figures come from the same records.See [Sessions & Traces](/sessions-and-traces).### OmniMessage-OmniMessage is the single message format PenguinHarness uses everywhere: the SDK streams it, the Trace stores it, and the engine works with it internally. Marketing materials also call it Penguin Message; the documentation uses OmniMessage.+OmniMessage is the single message format Adelie uses everywhere: the SDK streams it, the Trace stores it, and the engine works with it internally. Marketing materials also call it Adelie Message; the documentation uses OmniMessage.See [The OmniMessage Protocol](/omni-message).@@ -104,7 +104,7 @@ See [Skills & Plugins](/skills).### Hook package-A hook package is a set of scripts that PenguinHarness runs at fixed points of the agent loop: when a prompt is submitted, before each tool call is approved, and when a Task ends. A hook can, for example, deny a tool call or start another Task to keep the agent working.+A hook package is a set of scripts that Adelie runs at fixed points of the agent loop: when a prompt is submitted, before each tool call is approved, and when a Task ends. A hook can, for example, deny a tool call or start another Task to keep the agent working.See [Skills & Plugins](/skills#hook-packages).@@ -174,13 +174,13 @@ See [Self-Improvement](/self-improvement#snapshots-and-versions).### Provider-A provider is a named group of models in the Project's model table, such as `deepseek`, `anthropic` or the `tokendance` gateway. PenguinHarness includes built-in groups, and you can add your own.+A provider is a named group of models in the Project's model table, such as `deepseek`, `anthropic` or the `tokendance` gateway. Adelie includes built-in groups, and you can add your own.See [Models & Providers](/models).### Model-A model is always identified by the pair `(provider, model_id)`: its provider group and its id at that provider. PenguinHarness never guesses the provider from the id. Each Project has a default model, and you pick the model when you start a Session.+A model is always identified by the pair `(provider, model_id)`: its provider group and its id at that provider. Adelie never guesses the provider from the id. Each Project has a default model, and you pick the model when you start a Session.See [Models & Providers](/models).diff --git a/packages/docs/content/concepts.zh.md b/packages/docs/content/concepts.zh.mdindex 0f6ebd03..ea609fd4 100644--- a/packages/docs/content/concepts.zh.md+++ b/packages/docs/content/concepts.zh.md@@ -1,9 +1,9 @@---title: 核心概念-description: PenguinHarness 使用的术语,按主题分组,每条都附有深入讲解它的页面链接。+description: Adelie 使用的术语,按主题分组,每条都附有深入讲解它的页面链接。----PenguinHarness 用到一组含义明确的术语。本页按主题分组给出定义,每条定义都链接到详细讲解它的页面。+Adelie 用到一组含义明确的术语。本页按主题分组给出定义,每条定义都链接到详细讲解它的页面。- [工作如何组织](#工作如何组织):Project、Agent、Agent State、Workspace、数据目录- [工作如何运行](#工作如何运行):Session、Task、Trace、OmniMessage、审批模式、子 Agent@@ -34,13 +34,13 @@ Agent State 是 Agent 的持久化目录 `agent_state/`,存放 Agent 的配置### Workspace-Workspace 是 Agent 在一个 Session 中工作的目录,它读取、创建和修改的文件都在这里。启动 Session 时由你选择 Workspace;如果不选,PenguinHarness 会在 Agent 的目录下创建一个临时 Workspace。+Workspace 是 Agent 在一个 Session 中工作的目录,它读取、创建和修改的文件都在这里。启动 Session 时由你选择 Workspace;如果不选,Adelie 会在 Agent 的目录下创建一个临时 Workspace。见 [Session 与 Trace](/sessions-and-traces#运行模型)。### 数据目录-数据目录是 PenguinHarness 存放 Project、Agent、模型设置和 Trace 的地方,默认为 `~/.penguin/data`(Windows 为 `%USERPROFILE%\.penguin\data`)。同一台机器上的桌面应用、CLI 和 SDK 都使用它。要改用其他目录,设置 `PENGUIN_HOME` 即可。+数据目录是 Adelie 存放 Project、Agent、模型设置和 Trace 的地方,默认为 `~/.adelie/data`(Windows 为 `%USERPROFILE%\.adelie\data`)。同一台机器上的桌面应用、CLI 和 SDK 都使用它。要改用其他目录,设置 `ADELIE_HOME` 即可。见[快速开始](/quickstart)。@@ -60,13 +60,13 @@ Task 是一条 Prompt 发起的工作。Agent 会调用模型一次或多次(### Trace-Trace 是一个 Session 的记录:每条消息、每次工具调用、每个审批决定和 Token 用量,都按顺序追加写入 JSON Lines 文件。PenguinHarness 依据 Trace 恢复 Session,用量与成本的数据也来自这些记录。+Trace 是一个 Session 的记录:每条消息、每次工具调用、每个审批决定和 Token 用量,都按顺序追加写入 JSON Lines 文件。Adelie 依据 Trace 恢复 Session,用量与成本的数据也来自这些记录。见 [Session 与 Trace](/sessions-and-traces)。### OmniMessage-OmniMessage 是 PenguinHarness 各处通用的统一消息格式:SDK 用它流式输出,Trace 用它存储,引擎内部也用它运转。产品宣传中也叫 Penguin Message,文档一律使用 OmniMessage。+OmniMessage 是 Adelie 各处通用的统一消息格式:SDK 用它流式输出,Trace 用它存储,引擎内部也用它运转。产品宣传中也叫 Adelie Message,文档一律使用 OmniMessage。见 [OmniMessage 协议](/omni-message)。@@ -104,7 +104,7 @@ Skill 是一套可复用的指令:一个包含 `SKILL.md` 及其引用文件### 钩子包-钩子包是一组脚本,PenguinHarness 会在 Agent 运行循环的几个固定节点运行它们:提交 Prompt 时、每次工具调用审批之前,以及 Task 结束时。钩子可以拒绝一次工具调用,也可以再发起一个 Task,让 Agent 继续工作。+钩子包是一组脚本,Adelie 会在 Agent 运行循环的几个固定节点运行它们:提交 Prompt 时、每次工具调用审批之前,以及 Task 结束时。钩子可以拒绝一次工具调用,也可以再发起一个 Task,让 Agent 继续工作。见[技能与插件](/skills#钩子包)。@@ -174,13 +174,13 @@ Agent 的版本是 `system_config.yaml` 里的一个数字,每保留一次优### 供应商-供应商是 Project 模型表里的一个具名分组,例如 `deepseek`、`anthropic` 或 `tokendance` 网关。PenguinHarness 内置了一批分组,你也可以添加自己的分组。+供应商是 Project 模型表里的一个具名分组,例如 `deepseek`、`anthropic` 或 `tokendance` 网关。Adelie 内置了一批分组,你也可以添加自己的分组。见[模型与 Provider](/models)。### 模型-模型始终以 `(provider, model_id)` 二元组标识:它所属的供应商分组,加上它在该供应商处的 id。PenguinHarness 绝不根据 id 猜测供应商。每个 Project 都有一个默认模型,启动 Session 时由你选择模型。+模型始终以 `(provider, model_id)` 二元组标识:它所属的供应商分组,加上它在该供应商处的 id。Adelie 绝不根据 id 猜测供应商。每个 Project 都有一个默认模型,启动 Session 时由你选择模型。见[模型与 Provider](/models)。diff --git a/packages/docs/content/configuration.en.md b/packages/docs/content/configuration.en.mdindex c4b60f1f..6d8a75df 100644--- a/packages/docs/content/configuration.en.md+++ b/packages/docs/content/configuration.en.md@@ -1,9 +1,9 @@---title: Configuration Reference-description: Every PenguinHarness setting with its default and constraints, from environment variables to the Project, agent, memory, Vault and schedule files.+description: Every Adelie setting with its default and constraints, from environment variables to the Project, agent, memory, Vault and schedule files.----PenguinHarness configuration has three layers: environment variables shape the deployment, the Project config manages models and credentials, and the agent config defines one agent's behavior. Each agent also keeps state files for its [Memory](#memory), [Vault](#vault) and [Schedules](#schedules).+Adelie configuration has three layers: environment variables shape the deployment, the Project config manages models and credentials, and the agent config defines one agent's behavior. Each agent also keeps state files for its [Memory](#memory), [Vault](#vault) and [Schedules](#schedules).## Environment variables@@ -11,45 +11,46 @@ The CLI and the server load a `.env` file from the working directory on startup.| Variable | Description | Default || --- | --- | --- |-| `PENGUIN_HOME` | Data root directory | `~/.penguin/data` |+| `ADELIE_HOME` | Data root directory | `~/.adelie/data` || `PORT` | Web service listen port | `7364` || `HOST` | Web service listen address | `127.0.0.1` |-| `PENGUIN_WEB_DB` | Server SQLite database path | `<root>/web.db` |-| `PENGUIN_WEB_DIST` | Front-end static assets directory | The server package's bundled `web-dist` (in a source checkout, `packages/web/dist`) |-| `PENGUIN_PREVIEW_ORIGIN` | Origin that serves Workspace HTML previews, e.g. `https://preview.example.com` | Unset: the loopback counterpart is derived per request |+| `ADELIE_WEB_DB` | Server SQLite database path | `<root>/web.db` |+| `ADELIE_WEB_DIST` | Front-end static assets directory | The server package's bundled `web-dist` (in a source checkout, `packages/web/dist`) |+| `ADELIE_PREVIEW_ORIGIN` | Origin that serves Workspace HTML previews, e.g. `https://preview.example.com` | Unset: the loopback counterpart is derived per request || `PENGUIN_GO_ORIGIN` | Trusted origin the server-side Penguin Go key authorization calls | `https://token.penguin.ooo` || `MODELSCOPE_BRIDGE_URL` | Address of the authorization bridge the server-side ModelScope key authorization calls | `https://go.penguin.ooo/modelscope` |-| `PENGUIN_TRUST_PROXY` | `1` trusts the `x-forwarded-proto` header | Unset: the header is ignored |-| `PENGUIN_SEED_ADMIN_PASSWORD` | Fixed initial password for the seeded built-in admin (automated tests / e2e) | Unset: a random password is generated |-| `PENGUIN_LANG` | CLI language (`en` / `zh`), set with `penguin config lang` | `en` |-| `PENGUIN_UPDATE_CHECK` | `off` disables the Web App's new-release check | Enabled |+| `ADELIE_TRUST_PROXY` | `1` trusts the `x-forwarded-proto` header | Unset: the header is ignored |+| `ADELIE_SEED_ADMIN_PASSWORD` | Fixed initial password for the seeded built-in admin (automated tests / e2e) | Unset: a random password is generated |+| `ADELIE_LANG` | CLI language (`en` / `zh`), set with `penguin config lang` | `en` |+| `ADELIE_UPDATE_CHECK` | `off` disables the Web App's new-release check | Enabled || `PENGUIN_NO_LOGIN_SHELL_ENV` | Any non-empty value stops the desktop app from importing the login shell's environment on macOS/Linux GUI launches | Unset: the import runs |-| `PENGUIN_SHELL` | The shell that runs agent commands (an executable name or path) | Unset: picked automatically, see [Tools & Approval](/tools#command-sessions) |-| `PENGUIN_CLI_ENTRY` | The CLI entry script this installation offers the agents it runs (see [PATH launcher](#path-launcher)) | Set by `penguin server` / `penguin web` and by the desktop app |+| `ADELIE_SHELL` | The shell that runs agent commands (an executable name or path) | Unset: picked automatically, see [Tools & Approval](/tools#command-sessions) |+| `ADELIE_CLI_ENTRY` | The CLI entry script this installation offers the agents it runs (see [PATH launcher](#path-launcher)) | Set by `penguin server` / `penguin web` and by the desktop app |Notes:-- `PENGUIN_TRUST_PROXY`: set it behind a reverse proxy that terminates TLS and sets or strips the header itself. Session cookies are then marked `Secure`, and the hot-update network gate sees HTTPS.-- `PENGUIN_SEED_ADMIN_PASSWORD`: without it, the seed generates a random password that is hashed and discarded unseen, and you claim the account through the first-login link.+- **Pre-rename spellings:** the data root and the deployment wiring (`ADELIE_HOME`, `ADELIE_PROFILE`, `ADELIE_WEB_DIST`, `ADELIE_WEB_DB`, `ADELIE_CLI_ENTRY`, `ADELIE_PORT_FILE`, `ADELIE_DESKTOP_TOKEN`, `ADELIE_BUNDLED_SHELL`) are also read in their pre-rename `PENGUIN_*` spelling, the new name winning when both are set (`packages/core/src/state/boundary-env.ts`). The other variables above are Adelie's own and carry no alias: their pre-rename spelling is no longer read.+- `ADELIE_TRUST_PROXY`: set it behind a reverse proxy that terminates TLS and sets or strips the header itself. Session cookies are then marked `Secure`, and the hot-update network gate sees HTTPS.+- `ADELIE_SEED_ADMIN_PASSWORD`: without it, the seed generates a random password that is hashed and discarded unseen, and you claim the account through the first-login link.- `PENGUIN_GO_ORIGIN`: server configuration, not an endpoint the browser can name. It must be a bare HTTPS origin; plain HTTP is accepted only for `localhost`, `127.0.0.1` and `[::1]`, for integration environments. A path, credentials, a query string or a fragment is rejected at startup. See [Connect an account](/models#connect-an-account).- `MODELSCOPE_BRIDGE_URL`: server configuration like `PENGUIN_GO_ORIGIN`, not an endpoint the browser can name. It must be an HTTPS address with no credentials, query string or fragment. Unlike `PENGUIN_GO_ORIGIN`, a path prefix **is** allowed, because the production bridge lives under `https://go.penguin.ooo/modelscope`. See [Connect an account](/models#connect-an-account).-- `PENGUIN_UPDATE_CHECK`: `off` turns off the automatic release check, nothing else. Model requests, an enabled remote-control connection, provider key authorization and the proxy test still reach the network.+- `ADELIE_UPDATE_CHECK`: `off` turns off the automatic release check, nothing else. Model requests, an enabled remote-control connection, provider key authorization and the proxy test still reach the network.- `PENGUIN_NO_LOGIN_SHELL_ENV`: without it, the import fills only variables the launch left unset. See [Desktop quickstart](/quickstart-desktop).-- `PENGUIN_CLI_ENTRY`: when the server was started from a source checkout, it falls back to that checkout's `packages/cli/dist/penguin.js`.+- `ADELIE_CLI_ENTRY`: when the server was started from a source checkout, it falls back to that checkout's `packages/cli/dist/penguin.js`.### Environment of agent-run commandsCommands an agent runs with `exec_command` inherit the host environment, with these changes:-- **Removed:** `PORT`, `HOST`, `FORCE_COLOR`, `CLICOLOR_FORCE` and every `PENGUIN_*` variable. They configure PenguinHarness itself, not the command. Without this, a dev server started by `exec_command` would read `PORT` and try to bind the port meant for PenguinHarness instead of choosing its own.+- **Removed:** `PORT`, `HOST`, `FORCE_COLOR`, `CLICOLOR_FORCE` and every `PENGUIN_*` or `ADELIE_*` variable. They configure Adelie itself, not the command. Without this, a dev server started by `exec_command` would read `PORT` and try to bind the port meant for Adelie instead of choosing its own.- **Proxy:** in Sessions the server runs, the **Agent environment uses the proxy** switch in [Settings](/settings#proxy-options) decides the proxy variables. Off removes `HTTP_PROXY`, `HTTPS_PROXY` and `ALL_PROXY`; on injects the configured proxy address, or passes the host's variables through when no address is set.-- **Vault:** the agent's [Vault](#vault) is applied on top, so setting `PORT` or a `PENGUIN_*` variable there does reach commands.-- **Control variables:** a server-driven Session then injects `PENGUIN_API_URL`, `PENGUIN_API_TOKEN`, `PENGUIN_PROJECT_ID`, `PENGUIN_AGENT_ID` and `PENGUIN_SESSION_ID` (plus `PENGUIN_ORG_ID` in company mode), so the agent's own `penguin` calls reach the server that runs it. These override Vault entries of the same name. See [CLI Reference](/cli).+- **Vault:** the agent's [Vault](#vault) is applied on top, so setting `PORT` or an `ADELIE_*` variable there does reach commands.+- **Control variables:** a server-driven Session then injects `ADELIE_API_URL`, `ADELIE_API_TOKEN`, `ADELIE_PROJECT_ID`, `ADELIE_AGENT_ID` and `ADELIE_SESSION_ID` (plus `ADELIE_ORG_ID` in company mode), so the agent's own `penguin` calls reach the server that runs it. These override Vault entries of the same name. See [CLI Reference](/cli).- **Forced:** `GIT_EDITOR`, `GIT_TERMINAL_PROMPT`, `TERM`, `NO_COLOR`, `PAGER` and `GIT_PAGER` always get fixed values, so a command cannot hang waiting on an editor, a credential prompt or a pager. Nothing overrides them, the Vault included.### PATH launcher-This installation's own `penguin` is first on the PATH of every command an agent runs. At startup the server writes a launcher script at `<root>/bin/penguin`, which runs the CLI entry from `PENGUIN_CLI_ENTRY` on the server's own Node, and puts that directory at the front of PATH for each command. So `penguin` inside a command is the harness the agent is running in, whatever version is installed globally on the machine.+This installation's own `penguin` is first on the PATH of every command an agent runs. At startup the server writes a launcher script at `<root>/bin/penguin`, which runs the CLI entry from `ADELIE_CLI_ENTRY` on the server's own Node, and puts that directory at the front of PATH for each command. So `penguin` inside a command is the harness the agent is running in, whatever version is installed globally on the machine.The directory is prepended inside the shell as well as in the environment, because commands run through a login shell whose profile often rewrites PATH afterwards. This also puts it ahead of a `PATH` set in the [Vault](#vault), which otherwise replaces the inherited value outright.@@ -57,7 +58,7 @@ The launcher is rewritten at every start, so the next start picks up a moved ins### Workspace preview origin-`PENGUIN_PREVIEW_ORIGIN` must differ from the app's origin by **hostname**, not just by port: cookies ignore ports, so a second port would still share the session cookie.+`ADELIE_PREVIEW_ORIGIN` must differ from the app's origin by **hostname**, not just by port: cookies ignore ports, so a second port would still share the session cookie.- **Local use:** leave it unset. The app is canonicalized onto `localhost` and previews are served from `127.0.0.1`, which needs no configuration and no DNS.- **LAN address or real domain:** set it. Otherwise previews fall back to a same-origin sandbox where `localStorage`, cookies and third-party embeds do not work. On a real domain, keep the session cookie host-only (no `Domain=`), or a sibling subdomain shares it.@@ -66,7 +67,7 @@ An unparseable value stops the server at startup instead of falling back silentl### Provider credential variables-When a model entry has no inline `api_key`, it falls back to the provider's environment variable **only when its requests go to that provider's official endpoint**: the entry has no `base_url`, or its `base_url` is the vendor's own endpoint. A `*_BASE_URL` value is used only when the entry does not inline `base_url`; an entry with its own `base_url` is never covered by the environment, even when `OPENAI_BASE_URL` names the same server. Every other entry — the gateway groups' preset endpoints, custom, vLLM and user-created groups with their own endpoints — needs its own `api_key`, and PenguinHarness refuses to build a client for it otherwise; see [Set API keys](/models#set-api-keys).+When a model entry has no inline `api_key`, it falls back to the provider's environment variable **only when its requests go to that provider's official endpoint**: the entry has no `base_url`, or its `base_url` is the vendor's own endpoint. A `*_BASE_URL` value is used only when the entry does not inline `base_url`; an entry with its own `base_url` is never covered by the environment, even when `OPENAI_BASE_URL` names the same server. Every other entry — the gateway groups' preset endpoints, custom, vLLM and user-created groups with their own endpoints — needs its own `api_key`, and Adelie refuses to build a client for it otherwise; see [Set API keys](/models#set-api-keys).| Provider | API key | Base URL || --- | --- | --- |@@ -382,7 +383,7 @@ For developers:| `{{PLATFORM}}` | Runtime platform || `{{OS_VERSION}}` | Operating system version || `{{DATE}}` | Current date |-| `{{PROJECT_DIR}}` | App Data Dir: the PenguinHarness app data root (the Project directory) |+| `{{PROJECT_DIR}}` | App Data Dir: the Adelie app data root (the Project directory) || `{{AGENT_ID}}` | Agent id || `{{CWD}}` | Workspace path || `{{PROVIDER}}` | Model provider group |@@ -391,7 +392,7 @@ For developers:**Section placeholders.** The Vault, Skills, Memory and Schedules sections share one pattern: a placeholder, a switch and an editable prompt. The template holds only the `{{VAULT}}` / `{{SKILLS}}` / `{{MEMORY}}` / `{{SCHEDULES}}` placeholder, the section text lives in the matching `*.prompt` key (edited on its settings tab), and turning `*.enabled` off empties the whole block. A template without one of these placeholders injects no such section; the matching settings tab offers to insert the placeholder explicitly, or to migrate a legacy template. The four section placeholders are expanded last, in a single pass at assembly time. Expanded text is never rescanned, so placeholder-looking text inside a memory index or a section prompt stays literal.-**App Data Dir.** `{{PROJECT_DIR}}` is shown to the model as the **App Data Dir**: PenguinHarness's application data root, which holds every agent's data files (`agents/<agent_id>/…`) and the Project-level data. It is deliberately not described as a project or task directory, so the model does not mistake it for the task's working directory (`CWD`).+**App Data Dir.** `{{PROJECT_DIR}}` is shown to the model as the **App Data Dir**: Adelie's application data root, which holds every agent's data files (`agents/<agent_id>/…`) and the Project-level data. It is deliberately not described as a project or task directory, so the model does not mistake it for the task's working directory (`CWD`).**Windows paths.** On Windows, `{{PROJECT_DIR}}` and `{{CWD}}` are injected with forward slashes, like every other path core composes for the model (attachment lines, the goal-file line, truncated-output recovery paths). The model copies these spellings into JSON tool arguments and shell commands. Node's fs APIs and the package's (Git) Bash tool shell accept forward slashes, and they avoid JSON backslash-escaping mistakes.@@ -432,7 +433,7 @@ A workspace memory key is `<safe-basename>-<8 hex of the real path's sha256>`.- `user` is a reserved directory name. It is safe because every generated key has the form `<base>-<8 hex>` and so always contains a hyphen.- Identity is the directory itself and has nothing to do with Git. Two symlinks to one directory resolve to one key, while moving or renaming a directory makes it a new Workspace; the old Memory stays on disk under the old key.-- A temporary Workspace, one PenguinHarness allocated under `agents/<agent_id>/workspaces/`, gets no Workspace scope at all, including when a subagent inherits it. A temporary Workspace is allocated per Session, so no later Session would ever run there to read it back. Such a Session still gets the user scope, which is where anything it learns belongs anyway.+- A temporary Workspace, one Adelie allocated under `agents/<agent_id>/workspaces/`, gets no Workspace scope at all, including when a subagent inherits it. A temporary Workspace is allocated per Session, so no later Session would ever run there to read it back. Such a Session still gets the user scope, which is where anything it learns belongs anyway.### Topic filesdiff --git a/packages/docs/content/configuration.zh.md b/packages/docs/content/configuration.zh.mdindex ee360a24..ee925c28 100644--- a/packages/docs/content/configuration.zh.md+++ b/packages/docs/content/configuration.zh.md@@ -1,9 +1,9 @@---title: 配置参考-description: PenguinHarness 的每一项设置及其默认值与限制,从环境变量到 Project、Agent、记忆、密钥保险柜和定时任务文件。+description: Adelie 的每一项设置及其默认值与限制,从环境变量到 Project、Agent、记忆、密钥保险柜和定时任务文件。----PenguinHarness 的配置分三层:环境变量决定部署形态,Project 配置管理模型和凭证,Agent 配置定义单个 Agent 的行为。每个 Agent 还有自己的[记忆](#记忆)、[Vault](#vault) 和[定时任务](#定时任务)状态文件。+Adelie 的配置分三层:环境变量决定部署形态,Project 配置管理模型和凭证,Agent 配置定义单个 Agent 的行为。每个 Agent 还有自己的[记忆](#记忆)、[Vault](#vault) 和[定时任务](#定时任务)状态文件。## 环境变量@@ -11,45 +11,46 @@ CLI 和服务器启动时会从工作目录加载 `.env` 文件。| 变量 | 说明 | 默认值 || --- | --- | --- |-| `PENGUIN_HOME` | 数据根目录 | `~/.penguin/data` |+| `ADELIE_HOME` | 数据根目录 | `~/.adelie/data` || `PORT` | Web 服务监听端口 | `7364` || `HOST` | Web 服务监听地址 | `127.0.0.1` |-| `PENGUIN_WEB_DB` | 服务器 SQLite 数据库路径 | `<root>/web.db` |-| `PENGUIN_WEB_DIST` | 前端静态资源目录 | 服务器包自带的 `web-dist`(源码检出中为 `packages/web/dist`) |-| `PENGUIN_PREVIEW_ORIGIN` | 提供 Workspace HTML 预览的源,例如 `https://preview.example.com` | 未设置:每次请求推导对应的回环地址 |+| `ADELIE_WEB_DB` | 服务器 SQLite 数据库路径 | `<root>/web.db` |+| `ADELIE_WEB_DIST` | 前端静态资源目录 | 服务器包自带的 `web-dist`(源码检出中为 `packages/web/dist`) |+| `ADELIE_PREVIEW_ORIGIN` | 提供 Workspace HTML 预览的源,例如 `https://preview.example.com` | 未设置:每次请求推导对应的回环地址 || `PENGUIN_GO_ORIGIN` | 服务端发起 Penguin Go Key 授权时调用的可信源 | `https://token.penguin.ooo` || `MODELSCOPE_BRIDGE_URL` | 服务端发起 ModelScope Key 授权时调用的授权中转层地址 | `https://go.penguin.ooo/modelscope` |-| `PENGUIN_TRUST_PROXY` | 设为 `1` 时信任 `x-forwarded-proto` 请求头 | 未设置:忽略请求头 |-| `PENGUIN_SEED_ADMIN_PASSWORD` | 预置内置管理员的固定初始密码(自动化测试 / e2e) | 未设置:生成随机密码 |-| `PENGUIN_LANG` | CLI 语言(`en` / `zh`),用 `penguin config lang` 设置 | `en` |-| `PENGUIN_UPDATE_CHECK` | 设为 `off` 时关闭 Web App 的新版本检查 | 启用 |+| `ADELIE_TRUST_PROXY` | 设为 `1` 时信任 `x-forwarded-proto` 请求头 | 未设置:忽略请求头 |+| `ADELIE_SEED_ADMIN_PASSWORD` | 预置内置管理员的固定初始密码(自动化测试 / e2e) | 未设置:生成随机密码 |+| `ADELIE_LANG` | CLI 语言(`en` / `zh`),用 `penguin config lang` 设置 | `en` |+| `ADELIE_UPDATE_CHECK` | 设为 `off` 时关闭 Web App 的新版本检查 | 启用 || `PENGUIN_NO_LOGIN_SHELL_ENV` | 设为任意非空值后,桌面应用在 macOS/Linux 上从图形界面启动时不再导入登录 shell 的环境变量 | 未设置:照常导入 |-| `PENGUIN_SHELL` | 运行 Agent 命令的 shell(可执行文件名或路径) | 未设置:自动选择,见[工具与审批](/tools#命令会话) |-| `PENGUIN_CLI_ENTRY` | 本安装提供给所运行 Agent 的 CLI 入口脚本(见 [PATH 启动脚本](#path-启动脚本)) | 由 `penguin server` / `penguin web` 和桌面应用设置 |+| `ADELIE_SHELL` | 运行 Agent 命令的 shell(可执行文件名或路径) | 未设置:自动选择,见[工具与审批](/tools#命令会话) |+| `ADELIE_CLI_ENTRY` | 本安装提供给所运行 Agent 的 CLI 入口脚本(见 [PATH 启动脚本](#path-启动脚本)) | 由 `penguin server` / `penguin web` 和桌面应用设置 |说明:-- `PENGUIN_TRUST_PROXY`:只在反向代理终结 TLS、并由代理自己设置或清除这个请求头时启用。启用后,会话 Cookie 会带上 `Secure` 标记,热更新的网络检查也能识别出 HTTPS。-- `PENGUIN_SEED_ADMIN_PASSWORD`:不设置时,预置管理员时会生成一个随机密码,哈希后立即丢弃,没有人见过;账号通过首次登录链接认领。+- **旧拼写:** 数据根与部署接线(`ADELIE_HOME`、`ADELIE_PROFILE`、`ADELIE_WEB_DIST`、`ADELIE_WEB_DB`、`ADELIE_CLI_ENTRY`、`ADELIE_PORT_FILE`、`ADELIE_DESKTOP_TOKEN`、`ADELIE_BUNDLED_SHELL`)同时仍按改名前 `PENGUIN_*` 的拼写读取,两个都设置时新名优先(`packages/core/src/state/boundary-env.ts`)。上表其余变量是 Adelie 自己的,没有兼容别名:旧拼写不再被读取。+- `ADELIE_TRUST_PROXY`:只在反向代理终结 TLS、并由代理自己设置或清除这个请求头时启用。启用后,会话 Cookie 会带上 `Secure` 标记,热更新的网络检查也能识别出 HTTPS。+- `ADELIE_SEED_ADMIN_PASSWORD`:不设置时,预置管理员时会生成一个随机密码,哈希后立即丢弃,没有人见过;账号通过首次登录链接认领。- `PENGUIN_GO_ORIGIN`:它是服务端配置,不接受浏览器指定的端点。取值必须是不带路径的 HTTPS 源;只有 `localhost`、`127.0.0.1` 和 `[::1]` 这类集成环境可以用明文 HTTP。带路径、凭据、查询参数或 fragment 的取值会在启动时被拒绝。见[连接账户](/models#连接账户)。- `MODELSCOPE_BRIDGE_URL`:与 `PENGUIN_GO_ORIGIN` 一样是服务端配置,不接受浏览器指定的端点。它必须是不带凭据、查询参数或 fragment 的 HTTPS 地址。不同之处是**它允许带路径前缀**,因为生产环境的中转层就挂在 `https://go.penguin.ooo/modelscope` 下。见[连接账户](/models#连接账户)。-- `PENGUIN_UPDATE_CHECK`:设为 `off` 只关闭自动的版本检查,不影响其他对外请求:模型请求、已启用的远程控制连接、Key 授权和代理测试照常联网。+- `ADELIE_UPDATE_CHECK`:设为 `off` 只关闭自动的版本检查,不影响其他对外请求:模型请求、已启用的远程控制连接、Key 授权和代理测试照常联网。- `PENGUIN_NO_LOGIN_SHELL_ENV`:不设置时,导入只填补启动过程没有设置的变量。见[桌面应用快速开始](/quickstart-desktop)。-- `PENGUIN_CLI_ENTRY`:服务器从源码检出启动时,会回退到检出目录中的 `packages/cli/dist/penguin.js`。+- `ADELIE_CLI_ENTRY`:服务器从源码检出启动时,会回退到检出目录中的 `packages/cli/dist/penguin.js`。### Agent 所执行命令的环境Agent 用 `exec_command` 运行的命令继承宿主环境,但有以下改动:-- **移除:** `PORT`、`HOST`、`FORCE_COLOR`、`CLICOLOR_FORCE` 以及所有 `PENGUIN_*` 变量。这些变量配置的是 PenguinHarness 本身,不是命令。如果不移除,`exec_command` 启动的开发服务器会读到 `PORT`,试图绑定本应留给 PenguinHarness 的端口,而不是自己另选。+- **移除:** `PORT`、`HOST`、`FORCE_COLOR`、`CLICOLOR_FORCE` 以及所有 `PENGUIN_*` 与 `ADELIE_*` 变量。这些变量配置的是 Adelie 本身,不是命令。如果不移除,`exec_command` 启动的开发服务器会读到 `PORT`,试图绑定本应留给 Adelie 的端口,而不是自己另选。- **代理:** 在服务器运行的 Session 中,由[设置](/settings#代理选项)里的 **Agent 环境使用代理** 开关决定代理变量。关闭时移除 `HTTP_PROXY`、`HTTPS_PROXY` 和 `ALL_PROXY`;开启时注入已配置的代理地址,没有配置地址时透传宿主的变量。-- **密钥保险柜:** 之后再叠加 Agent 的[密钥保险柜](#vault),所以在保险柜里设置的 `PORT` 或 `PENGUIN_*` 变量确实能传给命令。-- **控制变量:** 由服务器驱动的 Session 随后注入 `PENGUIN_API_URL`、`PENGUIN_API_TOKEN`、`PENGUIN_PROJECT_ID`、`PENGUIN_AGENT_ID` 和 `PENGUIN_SESSION_ID`(公司模式下还有 `PENGUIN_ORG_ID`),Agent 自己发起的 `penguin` 调用因此能到达运行它的服务器。这些变量会覆盖密钥保险柜里的同名条目。见 [CLI 参考](/cli)。+- **密钥保险柜:** 之后再叠加 Agent 的[密钥保险柜](#vault),所以在保险柜里设置的 `PORT` 或 `ADELIE_*` 变量确实能传给命令。+- **控制变量:** 由服务器驱动的 Session 随后注入 `ADELIE_API_URL`、`ADELIE_API_TOKEN`、`ADELIE_PROJECT_ID`、`ADELIE_AGENT_ID` 和 `ADELIE_SESSION_ID`(公司模式下还有 `ADELIE_ORG_ID`),Agent 自己发起的 `penguin` 调用因此能到达运行它的服务器。这些变量会覆盖密钥保险柜里的同名条目。见 [CLI 参考](/cli)。- **强制:** `GIT_EDITOR`、`GIT_TERMINAL_PROMPT`、`TERM`、`NO_COLOR`、`PAGER` 和 `GIT_PAGER` 始终取固定值,命令不会因为等待编辑器、凭证提示或分页器而卡住。任何来源都无法覆盖它们,密钥保险柜也不例外。### PATH 启动脚本-Agent 运行的每条命令,PATH 的第一位都是本安装自带的 `penguin`。服务器启动时会在 `<root>/bin/penguin` 写入一个启动脚本:脚本用服务器自己的 Node 运行 `PENGUIN_CLI_ENTRY` 指向的 CLI 入口,并把这个目录放到每条命令 PATH 的最前面。这样,命令里调用的 `penguin` 就是 Agent 正在运行的这套 harness,无论机器上全局装的是什么版本。+Agent 运行的每条命令,PATH 的第一位都是本安装自带的 `penguin`。服务器启动时会在 `<root>/bin/penguin` 写入一个启动脚本:脚本用服务器自己的 Node 运行 `ADELIE_CLI_ENTRY` 指向的 CLI 入口,并把这个目录放到每条命令 PATH 的最前面。这样,命令里调用的 `penguin` 就是 Agent 正在运行的这套 harness,无论机器上全局装的是什么版本。这个目录既前置到环境变量里,也前置到 shell 内部,因为命令通过登录 shell 运行,而登录 shell 的 profile 常常随后重写 PATH。这也让它排在[密钥保险柜](#vault)里设置的 `PATH` 之前,而保险柜里的 `PATH` 原本会整体替换继承来的值。@@ -57,7 +58,7 @@ Agent 运行的每条命令,PATH 的第一位都是本安装自带的 `penguin### Workspace 预览源-`PENGUIN_PREVIEW_ORIGIN` 与应用本身的源必须在**主机名**上不同,不能只是端口不同:Cookie 不区分端口,换个端口仍然共享同一个会话 Cookie。+`ADELIE_PREVIEW_ORIGIN` 与应用本身的源必须在**主机名**上不同,不能只是端口不同:Cookie 不区分端口,换个端口仍然共享同一个会话 Cookie。- **本地使用:** 保持不设置。应用会规范化到 `localhost`,预览由 `127.0.0.1` 提供,不需要配置,也不需要 DNS。- **局域网地址或正式域名:** 必须设置。否则预览会回退到同源沙箱,`localStorage`、Cookie 和第三方嵌入都无法工作。使用正式域名时,会话 Cookie 要保持 host-only(不设 `Domain=`),否则同级子域名会共享这个 Cookie。@@ -66,7 +67,7 @@ Agent 运行的每条命令,PATH 的第一位都是本安装自带的 `penguin### 供应商凭证变量-模型条目没有内联 `api_key` 时,**只在请求确实发往该供应商的官方端点时**回退到供应商的环境变量:条目没有 `base_url`,或 `base_url` 是厂商自己的端点。`*_BASE_URL` 的值只在条目没有内联 `base_url` 时才会使用;自带 `base_url` 的条目一律不由环境变量覆盖,即使 `OPENAI_BASE_URL` 指向同一台服务器也不例外。其余条目——网关分组预置的端点、带自己端点的 custom、vLLM 与自建分组——必须有自己的 `api_key`,否则 PenguinHarness 拒绝为它构建客户端;见[设置 API key](/models#设置-api-key)。+模型条目没有内联 `api_key` 时,**只在请求确实发往该供应商的官方端点时**回退到供应商的环境变量:条目没有 `base_url`,或 `base_url` 是厂商自己的端点。`*_BASE_URL` 的值只在条目没有内联 `base_url` 时才会使用;自带 `base_url` 的条目一律不由环境变量覆盖,即使 `OPENAI_BASE_URL` 指向同一台服务器也不例外。其余条目——网关分组预置的端点、带自己端点的 custom、vLLM 与自建分组——必须有自己的 `api_key`,否则 Adelie 拒绝为它构建客户端;见[设置 API key](/models#设置-api-key)。| 供应商 | API key | Base URL || --- | --- | --- |@@ -382,7 +383,7 @@ compaction:| `{{PLATFORM}}` | 运行平台 || `{{OS_VERSION}}` | 操作系统版本 || `{{DATE}}` | 当前日期 |-| `{{PROJECT_DIR}}` | App Data Dir:PenguinHarness 的应用数据根目录(即 Project 目录) |+| `{{PROJECT_DIR}}` | App Data Dir:Adelie 的应用数据根目录(即 Project 目录) || `{{AGENT_ID}}` | Agent id || `{{CWD}}` | Workspace 路径 || `{{PROVIDER}}` | 模型供应商分组 |@@ -391,7 +392,7 @@ compaction:**小节占位符。** 密钥保险柜、技能、记忆、定时任务四个小节共用一套模式:一个占位符、一个开关、一段可编辑的提示词。模板里只保留 `{{VAULT}}` / `{{SKILLS}}` / `{{MEMORY}}` / `{{SCHEDULES}}` 占位符,小节文本放在对应的 `*.prompt` 键里(在设置标签页编辑),关闭 `*.enabled` 则整块为空。模板缺少其中某个占位符时,对应小节不会注入;相应的设置标签页会提供显式插入占位符或迁移旧版模板的操作。四个小节占位符在组装时最后展开,一趟完成。展开后的文本不会再次扫描,因此记忆索引或小节提示词里看起来像占位符的文本会按字面保留。-**App Data Dir。** `{{PROJECT_DIR}}` 会以 **App Data Dir** 的名义展示给模型:这是 PenguinHarness 的应用数据根目录,存放所有 Agent 的数据文件(`agents/<agent_id>/…`)和 Project 级数据。刻意不把它描述成 Project 或 Task 目录,避免模型误以为它是任务的工作目录(`CWD`)。+**App Data Dir。** `{{PROJECT_DIR}}` 会以 **App Data Dir** 的名义展示给模型:这是 Adelie 的应用数据根目录,存放所有 Agent 的数据文件(`agents/<agent_id>/…`)和 Project 级数据。刻意不把它描述成 Project 或 Task 目录,避免模型误以为它是任务的工作目录(`CWD`)。**Windows 路径。** 在 Windows 上,`{{PROJECT_DIR}}` 和 `{{CWD}}` 一律以正斜杠注入;core 为模型拼出的其他路径也是如此(附件行、目标模式的 goal 文件行、截断输出的恢复路径)。模型会把这种写法照搬进 JSON 工具参数和 shell 命令。Node 的 fs API 和包内工具所用的 Git Bash 都接受正斜杠,还能避开 JSON 反斜杠转义错误。@@ -432,7 +433,7 @@ Workspace 记忆键的格式是 `<safe-basename>-<8 hex of the real path's sha25- `user` 是保留的目录名,这样做是安全的:生成的键都形如 `<base>-<8 hex>`,一定包含连字符。- 标识就是目录本身,与 Git 无关。指向同一目录的两个符号链接解析出同一个键;移动或重命名目录会让它变成一个新 Workspace,旧记忆仍以旧键留在磁盘上。-- 临时 Workspace 由 PenguinHarness 分配在 `agents/<agent_id>/workspaces/` 下,完全没有 Workspace 作用域,子 Agent 继承时也不例外。临时 Workspace 按 Session 分配,之后不会再有 Session 在那里运行并读回内容。这种 Session 仍然会拿到用户作用域,它学到的东西本来也该存在那里。+- 临时 Workspace 由 Adelie 分配在 `agents/<agent_id>/workspaces/` 下,完全没有 Workspace 作用域,子 Agent 继承时也不例外。临时 Workspace 按 Session 分配,之后不会再有 Session 在那里运行并读回内容。这种 Session 仍然会拿到用户作用域,它学到的东西本来也该存在那里。### 主题文件diff --git a/packages/docs/content/files.en.md b/packages/docs/content/files.en.mdindex 581912d9..519c3c22 100644--- a/packages/docs/content/files.en.md+++ b/packages/docs/content/files.en.md@@ -80,7 +80,7 @@ A Markdown file larger than 64KB opens in the source view. You can still switchAn HTML file can also be opened in a new browser tab: in the preview, select **Open in new tab**.> [!NOTE]-> When the app is reached through an address with no separate preview origin, the tab opens sandboxed, without localStorage, cookies or third-party embeds. To avoid the sandbox, reach the app over 127.0.0.1 or localhost, or set `PENGUIN_PREVIEW_ORIGIN`. On the new-chat page HTML always opens sandboxed: the separate preview origin serves a conversation's files only.+> When the app is reached through an address with no separate preview origin, the tab opens sandboxed, without localStorage, cookies or third-party embeds. To avoid the sandbox, reach the app over 127.0.0.1 or localhost, or set `ADELIE_PREVIEW_ORIGIN`. On the new-chat page HTML always opens sandboxed: the separate preview origin serves a conversation's files only.A text preview reads up to 1MB. A larger file is shown truncated, with the message "File too large; preview truncated, download for the full file", and cannot be edited here. **Download** is in the preview header.diff --git a/packages/docs/content/files.zh.md b/packages/docs/content/files.zh.mdindex 39073027..3ef9203a 100644--- a/packages/docs/content/files.zh.md+++ b/packages/docs/content/files.zh.md@@ -80,7 +80,7 @@ description: 浏览、预览、编辑和管理对话 Workspace 里的文件。HTML 文件还可以在浏览器新标签页中打开:在预览中选择**新页面打开**。> [!NOTE]-> 如果当前访问地址没有独立的预览源,新标签页会以沙箱模式打开,localStorage、Cookie 和第三方嵌入内容都无法使用。要避开沙箱,请通过 127.0.0.1 或 localhost 访问应用,或设置 `PENGUIN_PREVIEW_ORIGIN`。在新建对话页上 HTML 一律以沙箱模式打开:独立预览源只提供对话的文件。+> 如果当前访问地址没有独立的预览源,新标签页会以沙箱模式打开,localStorage、Cookie 和第三方嵌入内容都无法使用。要避开沙箱,请通过 127.0.0.1 或 localhost 访问应用,或设置 `ADELIE_PREVIEW_ORIGIN`。在新建对话页上 HTML 一律以沙箱模式打开:独立预览源只提供对话的文件。文本预览最多读取 1MB。更大的文件会截断显示,提示「内容过大,预览已截断,请下载查看完整文件」,并且不能在这里编辑。**下载**按钮在预览顶栏。diff --git a/packages/docs/content/introduction.en.md b/packages/docs/content/introduction.en.mdindex 92025605..bef3340b 100644--- a/packages/docs/content/introduction.en.md+++ b/packages/docs/content/introduction.en.md@@ -1,15 +1,15 @@---title: Introduction-description: What PenguinHarness is, what ships in the box, and where to start.+description: What Adelie is, what ships in the box, and where to start.----Welcome to the PenguinHarness documentation. PenguinHarness is an open-source agent harness for building, running, evaluating and improving AI agents, built as one TypeScript stack. It deploys fully locally, so everything it stores stays on your machine; it runs on as little as a single CPU, and one unified model gateway reaches 1000+ online and local models.+Welcome to the Adelie documentation. Adelie is an open-source agent harness for building, running, evaluating and improving AI agents, built as one TypeScript stack. It deploys fully locally, so everything it stores stays on your machine; it runs on as little as a single CPU, and one unified model gateway reaches 1000+ online and local models.## Get startedWork through these pages in order:-1. [Quickstart](/quickstart): install PenguinHarness with the desktop app, the CLI, Docker or the SDK, and run your first Task.+1. [Quickstart](/quickstart): install Adelie with the desktop app, the CLI, Docker or the SDK, and run your first Task.2. [Key concepts](/concepts): learn the terms these docs use, such as Project, Session, Task and Workspace.3. [Conversations](/chat): work with an agent in a conversation and follow what it does.4. [Agents](/agents): create agents and configure their prompts, Skills, memory and tools.@@ -17,7 +17,7 @@ Work through these pages in order:## What ships in the box-PenguinHarness is made of these components. They share one data root and one message protocol, so you can mix them freely.+Adelie is made of these components. They share one data root and one message protocol, so you can mix them freely.| Component | Package | Description || --- | --- | --- |@@ -29,13 +29,13 @@ PenguinHarness is made of these components. They share one data root and one mes## The three pillars-PenguinHarness is summed up in one line, **Efficient Self-Improving Harness for Everyone**, and organized around three concepts: the message protocol, the SDK and the skill library. Each concept carries one pillar:+Adelie is summed up in one line, **Efficient Self-Improving Harness for Everyone**, and organized around three concepts: the message protocol, the SDK and the skill library. Each concept carries one pillar:| Pillar | Meaning || --- | --- || **Simplest Is the Best** | A deliberately minimal toolset over clean low-level interfaces: fewer tool calls, fewer Tokens, and complex tasks done efficiently. |-| **Harness for Building Agents** | With the PenguinHarness SDK, an agent builds complete agent applications for you, autonomously and from scratch. |-| **Harness for Recursive Self-Improvement** | With PenguinHarness Skills, an agent evaluates and optimizes itself, improving recursively over time. |+| **Harness for Building Agents** | With the Adelie SDK, an agent builds complete agent applications for you, autonomously and from scratch. |+| **Harness for Recursive Self-Improvement** | With Adelie Skills, an agent evaluates and optimizes itself, improving recursively over time. |## Design tenets@@ -50,7 +50,7 @@ These principles run through every component, and the design pages keep coming b## A note on naming-The unified message protocol is called **OmniMessage** in technical writing, and marketing materials also call it Penguin Message. This documentation uses OmniMessage throughout.+The unified message protocol is called **OmniMessage** in technical writing, and marketing materials also call it Adelie Message. This documentation uses OmniMessage throughout.## Learn how it worksdiff --git a/packages/docs/content/introduction.zh.md b/packages/docs/content/introduction.zh.mdindex d05a06f2..719461c2 100644--- a/packages/docs/content/introduction.zh.md+++ b/packages/docs/content/introduction.zh.md@@ -1,15 +1,15 @@---title: 产品介绍-description: PenguinHarness 是什么,它由哪些部分组成,以及从哪里开始。+description: Adelie 是什么,它由哪些部分组成,以及从哪里开始。----欢迎阅读 PenguinHarness 文档。PenguinHarness 是一个开源的 Agent Harness,用来构建、运行、评估和持续改进 AI Agent,整体是一套 TypeScript 技术栈。它完全本地部署,存储的一切都留在你的机器上;最低一颗 CPU 即可运行,通过统一的模型网关可以接入 1000+ 在线与本地模型。+欢迎阅读 Adelie 文档。Adelie 是一个开源的 Agent Harness,用来构建、运行、评估和持续改进 AI Agent,整体是一套 TypeScript 技术栈。它完全本地部署,存储的一切都留在你的机器上;最低一颗 CPU 即可运行,通过统一的模型网关可以接入 1000+ 在线与本地模型。## 开始使用建议按顺序阅读下面这些页面:-1. [快速开始](/quickstart):用桌面应用、CLI、Docker 或 SDK 安装 PenguinHarness,跑通第一个 Task。+1. [快速开始](/quickstart):用桌面应用、CLI、Docker 或 SDK 安装 Adelie,跑通第一个 Task。2. [核心概念](/concepts):了解文档里用到的术语,例如 Project、Session、Task 和 Workspace。3. [对话](/chat):在对话中与 Agent 协作,随时看到它在做什么。4. [Agent](/agents):创建 Agent,配置它的提示词、Skill、记忆和工具。@@ -17,7 +17,7 @@ description: PenguinHarness 是什么,它由哪些部分组成,以及从哪## 产品组成-PenguinHarness 由下面这些组件构成。它们共用同一个数据目录和同一套消息协议,因此可以自由混用。+Adelie 由下面这些组件构成。它们共用同一个数据目录和同一套消息协议,因此可以自由混用。| 组件 | 包名 | 说明 || --- | --- | --- |@@ -29,13 +29,13 @@ PenguinHarness 由下面这些组件构成。它们共用同一个数据目录## 三大支柱-PenguinHarness 可以用一句话概括:**Efficient Self-Improving Harness for Everyone**。它围绕三个概念展开,即消息协议、SDK 和技能库,每个概念支撑一个支柱:+Adelie 可以用一句话概括:**Efficient Self-Improving Harness for Everyone**。它围绕三个概念展开,即消息协议、SDK 和技能库,每个概念支撑一个支柱:| 支柱 | 含义 || --- | --- || **Simplest Is the Best** | 在干净的底层接口之上刻意保持极简的工具集:更少的工具调用、更少的 Token,高效完成复杂任务。 |-| **Harness for Building Agents** | 借助 PenguinHarness SDK,由 Agent 从零开始为你自主构建完整的 Agent 应用。 |-| **Harness for Recursive Self-Improvement** | 借助 PenguinHarness Skills,Agent 评估并优化自己,随着时间递归进化。 |+| **Harness for Building Agents** | 借助 Adelie SDK,由 Agent 从零开始为你自主构建完整的 Agent 应用。 |+| **Harness for Recursive Self-Improvement** | 借助 Adelie Skills,Agent 评估并优化自己,随着时间递归进化。 |## 设计信条@@ -50,7 +50,7 @@ PenguinHarness 可以用一句话概括:**Efficient Self-Improving Harness for## 命名说明-统一消息协议在技术文档中称为 **OmniMessage**,产品宣传中也叫 Penguin Message。本文档一律使用 OmniMessage。+统一消息协议在技术文档中称为 **OmniMessage**,产品宣传中也叫 Adelie Message。本文档一律使用 OmniMessage。## 了解工作原理diff --git a/packages/docs/content/models.en.md b/packages/docs/content/models.en.mdindex 2ae023b4..76b897b4 100644--- a/packages/docs/content/models.en.md+++ b/packages/docs/content/models.en.md@@ -75,7 +75,7 @@ The group appears in the list once its first model is saved.2. In **API key**, enter the endpoint's key. The server's `OPENAI_*` / `ANTHROPIC_*` variables are not used for an endpoint that is not the vendor's own (see [Set API keys](#set-api-keys)), so a listing without a key is refused.3. In **Custom base URL**, enter the endpoint's base URL.4. Select **Detect** at the top-right of the field, or pick the protocol from the menu at the right edge of the field. See [Detect a custom model's protocol](#detect-a-custom-models-protocol).-5. Select **Import all models**. PenguinHarness asks the endpoint for its model list and saves every model into the new group, in the endpoint's order.+5. Select **Import all models**. Adelie asks the endpoint for its model list and saves every model into the new group, in the endpoint's order.Each imported model gets the base URL, the protocol, and the key you entered. Only the model id comes from the endpoint: prices, context window, and display name stay empty, and vision stays off until you detect it or turn it on. That is the same starting point as a model you add by hand.@@ -117,7 +117,7 @@ Which protocol a new model uses depends on its group:### Built-in models only-Every built-in group except **Custom** and **vLLM** carries the models in PenguinHarness's built-in catalog and nothing else. Their keys are managed per group, and which models they hold is the catalog's to decide.+Every built-in group except **Custom** and **vLLM** carries the models in Adelie's built-in catalog and nothing else. Their keys are managed per group, and which models they hold is the catalog's to decide.- These groups have no **Add model**, and **Model settings** does not offer them as a group to move a model into.- The server refuses a new model in one of these groups unless it is one of the group's built-in models: saving it fails with "This group carries its built-in models only". `penguin config model add` refuses it the same way. A built-in model you deleted can be added back, which is what **Sync presets** does.@@ -191,7 +191,7 @@ Detection never blocks a save. If you select **Confirm** while the protocol is s## Detect vision support-**Vision support** can stay off until you ask the model. Select **Detect** next to the switch: PenguinHarness sends the model one 1x1 PNG with a one-word prompt.+**Vision support** can stay off until you ask the model. Select **Detect** next to the switch: Adelie sends the model one 1x1 PNG with a one-word prompt.- If the model answers, the switch turns on: "This model accepts images; vision turned on".- If the model says it does not take images, the switch turns off. That is a real answer, not an error.@@ -220,7 +220,7 @@ Three built-in groups can get their key for you: TokenDance, Penguin Go and Mode2. Select **Open authorization page**. The provider's authorization page opens in a new tab.3. Authorize there. The dialog, which shows "Waiting for the authorization to finish in the other tab…", reports the result on its own.-TokenDance creates a **new** key on your account; it does not read a key you already have. The provider sends the browser back to PenguinHarness, which exchanges the one-time code and saves the key. If the page cannot redirect back, for example because the browser cannot reach the server at the address it was given, select **Page can't redirect back? Enter the code by hand**. The authorization page then shows a one-time code instead of redirecting.+TokenDance creates a **new** key on your account; it does not read a key you already have. The provider sends the browser back to Adelie, which exchanges the one-time code and saves the key. If the page cannot redirect back, for example because the browser cannot reach the server at the address it was given, select **Page can't redirect back? Enter the code by hand**. The authorization page then shows a one-time code instead of redirecting.1. Paste the code into **Authorization code**.2. Select **Submit code**.@@ -234,18 +234,18 @@ Penguin Go differs in four ways:ModelScope differs in three ways:-- Authorization does not go through ModelScope's own pages but through an **authorization bridge**. The bridge holds ModelScope's client secret, runs the OAuth exchange on PenguinHarness's behalf, and hands back an access token that calls api-inference directly. The bridge's address comes from the server-side `MODELSCOPE_BRIDGE_URL` environment variable; see [Environment variables](/configuration#environment-variables).+- Authorization does not go through ModelScope's own pages but through an **authorization bridge**. The bridge holds ModelScope's client secret, runs the OAuth exchange on Adelie's behalf, and hands back an access token that calls api-inference directly. The bridge's address comes from the server-side `MODELSCOPE_BRIDGE_URL` environment variable; see [Environment variables](/configuration#environment-variables).- The authorization page's address is the bridge's, opened as given, rather than assembled here the way Penguin Go's is. This group likewise has no manual-code mode.-- The access token **expires**; PenguinHarness stores the refresh credential on the server and silently renews before model requests. Select **Reconnect** only when the refresh credential is missing or no longer valid.+- The access token **expires**; Adelie stores the refresh credential on the server and silently renews before model requests. Select **Reconnect** only when the refresh credential is missing or no longer valid.Keep in mind:- Only the Project owner can connect. With TokenDance, only their own signed-in session can finish it, which in practice is the tab the dialog is open in. The redirect itself is received without a session, because the browser the provider sends back is not always the one you started in, but it only hands the code over: nothing is exchanged and no key is saved until the dialog asks for the result.-- The whole exchange runs on the server. Neither TokenDance's PKCE verifier, Penguin Go's device secret, nor ModelScope's code and device secret ever reaches the browser, and the new key goes straight into the model table without passing through it. ModelScope's client secret is never in PenguinHarness at all; only the bridge holds it.+- The whole exchange runs on the server. Neither TokenDance's PKCE verifier, Penguin Go's device secret, nor ModelScope's code and device secret ever reaches the browser, and the new key goes straight into the model table without passing through it. ModelScope's client secret is never in Adelie at all; only the bridge holds it.- An authorization flow waits for at most ten minutes. ModelScope delivers an access token / refresh token pair: the access token is written to the model table, while the refresh token stays only in the server DB and is never returned to the frontend or written to the Project config.- A delivered key is handed over only once. Penguin Go and ModelScope both keep that one delivery briefly if saving it locally fails, so the write can be retried without authorizing again. ModelScope leaves nothing to clean up in ModelScope's console — what it returns is a token for your own account, not a newly minted key.- TokenDance hands over the new key only once. If saving it fails, authorize again and delete the unused key in the provider's console.-- A TokenDance key carries PenguinHarness's app URL from the [App attribution](#app-attribution) table, so calls made with it stay attributed even from another tool.+- A TokenDance key carries Adelie's app URL from the [App attribution](#app-attribution) table, so calls made with it stay attributed even from another tool.### Account balances@@ -286,7 +286,7 @@ To compare the models in a group:1. On the group's header, select the speed test icon (**Speed test**).2. Select **Start**.-PenguinHarness sends one real request to each model in turn, which uses a small amount of your API quota, and shows on each card:+Adelie sends one real request to each model in turn, which uses a small amount of your API quota, and shows on each card:- the time to first token, in milliseconds: green under 1000, yellow up to 3000, red above;- the output rate, in Tokens per second: green at 40 or more, yellow at 15 or more, red below.@@ -295,7 +295,7 @@ While the test runs, the same icon stops it (**Stop speed test**): the model bei## Sync preset models-PenguinHarness updates can change the built-in catalog of preset models. When they do, the Project owner sees:+Adelie updates can change the built-in catalog of preset models. When they do, the Project owner sees:- a red dot on **Models** in the sidebar;- a notice on the page, "Changes detected: {added} new, {updated} to upgrade", with **Update now** and **Dismiss**;@@ -487,7 +487,7 @@ The platform quotes peak rates in USD per million Tokens. The group's DeepSeek r`modelscope` is an aggregate gateway group: one ModelScope api-inference endpoint behind the preset base URL `https://api-inference.modelscope.cn/v1`. Model ids are upstream repo names, so they keep their vendor prefix (`deepseek-ai/DeepSeek-V4.1-Flash`, `Qwen/Qwen3.8-27B`). All three preset rows pin AgentHub's generic Responses client (`client_type = "openai-responses"`) and send inference requests to `{base_url}/responses`. A new Project gets these presets right away; an existing Project updates its stored protocol with **Sync presets** or the next ModelScope authorization.-The group's key comes from its header; see [Connect an account](#connect-an-account). Connecting goes through an authorization bridge, which holds the ModelScope client secret and returns an api-inference access token / refresh token pair, rather than through ModelScope's own pages. Nothing else about the group is special: inference requests go straight to `https://api-inference.modelscope.cn/v1` and never through the bridge. The access token is written into `.project_config.toml` like any other group key, while the refresh token stays only in the server DB. The access token expires, and PenguinHarness silently renews it before model requests; reconnect from the header only when the refresh token is missing or no longer valid.+The group's key comes from its header; see [Connect an account](#connect-an-account). Connecting goes through an authorization bridge, which holds the ModelScope client secret and returns an api-inference access token / refresh token pair, rather than through ModelScope's own pages. Nothing else about the group is special: inference requests go straight to `https://api-inference.modelscope.cn/v1` and never through the bridge. The access token is written into `.project_config.toml` like any other group key, while the refresh token stays only in the server DB. The access token expires, and Adelie silently renews it before model requests; reconnect from the header only when the refresh token is missing or no longer valid.The preset rows carry no price. ModelScope bills for api-inference and its model pages publish no read-able rate, so the rows are left unpriced: the models page shows no price badge on them and the cost center reports their usage as uncosted. That is the catalog's way of recording "nobody has looked this up" — see [Prices and promotions](#prices-and-promotions).@@ -585,7 +585,7 @@ The catalog decides these headers by **endpoint host**, not by the entry's provi| Endpoint | Header | Value || --- | --- | --- || `openrouter.ai` | `HTTP-Referer` | `https://penguin.ooo/` |-| `openrouter.ai` | `X-OpenRouter-Title` | `PenguinHarness` |+| `openrouter.ai` | `X-OpenRouter-Title` | `Adelie` || `openrouter.ai` | `X-OpenRouter-Categories` | `cli-agent,personal-agent` || `tokendance.space` | `X-App-URL` | `https://penguin.ooo/` || `opencode.ai` | `x-opencode-session` | The Session id; a request outside any Session (a connectivity test, a vision probe) sends a fresh id of its own |diff --git a/packages/docs/content/models.zh.md b/packages/docs/content/models.zh.mdindex a4ae2af3..8abd7313 100644--- a/packages/docs/content/models.zh.md+++ b/packages/docs/content/models.zh.md@@ -75,7 +75,7 @@ TokenDance 分组还没有 key 时,所有分组上方会有一条横幅,推2. 在 **API key** 里输入该端点的密钥。端点不是厂商自己的地址时,服务端的 `OPENAI_*` / `ANTHROPIC_*` 变量不会被使用(见[设置 API key](#设置-api-key)),不填 key 的导入会被拒绝。3. 在**自定义 base URL** 里输入端点的 base URL。4. 点击字段右上角的**检测协议**,或者在字段最右侧的菜单里选择协议。见[检测自定义模型的协议](#检测自定义模型的协议)。-5. 点击**批量导入模型**。PenguinHarness 会向端点请求模型列表,然后按端点返回的顺序把所有模型保存到新分组。+5. 点击**批量导入模型**。Adelie 会向端点请求模型列表,然后按端点返回的顺序把所有模型保存到新分组。每个导入的模型都会带上你填写的 base URL、协议和密钥。端点只提供模型 id:价格、上下文窗口和显示名都留空,视觉保持关闭,直到你检测或手动开启。这和手动添加的模型起点相同。@@ -117,7 +117,7 @@ TokenDance 分组还没有 key 时,所有分组上方会有一条横幅,推### 只承载内置模型-除 **Custom** 和 **vLLM** 以外,每个内置分组只承载 PenguinHarness 内置模型目录里的模型。这些分组的 key 按分组统一管理,组里有哪些模型由目录决定。+除 **Custom** 和 **vLLM** 以外,每个内置分组只承载 Adelie 内置模型目录里的模型。这些分组的 key 按分组统一管理,组里有哪些模型由目录决定。- 这些分组没有**添加模型**,**模型配置**的分组下拉里也不提供把模型移进这些分组。- 服务端会拒绝往这些分组新增不属于该分组内置模型的条目:保存时提示「该分组只承载内置模型」。`penguin config model add` 同样拒绝。删掉的内置模型可以重新加回来,**同步预置**做的就是这件事。@@ -191,7 +191,7 @@ TokenDance 分组还没有 key 时,所有分组上方会有一条横幅,推## 检测视觉支持-**支持视觉**开关可以一直关着,等你需要时再去问模型。点击开关旁的**检测**:PenguinHarness 会向模型发送一张 1x1 的 PNG,配一句只有一个词的提示。+**支持视觉**开关可以一直关着,等你需要时再去问模型。点击开关旁的**检测**:Adelie 会向模型发送一张 1x1 的 PNG,配一句只有一个词的提示。- 模型能回答,开关就打开:提示「该模型接受图片输入,已开启视觉」。- 模型表示自己不接受图片,开关就关闭。这是真实的回答,不是错误。@@ -220,7 +220,7 @@ TokenDance 分组还没有 key 时,所有分组上方会有一条横幅,推2. 点击**打开授权页**。供应商的授权页会在新标签页中打开。3. 在授权页完成授权。弹窗显示「等待在新标签页中完成授权…」,并自动报告结果。-TokenDance 会为你的账号创建一把**新** key,不会读取你已有的 key。供应商会把浏览器带回 PenguinHarness,由 PenguinHarness 用一次性授权码换取并保存 key。如果授权页跳不回来,比如浏览器无法访问重定向给出的服务器地址,点击**授权页跳不回来?改为手动填写授权码**。授权页随后不再重定向,改为直接显示一次性授权码。+TokenDance 会为你的账号创建一把**新** key,不会读取你已有的 key。供应商会把浏览器带回 Adelie,由 Adelie 用一次性授权码换取并保存 key。如果授权页跳不回来,比如浏览器无法访问重定向给出的服务器地址,点击**授权页跳不回来?改为手动填写授权码**。授权页随后不再重定向,改为直接显示一次性授权码。1. 把授权码粘贴进**授权码**输入框。2. 点击**提交授权码**。@@ -234,17 +234,17 @@ Penguin Go 有四处不同:ModelScope 有三处不同:-- 授权不经过魔搭自己的页面,而是经过一台**授权中转层**。中转层持有魔搭的 client secret,代 PenguinHarness 走完 OAuth,再把一把可直接调用 api-inference 的 access token 交回来。中转层的地址来自服务端环境变量 `MODELSCOPE_BRIDGE_URL`,见[环境变量](/configuration#环境变量)。-- 授权页的地址由中转层给出,PenguinHarness 原样打开,不像 Penguin Go 那样自己拼。同样没有手动填写授权码的方式。-- 拿到的 access token 是**会过期**的;PenguinHarness 会在服务端保存刷新凭据,并在模型请求前静默续期。刷新凭据失效或缺失时,才需要点一次**重新连接**。+- 授权不经过魔搭自己的页面,而是经过一台**授权中转层**。中转层持有魔搭的 client secret,代 Adelie 走完 OAuth,再把一把可直接调用 api-inference 的 access token 交回来。中转层的地址来自服务端环境变量 `MODELSCOPE_BRIDGE_URL`,见[环境变量](/configuration#环境变量)。+- 授权页的地址由中转层给出,Adelie 原样打开,不像 Penguin Go 那样自己拼。同样没有手动填写授权码的方式。+- 拿到的 access token 是**会过期**的;Adelie 会在服务端保存刷新凭据,并在模型请求前静默续期。刷新凭据失效或缺失时,才需要点一次**重新连接**。注意事项:- 只有 Project owner 能发起连接。TokenDance 还要求由他本人已登录的会话完成授权,实际上就是打开着弹窗的那个标签页。重定向本身不要求会话就能接收,因为供应商带回的浏览器未必是你发起授权时用的那个;但它只交回授权码:在弹窗来取结果之前,不会发生任何换取,也不会保存任何 key。-- 整个换取过程都在服务端完成。TokenDance 的 PKCE verifier、Penguin Go 的设备密钥、以及 ModelScope 的授权码和设备密钥都不会进入浏览器;新 key 直接写入模型表,同样不经过浏览器。ModelScope 的 client secret 从头到尾都不在 PenguinHarness 里,只有中转层持有。+- 整个换取过程都在服务端完成。TokenDance 的 PKCE verifier、Penguin Go 的设备密钥、以及 ModelScope 的授权码和设备密钥都不会进入浏览器;新 key 直接写入模型表,同样不经过浏览器。ModelScope 的 client secret 从头到尾都不在 Adelie 里,只有中转层持有。- 一次授权流程最多等待十分钟。ModelScope 交付的是一组 access token / refresh token:access token 写入模型表,refresh token 只保存在服务端 DB,不返回给前端,也不写入 Project 配置。- 交付回来的 key 只交一次。Penguin Go 和 ModelScope 都会在本地保存失败时短暂保留这一次交付,因此可以直接重试写入,不必再次授权。ModelScope 下无需去魔搭控制台清理——它交回的是你自己账号的 token,不是新造的 key。-- TokenDance 的 key 携带[应用归因](#应用归因)表中 PenguinHarness 的应用 URL,所以即使用其他工具发起调用,用量也仍会归到 PenguinHarness 名下。+- TokenDance 的 key 携带[应用归因](#应用归因)表中 Adelie 的应用 URL,所以即使用其他工具发起调用,用量也仍会归到 Adelie 名下。### 账户余额@@ -285,7 +285,7 @@ TokenDance 和 DeepSeek 可以查询 key 所属账户的余额。这两个分组1. 在分组标题栏上点击测速图标(**测速**)。2. 点击**开始测速**。-PenguinHarness 依次向每个模型发送一个真实请求,这会消耗少量 API 配额,然后在每张卡片上显示:+Adelie 依次向每个模型发送一个真实请求,这会消耗少量 API 配额,然后在每张卡片上显示:- 首个 Token 的延迟,单位毫秒:低于 1000 显示绿色,1000 到 3000 显示黄色,3000 以上显示红色;- 输出速率,单位 Token/秒:40 及以上显示绿色,15 及以上显示黄色,15 以下显示红色。@@ -294,7 +294,7 @@ PenguinHarness 依次向每个模型发送一个真实请求,这会消耗少## 同步预置模型-PenguinHarness 升级可能改变内置的预置模型目录。一旦发生,Project owner 会看到:+Adelie 升级可能改变内置的预置模型目录。一旦发生,Project owner 会看到:- 侧边栏**模型库**上出现红点;- 页面上出现通知「检测到变更:{added} 个新增,{updated} 个可升级」,附带**现在升级**和**忽略**按钮;@@ -486,7 +486,7 @@ OpenAI 兼容网关分组(openrouter / fireworks / siliconflow / tokendance /`modelscope` 是聚合网关分组:三条预置共用魔搭 api-inference 端点,预置 base URL 为 `https://api-inference.modelscope.cn/v1`。模型 id 就是上游仓库名,因此保留供应商前缀(`deepseek-ai/DeepSeek-V4.1-Flash`、`Qwen/Qwen3.8-27B`)。三条预置都固定使用 AgentHub 通用 Responses 客户端(`client_type = "openai-responses"`),推理请求发往 `{base_url}/responses`。新建的 Project 立即带上这些预置;既有 Project 可通过**同步预置**或下一次 ModelScope 授权更新已存的协议。-分组的 key 从标题栏取得,见[连接账户](#连接账户)。连接走一台授权中转层,由中转层持有魔搭的 client secret 并交回一组 api-inference access token / refresh token,而不是经过魔搭自己的页面。除此之外这个分组没有特别之处:推理请求直接发给 `https://api-inference.modelscope.cn/v1`,从不经过中转层;access token 和其他分组的 key 一样写进 `.project_config.toml`,refresh token 只保存在服务端 DB。access token 会过期,PenguinHarness 会在模型请求前静默续期;refresh token 缺失或失效时,才需要从标题栏重新连接一次。+分组的 key 从标题栏取得,见[连接账户](#连接账户)。连接走一台授权中转层,由中转层持有魔搭的 client secret 并交回一组 api-inference access token / refresh token,而不是经过魔搭自己的页面。除此之外这个分组没有特别之处:推理请求直接发给 `https://api-inference.modelscope.cn/v1`,从不经过中转层;access token 和其他分组的 key 一样写进 `.project_config.toml`,refresh token 只保存在服务端 DB。access token 会过期,Adelie 会在模型请求前静默续期;refresh token 缺失或失效时,才需要从标题栏重新连接一次。预置条目不带价格。魔搭的 api-inference 是计费的,但它的模型页面读不到费率,所以这些条目按未定价处理:模型页在它们上面不显示价格徽标,成本中心把它们的用量报为未计价。这是目录记录「没人查过这个价格」的方式,见[价格与促销](#价格与促销)。@@ -584,7 +584,7 @@ api_key = "sk-..."| 端点 | 请求头 | 值 || --- | --- | --- || `openrouter.ai` | `HTTP-Referer` | `https://penguin.ooo/` |-| `openrouter.ai` | `X-OpenRouter-Title` | `PenguinHarness` |+| `openrouter.ai` | `X-OpenRouter-Title` | `Adelie` || `openrouter.ai` | `X-OpenRouter-Categories` | `cli-agent,personal-agent` || `tokendance.space` | `X-App-URL` | `https://penguin.ooo/` || `opencode.ai` | `x-opencode-session` | Session id;不属于任何 Session 的请求(连通性测试、视觉探测)各自使用一个新生成的 id |diff --git a/packages/docs/content/omni-message.en.md b/packages/docs/content/omni-message.en.mdindex 3e59d3d5..42bec1b7 100644--- a/packages/docs/content/omni-message.en.md+++ b/packages/docs/content/omni-message.en.md@@ -3,7 +3,7 @@ title: The OmniMessage Protocoldescription: OmniMessage is the unified message protocol that the SDK yields, the Trace stores, and the Server streams verbatim over SSE.----OmniMessage is PenguinHarness's unified message protocol. The SDK yields OmniMessage objects, the Trace stores them line by line, and the Server pushes them verbatim over SSE. What streams, what is stored, and what the model sees are one structure: there is no second format between front end, back end, and storage.+OmniMessage is Adelie's unified message protocol. The SDK yields OmniMessage objects, the Trace stores them line by line, and the Server pushes them verbatim over SSE. What streams, what is stored, and what the model sees are one structure: there is no second format between front end, back end, and storage.This page starts with the envelope and its three message types, then lists every payload field by field, and ends with the rules that span the whole protocol: the streaming discipline, `stop_reason`, `origin` and provider fidelity. The type definitions live in `packages/core/src/omnimessage/types.ts`.@@ -438,7 +438,7 @@ Provider-specific wire data travels in a single optional field, `fidelity`. It i{ type: "thinking", thinking: "…", fidelity: { reasoning_field: "reasoning_content" } }```-The payload is opaque to PenguinHarness: it passes through and persists verbatim end to end. Some models require it byte for byte when history is replayed, so any rewriting or loss breaks compatibility. This is one of the preconditions for lossless Session recovery from the Trace.+The payload is opaque to Adelie: it passes through and persists verbatim end to end. Some models require it byte for byte when history is replayed, so any rewriting or loss breaks compatibility. This is one of the preconditions for lossless Session recovery from the Trace.## Surfaces and their message subsets@@ -448,7 +448,7 @@ The payload is opaque to PenguinHarness: it passes through and persists verbatim| Trace on disk | `session_meta` + complete `model_msg` + all `event_msg` (no partials, no `origin`-tagged messages) || Server SSE stream | same as the SDK boundary, verbatim single-line JSON — see [Server API](/server-api) |-The [Agent API](/agent-api) does not stream OmniMessage: its stream is [AMSP](/amsp), a projection the server makes of the same live stream for programs outside PenguinHarness. Nothing in OmniMessage changes for it: no field, type or value is added.+The [Agent API](/agent-api) does not stream OmniMessage: its stream is [AMSP](/amsp), a projection the server makes of the same live stream for programs outside Adelie. Nothing in OmniMessage changes for it: no field, type or value is added.How messages travel along these surfaces, and every ordering guarantee, is covered on [Message Flow & Ordering](/message-flow).diff --git a/packages/docs/content/omni-message.zh.md b/packages/docs/content/omni-message.zh.mdindex 8d8389e2..8c7cfda0 100644--- a/packages/docs/content/omni-message.zh.md+++ b/packages/docs/content/omni-message.zh.md@@ -3,7 +3,7 @@ title: OmniMessage 协议description: OmniMessage 是统一的消息协议:SDK 产出它,Trace 存储它,Server 经 SSE 原样推送它。----OmniMessage 是 PenguinHarness 的统一消息协议。SDK 产出 OmniMessage 对象,Trace 逐行存储,Server 经 SSE 原样推送。流出去的、存下来的和模型看到的是同一种结构,前端、后端与存储之间没有第二套格式。+OmniMessage 是 Adelie 的统一消息协议。SDK 产出 OmniMessage 对象,Trace 逐行存储,Server 经 SSE 原样推送。流出去的、存下来的和模型看到的是同一种结构,前端、后端与存储之间没有第二套格式。本页先讲信封和三类消息,再逐字段列出全部 payload,最后是贯穿整个协议的规则:流式纪律、`stop_reason`、`origin` 与保真字段。类型定义见 `packages/core/src/omnimessage/types.ts`。@@ -438,7 +438,7 @@ type StopReason = "completed" | "aborted" | "retryable" | "fatal";{ type: "thinking", thinking: "…", fidelity: { reasoning_field: "reasoning_content" } }```-这个负载对 PenguinHarness 完全不透明:全链路原样透传、原样存储。部分模型回放历史时要求它逐字节一致,任何改写或丢失都会破坏兼容性。这也是 Trace 能无损恢复 Session 的前提之一。+这个负载对 Adelie 完全不透明:全链路原样透传、原样存储。部分模型回放历史时要求它逐字节一致,任何改写或丢失都会破坏兼容性。这也是 Trace 能无损恢复 Session 的前提之一。## 各通道的消息子集@@ -448,7 +448,7 @@ type StopReason = "completed" | "aborted" | "retryable" | "fatal";| 落盘的 Trace | `session_meta` + 完整 `model_msg` + 全部 `event_msg`(不存分片,也不存带 `origin` 的消息) || Server 的 SSE 推送 | 与 SDK 边界相同,原样的单行 JSON,见 [Server API](/server-api) |-[Agent API](/agent-api) 不推送 OmniMessage,它的事件流是 [AMSP](/amsp):服务器为 PenguinHarness 之外的程序,对同一条实时流所做的投影。OmniMessage 不因此改变,没有新增任何字段、类型或取值。+[Agent API](/agent-api) 不推送 OmniMessage,它的事件流是 [AMSP](/amsp):服务器为 Adelie 之外的程序,对同一条实时流所做的投影。OmniMessage 不因此改变,没有新增任何字段、类型或取值。消息沿这些通道传递的机制与各项顺序保证,见[消息流转与时序](/message-flow)。diff --git a/packages/docs/content/quickstart-cli.en.md b/packages/docs/content/quickstart-cli.en.mdindex bf817c62..73b32fee 100644--- a/packages/docs/content/quickstart-cli.en.md+++ b/packages/docs/content/quickstart-cli.en.md@@ -39,7 +39,7 @@ For offline installs, building from source, install locations, version pinning a## Configure a model-PenguinHarness ships with no model credentials, so add a model before your first Task. This command adds DeepSeek's `deepseek-flash` and makes it the default:+Adelie ships with no model credentials, so add a model before your first Task. This command adds DeepSeek's `deepseek-flash` and makes it the default:```bashpenguin config model add --provider deepseek --model-id deepseek-flash --api-key sk-... --set-default@@ -47,7 +47,7 @@ penguin config model add --provider deepseek --model-id deepseek-flash --api-keyYou can also add models later on the **Models** page of the Web App.-- A model is always named by a `(provider, model_id)` pair, so `--provider` and `--model-id` are both required. PenguinHarness never infers the provider from the model id. See [Models & Providers](/models) for the built-in groups.+- A model is always named by a `(provider, model_id)` pair, so `--provider` and `--model-id` are both required. Adelie never infers the provider from the model id. See [Models & Providers](/models) for the built-in groups.- The API key can also come from an environment variable, for the vendor's own endpoint. When a model entry has no inline `api_key` and no `base_url` of its own (or one that is the vendor's official endpoint), AgentHub (the LLM gateway library) reads variables such as `DEEPSEEK_API_KEY`, `ANTHROPIC_API_KEY`, `OPENAI_API_KEY` and `GEMINI_API_KEY`. An entry pointed at a gateway or a server of your own needs `--api-key`. A `.env` file in the working directory is loaded automatically.## Start the Web App@@ -110,16 +110,11 @@ Other POSIX platforms do not fall back automatically. The script exits and asks### Download source and version-The stable entry point defaults to `PENGUIN_DOWNLOAD_SOURCE=auto`. It resolves the target through an immutable OSS release directory, and only after that release has been completely uploaded and verified. If the metadata is unavailable, it falls back to the matching GitHub Release.+The installer downloads from this repository's GitHub Releases. `PENGUIN_DOWNLOAD_SOURCE` accepts `auto`, the default, and `github`; they mean the same thing here, because Adelie publishes to one source. Upstream's `oss` mirror is not one of them: a script that still names it stops before downloading anything and says so.-Which source then serves the package is measured, not assumed:+To download through a mirror, point `PENGUIN_DOWNLOAD_BASE_URL` at a directory holding the release assets — the same layout a GitHub Release has — and optionally `PENGUIN_DOWNLOAD_FALLBACK_BASE_URL` at a second one. When the primary fails, the installer tries the fallback for the same version, so a mirror can never quietly install a different tag. Downloads are verified against the published `.sha256` either way.-- The installer times a probe file on GitHub and keeps GitHub whenever the download reaches 256 KB/s.-- Only below that does it measure the OSS mirror, and it switches only when the mirror is more than 1.5x faster. A mirror that is only a little quicker is not worth its bandwidth bill, and a slow GitHub download still resumes.--Set `PENGUIN_DOWNLOAD_SPEED_PROBE=0` to skip the measurement, or set `PENGUIN_DOWNLOAD_SOURCE` to `oss` or `github` to force a source. The normal installer output names the source without printing the mirror's full URL.--The [`releases/latest/download` entry](https://github.com/lmliheng/Adelie/releases/latest/download/install.sh) resolves the current stable version each time it runs. A standalone script downloaded from a versioned GitHub or OSS Release is stamped with that Release's tag and installs the same version by default, which keeps the installer and the package format matched. To override the version, set `PENGUIN_VERSION`, or pass `--version` on POSIX systems. On Windows, set the variable before you run the installer:+Version handling is unchanged by the source: the [`releases/latest/download` entry](https://github.com/lmliheng/Adelie/releases/latest/download/install.sh) resolves the current stable version each time it runs, and an installer downloaded from a versioned Release is stamped with that Release's tag and installs the same version by default, which keeps the installer and the package format matched. To override the version, set `PENGUIN_VERSION`, or pass `--version` on POSIX systems. On Windows, set the variable before you run the installer:```powershell$env:PENGUIN_VERSION = "vX.Y.Z"; irm https://github.com/lmliheng/Adelie/releases/latest/download/install.ps1 | iex@@ -157,16 +152,16 @@ pnpm install && pnpm buildAfter the build, run `pnpm penguin <args>` inside the repository as the dev runner, or use the globally linked `penguin` command.-The dev entry points (`pnpm penguin`, `pnpm dev`, `pnpm desktop`) default to a separate data root, `~/.penguin/dev-data`, while the linked or installed `penguin` keeps `~/.penguin/data`. Set `PENGUIN_HOME` to override. The desktop dev run also uses its own app identity (`PenguinHarness-Dev`), so it can run alongside an installed desktop app without conflicts.+The dev entry points (`pnpm penguin`, `pnpm dev`, `pnpm desktop`) default to a separate data root, `~/.penguin/dev-data`, while the linked or installed `penguin` keeps `~/.adelie/data`. Set `ADELIE_HOME` to override. The desktop dev run also uses its own app identity (`Adelie-Dev`), so it can run alongside an installed desktop app without conflicts.### Install location and options| Item | Details || --- | --- |-| Install directory | `~/.penguin` by default; override it with the `PENGUIN_INSTALL_DIR` environment variable |+| Install directory | `~/.adelie` by default; override it with the `PENGUIN_INSTALL_DIR` environment variable || Command entry | A symlink, `~/.local/bin/penguin`. The script warns if `~/.local/bin` is not on `PATH`. The `--no-modify-path` flag leaves the link alone, for a second installation beside the one `penguin` belongs to || Version | The `PENGUIN_VERSION=vX.Y.Z` environment variable, or the `--version vX.Y.Z` script flag. The stable entry installs the latest Release by default; a versioned Release installer installs its own tag |-| Download source | `PENGUIN_DOWNLOAD_SOURCE=auto` (default), `oss` or `github`. `auto` times a probe file and keeps the free GitHub download unless the OSS mirror is clearly faster, and falls back to the same version on the other source. `PENGUIN_DOWNLOAD_SPEED_PROBE=0` skips the measurement |+| Download source | `PENGUIN_DOWNLOAD_SOURCE=auto` (default) or `github` — Adelie publishes to GitHub Releases only, and anything else stops the script. A mirror goes in `PENGUIN_DOWNLOAD_BASE_URL`, with `PENGUIN_DOWNLOAD_FALLBACK_BASE_URL` beside it || Local archive | `PENGUIN_ARCHIVE=<file>` or `--archive <file>`. Accepts a Release bundle, which verifies itself with its sealed payload checksum, or a payload or legacy program archive with a `<file>.sha256` next to it. A renamed legacy file may use the platform asset's canonical `.sha256` || Integrity check | Always on. Online downloads are verified against the published `.sha256`, and bundle payloads against the checksum sealed inside the bundle || Upgrade | Run the install script again; files are swapped atomically |@@ -177,8 +172,8 @@ Script flags go after `sh -s --`, for example `curl -fsSL https://github.com/lml| Item | Details || --- | --- |-| Install directory | `%USERPROFILE%\.penguin` by default; override it with the `PENGUIN_INSTALL_DIR` environment variable |-| Command entry | The `bin\penguin.cmd` launcher. There is deliberately no `.ps1` launcher: batch files are exempt from the PowerShell execution policy, so `penguin` works even under the default Restricted policy. The installer adds `%USERPROFILE%\.penguin\bin` to your **user** Path and broadcasts the change. Open a **new terminal window** once; a new tab of an already-running terminal keeps the old Path. The `-NoModifyPath` switch leaves the Path alone, for a second installation beside the one `penguin` belongs to |+| Install directory | `%USERPROFILE%\.adelie` by default; override it with the `PENGUIN_INSTALL_DIR` environment variable |+| Command entry | The `bin\penguin.cmd` launcher. There is deliberately no `.ps1` launcher: batch files are exempt from the PowerShell execution policy, so `penguin` works even under the default Restricted policy. The installer adds `%USERPROFILE%\.adelie\bin` to your **user** Path and broadcasts the change. Open a **new terminal window** once; a new tab of an already-running terminal keeps the old Path. The `-NoModifyPath` switch leaves the Path alone, for a second installation beside the one `penguin` belongs to || Version pin | Set `$env:PENGUIN_VERSION = "vX.Y.Z"` before running the installer || Local archive | `$env:PENGUIN_ARCHIVE = "<file>"` or `-ArchivePath <file>`. Accepts the Release bundle, which verifies itself with its sealed payload checksum, or a payload or legacy zip with a `<file>.sha256` next to it. A renamed legacy file may use `penguin-win32-x64.zip.sha256` || Integrity check | Always on. Online downloads are verified against the published `.sha256`, and bundle payloads against the checksum sealed inside the bundle |@@ -186,7 +181,7 @@ Script flags go after `sh -s --`, for example `curl -fsSL https://github.com/lmlOther differences on Windows:-- **Agent shell**: the agent's `exec_command` runs in a POSIX shell, so Skills written for one keep working. The shell is picked in this order: `bash` on PATH, which is preferred because your own [Git for Windows](https://gitforwindows.org/) carries the full MSYS userland; then the **bundled bash**, since the Windows zip ships MinGit under `git\` and gives a machine without Git for Windows a POSIX shell, about sixty core utilities and `git.exe`; then PowerShell (`pwsh`, then `powershell`). Only npm installs, which bundle nothing, reach the PowerShell fallback. The `PENGUIN_SHELL` environment variable overrides the pick, and the Session's system prompt tells the model which shell is active. The bundled shell's licensing is recorded in [THIRD-PARTY-NOTICES.md](https://github.com/lmliheng/Adelie/blob/main/THIRD-PARTY-NOTICES.md).+- **Agent shell**: the agent's `exec_command` runs in a POSIX shell, so Skills written for one keep working. The shell is picked in this order: `bash` on PATH, which is preferred because your own [Git for Windows](https://gitforwindows.org/) carries the full MSYS userland; then the **bundled bash**, since the Windows zip ships MinGit under `git\` and gives a machine without Git for Windows a POSIX shell, about sixty core utilities and `git.exe`; then PowerShell (`pwsh`, then `powershell`). Only npm installs, which bundle nothing, reach the PowerShell fallback. The `ADELIE_SHELL` environment variable overrides the pick, and the Session's system prompt tells the model which shell is active. The bundled shell's licensing is recorded in [THIRD-PARTY-NOTICES.md](https://github.com/lmliheng/Adelie/blob/main/THIRD-PARTY-NOTICES.md).- **Ctrl-C**: sending Ctrl-C to a running command session (`input_command` with `"\u0003"`) terminates the whole command session tree instead of interrupting the foreground command. Windows cannot deliver a console Ctrl-C to a piped child process, so the interrupt becomes a hard kill of the tree.- **In-place update**: `penguin update` is not yet supported on Windows. To upgrade, run the installer again.- **Config file permissions**: on POSIX systems, config and credential files are written with `0600` (owner-only) permissions. Windows has no such mode bits, so these files fall under your profile's default NTFS ACLs.@@ -194,7 +189,7 @@ Other differences on Windows:### Data root-The data root is `~/.penguin/data` by default (`%USERPROFILE%\.penguin\data` on Windows). It sits under the install directory, but installing and upgrading never modify it. Set the `PENGUIN_HOME` environment variable to use another directory. Model configuration, Session records and other data are kept across upgrades.+The data root is `~/.adelie/data` by default (`%USERPROFILE%\.adelie\data` on Windows). It sits under the install directory, but installing and upgrading never modify it. Set the `ADELIE_HOME` environment variable to use another directory. Model configuration, Session records and other data are kept across upgrades.### Sandbox on Ubuntu@@ -233,7 +228,7 @@ All packages are published under the Apache-2.0 license.## Next steps-- [Web App](/web-app): use PenguinHarness from the browser.+- [Web App](/web-app): use Adelie from the browser.- [CLI Reference](/cli): every command and option.-- [Update PenguinHarness](/updates): check your version and upgrade.+- [Update Adelie](/updates): check your version and upgrade.- [SDK](/quickstart-sdk): embed the engine in your own program.diff --git a/packages/docs/content/quickstart-cli.zh.md b/packages/docs/content/quickstart-cli.zh.mdindex 667eaf99..ce987dc0 100644--- a/packages/docs/content/quickstart-cli.zh.md+++ b/packages/docs/content/quickstart-cli.zh.md@@ -39,7 +39,7 @@ penguin -v## 配置模型-PenguinHarness 不内置任何模型凭据,跑第一个 Task 之前要先添加模型。下面这条命令添加 DeepSeek 的 `deepseek-flash`,并设为默认模型:+Adelie 不内置任何模型凭据,跑第一个 Task 之前要先添加模型。下面这条命令添加 DeepSeek 的 `deepseek-flash`,并设为默认模型:```bashpenguin config model add --provider deepseek --model-id deepseek-flash --api-key sk-... --set-default@@ -47,7 +47,7 @@ penguin config model add --provider deepseek --model-id deepseek-flash --api-key之后也可以在 Web App 的**模型库**页面添加模型。-- 模型始终以 `(provider, model_id)` 二元组引用,因此 `--provider` 与 `--model-id` 都必填。PenguinHarness 不会根据模型 id 推断供应商。内置分组见[模型与 Provider](/models)。+- 模型始终以 `(provider, model_id)` 二元组引用,因此 `--provider` 与 `--model-id` 都必填。Adelie 不会根据模型 id 推断供应商。内置分组见[模型与 Provider](/models)。- API Key 也可以来自环境变量,但仅限厂商自己的端点。模型条目没有内联 `api_key`、且没有自己的 `base_url`(或 `base_url` 就是厂商官方端点)时,LLM 网关库 AgentHub 会读取 `DEEPSEEK_API_KEY`、`ANTHROPIC_API_KEY`、`OPENAI_API_KEY`、`GEMINI_API_KEY` 等变量。指向网关或自己服务器的条目需要 `--api-key`。工作目录下的 `.env` 文件会自动加载。## 启动 Web App@@ -110,16 +110,11 @@ penguin chat### 下载来源与版本-稳定入口默认使用 `PENGUIN_DOWNLOAD_SOURCE=auto`。它通过 OSS 上不可变的版本目录确定目标版本,而且只认已经完整上传并通过验证的版本;元数据不可用时,回退到对应的 GitHub Release。+安装器从这个仓库的 GitHub Release 下载。`PENGUIN_DOWNLOAD_SOURCE` 接受 `auto`(默认)与 `github`,在这里两者是一回事:Adelie 只发布到一个来源。上游的 `oss` 镜像不在其中 —— 脚本里若还写着它,会在下载任何东西之前停下并说明原因。-安装包实际从哪个来源下载,由实测决定,而不是预设:+要用镜像下载,就把 `PENGUIN_DOWNLOAD_BASE_URL` 指向一个放着发布资产的目录(与 GitHub Release 相同的布局),可选再用 `PENGUIN_DOWNLOAD_FALLBACK_BASE_URL` 指定第二个。主来源失败时,安装器改用回退来源取同一个版本,镜像不会悄悄装成另一个 tag。两条路上的下载都对发布的 `.sha256` 校验。-- 安装器先对 GitHub 上的测速文件计时,速度达到 256 KB/s 就继续用 GitHub。-- 只有低于这个速度,才会测量 OSS 镜像,并且镜像要快 1.5 倍以上才会切换。只快一点的镜像不值得为它支付带宽费用,GitHub 下载即使慢,也能断点续传。--设置 `PENGUIN_DOWNLOAD_SPEED_PROBE=0` 可以跳过测速,把 `PENGUIN_DOWNLOAD_SOURCE` 设为 `oss` 或 `github` 可以强制指定来源。安装器的常规输出只写明来源,不打印镜像的完整 URL。--[`releases/latest/download` 这个稳定入口](https://github.com/lmliheng/Adelie/releases/latest/download/install.sh)每次运行时都会解析当前的稳定版本。从 GitHub 或 OSS 某个版本的 Release 里单独下载的安装脚本,会写入所属 Release 的 tag,默认安装同一版本,从而保证安装器与安装包格式相互匹配。要改用其他版本,设置 `PENGUIN_VERSION`;在 POSIX 系统上也可以传入 `--version`。在 Windows 上,先设置环境变量,再运行安装器:+版本的处理与来源无关:[`releases/latest/download` 这个稳定入口](https://github.com/lmliheng/Adelie/releases/latest/download/install.sh)每次运行时都会解析当前的稳定版本;从某个版本的 Release 里单独下载的安装脚本,会写入所属 Release 的 tag,默认安装同一版本,从而保证安装器与安装包格式相互匹配。要改用其他版本,设置 `PENGUIN_VERSION`;在 POSIX 系统上也可以传入 `--version`。在 Windows 上,先设置环境变量,再运行安装器:```powershell$env:PENGUIN_VERSION = "vX.Y.Z"; irm https://github.com/lmliheng/Adelie/releases/latest/download/install.ps1 | iex@@ -157,16 +152,16 @@ pnpm install && pnpm build构建完成后,可以在仓库内用 `pnpm penguin <args>` 以开发方式运行,也可以使用全局链接的 `penguin` 命令。-开发入口(`pnpm penguin`、`pnpm dev`、`pnpm desktop`)默认使用独立的数据目录 `~/.penguin/dev-data`,全局链接或正式安装的 `penguin` 仍使用 `~/.penguin/data`,设置 `PENGUIN_HOME` 可以覆盖。桌面应用的开发运行还使用独立的应用标识(`PenguinHarness-Dev`),因此可以和已安装的桌面应用同时运行,互不冲突。+开发入口(`pnpm penguin`、`pnpm dev`、`pnpm desktop`)默认使用独立的数据目录 `~/.penguin/dev-data`,全局链接或正式安装的 `penguin` 仍使用 `~/.adelie/data`,设置 `ADELIE_HOME` 可以覆盖。桌面应用的开发运行还使用独立的应用标识(`Adelie-Dev`),因此可以和已安装的桌面应用同时运行,互不冲突。### 安装位置与选项| 项目 | 说明 || --- | --- |-| 安装目录 | 默认为 `~/.penguin`,可用环境变量 `PENGUIN_INSTALL_DIR` 覆盖 |+| 安装目录 | 默认为 `~/.adelie`,可用环境变量 `PENGUIN_INSTALL_DIR` 覆盖 || 命令入口 | 符号链接 `~/.local/bin/penguin`。如果 `~/.local/bin` 不在 `PATH` 中,脚本会给出提示。脚本参数 `--no-modify-path` 则不改动这个链接,用于在 `penguin` 所属的安装之外再装一份 || 版本 | 环境变量 `PENGUIN_VERSION=vX.Y.Z`,或脚本参数 `--version vX.Y.Z`。稳定入口默认安装最新的 Release,某个版本的 Release 安装器默认安装自身的 tag |-| 下载来源 | `PENGUIN_DOWNLOAD_SOURCE=auto`(默认)、`oss` 或 `github`。`auto` 会对测速文件计时,除非 OSS 镜像明显更快,否则保持免费的 GitHub 下载,并可回退到另一个来源的同一版本。`PENGUIN_DOWNLOAD_SPEED_PROBE=0` 跳过测速 |+| 下载来源 | `PENGUIN_DOWNLOAD_SOURCE=auto`(默认)或 `github` —— Adelie 只发布到 GitHub Release,写别的会让脚本停下。要用镜像就设 `PENGUIN_DOWNLOAD_BASE_URL`,回退来源用 `PENGUIN_DOWNLOAD_FALLBACK_BASE_URL` || 本地压缩包 | `PENGUIN_ARCHIVE=<file>` 或 `--archive <file>`。接受 Release 安装包(凭封入的负载校验值自行校验),或旁边带有 `<file>.sha256` 的负载、旧版程序压缩包。重命名过的旧版文件可以使用平台标准文件名的 `.sha256` || 完整性校验 | 始终开启。在线下载对照发布的 `.sha256` 校验,安装包里的负载对照包内封入的校验值校验 || 升级 | 重新运行安装脚本,文件以原子方式替换 |@@ -177,8 +172,8 @@ pnpm install && pnpm build| 项目 | 说明 || --- | --- |-| 安装目录 | 默认为 `%USERPROFILE%\.penguin`,可用环境变量 `PENGUIN_INSTALL_DIR` 覆盖 |-| 命令入口 | 启动器 `bin\penguin.cmd`。特意不提供 `.ps1` 启动器:批处理文件不受 PowerShell 执行策略限制,所以在默认的 Restricted 策略下 `penguin` 也能运行。安装器会把 `%USERPROFILE%\.penguin\bin` 加入**用户** Path 并广播这一变更。之后请**新开一个终端窗口**,已在运行的终端即使新开标签页,也仍沿用旧的 Path。`-NoModifyPath` 开关则不改动 Path,用于在 `penguin` 所属的安装之外再装一份 |+| 安装目录 | 默认为 `%USERPROFILE%\.adelie`,可用环境变量 `PENGUIN_INSTALL_DIR` 覆盖 |+| 命令入口 | 启动器 `bin\penguin.cmd`。特意不提供 `.ps1` 启动器:批处理文件不受 PowerShell 执行策略限制,所以在默认的 Restricted 策略下 `penguin` 也能运行。安装器会把 `%USERPROFILE%\.adelie\bin` 加入**用户** Path 并广播这一变更。之后请**新开一个终端窗口**,已在运行的终端即使新开标签页,也仍沿用旧的 Path。`-NoModifyPath` 开关则不改动 Path,用于在 `penguin` 所属的安装之外再装一份 || 版本固定 | 运行安装器之前设置 `$env:PENGUIN_VERSION = "vX.Y.Z"` || 本地压缩包 | `$env:PENGUIN_ARCHIVE = "<file>"` 或 `-ArchivePath <file>`。接受 Release 安装包(凭封入的负载校验值自行校验),或旁边带有 `<file>.sha256` 的负载、旧版 zip。重命名过的旧版文件可以使用 `penguin-win32-x64.zip.sha256` || 完整性校验 | 始终开启。在线下载对照发布的 `.sha256` 校验,安装包里的负载对照包内封入的校验值校验 |@@ -186,7 +181,7 @@ pnpm install && pnpm buildWindows 上还有以下不同:-- **Agent shell**:Agent 的 `exec_command` 在 POSIX shell 中运行,这样面向 POSIX 编写的 Skill 可以照常工作。shell 的选择顺序是:首先是 PATH 上的 `bash`,优先使用它,因为你自己安装的 [Git for Windows](https://gitforwindows.org/) 带有完整的 MSYS 工具集;其次是**内置 bash**,Windows zip 在 `git\` 下自带 MinGit,没有安装 Git for Windows 的机器也能得到 POSIX shell、约六十个核心工具和 `git.exe`;最后是 PowerShell(先 `pwsh`,后 `powershell`)。只有 npm 安装不带任何内置组件,才会用到 PowerShell 这一兜底。环境变量 `PENGUIN_SHELL` 可以强制指定 shell,Session 的系统提示词会告诉模型当前使用的是哪个 shell。内置 shell 的许可信息见 [THIRD-PARTY-NOTICES.md](https://github.com/lmliheng/Adelie/blob/main/THIRD-PARTY-NOTICES.md)。+- **Agent shell**:Agent 的 `exec_command` 在 POSIX shell 中运行,这样面向 POSIX 编写的 Skill 可以照常工作。shell 的选择顺序是:首先是 PATH 上的 `bash`,优先使用它,因为你自己安装的 [Git for Windows](https://gitforwindows.org/) 带有完整的 MSYS 工具集;其次是**内置 bash**,Windows zip 在 `git\` 下自带 MinGit,没有安装 Git for Windows 的机器也能得到 POSIX shell、约六十个核心工具和 `git.exe`;最后是 PowerShell(先 `pwsh`,后 `powershell`)。只有 npm 安装不带任何内置组件,才会用到 PowerShell 这一兜底。环境变量 `ADELIE_SHELL` 可以强制指定 shell,Session 的系统提示词会告诉模型当前使用的是哪个 shell。内置 shell 的许可信息见 [THIRD-PARTY-NOTICES.md](https://github.com/lmliheng/Adelie/blob/main/THIRD-PARTY-NOTICES.md)。- **Ctrl-C**:向运行中的命令会话发送 Ctrl-C(`input_command` 传入 `"\u0003"`),会终止整棵命令会话进程树,而不是中断前台命令。Windows 无法把控制台 Ctrl-C 投递给通过管道连接的子进程,中断因此退化为强制结束整棵进程树。- **就地更新**:Windows 暂不支持 `penguin update`,升级请重新运行安装器。- **配置文件权限**:在 POSIX 系统上,配置文件与凭据文件以 `0600`(仅属主可读写)权限写入。Windows 没有这类权限位,这些文件遵循你用户目录的默认 NTFS ACL。@@ -194,7 +189,7 @@ Windows 上还有以下不同:### 数据目录-数据目录默认为 `~/.penguin/data`(Windows 为 `%USERPROFILE%\.penguin\data`)。它位于安装目录之下,但安装和升级都不会改动它。设置环境变量 `PENGUIN_HOME` 可以改用其他目录。模型配置、Session 记录等数据在升级后都会保留。+数据目录默认为 `~/.adelie/data`(Windows 为 `%USERPROFILE%\.adelie\data`)。它位于安装目录之下,但安装和升级都不会改动它。设置环境变量 `ADELIE_HOME` 可以改用其他目录。模型配置、Session 记录等数据在升级后都会保留。### Ubuntu 上的沙盒@@ -233,7 +228,7 @@ sudo apparmor_parser -r /etc/apparmor.d/adelie-sandbox-bwrap## 下一步-- [Web App](/web-app):在浏览器里使用 PenguinHarness。+- [Web App](/web-app):在浏览器里使用 Adelie。- [CLI 参考](/cli):全部命令与选项。-- [更新 PenguinHarness](/updates):查看版本并升级。+- [更新 Adelie](/updates):查看版本并升级。- [SDK](/quickstart-sdk):把引擎嵌入自己的程序。diff --git a/packages/docs/content/quickstart-desktop.en.md b/packages/docs/content/quickstart-desktop.en.mdindex 0f45f520..fe75ef7a 100644--- a/packages/docs/content/quickstart-desktop.en.md+++ b/packages/docs/content/quickstart-desktop.en.md@@ -1,6 +1,6 @@---title: Desktop app-description: Install the PenguinHarness desktop app, configure a model, and run your first Task, with no terminal required.+description: Install the Adelie desktop app, configure a model, and run your first Task, with no terminal required.---The desktop app is the full Web App as a standalone application. It embeds the server and opens already signed in, so there is no login page, no initial password to copy, and nothing to install from a command line. It also installs the `penguin` command, so the terminal is there when you want it.@@ -12,7 +12,7 @@ The desktop app is the full Web App as a standalone application. It embeds the s## Download and install-Download the installer for your platform from the [download page](https://github.com/lmliheng/Adelie/releases/latest); the installer prefers the OSS-accelerated mirror when it is reachable. Every [GitHub Release](https://github.com/lmliheng/Adelie/releases) carries the same files.+Download the installer for your platform from the [latest Release](https://github.com/lmliheng/Adelie/releases/latest); every [GitHub Release](https://github.com/lmliheng/Adelie/releases) carries the same files.| Platform | Installers || --- | --- |@@ -36,7 +36,7 @@ The app opens signed in. The window signs itself in, so there is no password to## Configure a model-PenguinHarness ships with no model credentials. Give it an API key for the model you want to use:+Adelie ships with no model credentials. Give it an API key for the model you want to use:1. In the sidebar, select **Models**. Models are listed in one group per provider, and the default model is marked **Default**.2. In your provider's group, click **Enter key**, enter the API key, and click **Confirm**. The key is written to every model in that group. TokenDance, Penguin Go and ModelScope can also get a key for you: click **Connect** on their group.@@ -62,7 +62,7 @@ Tool calls appear inline as cards; open one to inspect its arguments and output.> [!INFO]- On macOS, the directory browser can't read Desktop, Documents or Downloads>-> macOS protects these folders. Click **Allow access** in the directory browser: the app asks macOS for the folder in its own name, and once you allow it, your agents can read the folder too. If macOS doesn't allow it, **Open System Settings** takes you to Privacy & Security; if PenguinHarness is not listed under **Files and Folders**, add it under **Full Disk Access**. A development build started from a terminal counts as that terminal to macOS, so allow the terminal there instead.+> macOS protects these folders. Click **Allow access** in the directory browser: the app asks macOS for the folder in its own name, and once you allow it, your agents can read the folder too. If macOS doesn't allow it, **Open System Settings** takes you to Privacy & Security; if Adelie is not listed under **Files and Folders**, add it under **Full Disk Access**. A development build started from a terminal counts as that terminal to macOS, so allow the terminal there instead.## The `penguin` command@@ -98,6 +98,6 @@ That command is also the way out if a window ever does show the login page: the## Next steps- [Web App](/web-app): find your way around the interface.-- [Update PenguinHarness](/updates): how the desktop app updates itself.+- [Update Adelie](/updates): how the desktop app updates itself.- [CLI and Web App](/quickstart-cli): a standalone install, for a server or a remote machine. On the same machine you don't need it: the app already provides `penguin`, and installing the CLI puts a second copy on your `PATH`.- [Architecture](/architecture): how the pieces fit together.diff --git a/packages/docs/content/quickstart-desktop.zh.md b/packages/docs/content/quickstart-desktop.zh.mdindex 6f113305..d0aa4214 100644--- a/packages/docs/content/quickstart-desktop.zh.md+++ b/packages/docs/content/quickstart-desktop.zh.md@@ -1,6 +1,6 @@---title: 桌面应用-description: 安装 PenguinHarness 桌面应用,配置模型,跑通第一个 Task,全程不需要终端。+description: 安装 Adelie 桌面应用,配置模型,跑通第一个 Task,全程不需要终端。---桌面应用把完整的 Web App 做成了一个独立应用。它内置服务端,打开即已登录:没有登录页,不用抄初始密码,也不必从命令行安装任何东西。它还会替你装好 `penguin` 命令,需要终端时随时可用。@@ -12,7 +12,7 @@ description: 安装 PenguinHarness 桌面应用,配置模型,跑通第一个## 下载并安装-从[下载页](https://github.com/lmliheng/Adelie/releases/latest)下载对应平台的安装包;安装器在 OSS 加速镜像可用时会优先走镜像。每个 [GitHub Release](https://github.com/lmliheng/Adelie/releases) 里都有同样的文件。+从[最新 Release](https://github.com/lmliheng/Adelie/releases/latest)下载对应平台的安装包;每个 [GitHub Release](https://github.com/lmliheng/Adelie/releases) 里都有同样的文件。| 平台 | 安装包 || --- | --- |@@ -36,7 +36,7 @@ macOS 安装包已经过 Developer ID 签名和公证,Windows 安装程序已## 配置模型-PenguinHarness 不内置任何模型凭据。为要使用的模型配置 API Key:+Adelie 不内置任何模型凭据。为要使用的模型配置 API Key:1. 在侧边栏选择**模型库**。模型按供应商分组列出,默认模型带有**默认**标记。2. 在你所用供应商的分组里点击**填写密钥**,输入 API Key,然后点击**确认**。这个 Key 会写入分组里的每个模型。TokenDance、Penguin Go 和 ModelScope 还可以替你取得 key:在它们的分组上点击**连接**。@@ -62,7 +62,7 @@ PenguinHarness 不内置任何模型凭据。为要使用的模型配置 API Key> [!INFO]- macOS 上目录浏览器读不到桌面、文稿或下载>-> 这些文件夹受 macOS 保护。在目录浏览器里点击**允许访问**:应用会以自己的名义向 macOS 申请,你允许之后,Agent 也能读取这个文件夹。macOS 没有放行时,**打开系统设置**会进入「隐私与安全性」;若「文件与文件夹」里没有 PenguinHarness,请在「完全磁盘访问权限」里添加它。从终端启动的开发构建在 macOS 看来归该终端所有,这时要放行的是那个终端。+> 这些文件夹受 macOS 保护。在目录浏览器里点击**允许访问**:应用会以自己的名义向 macOS 申请,你允许之后,Agent 也能读取这个文件夹。macOS 没有放行时,**打开系统设置**会进入「隐私与安全性」;若「文件与文件夹」里没有 Adelie,请在「完全磁盘访问权限」里添加它。从终端启动的开发构建在 macOS 看来归该终端所有,这时要放行的是那个终端。## `penguin` 命令@@ -98,6 +98,6 @@ penguin server reset-admin-password## 下一步- [Web App](/web-app):熟悉界面。-- [更新 PenguinHarness](/updates):桌面应用如何更新自身。+- [更新 Adelie](/updates):桌面应用如何更新自身。- [命令行与 Web App](/quickstart-cli):独立安装,适用于服务器或远程机器。同一台机器上不需要再装:应用已经提供了 `penguin`,再装 CLI 只会在 `PATH` 上多出一份。- [架构总览](/architecture):各个部分如何协作。diff --git a/packages/docs/content/quickstart-docker.en.md b/packages/docs/content/quickstart-docker.en.mdindex 7a0282f3..d6d44ff2 100644--- a/packages/docs/content/quickstart-docker.en.md+++ b/packages/docs/content/quickstart-docker.en.md@@ -1,13 +1,13 @@---title: Docker-description: Run the official PenguinHarness image, with one container and one volume serving the full Web App on port 7364.+description: Run the official Adelie image, with one container and one volume serving the full Web App on port 7364.---The official image runs the same server that `penguin server` starts, with the Web App inside it. One container and one volume are the whole deployment, which makes Docker the shortest route onto a machine that is not your laptop.## Before you begin-- Docker on the machine that will run PenguinHarness. The examples below cover both Docker Compose and `docker run`.+- Docker on the machine that will run Adelie. The examples below cover both Docker Compose and `docker run`.- An API key for one model provider.## Start the container@@ -78,14 +78,14 @@ If reading a link from a log does not suit your setup, pin the password instead.```yamlenvironment:- PENGUIN_SEED_ADMIN_PASSWORD: "choose-something-long"+ ADELIE_SEED_ADMIN_PASSWORD: "choose-something-long"```The server then creates the built-in `admin` with that password (at least 8 characters) and prints no notice. The variable applies only while no user exists, which means the first boot of an empty data root. Adding it to a data root that has already been claimed changes nothing, and neither does changing it later.## Configure a model-PenguinHarness ships with no model credentials. Add a model on the **Models** page of the Web App, or with the CLI inside the container:+Adelie ships with no model credentials. Add a model on the **Models** page of the Web App, or with the CLI inside the container:```bashdocker compose exec -u penguin penguin \@@ -152,21 +152,21 @@ These are the variables a container deployment touches. The full list is in the| Variable | In this image || --- | --- |-| `PENGUIN_HOME` | `/data`. Change it only if you also move the volume |+| `ADELIE_HOME` | `/data`. Change it only if you also move the volume || `HOST` | `0.0.0.0`, inside the container's own network namespace. `-p` decides the host side, and the examples keep it on loopback || `PORT` | `7364`. Changing it moves the healthcheck with it |-| `PENGUIN_SEED_ADMIN_PASSWORD` | Pins the initial admin password, on the first boot only. See [Set the password in advance](#set-the-password-in-advance) |-| `PENGUIN_TRUST_PROXY` | Set to `1` behind a reverse proxy that terminates TLS, so session cookies are marked `Secure` |-| `PENGUIN_PREVIEW_ORIGIN` | A second hostname routed to the same container, for Workspace HTML previews |-| `PENGUIN_UPDATE_CHECK` | `off` turns off the automatic release check. Model requests, remote-control connections, key authorization and the proxy test still go out |+| `ADELIE_SEED_ADMIN_PASSWORD` | Pins the initial admin password, on the first boot only. See [Set the password in advance](#set-the-password-in-advance) |+| `ADELIE_TRUST_PROXY` | Set to `1` behind a reverse proxy that terminates TLS, so session cookies are marked `Secure` |+| `ADELIE_PREVIEW_ORIGIN` | A second hostname routed to the same container, for Workspace HTML previews |+| `ADELIE_UPDATE_CHECK` | `off` turns off the automatic release check. Model requests, remote-control connections, key authorization and the proxy test still go out |### Run behind a reverse proxy-Publish the container on loopback, terminate TLS in front of it, and set `PENGUIN_TRUST_PROXY=1`. The proxy must set or strip `x-forwarded-proto` itself. That header comes from the caller, which is exactly why the server ignores it until you tell it otherwise. If you leave `PENGUIN_TRUST_PROXY` unset on an HTTPS deployment, session cookies are issued without the `Secure` flag.+Publish the container on loopback, terminate TLS in front of it, and set `ADELIE_TRUST_PROXY=1`. The proxy must set or strip `x-forwarded-proto` itself. That header comes from the caller, which is exactly why the server ignores it until you tell it otherwise. If you leave `ADELIE_TRUST_PROXY` unset on an HTTPS deployment, session cookies are issued without the `Secure` flag.### Serve Workspace previews-Previews of the HTML a Task produces are served from a separate origin when there is one. On a non-loopback bind there is no loopback counterpart to derive, so previews fall back to a same-origin sandbox, where cookies, `localStorage` and third-party embeds do not work. To get the isolated previews back, point `PENGUIN_PREVIEW_ORIGIN` at a second hostname routed to the same container. It must differ by hostname, not just by port.+Previews of the HTML a Task produces are served from a separate origin when there is one. On a non-loopback bind there is no loopback counterpart to derive, so previews fall back to a same-origin sandbox, where cookies, `localStorage` and third-party embeds do not work. To get the isolated previews back, point `ADELIE_PREVIEW_ORIGIN` at a second hostname routed to the same container. It must differ by hostname, not just by port.## Upgrade the container@@ -195,7 +195,7 @@ The reset needs no other authorization: the data root is the authorization, and## Next steps-- [Web App](/web-app): use PenguinHarness from the browser.-- [Update PenguinHarness](/updates): check your version and upgrade.+- [Web App](/web-app): use Adelie from the browser.+- [Update Adelie](/updates): check your version and upgrade.- [Security Model](/security): who can do what, and on the strength of which proof.- [Configuration Reference](/configuration): every environment variable and config field.diff --git a/packages/docs/content/quickstart-docker.zh.md b/packages/docs/content/quickstart-docker.zh.mdindex a7ddd8d6..7b4d5e6c 100644--- a/packages/docs/content/quickstart-docker.zh.md+++ b/packages/docs/content/quickstart-docker.zh.md@@ -1,13 +1,13 @@---title: Docker-description: 运行官方 PenguinHarness 镜像,一个容器加一个数据卷,就在 7364 端口提供完整的 Web App。+description: 运行官方 Adelie 镜像,一个容器加一个数据卷,就在 7364 端口提供完整的 Web App。----官方镜像运行的就是 `penguin server` 启动的那个服务端,Web App 也在其中。整套部署只有一个容器和一个数据卷,所以要把 PenguinHarness 装到自己电脑以外的机器上,Docker 是最短的一条路。+官方镜像运行的就是 `penguin server` 启动的那个服务端,Web App 也在其中。整套部署只有一个容器和一个数据卷,所以要把 Adelie 装到自己电脑以外的机器上,Docker 是最短的一条路。## 开始之前-- 在要运行 PenguinHarness 的机器上装好 Docker。下面的示例同时给出 Docker Compose 和 `docker run` 两种写法。+- 在要运行 Adelie 的机器上装好 Docker。下面的示例同时给出 Docker Compose 和 `docker run` 两种写法。- 一个模型供应商的 API Key。## 启动容器@@ -78,14 +78,14 @@ docker compose logs penguin # or: docker logs penguin```yamlenvironment:- PENGUIN_SEED_ADMIN_PASSWORD: "choose-something-long"+ ADELIE_SEED_ADMIN_PASSWORD: "choose-something-long"```服务端会用这个密码(至少 8 个字符)创建内置的 `admin` 账号,并且不再打印登录提示。这个变量只在还没有任何用户时生效,也就是空数据目录第一次启动的时候。给已经认领过的数据目录加上它不会有任何效果,事后修改同样无效。## 配置模型-PenguinHarness 不内置任何模型凭据。可以在 Web App 的**模型库**页面添加模型,也可以在容器里用 CLI 添加:+Adelie 不内置任何模型凭据。可以在 Web App 的**模型库**页面添加模型,也可以在容器里用 CLI 添加:```bashdocker compose exec -u penguin penguin \@@ -152,21 +152,21 @@ USER penguin| 变量 | 在本镜像中 || --- | --- |-| `PENGUIN_HOME` | `/data`。除非同时移动数据卷,否则不要修改 |+| `ADELIE_HOME` | `/data`。除非同时移动数据卷,否则不要修改 || `HOST` | `0.0.0.0`,作用于容器自己的网络命名空间。宿主机一侧由 `-p` 决定,示例都保持在回环接口上 || `PORT` | `7364`。修改后,健康检查会随之改用新端口 |-| `PENGUIN_SEED_ADMIN_PASSWORD` | 固定初始管理员密码,仅在首次启动时生效,见[提前设置密码](#提前设置密码) |-| `PENGUIN_TRUST_PROXY` | 放在终结 TLS 的反向代理之后时设为 `1`,会话 Cookie 才会带上 `Secure` 标记 |-| `PENGUIN_PREVIEW_ORIGIN` | 路由到同一容器的第二个主机名,用于 Workspace 中的 HTML 预览 |-| `PENGUIN_UPDATE_CHECK` | 设为 `off` 关闭自动的版本检查。模型请求、远程控制连接、Key 授权和代理测试照常出站 |+| `ADELIE_SEED_ADMIN_PASSWORD` | 固定初始管理员密码,仅在首次启动时生效,见[提前设置密码](#提前设置密码) |+| `ADELIE_TRUST_PROXY` | 放在终结 TLS 的反向代理之后时设为 `1`,会话 Cookie 才会带上 `Secure` 标记 |+| `ADELIE_PREVIEW_ORIGIN` | 路由到同一容器的第二个主机名,用于 Workspace 中的 HTML 预览 |+| `ADELIE_UPDATE_CHECK` | 设为 `off` 关闭自动的版本检查。模型请求、远程控制连接、Key 授权和代理测试照常出站 |### 在反向代理后运行-把容器发布在回环接口上,在它前面终结 TLS,并设置 `PENGUIN_TRUST_PROXY=1`。反向代理必须自己设置或清除 `x-forwarded-proto`:这个请求头由调用方提供,服务端正因如此,在你明确开启之前一直不采信它。HTTPS 部署如果不设置 `PENGUIN_TRUST_PROXY`,签发的会话 Cookie 就不带 `Secure` 标记。+把容器发布在回环接口上,在它前面终结 TLS,并设置 `ADELIE_TRUST_PROXY=1`。反向代理必须自己设置或清除 `x-forwarded-proto`:这个请求头由调用方提供,服务端正因如此,在你明确开启之前一直不采信它。HTTPS 部署如果不设置 `ADELIE_TRUST_PROXY`,签发的会话 Cookie 就不带 `Secure` 标记。### 提供 Workspace 预览-Task 生成的 HTML 在有独立来源时,会从独立的来源提供预览。绑定在非回环地址上时,推导不出对应的回环地址,预览会退回同源沙箱,这时 Cookie、`localStorage` 和第三方嵌入内容都不能用。要恢复隔离的预览,把 `PENGUIN_PREVIEW_ORIGIN` 指向路由到同一容器的第二个主机名。它必须在主机名上有所不同,只换端口不行。+Task 生成的 HTML 在有独立来源时,会从独立的来源提供预览。绑定在非回环地址上时,推导不出对应的回环地址,预览会退回同源沙箱,这时 Cookie、`localStorage` 和第三方嵌入内容都不能用。要恢复隔离的预览,把 `ADELIE_PREVIEW_ORIGIN` 指向路由到同一容器的第二个主机名。它必须在主机名上有所不同,只换端口不行。## 升级容器@@ -195,7 +195,7 @@ docker compose start penguin## 下一步-- [Web App](/web-app):在浏览器里使用 PenguinHarness。-- [更新 PenguinHarness](/updates):查看版本并升级。+- [Web App](/web-app):在浏览器里使用 Adelie。+- [更新 Adelie](/updates):查看版本并升级。- [安全模型](/security):谁能做什么,凭的是什么。- [配置参考](/configuration):全部环境变量与配置字段。diff --git a/packages/docs/content/quickstart-sdk.en.md b/packages/docs/content/quickstart-sdk.en.mdindex e75689ee..2796a1a0 100644--- a/packages/docs/content/quickstart-sdk.en.md+++ b/packages/docs/content/quickstart-sdk.en.md@@ -20,7 +20,7 @@ npm install @adelie/core## Configure a model-The SDK reads the same data root as the desktop app and the CLI, `~/.penguin/data`. A model configured in the [desktop app](/quickstart-desktop) or the [CLI](/quickstart-cli) is immediately usable, so there is nothing to configure twice.+The SDK reads the same data root as the desktop app and the CLI, `~/.adelie/data`. A model configured in the [desktop app](/quickstart-desktop) or the [CLI](/quickstart-cli) is immediately usable, so there is nothing to configure twice.If this machine has no model configured yet, the shortest path is to install the CLI and configure one there:diff --git a/packages/docs/content/quickstart-sdk.zh.md b/packages/docs/content/quickstart-sdk.zh.mdindex 3c047a60..8c960a79 100644--- a/packages/docs/content/quickstart-sdk.zh.md+++ b/packages/docs/content/quickstart-sdk.zh.md@@ -20,7 +20,7 @@ npm install @adelie/core## 配置模型-SDK 与桌面应用、CLI 读取同一个数据目录 `~/.penguin/data`。在[桌面应用](/quickstart-desktop)或 [CLI](/quickstart-cli) 里配置好的模型,SDK 可以直接使用,不需要重复配置。+SDK 与桌面应用、CLI 读取同一个数据目录 `~/.adelie/data`。在[桌面应用](/quickstart-desktop)或 [CLI](/quickstart-cli) 里配置好的模型,SDK 可以直接使用,不需要重复配置。如果这台机器上还没有配置过模型,最省事的办法是装上 CLI,在 CLI 里配置一次:diff --git a/packages/docs/content/quickstart.en.md b/packages/docs/content/quickstart.en.mdindex 17a6601d..27327787 100644--- a/packages/docs/content/quickstart.en.md+++ b/packages/docs/content/quickstart.en.md@@ -1,13 +1,13 @@---title: Quickstart-description: Pick one of four routes, the desktop app, the CLI and Web App, Docker, or the SDK, to install PenguinHarness and run your first Task.+description: Pick one of four routes, the desktop app, the CLI and Web App, Docker, or the SDK, to install Adelie and run your first Task.----PenguinHarness has four ways in: the desktop app, the CLI and Web App, Docker, and the SDK. They run the same engine and differ only in how you meet it. Pick the route that fits you; each route's page takes you all the way to a first Task.+Adelie has four ways in: the desktop app, the CLI and Web App, Docker, and the SDK. They run the same engine and differ only in how you meet it. Pick the route that fits you; each route's page takes you all the way to a first Task.## Before you begin-PenguinHarness ships with no built-in model credentials, so you configure a model before your first Task. An API key for one provider is enough, and each route's page covers this step.+Adelie ships with no built-in model credentials, so you configure a model before your first Task. An API key for one provider is enough, and each route's page covers this step.A model is always referenced as a `(provider, model_id)` pair; the provider is never inferred from the model id. See [Models & Providers](/models) for the built-in groups.@@ -15,7 +15,7 @@ A model is always referenced as a `(provider, model_id)` pair; the provider is n| Route | Best for | Terminal needed? || --- | --- | --- |-| [Desktop app](/quickstart-desktop) | Using PenguinHarness as a product, straight away | No, and it installs the `penguin` command for you |+| [Desktop app](/quickstart-desktop) | Using Adelie as a product, straight away | No, and it installs the `penguin` command for you || [CLI and Web App](/quickstart-cli) | Servers and remote machines, or wanting the `penguin` command | Once, to install || [Docker](/quickstart-docker) | A server you deploy rather than install, with one container and one volume | Once, to start it || [SDK](/quickstart-sdk) | Embedding the engine in your own TypeScript program | Yes |@@ -24,7 +24,7 @@ If you are unsure, take the [desktop app](/quickstart-desktop). It has the fewes## What all routes share-- **One data root**: `~/.penguin/data` (`%USERPROFILE%\.penguin\data` on Windows; `/data` inside the container). Agents, model configuration and past Sessions live there, so routes on the same machine can be mixed freely: a model configured in the desktop app is immediately usable from the CLI and the SDK.+- **One data root**: `~/.adelie/data` (`%USERPROFILE%\.adelie\data` on Windows; `/data` inside the container). Agents, model configuration and past Sessions live there, so routes on the same machine can be mixed freely: a model configured in the desktop app is immediately usable from the CLI and the SDK.- **One server at a time**: a data root only ever runs one server process. If you already started one with `penguin web`, the desktop app attaches to it instead of starting a second one.- **One interface**: the desktop app and `penguin web` open the same Web App. The desktop app embeds the server and skips the login.diff --git a/packages/docs/content/quickstart.zh.md b/packages/docs/content/quickstart.zh.mdindex 621663a6..e5ea1e99 100644--- a/packages/docs/content/quickstart.zh.md+++ b/packages/docs/content/quickstart.zh.md@@ -1,13 +1,13 @@---title: 快速开始-description: 在桌面应用、命令行与 Web App、Docker、SDK 四条路线中任选一条,安装 PenguinHarness 并跑通第一个 Task。+description: 在桌面应用、命令行与 Web App、Docker、SDK 四条路线中任选一条,安装 Adelie 并跑通第一个 Task。----PenguinHarness 有四条入口:桌面应用、命令行与 Web App、Docker 和 SDK。它们背后是同一个引擎,区别只在于你以什么方式接触它。挑一条适合自己的路线,每条路线的页面都会一路带你跑通第一个 Task。+Adelie 有四条入口:桌面应用、命令行与 Web App、Docker 和 SDK。它们背后是同一个引擎,区别只在于你以什么方式接触它。挑一条适合自己的路线,每条路线的页面都会一路带你跑通第一个 Task。## 开始之前-PenguinHarness 不内置任何模型凭据,跑第一个 Task 之前要先配置一个模型。准备好一个供应商的 API Key 即可,每条路线的页面都包含这一步。+Adelie 不内置任何模型凭据,跑第一个 Task 之前要先配置一个模型。准备好一个供应商的 API Key 即可,每条路线的页面都包含这一步。模型始终以 `(provider, model_id)` 二元组引用,供应商绝不由模型 id 推断。内置分组见[模型与 Provider](/models)。@@ -15,7 +15,7 @@ PenguinHarness 不内置任何模型凭据,跑第一个 Task 之前要先配| 路线 | 适合 | 需要终端吗? || --- | --- | --- |-| [桌面应用](/quickstart-desktop) | 想直接把 PenguinHarness 当作产品来用 | 不需要,而且它会替你装好 `penguin` 命令 |+| [桌面应用](/quickstart-desktop) | 想直接把 Adelie 当作产品来用 | 不需要,而且它会替你装好 `penguin` 命令 || [命令行与 Web App](/quickstart-cli) | 装到服务器或远程机器上,或者想要 `penguin` 命令 | 安装时用一次 || [Docker](/quickstart-docker) | 部署而非安装的服务端:一个容器、一个卷 | 启动时用一次 || [SDK](/quickstart-sdk) | 把引擎嵌入自己的 TypeScript 程序 | 需要 |@@ -24,7 +24,7 @@ PenguinHarness 不内置任何模型凭据,跑第一个 Task 之前要先配## 各条路线的共同点-- **同一个数据目录**:`~/.penguin/data`(Windows 为 `%USERPROFILE%\.penguin\data`,容器内为 `/data`)。Agent、模型配置和历史会话都在其中,所以同一台机器上的几条路线可以随意混用:在桌面应用里配好的模型,CLI 和 SDK 立刻就能用。+- **同一个数据目录**:`~/.adelie/data`(Windows 为 `%USERPROFILE%\.adelie\data`,容器内为 `/data`)。Agent、模型配置和历史会话都在其中,所以同一台机器上的几条路线可以随意混用:在桌面应用里配好的模型,CLI 和 SDK 立刻就能用。- **同一时刻只有一个服务端**:一个数据目录只运行一个服务端进程。如果你已经用 `penguin web` 启动了一个,桌面应用会直接接入它,而不会再启动第二个。- **同一套界面**:桌面应用与 `penguin web` 打开的是同一个 Web App,只是桌面应用内嵌了服务端,并免去了登录。diff --git a/packages/docs/content/remote-control.en.md b/packages/docs/content/remote-control.en.mdindex e9dbc8e0..873eb250 100644--- a/packages/docs/content/remote-control.en.md+++ b/packages/docs/content/remote-control.en.md@@ -3,7 +3,7 @@ title: Remote controldescription: Connect a conversation to a Feishu, Telegram, QQ or WeChat bot, and talk to its agent from that app.----Remote control connects one conversation to a bot on Feishu, Telegram, QQ or WeChat. Messages you send to the bot go into the conversation exactly as if you had typed them in the Web App, and the agent's replies are sent back to the chat. PenguinHarness opens the connection to the messaging platform itself, so you need no public address or callback URL.+Remote control connects one conversation to a bot on Feishu, Telegram, QQ or WeChat. Messages you send to the bot go into the conversation exactly as if you had typed them in the Web App, and the agent's replies are sent back to the chat. Adelie opens the connection to the messaging platform itself, so you need no public address or callback URL.- To connect a bot, follow the section for your app: [Connect Feishu](#connect-feishu), [Connect Telegram](#connect-telegram), [Connect QQ](#connect-qq) or [Connect WeChat](#connect-wechat).- To learn what arrives where once a bot is connected, see [After you connect](#after-you-connect).@@ -13,7 +13,7 @@ Remote control connects one conversation to a bot on Feishu, Telegram, QQ or WeC- **The conversation has started.** Remote control belongs to a conversation, and a conversation exists only after its first message. In a new, unsent chat, the panel shows "Available once the conversation starts".- **You are the Project owner.** Only the owner can save credentials, scan a QR code, and turn a connection on or off. Other members can open the settings, see the status, and run the tests.-- **PenguinHarness is running.** The connection lives in the PenguinHarness server or desktop app. While it is stopped, the bot does not answer.+- **Adelie is running.** The connection lives in the Adelie server or desktop app. While it is stopped, the bot does not answer.## Open remote control@@ -66,7 +66,7 @@ A saved secret is never shown again. Leave its field empty to keep it. To delete1. In the [Feishu developer console](https://open.feishu.cn/app), create a self-built app.2. Enable the bot capability for the app.3. Subscribe to the message-receive event, and set the subscription mode to long connection.-4. In PenguinHarness, open **Remote control** for the conversation and select the **Feishu** tab.+4. In Adelie, open **Remote control** for the conversation and select the **Feishu** tab.5. From the app's credentials page, copy the App ID and App Secret into **App ID** and **App Secret**.6. If you use Lark, change **API domain** to `https://open.larksuite.com`. The default, `https://open.feishu.cn`, is for Feishu.7. Select **Save**.@@ -86,7 +86,7 @@ To receive images and files, the Feishu app needs the permission to read message1. In Telegram, open [@BotFather](https://t.me/BotFather) and send `/newbot` to create a bot.2. Name the bot as prompted, and copy the Bot Token that @BotFather returns.-3. In PenguinHarness, open **Remote control** for the conversation and select the **Telegram** tab.+3. In Adelie, open **Remote control** for the conversation and select the **Telegram** tab.4. Paste the token into **Bot Token**. A Bot Token looks like `<digits>:<secret>`.5. Select **Save**.6. Turn on **Enable connection**, and wait for **Connected**.@@ -96,7 +96,7 @@ To receive images and files, the Feishu app needs the permission to read messageIn a forum group, replies stay in the topic the message came from. Telegram channel posts are not supported; the bot handles groups and direct chats.-A Bot Token can serve only one program at a time. Do not use the same token in another PenguinHarness server or bot script while the connection is on.+A Bot Token can serve only one program at a time. Do not use the same token in another Adelie server or bot script while the connection is on.## Connect QQ@@ -106,21 +106,21 @@ A Bot Token can serve only one program at a time. Do not use the same token in a- In the bot's development settings, the event subscription mode is set to WebSocket, with the callback URL left empty.- Your own QQ account, or a test group, is on the bot's sandbox allowlist.-You can give PenguinHarness the bot's credentials by scanning a QR code or by entering them by hand.+You can give Adelie the bot's credentials by scanning a QR code or by entering them by hand.### Connect with a QR code-1. In PenguinHarness, open **Remote control** for the conversation and select the **QQ** tab.+1. In Adelie, open **Remote control** for the conversation and select the **QQ** tab.2. Select **Connect by QR**.3. Scan the code with QQ on your phone.-4. On the page that opens, pick the bot to authorize, and confirm. PenguinHarness saves the credentials and shows "Saved the credentials for bot {appId} — the connection can be enabled now".+4. On the page that opens, pick the bot to authorize, and confirm. Adelie saves the credentials and shows "Saved the credentials for bot {appId} — the connection can be enabled now".5. Turn on **Enable connection**, and wait for **Connected**.6. In QQ, find the bot and send it a message.### Enter the credentials by hand1. On the QQ open platform, copy the App ID and App Secret from the bot's development settings page.-2. In PenguinHarness, open **Remote control**, select the **QQ** tab, and under **Or enter them by hand**, fill in **App ID** and **App Secret**.+2. In Adelie, open **Remote control**, select the **QQ** tab, and under **Or enter them by hand**, fill in **App ID** and **App Secret**.3. Select **Save**.4. Turn on **Enable connection**, and wait for **Connected**.5. In QQ, find the bot and send it a message.@@ -140,11 +140,11 @@ This rule shapes how QQ behaves:WeChat connects through its official bot channel. There is no console and nothing to register: you scan a QR code, and the credential is saved for you.-1. In PenguinHarness, open **Remote control** for the conversation and select the **WeChat** tab.+1. In Adelie, open **Remote control** for the conversation and select the **WeChat** tab.2. Select **Connect by scanning** to generate a QR code.3. Scan the code with WeChat on your phone.4. If your phone shows a number, type it into **Pairing code** and select **Confirm**.-5. Confirm the authorization on your phone. PenguinHarness saves the credential and shows "Saved the credential for bot {botId} — the connection can be enabled now".+5. Confirm the authorization on your phone. Adelie saves the credential and shows "Saved the credential for bot {botId} — the connection can be enabled now".6. Turn on **Enable connection**, and wait for **Connected**.7. Wait about 15 seconds.8. Find the bot in WeChat and send it a message. If you get no reply, send the message again.@@ -182,7 +182,7 @@ A connected conversation shows a paper-plane icon on its row in the sidebar. Poi### Approvals-Tool approvals cannot be answered from the chat. When a tool call needs approval, the bot sends "A tool call is waiting for your approval in the PenguinHarness web UI." Approve or deny it in the Web App.+Tool approvals cannot be answered from the chat. When a tool call needs approval, the bot sends "A tool call is waiting for your approval in the Adelie web UI." Approve or deny it in the Web App.Whether a tool call needs approval depends on the conversation's [approval mode](/tools#approval). New conversations start in **Approve everything**, which asks for nothing, so read [Security](#security) before you bind a bot to one.@@ -236,7 +236,7 @@ Credentials are stored on the server and never sent back to the browser in full.**Telegram: the bot ignores messages in a group.** Telegram's Group Privacy is on by default. Under it, a bot that is not a group administrator receives only commands addressed to it and replies to its own messages. Either make the bot an administrator of the group, or turn Group Privacy off with `/setprivacy` in @BotFather and then remove the bot from the group and add it back. A group the bot is already in does not pick up the privacy change until you do.-**Telegram: another program is polling.** A Bot Token serves one program at a time. Close the other PenguinHarness server or script that uses the token, or give this conversation its own bot. A `getUpdates` call you run by hand counts as another program too, so turn off the connection before running one.+**Telegram: another program is polling.** A Bot Token serves one program at a time. Close the other Adelie server or script that uses the token, or give this conversation its own bot. A `getUpdates` call you run by hand counts as another program too, so turn off the connection before running one.**Telegram: the panel says no message has arrived.** That line covers only the current connection. Turning the connection off and on, or saving the credentials, starts a new one. Send a fresh message. If nothing arrives, check that the bot is still in the group and that nothing else is polling the token.diff --git a/packages/docs/content/remote-control.zh.md b/packages/docs/content/remote-control.zh.mdindex 466de543..46275fe7 100644--- a/packages/docs/content/remote-control.zh.md+++ b/packages/docs/content/remote-control.zh.md@@ -3,7 +3,7 @@ title: 远程控制description: 把对话连接到飞书、Telegram、QQ 或微信机器人,在聊天应用里直接和 Agent 对话。----远程控制把一个对话连接到飞书、Telegram、QQ 或微信上的机器人。发给机器人的消息会进入这个对话,效果和在 Web App 里输入完全一样;Agent 的回复也会发回聊天里。连接由 PenguinHarness 主动向消息平台发起,所以不需要公网地址或回调 URL。+远程控制把一个对话连接到飞书、Telegram、QQ 或微信上的机器人。发给机器人的消息会进入这个对话,效果和在 Web App 里输入完全一样;Agent 的回复也会发回聊天里。连接由 Adelie 主动向消息平台发起,所以不需要公网地址或回调 URL。- 连接机器人:按所用的应用查看[连接飞书](#连接飞书)、[连接 Telegram](#连接-telegram)、[连接 QQ](#连接-qq) 或[连接微信](#连接微信)。- 了解连接之后消息怎么流转:见[连接之后](#连接之后)。@@ -13,7 +13,7 @@ description: 把对话连接到飞书、Telegram、QQ 或微信机器人,在- **对话已经开始。** 远程控制属于某个对话,而对话要在发出第一条消息后才存在。新建但还没发消息的对话里,面板会显示「发送第一条消息后可用」。- **你是 Project owner。** 只有 owner 能保存凭证、扫码,以及开启或关闭连接。其他成员可以打开设置、查看状态和运行测试。-- **PenguinHarness 正在运行。** 连接运行在 PenguinHarness 服务端或桌面应用里,它们停止运行时,机器人不会应答。+- **Adelie 正在运行。** 连接运行在 Adelie 服务端或桌面应用里,它们停止运行时,机器人不会应答。## 打开远程控制@@ -66,7 +66,7 @@ description: 把对话连接到飞书、Telegram、QQ 或微信机器人,在1. 在[飞书开发者后台](https://open.feishu.cn/app)创建一个企业自建应用。2. 为应用开通机器人能力。3. 订阅「接收消息」事件,事件订阅方式选择「长连接」。-4. 在 PenguinHarness 中打开这个对话的**远程控制**,选择**飞书**标签页。+4. 在 Adelie 中打开这个对话的**远程控制**,选择**飞书**标签页。5. 在应用的「凭证与基础信息」页取得 App ID 和 App Secret,分别填入 **App ID** 和 **App Secret**。6. 如果用的是 Lark,把 **API 域名**改为 `https://open.larksuite.com`。默认值 `https://open.feishu.cn` 对应飞书。7. 选择**保存**。@@ -86,7 +86,7 @@ description: 把对话连接到飞书、Telegram、QQ 或微信机器人,在1. 在 Telegram 中打开 [@BotFather](https://t.me/BotFather),发送 `/newbot` 创建机器人。2. 按提示给机器人取名,复制 @BotFather 返回的 Bot Token。-3. 在 PenguinHarness 中打开这个对话的**远程控制**,选择 **Telegram** 标签页。+3. 在 Adelie 中打开这个对话的**远程控制**,选择 **Telegram** 标签页。4. 把 Token 粘贴到 **Bot Token**。Bot Token 形如 `<digits>:<secret>`。5. 选择**保存**。6. 打开**启用连接**,等状态变为**已连接**。@@ -96,7 +96,7 @@ description: 把对话连接到飞书、Telegram、QQ 或微信机器人,在在开启了话题的群组里,回复会留在消息所在的话题中。Telegram 频道的贴文不受支持,机器人只处理群聊和单聊。-一个 Bot Token 同一时刻只能供一个程序使用。连接开启期间,不要在另一个 PenguinHarness 服务端或机器人脚本里使用同一个 Token。+一个 Bot Token 同一时刻只能供一个程序使用。连接开启期间,不要在另一个 Adelie 服务端或机器人脚本里使用同一个 Token。## 连接 QQ@@ -106,21 +106,21 @@ description: 把对话连接到飞书、Telegram、QQ 或微信机器人,在- 机器人的「开发配置」里,事件订阅方式已设为 WebSocket,回调地址留空。- 你自己的 QQ 号或某个测试群已经加入机器人的沙箱白名单。-机器人的凭证可以扫码交给 PenguinHarness,也可以手动填写。+机器人的凭证可以扫码交给 Adelie,也可以手动填写。### 扫码连接-1. 在 PenguinHarness 中打开这个对话的**远程控制**,选择 **QQ** 标签页。+1. 在 Adelie 中打开这个对话的**远程控制**,选择 **QQ** 标签页。2. 选择**扫码连接**。3. 用手机 QQ 扫描二维码。-4. 在打开的页面里选择要授权的机器人并确认。PenguinHarness 会保存凭证,并显示「已保存机器人 {appId} 的凭据,可以启用连接了」。+4. 在打开的页面里选择要授权的机器人并确认。Adelie 会保存凭证,并显示「已保存机器人 {appId} 的凭据,可以启用连接了」。5. 打开**启用连接**,等状态变为**已连接**。6. 在 QQ 中找到这个机器人,给它发一条消息。### 手动填写凭证1. 在 QQ 开放平台机器人的「开发设置」页,复制 App ID 和 App Secret。-2. 在 PenguinHarness 中打开**远程控制**,选择 **QQ** 标签页,在**或手动填写**下方填入 **App ID** 和 **App Secret**。+2. 在 Adelie 中打开**远程控制**,选择 **QQ** 标签页,在**或手动填写**下方填入 **App ID** 和 **App Secret**。3. 选择**保存**。4. 打开**启用连接**,等状态变为**已连接**。5. 在 QQ 中找到这个机器人,给它发一条消息。@@ -140,11 +140,11 @@ description: 把对话连接到飞书、Telegram、QQ 或微信机器人,在微信通过官方的机器人通道连接。不需要后台,也不用注册:扫码之后,凭证会自动保存。-1. 在 PenguinHarness 中打开这个对话的**远程控制**,选择**微信**标签页。+1. 在 Adelie 中打开这个对话的**远程控制**,选择**微信**标签页。2. 选择**扫码连接**,生成二维码。3. 用手机微信扫描二维码。4. 如果手机上显示了一组数字,把它填入**配对码**,然后选择**确认**。-5. 在手机上确认授权。PenguinHarness 会保存凭证,并显示「已保存机器人 {botId} 的凭据,可以启用连接了」。+5. 在手机上确认授权。Adelie 会保存凭证,并显示「已保存机器人 {botId} 的凭据,可以启用连接了」。6. 打开**启用连接**,等状态变为**已连接**。7. 等待约 15 秒。8. 在微信里找到这个机器人,给它发一条消息。如果没有收到回复,再发一次。@@ -236,7 +236,7 @@ description: 把对话连接到飞书、Telegram、QQ 或微信机器人,在**Telegram:机器人不理会群里的消息。** Telegram 的 Group Privacy 默认开启。开启时,不担任群管理员的机器人只能收到明确发给它的命令,以及对它自己消息的回复。解决办法有两个:把机器人设为这个群的管理员;或者在 @BotFather 里用 `/setprivacy` 关闭 Group Privacy,再把机器人移出群、重新拉进来。机器人已经在的群,不做这一步就不会应用隐私设置的变更。-**Telegram:提示有其他程序在轮询。** 一个 Bot Token 同一时刻只能供一个程序使用。关掉正在用这个 Token 的另一个 PenguinHarness 服务端或脚本,或者给这个对话单独建一个机器人。手动调用 `getUpdates` 也算另一个程序,调用之前先关闭连接。+**Telegram:提示有其他程序在轮询。** 一个 Bot Token 同一时刻只能供一个程序使用。关掉正在用这个 Token 的另一个 Adelie 服务端或脚本,或者给这个对话单独建一个机器人。手动调用 `getUpdates` 也算另一个程序,调用之前先关闭连接。**Telegram:面板显示还没有收到过消息。** 这一行只统计当前这条连接。关闭再开启连接,或者再保存一次凭证,都会开启一条新连接。先重新发一条消息。如果仍然显示没有收到,检查机器人是否还在群里,以及有没有别的程序在轮询这个 Token。diff --git a/packages/docs/content/schedules.en.md b/packages/docs/content/schedules.en.mdindex 60f76fe2..034db8de 100644--- a/packages/docs/content/schedules.en.md+++ b/packages/docs/content/schedules.en.md@@ -100,7 +100,7 @@ Nothing on the overview creates, edits or deletes a task: creating one picks an## Limits- A repeating task runs at most once every 5 minutes: the shortest period is 5 minutes. A shorter period makes the task invalid.-- Tasks run only while the PenguinHarness service is running.+- Tasks run only while the Adelie service is running.- Missed runs are not made up. When a fire time passes while the service is stopped, a repeating task skips it and a one-off task is marked missed.## How it worksdiff --git a/packages/docs/content/schedules.zh.md b/packages/docs/content/schedules.zh.mdindex 602ad0c2..d16f6b17 100644--- a/packages/docs/content/schedules.zh.md+++ b/packages/docs/content/schedules.zh.md@@ -100,7 +100,7 @@ Project 的所有成员都可以用这种方式创建任务。创建由这段对## 限制- 周期性任务最快每 5 分钟运行一次,即最短周期为 5 分钟。周期短于 5 分钟的任务会被判为无效。-- 定时任务只在 PenguinHarness 服务运行期间执行。+- 定时任务只在 Adelie 服务运行期间执行。- 错过的运行不会补跑。服务停止期间错过的触发时间,周期性任务直接跳过,一次性任务标记为已错过。## 工作原理diff --git a/packages/docs/content/security.en.md b/packages/docs/content/security.en.mdindex 1ce79ee2..51909c54 100644--- a/packages/docs/content/security.en.md+++ b/packages/docs/content/security.en.md@@ -1,9 +1,9 @@---title: Security Model-description: How access to PenguinHarness works, from claiming a fresh server to revoking sessions, plus the mechanics underneath.+description: How access to Adelie works, from claiming a fresh server to revoking sessions, plus the mechanics underneath.----PenguinHarness runs agents with real credentials on real machines, so it is worth knowing exactly who can do what, and on what proof. This page follows the scenarios in the order you meet them, and collects the mechanics (session tokens, what is on disk, the network surface) at the end.+Adelie runs agents with real credentials on real machines, so it is worth knowing exactly who can do what, and on what proof. This page follows the scenarios in the order you meet them, and collects the mechanics (session tokens, what is on disk, the network surface) at the end.- **First start of a new server?** See [Claim a fresh server](#claim-a-fresh-server).- **Need to set, change, or recover a password?** See [Manage passwords](#manage-passwords).@@ -13,7 +13,7 @@ PenguinHarness runs agents with real credentials on real machines, so it is wortOne principle runs through every scenario:-> **Reading the data root is ownership.** The data root (`~/.penguin/data` by default) holds every model credential and every conversation. A secret stored beside them could not protect them from someone who can already read them, so the model never pretends otherwise. Instead, it makes that ownership safe to use: short-lived, revocable, and never requiring a password to be stored or sent.+> **Reading the data root is ownership.** The data root (`~/.adelie/data` by default) holds every model credential and every conversation. A secret stored beside them could not protect them from someone who can already read them, so the model never pretends otherwise. Instead, it makes that ownership safe to use: short-lived, revocable, and never requiring a password to be stored or sent.## What you get@@ -66,7 +66,7 @@ The link is not one-shot, because a mail client may fetch it before you do and a> [!NOTE]> In a container, the notice goes to the container's log (`docker logs`). The `localhost` in the link is the server's own view of itself. With the documented loopback port mapping, that is your view too, so open the link as printed on the machine running Docker. If the container is published to a network, replace `localhost` with the host you reach it on. Keep the token as it is either way.-`PENGUIN_SEED_ADMIN_PASSWORD` pins the password instead, but only on the first start with an empty data root.+`ADELIE_SEED_ADMIN_PASSWORD` pins the password instead, but only on the first start with an empty data root.The session the link grants carries `via: setup`. It has exactly one special allowance, setting a password without entering an old one (none exists), and nothing else; in particular, it gets none of the desktop-only routes.@@ -165,7 +165,7 @@ Each cookie carries a 32-byte random token. The session is the `auth_sessions` rA browser session lasts 30 days. Using it a day or more after it was issued or last renewed renews it **in place** for another 30 days: the row's expiry moves, and the cookie value stays the same. The 30 days therefore act as an idle timeout: a session in regular use never expires, and there is never a second copy to chase. Only a session whose own lifetime reaches the renewal window slides, so a one-hour minted token expires after its hour.-Cookies are HttpOnly and SameSite=Lax. They are also Secure when the request really is https, or when a **trusted** proxy says so (`PENGUIN_TRUST_PROXY=1`); by default the `x-forwarded-proto` header is ignored.+Cookies are HttpOnly and SameSite=Lax. They are also Secure when the request really is https, or when a **trusted** proxy says so (`ADELIE_TRUST_PROXY=1`); by default the `x-forwarded-proto` header is ignored.### What is on diskdiff --git a/packages/docs/content/security.zh.md b/packages/docs/content/security.zh.mdindex de2d8d00..77b9d616 100644--- a/packages/docs/content/security.zh.md+++ b/packages/docs/content/security.zh.md@@ -1,9 +1,9 @@---title: 安全模型-description: PenguinHarness 的访问机制如何运作:从认领新服务器到收回会话,以及底层的实现细节。+description: Adelie 的访问机制如何运作:从认领新服务器到收回会话,以及底层的实现细节。----PenguinHarness 用真实凭据在真实机器上运行 Agent,所以值得弄清楚:谁能做什么,凭什么。本页按你遇到这些场景的顺序依次讲解,最后集中说明底层机制(会话令牌、磁盘内容、网络暴露面)。+Adelie 用真实凭据在真实机器上运行 Agent,所以值得弄清楚:谁能做什么,凭什么。本页按你遇到这些场景的顺序依次讲解,最后集中说明底层机制(会话令牌、磁盘内容、网络暴露面)。- **第一次启动新服务器?** 参见[认领新服务器](#认领新服务器)。- **需要设置、修改或找回密码?** 参见[管理密码](#管理密码)。@@ -13,7 +13,7 @@ PenguinHarness 用真实凭据在真实机器上运行 Agent,所以值得弄所有场景都贯穿着同一条原则:-> **能读到数据根目录,就等于拥有它。** 数据根目录(默认为 `~/.penguin/data`)存放着全部模型凭据和全部对话。在它们旁边再藏一个秘密,也拦不住本来就能读到这些内容的人,所以这套安全模型从不假装做得到。它做的反而是让这种所有权可以放心使用:有效期短、随时可收回,而且从不要求存储或发送密码。+> **能读到数据根目录,就等于拥有它。** 数据根目录(默认为 `~/.adelie/data`)存放着全部模型凭据和全部对话。在它们旁边再藏一个秘密,也拦不住本来就能读到这些内容的人,所以这套安全模型从不假装做得到。它做的反而是让这种所有权可以放心使用:有效期短、随时可收回,而且从不要求存储或发送密码。## 功能一览@@ -66,7 +66,7 @@ PenguinHarness 用真实凭据在真实机器上运行 Agent,所以值得弄> [!NOTE]> 在容器里,这条提示输出到容器日志(`docker logs`)。链接中的 `localhost` 是服务器眼中的自己。按文档给出的回环端口映射来部署时,这也是你眼中的它,所以在运行 Docker 的那台机器上按打印的原样打开链接即可。如果容器发布到了网络上,就把 `localhost` 换成你实际访问所用的主机;无论哪种情况,token 都保持原样。-也可以改用 `PENGUIN_SEED_ADMIN_PASSWORD` 直接固定密码,但只在数据根目录为空的首次启动时生效。+也可以改用 `ADELIE_SEED_ADMIN_PASSWORD` 直接固定密码,但只在数据根目录为空的首次启动时生效。链接授予的会话带有 `via: setup`。它只有一项特殊许可:设置密码时不必输入旧密码(反正也不存在);除此之外没有任何特权,尤其拿不到任何仅限桌面应用的路由。@@ -165,7 +165,7 @@ penguin auth token # no password, no prompt: inserts a session row浏览器会话有效期 30 天。签发或上次续期之后满一天再使用,会话就**原地**续期 30 天:只更新记录里的过期时间,cookie 值保持不变。因此这 30 天相当于空闲超时:经常使用的会话永不过期,也不会冒出需要追查的第二份副本。只有自身寿命能撑到续期窗口的会话才会顺延,所以铸造的一小时 token 到一小时就到期。-Cookie 设置为 HttpOnly 和 SameSite=Lax。请求确实是 https,或者**受信任**的代理声明如此(`PENGUIN_TRUST_PROXY=1`)时,还会加上 Secure。默认忽略 `x-forwarded-proto` 头。+Cookie 设置为 HttpOnly 和 SameSite=Lax。请求确实是 https,或者**受信任**的代理声明如此(`ADELIE_TRUST_PROXY=1`)时,还会加上 Secure。默认忽略 `x-forwarded-proto` 头。### 磁盘上存了什么diff --git a/packages/docs/content/self-improvement.en.md b/packages/docs/content/self-improvement.en.mdindex 4d852728..8e1c421d 100644--- a/packages/docs/content/self-improvement.en.md+++ b/packages/docs/content/self-improvement.en.md@@ -3,7 +3,7 @@ title: Self-Improvementdescription: How Skills build a Benchmark, score an agent on it, and keep only the changes that raise its score, with every version snapshotted and every score traceable.----Self-improvement in PenguinHarness is a loop: build a Benchmark for an agent, score the agent on it, change the agent, and keep a change only when the score strictly improves. The loop adds no runtime of its own. Skills orchestrate the ordinary agent machinery: evaluations are ordinary Sessions, optimization is ordinary file editing, and every result is a file in the Project.+Self-improvement in Adelie is a loop: build a Benchmark for an agent, score the agent on it, change the agent, and keep a change only when the score strictly improves. The loop adds no runtime of its own. Skills orchestrate the ordinary agent machinery: evaluations are ordinary Sessions, optimization is ordinary file editing, and every result is a file in the Project.Building a Benchmark and optimizing an agent run in two independent top-level Sessions, and each single evaluation is delegated through the built-in `run_subagent` tool. The top-level prompt supplies the settings for the task: the agent, the Benchmark, the capability, the scores and the rounds. The Skills own everything else: call relationships, calibration, Freeze, the result protocol, repair, rollback and reporting.diff --git a/packages/docs/content/self-improvement.zh.md b/packages/docs/content/self-improvement.zh.mdindex 6f2c3b2d..ba82694d 100644--- a/packages/docs/content/self-improvement.zh.md+++ b/packages/docs/content/self-improvement.zh.md@@ -3,7 +3,7 @@ title: 自我进化description: Skill 如何构建 Benchmark、给 Agent 打分,并只保留让分数提高的改动;每个版本都有快照,每个分数都能追溯。----PenguinHarness 的自我进化是一个循环:为 Agent 构建 Benchmark,在上面给 Agent 打分,修改 Agent,只有分数严格提升才保留改动。这个循环不额外引入任何运行机制,而是由 Skill 编排普通的 Agent 机制:评估是普通的 Session,优化是普通的文件编辑,每个结果都是 Project 里的文件。+Adelie 的自我进化是一个循环:为 Agent 构建 Benchmark,在上面给 Agent 打分,修改 Agent,只有分数严格提升才保留改动。这个循环不额外引入任何运行机制,而是由 Skill 编排普通的 Agent 机制:评估是普通的 Session,优化是普通的文件编辑,每个结果都是 Project 里的文件。构建 Benchmark 和优化 Agent 分别在两个独立的顶层 Session 中运行,每一次单独的评估则通过内置的 `run_subagent` 工具委派出去。顶层 Prompt 提供这次任务的设定:Agent、Benchmark、要考察的能力、分数和轮数。其余一切都由 Skill 负责:调用关系、校准、Freeze、结果协议、修复、回滚和汇报。diff --git a/packages/docs/content/server-api.en.md b/packages/docs/content/server-api.en.mdindex f3f2ee24..a531149c 100644--- a/packages/docs/content/server-api.en.md+++ b/packages/docs/content/server-api.en.md@@ -1,14 +1,14 @@---title: Server API-description: Reference for the PenguinHarness server's HTTP API, covering authentication, every route group, the SSE streaming protocol and DTO type imports.+description: Reference for the Adelie server's HTTP API, covering authentication, every route group, the SSE streaming protocol and DTO type imports.----The PenguinHarness server exposes a same-origin HTTP API that the bundled Web App and any other HTTP client use. This page covers authentication first, then the routes grouped by area, each with a route table followed by details, and ends with the SSE streaming protocol. To start the server, see the [Quickstart](/quickstart). The API that programs outside PenguinHarness call with an agent's key is on its own page, [Agent API](/agent-api).+The Adelie server exposes a same-origin HTTP API that the bundled Web App and any other HTTP client use. This page covers authentication first, then the routes grouped by area, each with a route table followed by details, and ends with the SSE streaming protocol. To start the server, see the [Quickstart](/quickstart). The API that programs outside Adelie call with an agent's key is on its own page, [Agent API](/agent-api).## Overview- Stack: Hono and `@hono/node-server`; requires Node >= 24.-- Storage: SQLite (the built-in `node:sqlite`, in WAL mode) holds only indexes and aggregates: users, auth sessions, Project authorization, agent and Session indexes, usage, UI preferences, error records and schedule state. All agent, Trace and Workspace data stays as files under `~/.penguin/data`, shared with the CLI and SDK; see the [Configuration Reference](/configuration).+- Storage: SQLite (the built-in `node:sqlite`, in WAL mode) holds only indexes and aggregates: users, auth sessions, Project authorization, agent and Session indexes, usage, UI preferences, error records and schedule state. All agent, Trace and Workspace data stays as files under `~/.adelie/data`, shared with the CLI and SDK; see the [Configuration Reference](/configuration).- Binding: `127.0.0.1:7364` by default, adjustable with the `PORT` / `HOST` environment variables.- Request bodies: writes accept JSON only; the Content-Type check is one of the CSRF defenses. The body size cap is derived from the attachment budget rather than fixed. Attachments travel in the request as base64 `data:` URLs, which inflate them by 4/3, so the cap is `base64(attachmentTotalMb)` plus headroom for one inline image and the JSON framing. That is about 190MB at the default 120MB total, and the cap drops again if an admin lowers the total. The server counts bytes as it reads the body, so a request that declares no length (chunked) is capped the same way.- Errors share one shape:@@ -41,7 +41,7 @@ The API accepts two credentials: a cookie session and the local API token.- Cookie session: `penguin_session` (HttpOnly, SameSite=Lax), valid for 30 days with sliding renewal.- Passwords are stored as scrypt hashes. A session is a row in `auth_sessions`, keyed by the sha256 of a random cookie token; the raw token is never stored. A session survives a restart and renews in place, and logout deletes the row.-- There is no open registration. At startup the server seeds the built-in admin `admin` with a random password, which it hashes and discards without anyone seeing it. Until a password is set, every start prints a first-login link that claims the account. For automation, `PENGUIN_SEED_ADMIN_PASSWORD` pins a known password instead. An admin creates all other accounts.+- There is no open registration. At startup the server seeds the built-in admin `admin` with a random password, which it hashes and discards without anyone seeing it. Until a password is set, every start prints a first-login link that claims the account. For automation, `ADELIE_SEED_ADMIN_PASSWORD` pins a known password instead. An admin creates all other accounts.- Same-origin only: no CORS middleware is enabled, except on the Agent API's `/api/amsp/v1`, which answers a preflight from any origin and sends `Access-Control-Allow-Origin: *` on a request that carries `Authorization`. That group takes neither credential above: a request presents the agent's API key, or none when the agent allows keyless access. See [Agent API](/agent-api).- Routes marked admin only answer other users with `403` `admin_required`.@@ -58,13 +58,13 @@ Every protected route also accepts `Authorization: Bearer <token>` with the **lo- The server mints a fresh token at every boot and writes it to `<root>/api-token` with owner-only permissions (`0600`). The previous boot's token stops working as soon as the new one is minted.- A valid Bearer token authenticates as the built-in `admin`. This is the authorization model by design: local filesystem access to the data root already is admin authority, since whoever can read `api-token` can also read `web.db` next to it. `penguin server reset-admin-password` relies on the same rule.-- Server-driven sessions inject the current token into every tool subprocess as `PENGUIN_API_TOKEN`, together with `PENGUIN_API_URL`, `PENGUIN_PROJECT_ID`, `PENGUIN_AGENT_ID` and `PENGUIN_SESSION_ID`. That is what authorizes an agent's own `penguin` and API calls to reach the server that runs them.+- Server-driven sessions inject the current token into every tool subprocess as `ADELIE_API_TOKEN`, together with `ADELIE_API_URL`, `ADELIE_PROJECT_ID`, `ADELIE_AGENT_ID` and `ADELIE_SESSION_ID`. That is what authorizes an agent's own `penguin` and API calls to reach the server that runs them.- The token cannot change an agent's exposure. `PUT …/agents/:agentId/api`, `POST …/api/keys`, `DELETE …/api/keys/:keyId`, `POST …/api/try`, and a `PUT /api/admin/settings` whose body carries `agentApiEnabled` answer it `403` `human_required` and write nothing; they take a cookie session. It is the same refusal the built-in browser gives the token for choosing a backend and minting a pairing code. The reads stay open to it. Since every tool subprocess holds the token, an agent could otherwise open itself to the network from its own shell. This narrows the credential an agent is handed; it is not a boundary. A process that runs as the data root's OS account outside the sandbox can mint a session itself with `penguin auth token`. The sandbox is the boundary.- SSE endpoints accept the header like any other route. Consume them with `fetch`, not `EventSource`, which cannot send headers.- The JSON-only Content-Type check on writes applies to Bearer requests too.```bash-curl -H "Authorization: Bearer $(cat ~/.penguin/data/api-token)" \+curl -H "Authorization: Bearer $(cat ~/.adelie/data/api-token)" \http://127.0.0.1:7364/api/me```@@ -307,7 +307,7 @@ The lookup fails softly:- A failed lookup still returns 200, with `error` set (`network`, `rate_limited` or `bad_response`) and `latestVersion: null`.- Results are cached in memory: for 1 h after a success and 10 min after a failure.-- `PENGUIN_UPDATE_CHECK=off` disables the lookup entirely: the response carries `disabled: true`, and no network call is made.+- `ADELIE_UPDATE_CHECK=off` disables the lookup entirely: the response carries `disabled: true`, and no network call is made.That switch turns off this check and nothing else. Model requests, an enabled remote-control connection, owner-initiated provider key authorization and the proxy test go out whatever it is set to.@@ -612,7 +612,7 @@ All paths below are under `/api/projects/:projectId/organizations`. While the se### Caller identity-Write bodies may carry `agentId` and `sessionId`, the calling employee and the calling session, which the CLI fills in from `PENGUIN_AGENT_ID` and `PENGUIN_SESSION_ID`. The file then records the employee rather than the token's user: `agentId` wins when it names an employee, and the session decides otherwise. The channel reads and the member DELETE have no body, so they take the same pair as `?agentId=` / `?sessionId=`. The server honours both only on requests that carry the local API token; that is how an employee is answered as itself instead of as the signed-in person.+Write bodies may carry `agentId` and `sessionId`, the calling employee and the calling session, which the CLI fills in from `ADELIE_AGENT_ID` and `ADELIE_SESSION_ID`. The file then records the employee rather than the token's user: `agentId` wins when it names an employee, and the session decides otherwise. The channel reads and the member DELETE have no body, so they take the same pair as `?agentId=` / `?sessionId=`. The server honours both only on requests that carry the local API token; that is how an employee is answered as itself instead of as the signed-in person.### Organizations@@ -934,9 +934,9 @@ GET /api/sessions/:sessionId/files/preview-redirect?path=index.htmlGET /preview/<token>/<relative path> (unauthenticated; the token is the credential)```-- Why a separate origin: the page needs a real origin for storage, cookies and third-party embeds to work, but it must not be the app's origin, or HTML an agent wrote would run with the session cookie. Locally, the app is canonicalized onto `localhost` and previews are served from `127.0.0.1`. Cookies are keyed by host and ignore the port, so those two hosts get separate cookie jars, which a second port would not. Otherwise `PENGUIN_PREVIEW_ORIGIN` applies. With neither (a wildcard or non-loopback bind, or the variable unset), the redirect falls back to the same-origin sandbox described above, and `previewIsolated` on `GET /api/me` reports `false` so the UI can tell the user first.+- Why a separate origin: the page needs a real origin for storage, cookies and third-party embeds to work, but it must not be the app's origin, or HTML an agent wrote would run with the session cookie. Locally, the app is canonicalized onto `localhost` and previews are served from `127.0.0.1`. Cookies are keyed by host and ignore the port, so those two hosts get separate cookie jars, which a second port would not. Otherwise `ADELIE_PREVIEW_ORIGIN` applies. With neither (a wildcard or non-loopback bind, or the variable unset), the redirect falls back to the same-origin sandbox described above, and `previewIsolated` on `GET /api/me` reports `false` so the UI can tell the user first.- In-app rendering uses the same URL: the **Files** panel embeds the redirect URL in an iframe sandboxed with `allow-scripts allow-same-origin allow-forms allow-popups allow-modals allow-downloads`. Here `allow-same-origin` grants the preview origin's identity, not the app's, so this stays strictly tighter than the new tab, which has no sandbox. Without a separate preview origin, the panel falls back to inline `srcdoc` rendering (`allow-scripts` only, plus an in-memory storage shim), where relative subresources cannot load. Some browsers partition or block storage inside a cross-site iframe, so a page may behave slightly differently in the panel than in a top-level tab.-- The preview host serves only `/preview/*`. It is the same process as the app, so it answers `/api` with `401` and redirects every other route with `302` to the canonical app host. A session cookie is therefore never set or accepted on the preview host, and agent HTML there cannot reach the API from the same origin. For a deployed `PENGUIN_PREVIEW_ORIGIN`, the reverse proxy must enforce the same thing: route only `/preview/*` to the app on that origin.+- The preview host serves only `/preview/*`. It is the same process as the app, so it answers `/api` with `401` and redirects every other route with `302` to the canonical app host. A session cookie is therefore never set or accepted on the preview host, and agent HTML there cannot reach the API from the same origin. For a deployed `ADELIE_PREVIEW_ORIGIN`, the reverse proxy must enforce the same thing: route only `/preview/*` to the app on that origin.- The token sits in the path, not in a query parameter, so a page's relative subresources (`app.js`, `style.css`, images) resolve against the document and load under the same token.- The token binds the Session, the preview host and an expiry time. The host binding matters: the same process also answers on the app origin, so `/preview/...` refuses to serve there, which would otherwise be a same-origin XSS. Access is read-only and limited to that Session's Workspace, and the server resolves the path again, so `..` and symlink escapes are rejected as for any read.- Responses carry `Referrer-Policy: no-referrer`. Otherwise the URL, with its token, would leak through `Referer` to every third party the page embeds, a risk that exists precisely because embeds now work.@@ -1140,7 +1140,7 @@ Routes that serve the desktop shell, hot updates and the Web App's own module sy- `POST /api/desktop/shutdown` does not use the cookie session. It authenticates with the desktop shell's own Bearer token (`401` `unauthorized` otherwise), answers first, and starts the graceful shutdown right after.- The update, tray and privacy-settings routes answer only the desktop shell's own window: any other session gets `403` `desktop_shell_only`. When the shell is not listening, they return `503` `shell_unreachable`. `PUT /api/desktop/tray` returns `400` `invalid_show_tray_icon` for a non-boolean `showTrayIcon`, `400` `invalid_locale` for a `locale` other than `zh` or `en`, and `400` `empty_tray_patch` when neither field is given. The PUT only acknowledges the change; read the result back with GET.- `POST /api/desktop/privacy-settings` returns `400` `invalid_privacy_pane` for a `pane` other than `files` (Files and Folders) or `fullDisk` (Full Disk Access). The shell opens the pane on macOS only.-- The `/api/hmr` routes are admin only (`403` `forbidden`). On a non-loopback bind they also require HTTPS and otherwise return `403` `hmr_disabled`. `X-Forwarded-Proto` counts only when `PENGUIN_TRUST_PROXY=1`. A completed upgrade sends `web_updated` to every connected client, so they reload.+- The `/api/hmr` routes are admin only (`403` `forbidden`). On a non-loopback bind they also require HTTPS and otherwise return `403` `hmr_disabled`. `X-Forwarded-Proto` counts only when `ADELIE_TRUST_PROXY=1`. A completed upgrade sends `web_updated` to every connected client, so they reload.## Streaming (SSE)diff --git a/packages/docs/content/server-api.zh.md b/packages/docs/content/server-api.zh.mdindex 7387adfc..e3bba183 100644--- a/packages/docs/content/server-api.zh.md+++ b/packages/docs/content/server-api.zh.md@@ -1,14 +1,14 @@---title: Server API-description: PenguinHarness 服务器的 HTTP API 参考:认证、全部路由分组、SSE 流式协议和 DTO 类型导入。+description: Adelie 服务器的 HTTP API 参考:认证、全部路由分组、SSE 流式协议和 DTO 类型导入。----PenguinHarness 服务器提供一组同源 HTTP API,内置 Web App 和其他任何 HTTP 客户端用的都是它。本页先讲认证,再按功能分组介绍路由(每组先给路由表,再补充细节),最后讲 SSE 流式协议。启动服务器的方法见[快速开始](/quickstart)。PenguinHarness 之外的程序凭 Agent 的密钥调用的 API 另有专页,见 [Agent API](/agent-api)。+Adelie 服务器提供一组同源 HTTP API,内置 Web App 和其他任何 HTTP 客户端用的都是它。本页先讲认证,再按功能分组介绍路由(每组先给路由表,再补充细节),最后讲 SSE 流式协议。启动服务器的方法见[快速开始](/quickstart)。Adelie 之外的程序凭 Agent 的密钥调用的 API 另有专页,见 [Agent API](/agent-api)。## 概览- 技术栈:Hono 和 `@hono/node-server`,要求 Node >= 24。-- 存储:SQLite(内置的 `node:sqlite`,WAL 模式)只保存索引和聚合数据:用户、认证会话、Project 授权、Agent 与 Session 索引、用量、UI 偏好、错误记录和定时任务状态。所有 Agent、Trace 和 Workspace 数据都以文件形式存放在 `~/.penguin/data` 下,与 CLI 和 SDK 共享;参见[配置参考](/configuration)。+- 存储:SQLite(内置的 `node:sqlite`,WAL 模式)只保存索引和聚合数据:用户、认证会话、Project 授权、Agent 与 Session 索引、用量、UI 偏好、错误记录和定时任务状态。所有 Agent、Trace 和 Workspace 数据都以文件形式存放在 `~/.adelie/data` 下,与 CLI 和 SDK 共享;参见[配置参考](/configuration)。- 绑定地址:默认 `127.0.0.1:7364`,可通过 `PORT` / `HOST` 环境变量调整。- 请求体:写操作只接受 JSON,检查 Content-Type 是防 CSRF 的手段之一。请求体大小上限并非固定值,而是由附件额度推导出来的。附件以 base64 `data:` URL 的形式随请求传输,体积会膨胀 4/3,所以上限按 `base64(attachmentTotalMb)` 计算,再为一张内嵌图片和 JSON 封装留出余量。按默认 120MB 的总量计,约为 190MB;管理员调低总量,上限也会随之下降。服务器边读请求体边统计字节数,因此不声明长度(chunked)的请求同样受此限制。- 所有错误共用同一种结构:@@ -41,7 +41,7 @@ API 接受两种凭证:Cookie 会话和本地 API token。- Cookie 会话:`penguin_session`(HttpOnly,SameSite=Lax),有效期 30 天,滑动续期。- 密码以 scrypt 哈希存储。会话是 `auth_sessions` 表中的一行,以随机 Cookie token 的 sha256 为键;原始 token 从不存储。会话重启后依然有效,并在原地续期;登出则删除这一行。-- 不开放注册。启动时,服务器会用一个随机密码初始化内置管理员 `admin`:密码哈希后保存,明文随即丢弃,没有任何人见过它。在设置密码之前,每次启动都会打印一条首次登录链接,用来认领账号。自动化场景可以改用 `PENGUIN_SEED_ADMIN_PASSWORD` 固定一个已知密码。其余所有账号都由管理员创建。+- 不开放注册。启动时,服务器会用一个随机密码初始化内置管理员 `admin`:密码哈希后保存,明文随即丢弃,没有任何人见过它。在设置密码之前,每次启动都会打印一条首次登录链接,用来认领账号。自动化场景可以改用 `ADELIE_SEED_ADMIN_PASSWORD` 固定一个已知密码。其余所有账号都由管理员创建。- 仅限同源:未启用任何 CORS 中间件。例外是 Agent API 的 `/api/amsp/v1`:它应答任何来源的预检,并在带 `Authorization` 的请求上返回 `Access-Control-Allow-Origin: *`。这组路由不接受上面两种凭证:请求出示的是该 Agent 的 API 密钥;Agent 允许无密钥访问时,也可以不出示。见 [Agent API](/agent-api)。- 标为「仅管理员」的路由,对其他用户一律返回 `403` `admin_required`。@@ -58,13 +58,13 @@ curl -c cookies.txt -H "Content-Type: application/json" \- 服务器每次启动都生成一个新 token,写入 `<root>/api-token`,文件权限仅限所有者(`0600`)。新 token 一经生成,上一次启动的 token 立即失效。- 有效的 Bearer token 以内置 `admin` 的身份通过认证。这是有意设计的授权模型:在本机文件系统上能访问数据根目录,本身就等于管理员权限,因为能读 `api-token` 的人也能读它旁边的 `web.db`。`penguin server reset-admin-password` 依赖的正是这条规则。-- 服务器驱动的会话会把当前 token 注入每个工具子进程的环境变量 `PENGUIN_API_TOKEN`,同时注入 `PENGUIN_API_URL`、`PENGUIN_PROJECT_ID`、`PENGUIN_AGENT_ID` 和 `PENGUIN_SESSION_ID`。Agent 自己的 `penguin` 命令和 API 调用正是靠这些变量获得授权,才能连上运行自己的服务器。+- 服务器驱动的会话会把当前 token 注入每个工具子进程的环境变量 `ADELIE_API_TOKEN`,同时注入 `ADELIE_API_URL`、`ADELIE_PROJECT_ID`、`ADELIE_AGENT_ID` 和 `ADELIE_SESSION_ID`。Agent 自己的 `penguin` 命令和 API 调用正是靠这些变量获得授权,才能连上运行自己的服务器。- 这个 token 不能改变 Agent 的对外暴露。`PUT …/agents/:agentId/api`、`POST …/api/keys`、`DELETE …/api/keys/:keyId`、`POST …/api/try`,以及请求体带 `agentApiEnabled` 的 `PUT /api/admin/settings`,对它一律答 `403` `human_required`,不写入任何内容;这些路由只接受 Cookie 会话。内置浏览器在选择后端与生成配对码时对它也是同一种拒绝。读取路由对它照常开放。每个工具子进程都持有这个 token,否则 Agent 就能在自己的 shell 里把自己开放到网络上。这收窄了交给 Agent 的凭据,但不是边界:在沙盒之外、以数据根目录所属操作系统账号运行的进程可以用 `penguin auth token` 自行铸造会话。边界是沙盒。- SSE 端点和其他路由一样接受这个请求头。消费它们要用 `fetch`,不要用 `EventSource`——后者无法发送请求头。- 写请求只接受 JSON 的 Content-Type 检查,对 Bearer 请求同样生效。```bash-curl -H "Authorization: Bearer $(cat ~/.penguin/data/api-token)" \+curl -H "Authorization: Bearer $(cat ~/.adelie/data/api-token)" \http://127.0.0.1:7364/api/me```@@ -307,7 +307,7 @@ URL 使用机器自身的 id,而不是连接所用的 ssh 别名。别名只- 查询失败仍返回 200,只是 `error` 会带值(`network`、`rate_limited` 或 `bad_response`),且 `latestVersion` 为 null。- 结果缓存在内存中:成功后缓存 1 小时,失败后缓存 10 分钟。-- `PENGUIN_UPDATE_CHECK=off` 可彻底关闭查询:响应带 `disabled: true`,且不发起任何网络请求。+- `ADELIE_UPDATE_CHECK=off` 可彻底关闭查询:响应带 `disabled: true`,且不发起任何网络请求。这个开关只关掉这一项检查。无论它取什么值,模型请求、已启用的远程控制连接、由所有者发起的供应商 Key 授权和代理测试都照常出站。@@ -612,7 +612,7 @@ Benchmark 属于 Project,不属于某个 Agent:一个 Benchmark 可以评估### 调用者身份-写操作的请求体可以携带 `agentId` 和 `sessionId`,分别对应发起调用的员工和会话;CLI 会从 `PENGUIN_AGENT_ID` 和 `PENGUIN_SESSION_ID` 自动填入这两个值。文件里因此记录的是员工,而不是 token 对应的用户:`agentId` 指向员工时以 `agentId` 为准,否则由会话决定。频道读取和成员 DELETE 没有请求体,所以改用查询参数 `?agentId=` / `?sessionId=` 传入同一对值。只有携带本地 API token 的请求,服务器才会认可这两个字段;员工就是这样以自己的身份、而不是以登录者的身份得到响应的。+写操作的请求体可以携带 `agentId` 和 `sessionId`,分别对应发起调用的员工和会话;CLI 会从 `ADELIE_AGENT_ID` 和 `ADELIE_SESSION_ID` 自动填入这两个值。文件里因此记录的是员工,而不是 token 对应的用户:`agentId` 指向员工时以 `agentId` 为准,否则由会话决定。频道读取和成员 DELETE 没有请求体,所以改用查询参数 `?agentId=` / `?sessionId=` 传入同一对值。只有携带本地 API token 的请求,服务器才会认可这两个字段;员工就是这样以自己的身份、而不是以登录者的身份得到响应的。### 组织@@ -934,9 +934,9 @@ GET /api/sessions/:sessionId/files/preview-redirect?path=index.htmlGET /preview/<token>/<relative path> (unauthenticated; the token is the credential)```-- 为什么需要独立的源:页面要有真实的源,存储、cookie 和第三方嵌入才能工作;但这个源不能是应用的源,否则 Agent 写的 HTML 会带着会话 cookie 运行。本地运行时,应用地址规范化为 `localhost`,预览由 `127.0.0.1` 提供。cookie 按主机名隔离、忽略端口,所以这两个主机拥有各自独立的 cookie jar;换成第二个端口就做不到这一点。其他情况则使用 `PENGUIN_PREVIEW_ORIGIN`。两者都没有时(通配或非回环绑定,或变量未设置),重定向回退到前文所述的同源沙盒,同时 `GET /api/me` 上的 `previewIsolated` 报告 `false`,UI 得以提前告知用户。+- 为什么需要独立的源:页面要有真实的源,存储、cookie 和第三方嵌入才能工作;但这个源不能是应用的源,否则 Agent 写的 HTML 会带着会话 cookie 运行。本地运行时,应用地址规范化为 `localhost`,预览由 `127.0.0.1` 提供。cookie 按主机名隔离、忽略端口,所以这两个主机拥有各自独立的 cookie jar;换成第二个端口就做不到这一点。其他情况则使用 `ADELIE_PREVIEW_ORIGIN`。两者都没有时(通配或非回环绑定,或变量未设置),重定向回退到前文所述的同源沙盒,同时 `GET /api/me` 上的 `previewIsolated` 报告 `false`,UI 得以提前告知用户。- 应用内渲染用同一个 URL:**文件浏览**面板把重定向 URL 嵌入 iframe,沙盒标志为 `allow-scripts allow-same-origin allow-forms allow-popups allow-modals allow-downloads`。这里的 `allow-same-origin` 授予的是预览源的身份,不是应用的,所以这套配置仍然严格比新标签页收紧——新标签页没有沙盒。没有独立预览源时,面板回退到内联 `srcdoc` 渲染(只给 `allow-scripts`,外加一个内存版 storage 垫片),相对子资源无法加载。部分浏览器会对跨站 iframe 内的存储做分区或阻止,所以同一个页面在面板里的行为可能与顶层标签页略有差异。-- 预览主机只服务 `/preview/*`。它与应用是同一个进程,所以对 `/api` 返回 `401`,把其余所有路由以 `302` 重定向到规范的应用主机。因此,预览主机从不设置、也不接受会话 cookie,那里的 Agent HTML 无法从同一源访问 API。部署了 `PENGUIN_PREVIEW_ORIGIN` 时,反向代理必须执行同样的约束:只把 `/preview/*` 路由到这个源上的应用。+- 预览主机只服务 `/preview/*`。它与应用是同一个进程,所以对 `/api` 返回 `401`,把其余所有路由以 `302` 重定向到规范的应用主机。因此,预览主机从不设置、也不接受会话 cookie,那里的 Agent HTML 无法从同一源访问 API。部署了 `ADELIE_PREVIEW_ORIGIN` 时,反向代理必须执行同样的约束:只把 `/preview/*` 路由到这个源上的应用。- token 放在路径里,而不是查询参数里,这样页面的相对子资源(`app.js`、`style.css`、图片)相对文档解析,并在同一个 token 下加载。- token 绑定 Session、预览主机和过期时间。主机绑定很关键:同一个进程也在应用源上应答,所以 `/preview/...` 拒绝在那个源上服务,否则会构成同源 XSS。访问是只读的,限于这个 Session 的 Workspace;服务器会重新解析路径,对 `..` 和符号链接逃逸的拒绝方式与任何读取相同。- 响应带 `Referrer-Policy: no-referrer`。否则 URL 连同其中的 token 会通过 `Referer` 泄露给页面嵌入的每一个第三方——正因为嵌入如今可以工作,这个风险才随之而来。@@ -1140,7 +1140,7 @@ Telegram 连接时会先清空积压,跳过无连接期间发送的消息。- `POST /api/desktop/shutdown` 不使用 cookie 会话。它用桌面 shell 专有的 Bearer token 认证(否则返回 `401` `unauthorized`),先应答,再立即开始优雅关闭。- update、tray 和 privacy-settings 路由只响应桌面 shell 自己的窗口:其他任何会话都会得到 `403` `desktop_shell_only`。shell 未监听时,返回 `503` `shell_unreachable`。`showTrayIcon` 不是布尔值时,`PUT /api/desktop/tray` 返回 `400` `invalid_show_tray_icon`;`locale` 不是 `zh` 或 `en` 时返回 `400` `invalid_locale`;两个字段都未提供时返回 `400` `empty_tray_patch`。PUT 只确认收到更改;请用 GET 读回实际结果。- `pane` 不是 `files`(文件与文件夹)或 `fullDisk`(完全磁盘访问权限)时,`POST /api/desktop/privacy-settings` 返回 `400` `invalid_privacy_pane`。shell 只在 macOS 上打开面板。-- `/api/hmr` 路由仅限管理员(`403` `forbidden`)。绑定在非环回地址上时还要求 HTTPS,否则返回 `403` `hmr_disabled`。只有 `PENGUIN_TRUST_PROXY=1` 时 `X-Forwarded-Proto` 才生效。升级完成后,每个已连接的客户端都会收到 `web_updated` 并重新加载。+- `/api/hmr` 路由仅限管理员(`403` `forbidden`)。绑定在非环回地址上时还要求 HTTPS,否则返回 `403` `hmr_disabled`。只有 `ADELIE_TRUST_PROXY=1` 时 `X-Forwarded-Proto` 才生效。升级完成后,每个已连接的客户端都会收到 `web_updated` 并重新加载。## 流式传输(SSE)diff --git a/packages/docs/content/server-boot.en.md b/packages/docs/content/server-boot.en.mdindex 05cf803d..8a2ce925 100644--- a/packages/docs/content/server-boot.en.md+++ b/packages/docs/content/server-boot.en.md@@ -22,15 +22,15 @@ Four mechanisms start the server. All of them converge: the same env vars drive| Entry | Mechanism || --- | --- || Direct | `node dist/index.js` (`start` in `server/package.json`) |-| CLI (`penguin server` / `penguin web`) | Sets `PORT`/`HOST` and exports `PENGUIN_CLI_ENTRY`, then runs the server as a **supervised child process** that imports `@adelie/server` |+| CLI (`penguin server` / `penguin web`) | Sets `PORT`/`HOST` and exports `ADELIE_CLI_ENTRY`, then runs the server as a **supervised child process** that imports `@adelie/server` || CLI auto-start | A CLI command that finds no running server spawns a detached `server` subcommand with `PORT=0` and attaches once the root's lock is live || Desktop | `utilityProcess.fork` launches a separate server process with the server's env injected |-The supervised child runs as `node <entry> server …`, marked `PENGUIN_SERVE_CHILD=1` and told `PENGUIN_SUPERVISED=1`. The parent forwards the terminal's signals, exits with the child's code, and relaunches the child when it exits with the restart code that **Restart to update** asks for. A dev run through tsx cannot be re-spawned by node, so the CLI imports the server in-process instead. `penguin web` additionally polls for readiness and opens the browser.+The supervised child runs as `node <entry> server …`, marked `ADELIE_SERVE_CHILD=1` and told `ADELIE_SUPERVISED=1`. The parent forwards the terminal's signals, exits with the child's code, and relaunches the child when it exits with the restart code that **Restart to update** asks for. A dev run through tsx cannot be re-spawned by node, so the CLI imports the server in-process instead. `penguin web` additionally polls for readiness and opens the browser.Auto-start output goes to `<root>/logs/server-auto-<date>.log`.-The desktop process injects `PENGUIN_HOME`, `HOST`, `PORT`, `PENGUIN_DESKTOP_TOKEN` and `PENGUIN_PORT_FILE` via env, plus `PENGUIN_WEB_DIST` and `PENGUIN_CLI_ENTRY` when the app pins them.+The desktop process injects `ADELIE_HOME`, `HOST`, `PORT`, `ADELIE_DESKTOP_TOKEN` and `ADELIE_PORT_FILE` via env, plus `ADELIE_WEB_DIST` and `ADELIE_CLI_ENTRY` when the app pins them. Every one of these deployment names is also read in its pre-rename `PENGUIN_*` spelling (see [Configuration Reference](/configuration#environment-variables)).> [!NOTE]> The server's own configuration comes from environment variables only (`server/src/config.ts`). `system_config.yaml` is agent-level state, read when a Session runs; it plays no part in server boot.@@ -43,7 +43,7 @@ The desktop process injects `PENGUIN_HOME`, `HOST`, `PORT`, `PENGUIN_DESKTOP_TOKmain() —— one PenguinServer method per line│├─ ① loadEnv · installProxy dotenv first (.env may define HTTP_PROXY itself), then the proxy takes over fetch-├─ ② readConfig env only: PENGUIN_HOME, PORT, HOST, PENGUIN_WEB_DB …+├─ ② readConfig env only: ADELIE_HOME, PORT, HOST, ADELIE_WEB_DB …├─ ③ ensureSoleInstance data root held by another live instance → exit code 3 (before the DB opens)├─ ④ listen bind the port now; answer 503 "starting" until ⑧. The callback writes back│ the real port, takes the lock, and opens the ::1 companion on a loopback bind@@ -59,7 +59,7 @@ main() —— one PenguinServer method per line│ ├─ ⑨ seedAdmin built-in admin seed; decides whether a first-login link is due│ ├─ ⑩ installProcessHandlers signals, the desktop quit path, restart-to-update, the process-level error fallback│ └─ ⑪ printFirstLoginNotice the one-time sign-in link, when one is due-└─ ⑫ announce write the port to PENGUIN_PORT_FILE: the App is up+└─ ⑫ announce write the port to ADELIE_PORT_FILE: the App is up```The order is not arbitrary, and its constraints are hard:diff --git a/packages/docs/content/server-boot.zh.md b/packages/docs/content/server-boot.zh.mdindex bbc28c10..26a2731f 100644--- a/packages/docs/content/server-boot.zh.md+++ b/packages/docs/content/server-boot.zh.md@@ -22,15 +22,15 @@ description: 从进程入口到 App 开始服务的组装顺序、各子系统| 入口 | 机制 || --- | --- || 直接运行 | `node dist/index.js`(`server/package.json` 里的 `start`) |-| CLI(`penguin server` / `penguin web`) | 设好 `PORT`/`HOST` 并导出 `PENGUIN_CLI_ENTRY`,然后以**受监管的子进程**运行 Server,由子进程导入 `@adelie/server` |+| CLI(`penguin server` / `penguin web`) | 设好 `PORT`/`HOST` 并导出 `ADELIE_CLI_ENTRY`,然后以**受监管的子进程**运行 Server,由子进程导入 `@adelie/server` || CLI 自动启动 | CLI 命令发现没有运行中的 Server 时,以 `PORT=0` 派生一个分离的 `server` 子命令,等数据根的锁生效后再接入 || 桌面应用 | `utilityProcess.fork` 拉起一个**独立**的 Server 进程,并注入它需要的环境变量 |-受监管的子进程以 `node <entry> server …` 运行,带有 `PENGUIN_SERVE_CHILD=1` 标记,并通过 `PENGUIN_SUPERVISED=1` 得知有监管者。父进程转发终端的信号,以子进程的退出码退出;子进程以 **重启以更新** 所要求的重启码退出时,父进程重新拉起它。用 tsx 运行的开发实例无法由 node 重新派生,CLI 就改为在本进程内导入 Server。`penguin web` 还会轮询到就绪后打开浏览器。+受监管的子进程以 `node <entry> server …` 运行,带有 `ADELIE_SERVE_CHILD=1` 标记,并通过 `ADELIE_SUPERVISED=1` 得知有监管者。父进程转发终端的信号,以子进程的退出码退出;子进程以 **重启以更新** 所要求的重启码退出时,父进程重新拉起它。用 tsx 运行的开发实例无法由 node 重新派生,CLI 就改为在本进程内导入 Server。`penguin web` 还会轮询到就绪后打开浏览器。自动启动的输出写入 `<root>/logs/server-auto-<date>.log`。-桌面应用经环境变量注入 `PENGUIN_HOME`、`HOST`、`PORT`、`PENGUIN_DESKTOP_TOKEN` 和 `PENGUIN_PORT_FILE`;应用指定了 `PENGUIN_WEB_DIST` 和 `PENGUIN_CLI_ENTRY` 时,也一并注入。+桌面应用经环境变量注入 `ADELIE_HOME`、`HOST`、`PORT`、`ADELIE_DESKTOP_TOKEN` 和 `ADELIE_PORT_FILE`;应用指定了 `ADELIE_WEB_DIST` 和 `ADELIE_CLI_ENTRY` 时,也一并注入。这些部署变量同时仍按改名前 `PENGUIN_*` 的拼写读取(见[配置参考](/configuration#环境变量))。> [!NOTE]> Server 自身的配置只来自环境变量(`server/src/config.ts`)。`system_config.yaml` 是 Agent 级状态,在 Session 运行时读取,与 Server 启动无关。@@ -43,7 +43,7 @@ description: 从进程入口到 App 开始服务的组装顺序、各子系统main() —— one PenguinServer method per line│├─ ① loadEnv · installProxy dotenv first (.env may define HTTP_PROXY itself), then the proxy takes over fetch-├─ ② readConfig env only: PENGUIN_HOME, PORT, HOST, PENGUIN_WEB_DB …+├─ ② readConfig env only: ADELIE_HOME, PORT, HOST, ADELIE_WEB_DB …├─ ③ ensureSoleInstance data root held by another live instance → exit code 3 (before the DB opens)├─ ④ listen bind the port now; answer 503 "starting" until ⑧. The callback writes back│ the real port, takes the lock, and opens the ::1 companion on a loopback bind@@ -59,7 +59,7 @@ main() —— one PenguinServer method per line│ ├─ ⑨ seedAdmin built-in admin seed; decides whether a first-login link is due│ ├─ ⑩ installProcessHandlers signals, the desktop quit path, restart-to-update, the process-level error fallback│ └─ ⑪ printFirstLoginNotice the one-time sign-in link, when one is due-└─ ⑫ announce write the port to PENGUIN_PORT_FILE: the App is up+└─ ⑫ announce write the port to ADELIE_PORT_FILE: the App is up```这个顺序不是随意排的,其中的约束都是硬性的:diff --git a/packages/docs/content/sessions-and-traces.en.md b/packages/docs/content/sessions-and-traces.en.mdindex 9a5dca97..62224b82 100644--- a/packages/docs/content/sessions-and-traces.en.md+++ b/packages/docs/content/sessions-and-traces.en.md@@ -3,7 +3,7 @@ title: Sessions & Tracesdescription: The six-level run model, the data layout on disk, how the append-only Trace is written, and how a Session is recovered from it.----All PenguinHarness runtime data lives on the local file system. Configuration is editable files, and history is an append-only **Trace**. This page defines each level of the run model and the layout on disk, then explains how the Trace serves as history, recovery source and statistics source at once.+All Adelie runtime data lives on the local file system. Configuration is editable files, and history is an append-only **Trace**. This page defines each level of the run model and the layout on disk, then explains how the Trace serves as history, recovery source and statistics source at once.## Run model@@ -22,7 +22,7 @@ For how the levels work together, see [Architecture](/architecture). For how Req## Data layout-The data root is the `PENGUIN_HOME` environment variable, `~/.penguin/data` by default. The layout is defined in one place, `packages/core/src/state/paths.ts`:+The data root is the `ADELIE_HOME` environment variable, `~/.adelie/data` by default. The layout is defined in one place, `packages/core/src/state/paths.ts`:```text<root>/<project>/@@ -74,7 +74,7 @@ An illustrative Trace head follows, one OmniMessage envelope per line. Note the- On the first run, the toolset follows the input as a `tool_list_ready` event, after an `mcp_connect_begin` / `mcp_connect_end` pair when MCP servers are configured. `session_meta` does not carry the tool definitions.```jsonl-{"timestamp":"2026-07-18T03:10:22.531Z","type":"session_meta","payload":{"session_id":"session-2026-07-18-11-10-22-3f8a1c2d","provider":"deepseek","model_id":"deepseek-v4-pro","model_context_window":1000000,"system_prompt":"…","agent_state":"/home/u/.penguin/data/default_project/agents/default_agent/agent_state","workspace":"/home/u/work"}}+{"timestamp":"2026-07-18T03:10:22.531Z","type":"session_meta","payload":{"session_id":"session-2026-07-18-11-10-22-3f8a1c2d","provider":"deepseek","model_id":"deepseek-v4-pro","model_context_window":1000000,"system_prompt":"…","agent_state":"/home/u/.adelie/data/default_project/agents/default_agent/agent_state","workspace":"/home/u/work"}}{"timestamp":"…","type":"model_msg","payload":{"type":"text","role":"user","text":"Create hello.txt"}}{"timestamp":"…","type":"event_msg","payload":{"type":"tool_list_ready","tools":[…]}}{"timestamp":"…","type":"event_msg","payload":{"type":"request_begin"}}diff --git a/packages/docs/content/sessions-and-traces.zh.md b/packages/docs/content/sessions-and-traces.zh.mdindex 8b004c9c..a6695c31 100644--- a/packages/docs/content/sessions-and-traces.zh.md+++ b/packages/docs/content/sessions-and-traces.zh.md@@ -3,7 +3,7 @@ title: Session 与 Tracedescription: 六层运行模型、磁盘上的数据布局、只追加的 Trace 如何写入,以及 Session 如何从中恢复。----PenguinHarness 的全部运行时数据都存放在本地文件系统上。配置是可编辑的文件,历史是只追加的 **Trace**。本页逐层定义运行模型和磁盘上的数据布局,然后说明 Trace 如何同时充当历史记录、恢复来源和统计来源。+Adelie 的全部运行时数据都存放在本地文件系统上。配置是可编辑的文件,历史是只追加的 **Trace**。本页逐层定义运行模型和磁盘上的数据布局,然后说明 Trace 如何同时充当历史记录、恢复来源和统计来源。## 运行模型@@ -22,7 +22,7 @@ PenguinHarness 的全部运行时数据都存放在本地文件系统上。配## 数据目录-数据根目录由环境变量 `PENGUIN_HOME` 指定,默认为 `~/.penguin/data`。目录布局统一定义在 `packages/core/src/state/paths.ts` 中:+数据根目录由环境变量 `ADELIE_HOME` 指定,默认为 `~/.adelie/data`。目录布局统一定义在 `packages/core/src/state/paths.ts` 中:```text<root>/<project>/@@ -74,7 +74,7 @@ Trace 是只追加的 JSON Lines 文件,每行是一个 OmniMessage 信封,- 首次运行时,工具集以 `tool_list_ready` 事件跟在输入之后;如果配置了 MCP Server,在这之前还有一对 `mcp_connect_begin` / `mcp_connect_end`。`session_meta` 不携带工具定义。```jsonl-{"timestamp":"2026-07-18T03:10:22.531Z","type":"session_meta","payload":{"session_id":"session-2026-07-18-11-10-22-3f8a1c2d","provider":"deepseek","model_id":"deepseek-v4-pro","model_context_window":1000000,"system_prompt":"…","agent_state":"/home/u/.penguin/data/default_project/agents/default_agent/agent_state","workspace":"/home/u/work"}}+{"timestamp":"2026-07-18T03:10:22.531Z","type":"session_meta","payload":{"session_id":"session-2026-07-18-11-10-22-3f8a1c2d","provider":"deepseek","model_id":"deepseek-v4-pro","model_context_window":1000000,"system_prompt":"…","agent_state":"/home/u/.adelie/data/default_project/agents/default_agent/agent_state","workspace":"/home/u/work"}}{"timestamp":"…","type":"model_msg","payload":{"type":"text","role":"user","text":"Create hello.txt"}}{"timestamp":"…","type":"event_msg","payload":{"type":"tool_list_ready","tools":[…]}}{"timestamp":"…","type":"event_msg","payload":{"type":"request_begin"}}diff --git a/packages/docs/content/settings.en.md b/packages/docs/content/settings.en.mdindex cd33b036..ccf7f215 100644--- a/packages/docs/content/settings.en.md+++ b/packages/docs/content/settings.en.md@@ -264,7 +264,7 @@ Turning it off stops the organization scheduler and every organization route, an## Agent API-The **Agent API** page (**Settings › Server › Agent API**) is admin-only and server-global. It holds the **Allow the Agent API** switch, on by default, over every agent's API: the HTTP API through which programs outside PenguinHarness talk to an agent (see [Agent API](/agent-api)).+The **Agent API** page (**Settings › Server › Agent API**) is admin-only and server-global. It holds the **Allow the Agent API** switch, on by default, over every agent's API: the HTTP API through which programs outside Adelie talk to an agent (see [Agent API](/agent-api)).The switch applies the moment it is flipped. There is no Save button.diff --git a/packages/docs/content/settings.zh.md b/packages/docs/content/settings.zh.mdindex d6cd6e50..beabf726 100644--- a/packages/docs/content/settings.zh.md+++ b/packages/docs/content/settings.zh.md@@ -46,7 +46,7 @@ description: 管理个人资料、偏好设置和密码;管理员还可以管设置项标题旁的「?」可以查看这一项的说明,页面标题旁的「?」则说明整个页面。-检查更新不在这个对话框里,见[更新 PenguinHarness](/updates)。+检查更新不在这个对话框里,见[更新 Adelie](/updates)。## 个人资料@@ -264,7 +264,7 @@ Trace 会成为该 Agent 的一段新对话。如果该 Agent 下已有相同 id## Agent API-**Agent API** 页(**设置 › 服务器 › Agent API**)仅管理员可见,作用于整台服务器。页面上只有**允许 Agent API** 这一个开关,默认开启,统管所有 Agent 的 API,也就是 PenguinHarness 之外的程序与 Agent 对话所用的 HTTP API(见 [Agent API](/agent-api))。+**Agent API** 页(**设置 › 服务器 › Agent API**)仅管理员可见,作用于整台服务器。页面上只有**允许 Agent API** 这一个开关,默认开启,统管所有 Agent 的 API,也就是 Adelie 之外的程序与 Agent 对话所用的 HTTP API(见 [Agent API](/agent-api))。开关一拨即生效,没有保存按钮。diff --git a/packages/docs/content/skills.en.md b/packages/docs/content/skills.en.mdindex 6f10ae36..16faea85 100644--- a/packages/docs/content/skills.en.md+++ b/packages/docs/content/skills.en.md@@ -52,7 +52,7 @@ Other ways to install:## Update installed plugins-New versions of the built-in plugins arrive with PenguinHarness updates. An agent keeps its installed copy until you update it. When an install is behind the library, you see:+New versions of the built-in plugins arrive with Adelie updates. An agent keeps its installed copy until you update it. When an install is behind the library, you see:- a red dot on **Plugins** in the sidebar;- a notice at the top of the **Plugins** page, "Changes detected: N to upgrade", with **Update now** and **Dismiss**;@@ -73,7 +73,7 @@ To update:## Import, export and delete library plugins-Beside the plugins PenguinHarness ships, the library lists the plugins in the **user plugin directory**, `<data root>/plugins`. An admin fills it by importing — from a zip file on this machine, or from a URL the server downloads — and an agent can then install those plugins exactly like a built-in one. A plugin from there carries a **User** badge.+Beside the plugins Adelie ships, the library lists the plugins in the **user plugin directory**, `<data root>/plugins`. An admin fills it by importing — from a zip file on this machine, or from a URL the server downloads — and an agent can then install those plugins exactly like a built-in one. A plugin from there carries a **User** badge.To import a plugin, select **Upload plugin** or **Download from URL** in the page header and fill in the dialog:@@ -167,7 +167,7 @@ To upload a zip file:A server plugin extends the server itself rather than an agent: it is an npm package of server modules, such as a sandbox backend. A Project asks for the server plugins it needs, and the server runs every plugin that any of its Projects asks for, so what a plugin contributes is available to every Project.-On the **Plugins** page, a server plugin's row shows its package name, description, version and status, with tags for its categories, **built in** when it ships with PenguinHarness, and its keywords. Select a row to open the plugin's page, with its license, authors, links and documentation. The shelf is complete: the four sandbox backends are hand-written entries, and every plugin package this build carries has one of its own (the library's skills/hooks packages included), with version, description, license, category and keywords read from the package itself. Only a plugin imported on this machine has no entry, and therefore no page.+On the **Plugins** page, a server plugin's row shows its package name, description, version and status, with tags for its categories, **built in** when it ships with Adelie, and its keywords. Select a row to open the plugin's page, with its license, authors, links and documentation. The shelf is complete: the four sandbox backends are hand-written entries, and every plugin package this build carries has one of its own (the library's skills/hooks packages included), with version, description, license, category and keywords read from the package itself. Only a plugin imported on this machine has no entry, and therefore no page.To add a server plugin to the current Project:@@ -176,7 +176,7 @@ To add a server plugin to the current Project:To remove one, select **Remove** on its row under **Installed plugins**, and confirm. The plugin leaves the Project's list; nothing is deleted from disk.-Only admins see **Install** and **Remove**. Only plugins that ship with PenguinHarness can be added, so nothing is downloaded. A change applies without restarting the server: the server rebuilds its business surface around the new list, which is why runs in progress stop. Afterwards the row's status reads **running**, **restart to load** when the server could not apply the change without a restart, or **failed to load** with the reason.+Only admins see **Install** and **Remove**. Only plugins that ship with Adelie can be added, so nothing is downloaded. A change applies without restarting the server: the server rebuilds its business surface around the new list, which is why runs in progress stop. Afterwards the row's status reads **running**, **restart to load** when the server could not apply the change without a restart, or **failed to load** with the reason.The list is the `[plugins]` table of the Project's config; see [Configuration Reference](/configuration#plugins). For the routes, see [Server API](/server-api#plugin-registry-and-project-plugins), and for how the server loads plugins, see [Server Boot and Subsystems](/server-boot#re-assembly).diff --git a/packages/docs/content/skills.zh.md b/packages/docs/content/skills.zh.mdindex e7e50cbd..e029f503 100644--- a/packages/docs/content/skills.zh.md+++ b/packages/docs/content/skills.zh.md@@ -52,7 +52,7 @@ description: 浏览插件,为 Agent 安装 Skill 和钩子包,为 Project## 更新已安装的插件-内置插件的新版本随 PenguinHarness 更新一起发布。在你更新之前,Agent 会一直保留已安装的副本。当某个安装落后于插件库时,你会看到:+内置插件的新版本随 Adelie 更新一起发布。在你更新之前,Agent 会一直保留已安装的副本。当某个安装落后于插件库时,你会看到:- 侧边栏**插件市场**上出现红点;- **插件市场**页面顶部出现「检测到变更:N 个可升级」提示,带**现在升级**和**忽略**按钮;@@ -73,7 +73,7 @@ description: 浏览插件,为 Agent 安装 Skill 和钩子包,为 Project## 导入、导出与删除插件库中的插件-除了 PenguinHarness 自带的插件,插件库还会列出**用户插件目录**(`<数据根>/plugins`)里的插件。管理员通过导入来填充它——导入本机的一个 zip 文件,或导入一个由服务端下载的地址——之后 Agent 就能像安装内置插件一样安装它们。来自这个目录的插件带**用户**标签。+除了 Adelie 自带的插件,插件库还会列出**用户插件目录**(`<数据根>/plugins`)里的插件。管理员通过导入来填充它——导入本机的一个 zip 文件,或导入一个由服务端下载的地址——之后 Agent 就能像安装内置插件一样安装它们。来自这个目录的插件带**用户**标签。导入插件时,点击页面头部的**上传插件**或**远程下载**,然后在对话框里填写:@@ -167,7 +167,7 @@ zip 文件最大 14 MB,最多 200 个文件;解压后单个文件不超过 5服务端插件扩展的是服务器本身,而不是 Agent:它是一个由服务端模块组成的 npm 包,例如沙箱后端。每个 Project 声明自己需要的服务端插件,服务器运行任一 Project 要求的全部插件,因此插件提供的能力对所有 Project 都可用。-在**插件市场**页面上,服务端插件的一行显示包名、描述、版本和状态,标签标出它的分类、随 PenguinHarness 发布时的**内置**,以及关键词。点击这一行打开插件页面,查看许可证、作者、链接和说明文档。市场里条目齐全:四个沙箱后端是手写的条目,此外本次构建自带的每个插件包各有一条(插件库里的技能/钩子包也算),版本、简介、许可证、分类和关键词都读自包本身。只有本机导入的插件没有条目,也就没有页面。+在**插件市场**页面上,服务端插件的一行显示包名、描述、版本和状态,标签标出它的分类、随 Adelie 发布时的**内置**,以及关键词。点击这一行打开插件页面,查看许可证、作者、链接和说明文档。市场里条目齐全:四个沙箱后端是手写的条目,此外本次构建自带的每个插件包各有一条(插件库里的技能/钩子包也算),版本、简介、许可证、分类和关键词都读自包本身。只有本机导入的插件没有条目,也就没有页面。为当前 Project 添加服务端插件:@@ -176,7 +176,7 @@ zip 文件最大 14 MB,最多 200 个文件;解压后单个文件不超过 5移除插件:在**已安装的插件**下点击它那一行的**移除**,然后确认。插件会从 Project 的列表中去掉,磁盘上的文件不会被删除。-只有管理员能看到**安装**和**移除**。只能添加随 PenguinHarness 发布的插件,因此不会下载任何东西。改动无需重启服务器即可生效:服务器围绕新列表重建业务面,所以正在进行的运行会被中止。之后,这一行的状态显示为**运行中**;服务器无法免重启应用改动时显示**待重启**;加载失败时显示**加载失败**并附上原因。+只有管理员能看到**安装**和**移除**。只能添加随 Adelie 发布的插件,因此不会下载任何东西。改动无需重启服务器即可生效:服务器围绕新列表重建业务面,所以正在进行的运行会被中止。之后,这一行的状态显示为**运行中**;服务器无法免重启应用改动时显示**待重启**;加载失败时显示**加载失败**并附上原因。列表就是 Project 配置中的 `[plugins]` 表,见[配置参考](/configuration#插件)。路由见 [Server API](/server-api#插件注册表与-project-插件),服务器如何加载插件见 [Server 启动与子系统](/server-boot#重组)。diff --git a/packages/docs/content/tools.en.md b/packages/docs/content/tools.en.mdindex 96a14ff8..234e770b 100644--- a/packages/docs/content/tools.en.md+++ b/packages/docs/content/tools.en.md@@ -3,7 +3,7 @@ title: Tools & Approvaldescription: How the built-in tools run under one execution contract, how each call is approved and audited in the Trace, and how MCP servers join them.----PenguinHarness ships a deliberately minimal built-in toolset. Dedicated file tools (`read_file` / `edit_file` / `write_file`) cover precise reading and editing, because line-numbered output and exact-string replacement beat quoting `sed` one-liners. The shell (`exec_command`) remains the general-purpose fallback for everything else: running programs, searching, installing dependencies. Every tool that remains earns the schema Tokens it costs.+Adelie ships a deliberately minimal built-in toolset. Dedicated file tools (`read_file` / `edit_file` / `write_file`) cover precise reading and editing, because line-numbered output and exact-string replacement beat quoting `sed` one-liners. The shell (`exec_command`) remains the general-purpose fallback for everything else: running programs, searching, installing dependencies. Every tool that remains earns the schema Tokens it costs.The Environment runs every tool call through one shared contract and handles the close-out centrally. This page covers that contract first, then the per-tool configuration, the 7 built-in tools and their background behavior, the per-call approval recorded in the Trace, and how to customize the toolset and add MCP servers.@@ -179,7 +179,7 @@ The tools' arguments (explicit keys):}```-**Shell.** Commands run through `bash -lc` wherever a bash exists, and the system prompt tells the model which shell is active. `PENGUIN_SHELL` (an executable name or path) overrides the choice on every platform. Otherwise the shell is picked in this order:+**Shell.** Commands run through `bash -lc` wherever a bash exists, and the system prompt tells the model which shell is active. `ADELIE_SHELL` (an executable name or path) overrides the choice on every platform. Otherwise the shell is picked in this order:- On POSIX: `bash` on PATH, then the usual absolute bash locations, then the `$SHELL` login shell, then `sh`.- On Windows: a `bash` on PATH that is not the WSL launcher (for example Git for Windows), then the bundled MinGit bash, then `pwsh`, then `powershell`.diff --git a/packages/docs/content/tools.zh.md b/packages/docs/content/tools.zh.mdindex e208f736..5f742fdf 100644--- a/packages/docs/content/tools.zh.md+++ b/packages/docs/content/tools.zh.md@@ -3,7 +3,7 @@ title: 工具与审批description: 内置工具如何运行在同一套执行契约之下,每次调用如何经过审批、在 Trace 中留下审计记录,以及 MCP Server 如何接入。----PenguinHarness 刻意只提供一套极简的内置工具集。专用文件工具(`read_file` / `edit_file` / `write_file`)负责精确的读取和编辑,因为带行号的输出和精确字符串替换,比手写 `sed` 单行命令更可靠。Shell(`exec_command`)则是其他一切的通用兜底:运行程序、搜索、安装依赖。留下来的每个工具,都配得上它在 schema 上占用的 Token。+Adelie 刻意只提供一套极简的内置工具集。专用文件工具(`read_file` / `edit_file` / `write_file`)负责精确的读取和编辑,因为带行号的输出和精确字符串替换,比手写 `sed` 单行命令更可靠。Shell(`exec_command`)则是其他一切的通用兜底:运行程序、搜索、安装依赖。留下来的每个工具,都配得上它在 schema 上占用的 Token。Environment 让每一次工具调用都走同一套共享契约,并集中处理收尾。本页先讲这套契约,之后依次介绍:各工具的配置字段、7 个内置工具和它们的后台行为、记录在 Trace 中的逐次调用审批,以及如何自定义工具集、添加 MCP Server。@@ -179,7 +179,7 @@ exec_command(cmd)}```-**Shell:** 只要有 bash,命令就通过 `bash -lc` 执行,系统提示词会告诉模型当前使用的是哪个 shell。`PENGUIN_SHELL`(可执行文件名或路径)在所有平台上都能覆盖这个选择。否则按以下顺序挑选 shell:+**Shell:** 只要有 bash,命令就通过 `bash -lc` 执行,系统提示词会告诉模型当前使用的是哪个 shell。`ADELIE_SHELL`(可执行文件名或路径)在所有平台上都能覆盖这个选择。否则按以下顺序挑选 shell:- POSIX 上:先找 PATH 中的 `bash`,再找常见的 bash 绝对路径,然后是 `$SHELL` 登录 shell,最后是 `sh`。- Windows 上:先找 PATH 中非 WSL 启动器的 `bash`(例如 Git for Windows),然后是内置的 MinGit bash,然后是 `pwsh`,最后是 `powershell`。diff --git a/packages/docs/content/updates.en.md b/packages/docs/content/updates.en.mdindex 65fd57f1..71a2e641 100644--- a/packages/docs/content/updates.en.md+++ b/packages/docs/content/updates.en.md@@ -1,9 +1,9 @@----title: Update PenguinHarness+title: Update Adeliedescription: Check which version you are running, and update the desktop app, a CLI install, or a Docker deployment.----Check which version of PenguinHarness you are running, and update it in the way that matches your install.+Check which version of Adelie you are running, and update it in the way that matches your install.- **Which version is running?** See [Check the running version](#check-the-running-version).- **Updating from the browser?** See [Update from the Web App](#update-from-the-web-app).@@ -109,4 +109,4 @@ Updating from inside the container is not supported. See [Upgrade the container]## Turn off the update check-Set `PENGUIN_UPDATE_CHECK=off` to turn off the automatic release check. That is all it turns off: model requests, an enabled remote-control connection, provider key authorization and the proxy test still reach the network. With the check off, the update dialog says **Update checks are disabled (PENGUIN_UPDATE_CHECK=off)**. See the [Configuration Reference](/configuration#environment-variables).+Set `ADELIE_UPDATE_CHECK=off` to turn off the automatic release check. That is all it turns off: model requests, an enabled remote-control connection, provider key authorization and the proxy test still reach the network. With the check off, the update dialog says **Update checks are disabled (ADELIE_UPDATE_CHECK=off)**. See the [Configuration Reference](/configuration#environment-variables).diff --git a/packages/docs/content/updates.zh.md b/packages/docs/content/updates.zh.mdindex 1bc88846..e26c1e00 100644--- a/packages/docs/content/updates.zh.md+++ b/packages/docs/content/updates.zh.md@@ -1,9 +1,9 @@----title: 更新 PenguinHarness+title: 更新 Adeliedescription: 查看正在运行的版本,并更新桌面应用、CLI 安装或 Docker 部署。----查看正在运行的 PenguinHarness 版本,并按你的安装方式完成更新。+查看正在运行的 Adelie 版本,并按你的安装方式完成更新。- **想确认当前版本?** 见[查看当前版本](#查看当前版本)。- **在浏览器里更新?** 见[通过 Web App 更新](#通过-web-app-更新)。@@ -109,4 +109,4 @@ docker compose pull && docker compose up -d## 关闭更新检查-设置 `PENGUIN_UPDATE_CHECK=off` 可以关闭自动的版本检查。它只关掉这一项:模型请求、已启用的远程控制连接、Key 授权和代理测试照常联网。关闭后,更新弹窗会显示**更新检查已关闭(PENGUIN_UPDATE_CHECK=off)**。见[配置参考](/configuration#环境变量)。+设置 `ADELIE_UPDATE_CHECK=off` 可以关闭自动的版本检查。它只关掉这一项:模型请求、已启用的远程控制连接、Key 授权和代理测试照常联网。关闭后,更新弹窗会显示**更新检查已关闭(ADELIE_UPDATE_CHECK=off)**。见[配置参考](/configuration#环境变量)。diff --git a/packages/docs/content/web-app.en.md b/packages/docs/content/web-app.en.mdindex 1bfd9826..c7eb3a6e 100644--- a/packages/docs/content/web-app.en.md+++ b/packages/docs/content/web-app.en.md@@ -3,7 +3,7 @@ title: Web Appdescription: Sign in to the Web App, find your way around, manage Projects and members, and run the app in production.----PenguinHarness ships with a Web App: multi-user sign-in, streaming chat, agent configuration, and model and usage management all happen in the browser. The desktop app shows the same interface in its own window. This page is the overview; each part of the app has its own guide. For installation and first launch, see the [Quickstart](/quickstart).+Adelie ships with a Web App: multi-user sign-in, streaming chat, agent configuration, and model and usage management all happen in the browser. The desktop app shows the same interface in its own window. This page is the overview; each part of the app has its own guide. For installation and first launch, see the [Quickstart](/quickstart).- To sign in for the first time, see [Open the Web App and sign in](#open-the-web-app-and-sign-in).- To find your way around, see [The app layout](#the-app-layout).@@ -37,7 +37,7 @@ The initial account is `admin`, and it starts with no password of its own. Until> [!NOTE]> The link can be opened again. It lasts 30 days, or until a password is set. A restart prints a new link and the old one stops working. A link that no longer works lands on the login page with an explanation.-The desktop app does not print the notice. The server also skips it while a password pinned with `PENGUIN_SEED_ADMIN_PASSWORD` still works. For how these mechanisms are secured, see [Security](/security).+The desktop app does not print the notice. The server also skips it while a password pinned with `ADELIE_SEED_ADMIN_PASSWORD` still works. For how these mechanisms are secured, see [Security](/security).### Accounts@@ -94,7 +94,7 @@ From top to bottom, the sidebar holds:| **Agents** | Create agents and edit their prompt, memory, runtime, tools, Skills, hooks, Vault and scheduled tasks | [Agents](/agents) || **Models** | Configure the Project's models, providers and credentials | [Models](/models) || **Plugins** | Browse plugins, install their Skills and hook packages onto agents, and add server plugins to the Project | [Skills](/skills) |-| **Machines** | Install this PenguinHarness build on other hosts over ssh and manage the connections to them (admins only) | [Security Model](/security#manage-remote-machines-over-ssh) |+| **Machines** | Install this Adelie build on other hosts over ssh and manage the connections to them (admins only) | [Security Model](/security#manage-remote-machines-over-ssh) || **Cost Center** | Token usage, cost and server errors by agent, model and time range | [Cost Center](/usage) || **Evaluation Center** | Benchmarks: evaluate agents and optimize them against a Benchmark | [Evaluation Center](/evaluation-center) |@@ -219,6 +219,6 @@ The Scheduled tasks panel is the exception. Its way out is **Edit in this converThe server hosts the built SPA itself, on the same origin and with SPA fallback. A single `penguin web` or `penguin server` process is all production needs.-The npm package bundles the frontend build. To serve a custom static directory instead, override it with `PENGUIN_WEB_DIST`. See the [Configuration Reference](/configuration).+The npm package bundles the frontend build. To serve a custom static directory instead, override it with `ADELIE_WEB_DIST`. See the [Configuration Reference](/configuration).The server listens on `127.0.0.1` by default, so it answers only on its own machine. Exposing it on a network, with `HOST`, belongs behind a reverse proxy that terminates TLS. See [Security](/security).diff --git a/packages/docs/content/web-app.zh.md b/packages/docs/content/web-app.zh.mdindex a4560d5d..8ec66a25 100644--- a/packages/docs/content/web-app.zh.md+++ b/packages/docs/content/web-app.zh.md@@ -3,7 +3,7 @@ title: Web Appdescription: 登录 Web App,熟悉界面布局,管理 Project 与成员,并在生产环境中运行。----PenguinHarness 自带一个 Web App:多用户登录、流式对话、Agent 配置、模型与用量管理,都在浏览器里完成。桌面应用在自己的窗口中显示的也是同一套界面。本页是总览,各个部分另有专门的指南。安装与首次启动见[快速开始](/quickstart)。+Adelie 自带一个 Web App:多用户登录、流式对话、Agent 配置、模型与用量管理,都在浏览器里完成。桌面应用在自己的窗口中显示的也是同一套界面。本页是总览,各个部分另有专门的指南。安装与首次启动见[快速开始](/quickstart)。- 第一次登录,见[打开 Web App 并登录](#打开-web-app-并登录)。- 熟悉界面,见[应用布局](#应用布局)。@@ -37,7 +37,7 @@ penguin web> [!NOTE]> 链接可以重复打开,有效期 30 天,设置密码后即失效。重启服务会打印新链接,旧链接随之作废。打开已失效的链接会跳到登录页,并显示说明。-桌面应用不会打印这条提示;用 `PENGUIN_SEED_ADMIN_PASSWORD` 固定的密码仍然有效时,服务也不打印。这些机制如何保证安全,见[安全模型](/security)。+桌面应用不会打印这条提示;用 `ADELIE_SEED_ADMIN_PASSWORD` 固定的密码仍然有效时,服务也不打印。这些机制如何保证安全,见[安全模型](/security)。### 账号@@ -94,14 +94,14 @@ penguin web| **智能体** | 创建 Agent,编辑它们的提示词、记忆、运行参数、工具、Skill、钩子、密钥保险柜和定时任务 | [Agent](/agents) || **模型库** | 配置 Project 的模型、供应商和凭证 | [模型](/models) || **插件市场** | 浏览插件,把插件中的 Skill 和钩子包安装到 Agent 上,为 Project 添加服务端插件 | [Skill](/skills) |-| **机器管理** | 通过 ssh 把当前版本的 PenguinHarness 安装到其他主机上,并管理与它们的连接(仅管理员) | [安全模型](/security#通过-ssh-管理远程机器) |+| **机器管理** | 通过 ssh 把当前版本的 Adelie 安装到其他主机上,并管理与它们的连接(仅管理员) | [安全模型](/security#通过-ssh-管理远程机器) || **成本中心** | 按 Agent、模型和时间范围查看 Token 用量、成本和服务器异常 | [成本中心](/usage) || **评估中心** | Benchmark:评估 Agent,并以 Benchmark 为标准优化 Agent | [评估中心](/evaluation-center) |- 对话列表,可以搜索,可以按 Workspace、Agent 或时间分组。见[对话](/chat)。- 底部是你的用户行,点击打开账户菜单:- **设置**,见[设置](/settings)。- - 更新行,显示更新进行到哪一步,点击打开更新对话框,见[更新 PenguinHarness](/updates)。+ - 更新行,显示更新进行到哪一步,点击打开更新对话框,见[更新 Adelie](/updates)。- **登出**。### 常驻与可收起的入口@@ -219,6 +219,6 @@ Web App 中很多通过表单创建的东西,也可以改为向 Agent 描述服务端自己托管构建好的 SPA(同源、支持 SPA fallback),生产环境只需运行一个 `penguin web` 或 `penguin server` 进程。-npm 安装包已经内置前端构建产物。如果要使用自定义的静态目录,用 `PENGUIN_WEB_DIST` 覆盖即可,见[配置参考](/configuration)。+npm 安装包已经内置前端构建产物。如果要使用自定义的静态目录,用 `ADELIE_WEB_DIST` 覆盖即可,见[配置参考](/configuration)。服务默认监听 `127.0.0.1`,只能从本机访问。如果要通过 `HOST` 让它在网络上可访问,应当放在负责 TLS 终结的反向代理之后,见[安全模型](/security)。diff --git a/packages/docs/index.html b/packages/docs/index.htmlindex 39f71bcf..fe7ec497 100644--- a/packages/docs/index.html+++ b/packages/docs/index.html@@ -7,17 +7,17 @@<meta name="theme-color" content="#030712" media="(prefers-color-scheme: dark)" /><metaname="description"- content="PenguinHarness documentation — architecture, the OmniMessage protocol, SDK interfaces, CLI and Server API reference."+ content="Adelie documentation — architecture, the OmniMessage protocol, SDK interfaces, CLI and Server API reference."/><meta property="og:type" content="website" />- <meta property="og:title" content="PenguinHarness Docs" />+ <meta property="og:title" content="Adelie Docs" /><metaproperty="og:description"- content="Documentation for PenguinHarness — architecture, the OmniMessage protocol, SDK interfaces, CLI and Server API reference."+ content="Documentation for Adelie — architecture, the OmniMessage protocol, SDK interfaces, CLI and Server API reference."/><meta name="twitter:card" content="summary" /><link rel="icon" type="image/svg+xml" href="./adelie-icon.svg" />- <title>PenguinHarness Docs</title>+ <title>Adelie Docs</title><!-- Apply the stored/system theme before first paint so the page doesn't flash thewrong background while React boots. Reads the key shared with the sibling site(see src/state/site-prefs.ts), falling back to the retired per-site keys. -->diff --git a/packages/docs/src/lib/search.ts b/packages/docs/src/lib/search.tsindex 7997326d..41815d0a 100644--- a/packages/docs/src/lib/search.ts+++ b/packages/docs/src/lib/search.ts@@ -95,7 +95,7 @@ function normalizeSearchTextWithSourceMap(text: string): NormalizedSourceMap {/*** Remove only paired Markdown emphasis/strikethrough delimiters. Unmatched marker* characters can be part of documented identifiers or paths and must remain- * searchable (for example partial_*, model.*, and ~/.penguin).+ * searchable (for example partial_*, model.*, and ~/.adelie/data).*/function stripMarkdownFormatting(text: string): string {return textdiff --git a/packages/docs/src/lib/strings-en.ts b/packages/docs/src/lib/strings-en.tsindex 562ad963..9ef98dd5 100644--- a/packages/docs/src/lib/strings-en.ts+++ b/packages/docs/src/lib/strings-en.ts@@ -2,7 +2,7 @@import type { Strings } from "./strings";export const en: Strings = {- siteName: "PenguinHarness",+ siteName: "Adelie",nav: {highlights: "Highlights",diff --git a/packages/docs/src/lib/strings.ts b/packages/docs/src/lib/strings.tsindex 957077cf..65f6c57f 100644--- a/packages/docs/src/lib/strings.ts+++ b/packages/docs/src/lib/strings.ts@@ -6,7 +6,7 @@* reads inside components. Doc page bodies are Markdown files under content/, not here.*/export const zh = {- siteName: "PenguinHarness",+ siteName: "Adelie",nav: {// Landing-parity labels: the top bar mirrors the landing page's nav exactlydiff --git a/packages/docs/src/state/site-prefs.ts b/packages/docs/src/state/site-prefs.tsindex 61019a32..c37602a0 100644--- a/packages/docs/src/state/site-prefs.ts+++ b/packages/docs/src/state/site-prefs.ts@@ -1,15 +1,17 @@/**- * Preferences shared by the landing page and the docs site.+ * Preferences the docs site stores.*- * The two are separate SPAs but ship to one origin (penguin.ooo and penguin.ooo/docs/),- * so a single localStorage key is all it takes for a language or theme choice to survive- * the hop between them. They previously wrote `penguin-landing.*` and `penguin-docs.*`,- * which is why picking dark mode on the landing page and clicking through to the docs- * dropped you back into light.+ * The keys are the ones the docs shared with the site they were deployed beside — upstream's+ * landing page at the origin root — so a language or theme choice survived the hop between the+ * two SPAs. The retired per-site names below are still read once for the same reason: a visitor+ * who picked dark mode on the landing page and clicked through used to land back in light, and+ * that read is what keeps an existing choice from being dropped.+ * In this repository the docs are the whole site: the root `/Adelie/` is a one-page redirect to+ * `/Adelie/docs/`. The KEYS stay exactly as they are, because a stored choice is keyed on them.*- * This module is duplicated verbatim in packages/landing (as theme.tsx and locale.tsx- * already are — the two sites share no package). The KEYS below must stay identical on- * both sides; if they drift, the sync silently stops working with nothing failing.+ * The `packages/landing` copy this module was duplicated in is gone from this repository; if it+ * ever comes back, the KEYS have to match on both sides, since a drift makes the sync stop+ * silently rather than fail.*/export const THEME_KEY = "penguin-site.theme";diff --git a/packages/docs/src/styles.css b/packages/docs/src/styles.cssindex 917aa9af..94a4b8b3 100644--- a/packages/docs/src/styles.css+++ b/packages/docs/src/styles.css@@ -176,7 +176,8 @@chrome is scoped to inline code because the `.md-body pre code` reset below strips background,color and padding inside fenced blocks but would not strip a border. Prose often holds longunbroken paths and identifiers, so inline code gets the same `anywhere` treatment as links.- Kept identical to the landing site: penguin.ooo and penguin.ooo/docs share one design language. */+ Kept identical to the landing site: the site root `/Adelie/` and `/Adelie/docs/` share one+ design language. */.md-body :not(pre) > code {@apply rounded-md border border-brand-200/60 bg-brand-50/40 px-[0.3em] py-[0.1em] text-[0.875em] text-gray-900 dark:border-brand-900/70 dark:bg-brand-950/50 dark:text-gray-100;overflow-wrap: anywhere;diff --git a/packages/docs/vite.config.ts b/packages/docs/vite.config.tsindex fae4d6da..74561725 100644--- a/packages/docs/vite.config.ts+++ b/packages/docs/vite.config.ts@@ -16,7 +16,7 @@ import { defineConfig } from "vite";export default defineConfig({base: process.env.BASE_PATH ?? "/",plugins: [react(), tailwindcss()],- // Fixed PenguinHarness dev port (stands alone — only the main server default is+ // Fixed Adelie dev port (stands alone — only the main server default is// shared, as DEFAULT_SERVER_PORT in core; vite configs cannot import core TS).server: { port: 7367 },});