mirror of
https://github.com/getpaseo/paseo.git
synced 2026-11-22 08:15:05 +00:00
Compare commits
1
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
3f764885a6 |
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Antigravity
|
||||
description: Install and configure Antigravity for Paseo.
|
||||
description: Run Antigravity in Paseo through the official agy CLI over ACP.
|
||||
nav: Antigravity
|
||||
order: 23
|
||||
category: Providers
|
||||
@@ -8,41 +8,35 @@ category: Providers
|
||||
|
||||
# Antigravity
|
||||
|
||||
Run Antigravity in Paseo with your installed `agy` CLI and sign-in. This integration is not endorsed by Google.
|
||||
Paseo runs Antigravity through the official Agent Client Protocol (`agy acp`) on your installed `agy` CLI. Paseo drives your local CLI with your existing sign-in instead of calling Google endpoints directly.
|
||||
|
||||
## Getting started
|
||||
|
||||
Install Antigravity CLI (`agy`) 1.5.0 or later on your daemon host, then run `agy` once to sign in. In Paseo, select **Antigravity**. The provider ships with Paseo, so you do not install a plugin.
|
||||
Antigravity is built into Paseo and enabled by default. You do not need a plugin or extra configuration.
|
||||
|
||||
If `agy` is outside your daemon's PATH, override its command in `~/.paseo/config.json`. Use `env` for provider-specific environment variables:
|
||||
1. Install the [Antigravity CLI](https://antigravity.google/docs/getting-started?tab=cli) (`agy`) version 1.5.0 or later on your daemon host.
|
||||
2. Run `agy` in a terminal and sign in.
|
||||
3. In Paseo, choose **Antigravity** when you start an agent.
|
||||
|
||||
```json
|
||||
{
|
||||
"agents": {
|
||||
"providers": {
|
||||
"antigravity": {
|
||||
"command": ["/absolute/path/to/agy", "acp", "--disable-telemetry"],
|
||||
"env": { "EXAMPLE_VARIABLE": "value" }
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
If you already override the command, add `acp` to the command arguments. See [Custom providers](/docs/custom-providers) for command and environment overrides.
|
||||
|
||||
After the upgrade, a Hub trigger saved with an older model ID that includes the thinking level reports that its model is unavailable. In Hub, select the model and thinking level again.
|
||||
If `agy` is outside your daemon PATH, use a [command override](/docs/custom-providers#custom-binary) and keep `acp` in the arguments.
|
||||
|
||||
## Permissions
|
||||
|
||||
Paseo connects to `agy acp` and shows the permission modes the CLI offers. In **Default**, Paseo shows approval requests for edits and commands that Antigravity policy requires you to approve. In **Accept edits**, Antigravity approves workspace edits and still asks about commands that require approval. **Plan** lets Antigravity plan before it acts.
|
||||
Paseo connects to `agy acp` and shows the permission modes that the CLI provides. **Full access** is the default mode.
|
||||
|
||||
**Full access** is the default. Paseo approves tool requests that offer a single **Allow once** action. Antigravity still enforces its own tool policy. Existing chats saved in **Full access** keep that mode, and scheduled runs can use it without a person to approve each tool call.
|
||||
| Mode | Effect |
|
||||
| ------------ | ----------------------------------------------------------------------------------------------------------------------- |
|
||||
| Full access | Paseo approves tool requests that offer a single **Allow once** action. Antigravity still enforces its own tool policy. |
|
||||
| Default | Paseo shows approval requests for edits and commands that Antigravity policy requires you to approve. |
|
||||
| Accept edits | Antigravity approves workspace edits automatically and still asks about commands that require approval. |
|
||||
| Plan | Antigravity plans before it acts. |
|
||||
|
||||
Finish or stop the current turn before you switch to or from **Full access**.
|
||||
Scheduled runs can use **Full access** without a person to approve each tool call. Finish or stop the current turn before you switch to or from **Full access**.
|
||||
|
||||
## Sessions and tools
|
||||
|
||||
Paseo can import CLI sessions and restore conversation history when it reopens a chat. Antigravity publishes slash commands and accepts image attachments through ACP. It also receives the MCP servers configured for the agent.
|
||||
- Paseo can import CLI sessions and restore conversation history when it reopens a chat.
|
||||
- Antigravity publishes slash commands and skills, accepts image attachments, and receives the MCP servers configured for the agent.
|
||||
- Send a follow-up after the current turn finishes, or interrupt the turn to change direction.
|
||||
|
||||
Send a follow-up after the current turn finishes, or interrupt the turn to change direction.
|
||||
After an upgrade, an older Hub trigger can report that its Antigravity model is unavailable. Open the trigger in Hub and select the model and thinking level again.
|
||||
|
||||
@@ -1,46 +1,40 @@
|
||||
---
|
||||
title: Antigravity
|
||||
description: 为 Paseo 安装和配置 Antigravity。
|
||||
description: 通过官方 agy CLI 的 ACP 接口在 Paseo 中运行 Antigravity。
|
||||
nav: Antigravity
|
||||
---
|
||||
|
||||
# Antigravity {#antigravity}
|
||||
|
||||
使用你已安装的 `agy` CLI 和登录状态,在 Paseo 中运行 Antigravity。此集成未经 Google 认可。
|
||||
Paseo 通过你已安装的 `agy` CLI 提供的官方 Agent Client Protocol(`agy acp`)运行 Antigravity。Paseo 使用你现有的登录状态驱动本地 CLI,而不会直接调用 Google 端点。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
在 daemon 主机上安装 Antigravity CLI(`agy`)1.5.0 或更高版本,然后运行一次 `agy` 登录。在 Paseo 中选择 **Antigravity**。该 Provider 随 Paseo 一起提供,无需另外安装插件。
|
||||
Antigravity 内置于 Paseo 且默认启用,无需安装插件或额外配置。
|
||||
|
||||
如果 `agy` 不在 daemon 的 PATH 中,请在 `~/.paseo/config.json` 中覆盖它的命令。使用 `env` 设置 Provider 专用的环境变量:
|
||||
1. 在 daemon 主机上安装 1.5.0 或更高版本的 [Antigravity CLI](https://antigravity.google/docs/getting-started?tab=cli)(`agy`)。
|
||||
2. 在终端中运行 `agy` 并登录。
|
||||
3. 在 Paseo 中启动 Agent 时选择 **Antigravity**。
|
||||
|
||||
```json
|
||||
{
|
||||
"agents": {
|
||||
"providers": {
|
||||
"antigravity": {
|
||||
"command": ["/absolute/path/to/agy", "acp", "--disable-telemetry"],
|
||||
"env": { "EXAMPLE_VARIABLE": "value" }
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
如果你已覆盖命令,请在命令参数中加入 `acp`。命令和环境变量覆盖见[自定义 Provider](/docs/custom-providers)。
|
||||
|
||||
升级后,如果 Hub 中保存的触发器使用了包含思考级别的旧模型 ID,会提示模型不可用。请在 Hub 中重新选择模型和思考级别。
|
||||
如果 `agy` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers#custom-binary),并在参数中保留 `acp`。
|
||||
|
||||
## 权限 {#permissions}
|
||||
|
||||
Paseo 连接到 `agy acp`,并显示 CLI 提供的权限模式。在 **Default** 模式下,如果 Antigravity 的权限策略要求批准编辑或命令,Paseo 会显示审批请求。在 **Accept edits** 模式下,Antigravity 会自动批准工作区内的编辑,仍会询问是否批准需要审批的命令。**Plan** 模式让 Antigravity 先规划,再执行。
|
||||
Paseo 连接到 `agy acp`,并显示 CLI 提供的权限模式。**Full access** 是默认模式。
|
||||
|
||||
**Full access** 是默认模式。如果工具请求只提供一个 **Allow once** 操作,Paseo 会自动批准。Antigravity 仍会执行自己的工具策略。以前以 **Full access** 模式保存的聊天会保留该模式,计划任务也可以使用该模式,无需人为逐次审批。
|
||||
| 模式 | 效果 |
|
||||
| ------------ | -------------------------------------------------------------------------------------------------- |
|
||||
| Full access | 如果工具请求只提供一个 **Allow once** 操作,Paseo 会自动批准。Antigravity 仍会执行自己的工具策略。 |
|
||||
| Default | 如果 Antigravity 的策略要求批准编辑或命令,Paseo 会显示审批请求。 |
|
||||
| Accept edits | Antigravity 会自动批准工作区内的编辑,仍会询问需要审批的命令。 |
|
||||
| Plan | Antigravity 先规划,再执行。 |
|
||||
|
||||
切换到 **Full access** 或从该模式切换到其他模式前,请先完成或停止当前轮次。
|
||||
定时任务可以使用 **Full access**,无需人为逐次审批工具调用。切换到 **Full access** 或从该模式切换到其他模式前,请先完成或停止当前轮次。
|
||||
|
||||
## 会话和工具 {#sessions-and-tools}
|
||||
|
||||
Paseo 可以导入 CLI 会话,并在重新打开聊天时恢复对话历史。Antigravity 通过 ACP 提供斜杠命令、接收图片附件,也会使用为 Agent 配置的 MCP 服务器。
|
||||
- Paseo 可以导入 CLI 会话,并在重新打开聊天时恢复对话历史。
|
||||
- Antigravity 提供斜杠命令和技能、接收图片附件,也会使用为 Agent 配置的 MCP 服务器。
|
||||
- 你可以在当前轮次结束后发送后续消息,也可以中断当前轮次来改变方向。
|
||||
|
||||
你可以在当前轮次结束后发送后续消息,也可以中断当前轮次来改变方向。
|
||||
升级 Paseo 后,较早的 Hub 触发器可能会提示其 Antigravity 模型不可用。请在 Hub 中打开该触发器,并重新选择模型和思考级别。
|
||||
|
||||
@@ -8,25 +8,31 @@ category: Providers
|
||||
|
||||
# Claude Code
|
||||
|
||||
Paseo runs Claude Code through the official `claude` CLI using the Claude Agent SDK.
|
||||
Paseo runs Claude Code through the official `claude` CLI and the Claude Agent SDK. It uses your local installation and existing Claude account.
|
||||
|
||||
## Getting started
|
||||
|
||||
Claude Code is built into Paseo and enabled by default.
|
||||
|
||||
1. Install the [Claude Code CLI](https://code.claude.com/docs/en/setup#install-claude-code) on your daemon host.
|
||||
2. Run `claude` in a terminal and sign in.
|
||||
3. In Paseo, choose **Claude** when you start an agent.
|
||||
|
||||
If `claude` is outside your daemon PATH, use a [command override](/docs/custom-providers#custom-binary).
|
||||
|
||||
If your Claude login expires, sign in again in the Claude Code CLI and start a new session in Paseo. Running sessions keep the authentication they started with, so signing in again does not update an active session.
|
||||
|
||||
## Does Claude Code cost extra in Paseo?
|
||||
|
||||
No. Claude Code usage in Paseo counts against your normal Claude plan limits. It does not require a separate pool of Agent SDK credits.
|
||||
|
||||
You still need a Claude plan that includes Claude Code, and your plan's usual usage limits apply.
|
||||
|
||||
## Getting started
|
||||
|
||||
Install and sign in to the Claude Code CLI on the machine running Paseo. Paseo uses that existing installation and account when you start a Claude Code agent.
|
||||
|
||||
If your Claude login expires, re-authenticate with the Claude Code CLI, then start a new Claude Code session in Paseo. Existing Paseo sessions keep the authentication they started with, so re-authenticating does not update a session that is already running.
|
||||
You still need a Claude plan that includes Claude Code, and your plan's normal usage limits apply.
|
||||
|
||||
## Use Claude Code in the Paseo terminal
|
||||
|
||||
Claude Code also works great inside the Paseo terminal. If you prefer the standard CLI experience, open a terminal in your workspace and run `claude` as usual.
|
||||
Claude Code also works inside the Paseo terminal. Open a terminal in your workspace and run `claude` for the standard CLI experience.
|
||||
|
||||
You can use the terminal from Paseo's desktop, web, or mobile app while keeping access to your workspace, git changes, and other Paseo tools.
|
||||
You can use the terminal from Paseo's desktop, web, or mobile app. You keep access to your workspace, git changes, and other Paseo tools.
|
||||
|
||||
## See also
|
||||
|
||||
|
||||
@@ -6,7 +6,19 @@ nav: Claude Code
|
||||
|
||||
# Claude Code {#claude-code}
|
||||
|
||||
Paseo 通过官方的 `claude` CLI,借助 Claude Agent SDK 运行 Claude Code。
|
||||
Paseo 通过官方的 `claude` CLI 和 Claude Agent SDK 运行 Claude Code。它使用你的本地安装和现有的 Claude 账号。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
Claude Code 内置于 Paseo 且默认启用。
|
||||
|
||||
1. 在 daemon 主机上安装 [Claude Code CLI](https://code.claude.com/docs/en/setup#install-claude-code)。
|
||||
2. 在终端中运行 `claude` 并登录。
|
||||
3. 在 Paseo 中启动 Agent 时选择 **Claude**。
|
||||
|
||||
如果 `claude` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers#custom-binary)。
|
||||
|
||||
如果 Claude 登录过期,请在 Claude Code CLI 中重新登录,然后在 Paseo 中启动新的会话。正在运行的会话会保留启动时的认证状态,重新登录不会更新已有的活跃会话。
|
||||
|
||||
## 在 Paseo 中使用 Claude Code 需要额外付费吗? {#does-claude-code-cost-extra-in-paseo}
|
||||
|
||||
@@ -14,15 +26,9 @@ Paseo 通过官方的 `claude` CLI,借助 Claude Agent SDK 运行 Claude Code
|
||||
|
||||
你仍然需要一个包含 Claude Code 的 Claude 套餐,套餐原有的用量限制同样适用。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
在运行 Paseo 的机器上安装并登录 Claude Code CLI。你启动 Claude Code Agent 时,Paseo 会使用这份现有的安装和账号。
|
||||
|
||||
如果 Claude 登录过期,请用 Claude Code CLI 重新认证,然后在 Paseo 中启动新的 Claude Code 会话。已有的 Paseo 会话保留启动时的认证,因此重新认证不会更新已经在运行的会话。
|
||||
|
||||
## 在 Paseo 终端中使用 Claude Code {#use-claude-code-in-the-paseo-terminal}
|
||||
|
||||
Claude Code 在 Paseo 终端里也很好用。如果你更喜欢标准的 CLI 体验,在工作区中打开终端,像平常一样运行 `claude` 即可。
|
||||
Claude Code 也可以在 Paseo 终端中运行。在工作区中打开终端并运行 `claude`,即可获得标准的 CLI 体验。
|
||||
|
||||
你可以在 Paseo 的桌面端、网页端或移动端使用终端,同时保留对工作区、git 改动和其他 Paseo 工具的访问。
|
||||
|
||||
|
||||
@@ -8,53 +8,41 @@ category: Providers
|
||||
|
||||
# Codex
|
||||
|
||||
Paseo runs Codex through the official `codex` CLI and its app-server interface.
|
||||
|
||||
## Does Codex cost extra in Paseo?
|
||||
|
||||
No. Paseo does not add a charge for Codex. Sign in to the Codex CLI with ChatGPT to use the access included with your ChatGPT plan, or sign in with an API key for usage billed through your OpenAI Platform account.
|
||||
|
||||
Your plan's normal Codex limits and OpenAI's standard API pricing still apply.
|
||||
Paseo runs Codex through the official `codex` CLI and its app-server interface. It uses your local installation and existing OpenAI sign-in.
|
||||
|
||||
## Getting started
|
||||
|
||||
Install the [Codex CLI](https://learn.chatgpt.com/docs/codex/cli) on the machine running Paseo:
|
||||
Codex is built into Paseo and enabled by default.
|
||||
|
||||
```bash
|
||||
npm install -g @openai/codex
|
||||
```
|
||||
1. Install the [Codex CLI](https://developers.openai.com/codex/cli) on your daemon host:
|
||||
|
||||
Sign in with ChatGPT for subscription access:
|
||||
```bash
|
||||
npm install -g @openai/codex
|
||||
```
|
||||
|
||||
```bash
|
||||
codex login
|
||||
```
|
||||
2. Sign in with ChatGPT for subscription access:
|
||||
|
||||
Or sign in with an API key for usage billed through your OpenAI Platform account:
|
||||
```bash
|
||||
codex login
|
||||
```
|
||||
|
||||
```bash
|
||||
# macOS or Linux
|
||||
printenv OPENAI_API_KEY | codex login --with-api-key
|
||||
```
|
||||
3. In Paseo, choose **Codex** when you start an agent.
|
||||
|
||||
```powershell
|
||||
# Windows PowerShell
|
||||
$env:OPENAI_API_KEY | codex login --with-api-key
|
||||
```
|
||||
To bill through an OpenAI Platform API key instead, pipe `OPENAI_API_KEY` into `codex login --with-api-key`. See [Codex authentication](https://learn.chatgpt.com/docs/auth) for platform-specific sign-in commands.
|
||||
|
||||
Then confirm the CLI starts:
|
||||
If `codex` is outside your daemon PATH, use a [command override](/docs/custom-providers#custom-binary).
|
||||
|
||||
```bash
|
||||
codex
|
||||
```
|
||||
## Does Codex cost extra in Paseo?
|
||||
|
||||
Paseo uses this installation and its existing authentication when you start a Codex agent.
|
||||
No. Paseo does not add a charge for Codex. Sign in with ChatGPT to use the access included in your ChatGPT plan. Or sign in with an API key to bill through your OpenAI Platform account.
|
||||
|
||||
Your plan's normal Codex limits and OpenAI's standard API pricing still apply.
|
||||
|
||||
## Codex is missing in Paseo
|
||||
|
||||
The ChatGPT desktop app and the Codex CLI are separate installs. Installing the desktop app does not make the `codex` command available to Paseo.
|
||||
The ChatGPT desktop app and the Codex CLI are separate installs. Installing the desktop app does not add the `codex` command for Paseo.
|
||||
|
||||
Check whether the CLI is on your `PATH`:
|
||||
Make sure that `codex` is on your `PATH`:
|
||||
|
||||
```bash
|
||||
# macOS or Linux
|
||||
@@ -66,16 +54,18 @@ where.exe codex
|
||||
|
||||
If the command is not found:
|
||||
|
||||
1. Install the [Codex CLI](https://learn.chatgpt.com/docs/codex/cli).
|
||||
2. Sign in with ChatGPT or an API key using the commands above. See [Codex authentication](https://learn.chatgpt.com/docs/auth).
|
||||
3. Restart Paseo if its daemon was already running when you installed the CLI.
|
||||
4. In Paseo, open **Settings → Providers → Codex** and select **Refresh**.
|
||||
1. Install the [Codex CLI](https://developers.openai.com/codex/cli).
|
||||
2. Sign in with `codex login` or an API key.
|
||||
3. If the Paseo daemon was already running when you installed the CLI, restart Paseo.
|
||||
4. In Paseo, open **Settings → Hosts → your host → Providers → Codex** and select **Refresh**.
|
||||
|
||||
The provider should become available once Paseo can find and start the `codex` command.
|
||||
Codex becomes available once Paseo can find and start the `codex` command.
|
||||
|
||||
## Use Codex in the Paseo terminal
|
||||
|
||||
Codex also works inside the Paseo terminal. Open a terminal in your workspace and run `codex` for the standard CLI experience while keeping access to your workspace, git changes, and other Paseo tools.
|
||||
Codex also works inside the Paseo terminal. Open a terminal in your workspace and run `codex` for the standard CLI experience.
|
||||
|
||||
You can use the terminal from Paseo's desktop, web, or mobile app. You keep access to your workspace, git changes, and other Paseo tools.
|
||||
|
||||
## See also
|
||||
|
||||
|
||||
@@ -6,53 +6,41 @@ nav: Codex
|
||||
|
||||
# Codex {#codex}
|
||||
|
||||
Paseo 通过官方的 `codex` CLI 及其 app-server 接口运行 Codex。
|
||||
|
||||
## 在 Paseo 中使用 Codex 需要额外付费吗? {#does-codex-cost-extra-in-paseo}
|
||||
|
||||
不需要。Paseo 不会为 Codex 额外收费。用 ChatGPT 登录 Codex CLI,即可使用 ChatGPT 套餐包含的额度;或者用 API key 登录,用量通过你的 OpenAI Platform 账号计费。
|
||||
|
||||
你套餐中常规的 Codex 限额和 OpenAI 的标准 API 价格仍然适用。
|
||||
Paseo 通过官方的 `codex` CLI 及其 app-server 接口运行 Codex。它使用你的本地安装和现有的 OpenAI 登录状态。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
在运行 Paseo 的机器上安装 [Codex CLI](https://learn.chatgpt.com/docs/codex/cli):
|
||||
Codex 内置于 Paseo 且默认启用。
|
||||
|
||||
```bash
|
||||
npm install -g @openai/codex
|
||||
```
|
||||
1. 在 daemon 主机上安装 [Codex CLI](https://developers.openai.com/codex/cli):
|
||||
|
||||
用 ChatGPT 登录以使用订阅额度:
|
||||
```bash
|
||||
npm install -g @openai/codex
|
||||
```
|
||||
|
||||
```bash
|
||||
codex login
|
||||
```
|
||||
2. 用 ChatGPT 登录以使用订阅额度:
|
||||
|
||||
或者用 API key 登录,用量通过你的 OpenAI Platform 账号计费:
|
||||
```bash
|
||||
codex login
|
||||
```
|
||||
|
||||
```bash
|
||||
# macOS or Linux
|
||||
printenv OPENAI_API_KEY | codex login --with-api-key
|
||||
```
|
||||
3. 在 Paseo 中启动 Agent 时选择 **Codex**。
|
||||
|
||||
```powershell
|
||||
# Windows PowerShell
|
||||
$env:OPENAI_API_KEY | codex login --with-api-key
|
||||
```
|
||||
如需通过 OpenAI Platform API key 计费,请将 `OPENAI_API_KEY` 通过管道传给 `codex login --with-api-key`。各平台的登录命令见 [Codex 认证](https://learn.chatgpt.com/docs/auth)。
|
||||
|
||||
然后确认 CLI 能够启动:
|
||||
如果 `codex` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers#custom-binary)。
|
||||
|
||||
```bash
|
||||
codex
|
||||
```
|
||||
## 在 Paseo 中使用 Codex 需要额外付费吗? {#does-codex-cost-extra-in-paseo}
|
||||
|
||||
你启动 Codex Agent 时,Paseo 会使用这份安装及其现有的认证。
|
||||
不需要。Paseo 不会为 Codex 额外收费。用 ChatGPT 登录可使用 ChatGPT 套餐包含的额度;用 API key 登录则通过你的 OpenAI Platform 账号计费。
|
||||
|
||||
你套餐中常规的 Codex 限额和 OpenAI 的标准 API 价格仍然适用。
|
||||
|
||||
## Paseo 中找不到 Codex {#codex-is-missing-in-paseo}
|
||||
|
||||
ChatGPT 桌面应用和 Codex CLI 是分开安装的。安装桌面应用并不会让 Paseo 找到 `codex` 命令。
|
||||
ChatGPT 桌面应用和 Codex CLI 是分开安装的。安装桌面应用并不会为 Paseo 添加 `codex` 命令。
|
||||
|
||||
检查 CLI 是否在你的 `PATH` 中:
|
||||
确认 `codex` 在你的 `PATH` 中:
|
||||
|
||||
```bash
|
||||
# macOS or Linux
|
||||
@@ -64,16 +52,18 @@ where.exe codex
|
||||
|
||||
如果找不到该命令:
|
||||
|
||||
1. 安装 [Codex CLI](https://learn.chatgpt.com/docs/codex/cli)。
|
||||
2. 使用上面的命令通过 ChatGPT 或 API key 登录。参见 [Codex 认证](https://learn.chatgpt.com/docs/auth)。
|
||||
1. 安装 [Codex CLI](https://developers.openai.com/codex/cli)。
|
||||
2. 使用 `codex login` 或 API key 登录。
|
||||
3. 如果安装 CLI 时 Paseo 的 daemon 已在运行,请重启 Paseo。
|
||||
4. 在 Paseo 中打开 **设置 → Providers → Codex** 并选择 **刷新**。
|
||||
4. 在 Paseo 中打开 **设置 → Hosts → 你的主机 → Providers → Codex**,然后选择 **刷新**。
|
||||
|
||||
当 Paseo 能找到并启动 `codex` 命令后,这个 Provider 就会变为可用。
|
||||
当 Paseo 能找到并启动 `codex` 命令后,Codex 就会变为可用。
|
||||
|
||||
## 在 Paseo 终端中使用 Codex {#use-codex-in-the-paseo-terminal}
|
||||
|
||||
Codex 在 Paseo 终端里同样可用。在工作区中打开终端并运行 `codex`,即可获得标准的 CLI 体验,同时保留对工作区、git 改动和其他 Paseo 工具的访问。
|
||||
Codex 也可以在 Paseo 终端中运行。在工作区中打开终端并运行 `codex`,即可获得标准的 CLI 体验。
|
||||
|
||||
你可以在 Paseo 的桌面端、网页端或移动端使用终端,同时保留对工作区、git 改动和其他 Paseo 工具的访问。
|
||||
|
||||
## 另请参阅 {#see-also}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: fx
|
||||
description: Install and configure fx for Paseo.
|
||||
description: Install and add fx for Paseo.
|
||||
nav: fx
|
||||
order: 26
|
||||
category: Providers
|
||||
@@ -8,22 +8,22 @@ category: Providers
|
||||
|
||||
# fx
|
||||
|
||||
Run fx, the coding agent from Vercel Labs, in Paseo with your existing fx installation and credentials.
|
||||
Paseo runs fx, the coding agent from Vercel Labs, through the Agent Client Protocol (`fx acp`) on your installed `fx` CLI. It uses your existing fx credentials and settings.
|
||||
|
||||
## Getting started
|
||||
|
||||
Add fx from Settings in Paseo before you start an agent.
|
||||
|
||||
1. [Install fx](https://fx.sh/docs/getting-started/installation) on your daemon host.
|
||||
2. [Connect fx to a model provider](https://fx.sh/docs/getting-started/authentication), for example with `fx login`.
|
||||
3. In Paseo, open **Settings → Hosts → your host → Providers**, select **+ Provider**, find **fx**, and choose **Add**.
|
||||
2. [Connect fx to a model provider](https://fx.sh/docs/getting-started/authentication), such as with `fx login`.
|
||||
3. In Paseo, open **Settings → Hosts → your host → Providers**, select **+ Provider**, find **fx**, and select **Add**.
|
||||
|
||||
Paseo launches `fx acp` and uses your fx credentials and settings. Until fx has credentials, the provider reports the sign-in message from fx.
|
||||
|
||||
If `fx` is outside your daemon's PATH, use a [command override](/docs/custom-providers) and keep `acp` in the arguments.
|
||||
Until fx has credentials, Paseo shows the sign-in message from fx. If `fx` is outside your daemon PATH, use a [command override](/docs/custom-providers#custom-binary) and keep `acp` in the arguments.
|
||||
|
||||
## Models and permissions
|
||||
|
||||
The model list comes from the model provider that is active in fx. Run `fx provider` to change the list that a new agent starts from.
|
||||
The model list comes from the active model provider in fx. Run `fx provider` to change the list that new agents start from.
|
||||
|
||||
Changing an agent's permission mode in Paseo also changes fx's saved permission mode.
|
||||
When you change an agent's permission mode in Paseo, fx also updates its saved permission mode.
|
||||
|
||||
See [fx's ACP guide](https://fx.sh/docs/using-fx/acp) for what fx supports.
|
||||
See [fx's ACP guide](https://fx.sh/docs/using-fx/acp) for supported features.
|
||||
|
||||
@@ -1,27 +1,27 @@
|
||||
---
|
||||
title: fx
|
||||
description: 为 Paseo 安装和配置 fx。
|
||||
description: 为 Paseo 安装并添加 fx。
|
||||
nav: fx
|
||||
---
|
||||
|
||||
# fx {#fx}
|
||||
|
||||
使用你现有的 fx 安装和凭据,在 Paseo 中运行 Vercel Labs 的编程 Agent fx。
|
||||
Paseo 通过你已安装的 `fx` CLI 提供的 Agent Client Protocol(`fx acp`)运行 Vercel Labs 的编程 Agent fx。它使用你现有的 fx 凭据和设置。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
启动 Agent 前,请先在 Paseo 设置中添加 fx。
|
||||
|
||||
1. 在 daemon 主机上[安装 fx](https://fx.sh/docs/getting-started/installation)。
|
||||
2. [为 fx 连接一个模型提供方](https://fx.sh/docs/getting-started/authentication),例如运行 `fx login`。
|
||||
3. 在 Paseo 中打开 **设置 → Hosts → 你的主机 → Providers**,选择 **+ Provider**,找到 **fx** 并选择 **添加**。
|
||||
3. 在 Paseo 中打开 **设置 → Hosts → 你的主机 → Providers**,选择 **+ Provider**,找到 **fx**,然后选择 **添加**。
|
||||
|
||||
Paseo 会启动 `fx acp`,并使用你的 fx 凭据和设置。在 fx 拿到凭据之前,该 Provider 会显示 fx 给出的登录提示。
|
||||
|
||||
如果 `fx` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers),并在参数中保留 `acp`。
|
||||
在 fx 拿到凭据之前,Paseo 会显示 fx 给出的登录提示。如果 `fx` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers#custom-binary),并在参数中保留 `acp`。
|
||||
|
||||
## 模型和权限 {#models-and-permissions}
|
||||
|
||||
模型列表来自 fx 中当前启用的模型提供方。运行 `fx provider` 可以更改新 Agent 使用的列表。
|
||||
|
||||
在 Paseo 中更改 Agent 的权限模式,也会更改 fx 保存的权限模式。
|
||||
在 Paseo 中更改 Agent 的权限模式时,fx 也会更新它保存的权限模式。
|
||||
|
||||
fx 支持的功能见 [fx 的 ACP 指南](https://fx.sh/docs/using-fx/acp)。
|
||||
|
||||
@@ -8,22 +8,24 @@ category: Providers
|
||||
|
||||
# GitHub Copilot
|
||||
|
||||
Run GitHub Copilot in Paseo with your existing `copilot` CLI and GitHub account.
|
||||
Paseo runs GitHub Copilot through the official Agent Client Protocol (`copilot --acp`) on your installed `copilot` CLI. It uses your local CLI and existing GitHub sign-in.
|
||||
|
||||
## Getting started
|
||||
|
||||
GitHub Copilot is built into Paseo and enabled by default.
|
||||
|
||||
1. Install the [GitHub Copilot CLI](https://github.com/features/copilot/cli/) on your daemon host.
|
||||
2. Run `copilot` in a terminal and sign in to GitHub.
|
||||
3. In Paseo, choose **Copilot** when you start an agent.
|
||||
|
||||
Paseo launches `copilot --acp` and uses the sign-in that the CLI already has. If `copilot` is outside your daemon's PATH, use a [command override](/docs/custom-providers#custom-binary) and keep `--acp` in the arguments.
|
||||
If `copilot` is outside your daemon PATH, use a [command override](/docs/custom-providers#custom-binary) and keep `--acp` in the arguments.
|
||||
|
||||
## Modes
|
||||
|
||||
**Agent** is the default mode.
|
||||
|
||||
| Mode | Effect |
|
||||
| --------- | ------------------------------------------------------------- |
|
||||
| Agent | The default mode for conversational work. |
|
||||
| Plan | Copilot creates multi-step plans and executes them. |
|
||||
| Allow All | Copilot approves every tool, path, and URL request by itself. |
|
||||
| Mode | Effect |
|
||||
| --------- | ------------------------------------------------------------------ |
|
||||
| Agent | The default mode for conversational work. |
|
||||
| Plan | Copilot creates and runs multi-step plans. |
|
||||
| Allow All | Copilot approves every tool, path, and URL request without asking. |
|
||||
|
||||
@@ -6,22 +6,24 @@ nav: GitHub Copilot
|
||||
|
||||
# GitHub Copilot {#github-copilot}
|
||||
|
||||
使用你现有的 `copilot` CLI 和 GitHub 账号,在 Paseo 中运行 GitHub Copilot。
|
||||
Paseo 通过你已安装的 `copilot` CLI 提供的官方 Agent Client Protocol(`copilot --acp`)运行 GitHub Copilot。它使用你的本地 CLI 和现有的 GitHub 登录状态。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
GitHub Copilot 内置于 Paseo 且默认启用。
|
||||
|
||||
1. 在 daemon 主机上安装 [GitHub Copilot CLI](https://github.com/features/copilot/cli/)。
|
||||
2. 在终端中运行 `copilot` 并登录 GitHub。
|
||||
3. 在 Paseo 中启动 Agent 时选择 **Copilot**。
|
||||
|
||||
Paseo 会启动 `copilot --acp`,并使用 CLI 已有的登录状态。如果 `copilot` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers#custom-binary),并在参数中保留 `--acp`。
|
||||
如果 `copilot` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers#custom-binary),并在参数中保留 `--acp`。
|
||||
|
||||
## 模式 {#modes}
|
||||
|
||||
**Agent** 是默认模式。
|
||||
|
||||
| 模式 | 效果 |
|
||||
| --------- | ------------------------------------------- |
|
||||
| Agent | 用于对话式工作的默认模式。 |
|
||||
| Plan | Copilot 创建多步骤计划并执行。 |
|
||||
| Allow All | Copilot 自行批准所有工具、路径和 URL 请求。 |
|
||||
| 模式 | 效果 |
|
||||
| --------- | ------------------------------------------------- |
|
||||
| Agent | 用于对话式工作的默认模式。 |
|
||||
| Plan | Copilot 创建并运行多步骤计划。 |
|
||||
| Allow All | Copilot 无需询问即批准所有工具、路径和 URL 请求。 |
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Hoplite
|
||||
description: Install and configure Hoplite for Paseo.
|
||||
description: Install and add Hoplite for Paseo.
|
||||
nav: Hoplite
|
||||
order: 28
|
||||
category: Providers
|
||||
@@ -8,20 +8,20 @@ category: Providers
|
||||
|
||||
# Hoplite
|
||||
|
||||
Run Hoplite's cloud coding agent in Paseo through the Hoplite CLI on your daemon host.
|
||||
Paseo runs Hoplite's cloud coding agent through the Agent Client Protocol (`hoplite acp`) on your installed `hoplite` CLI.
|
||||
|
||||
## Getting started
|
||||
|
||||
Add Hoplite from Settings in Paseo before you start an agent.
|
||||
|
||||
1. Install the [Hoplite CLI](https://hoplite.sh/docs/cli) on your daemon host.
|
||||
2. Run `hoplite login`.
|
||||
3. In Paseo, open **Settings → Hosts → your host → Providers**, select **+ Provider**, find **Hoplite**, and choose **Add**.
|
||||
2. Run `hoplite login` in a terminal.
|
||||
3. In Paseo, open **Settings → Hosts → your host → Providers**, select **+ Provider**, find **Hoplite**, and select **Add**.
|
||||
|
||||
Paseo launches `hoplite acp`. See [Hoplite's ACP guide](https://hoplite.sh/docs/cli/acp) for authentication and project setup.
|
||||
|
||||
If `hoplite` is outside your daemon's PATH, use a [command override](/docs/custom-providers) and keep `acp` in the arguments.
|
||||
See [Hoplite's ACP guide](https://hoplite.sh/docs/cli/acp) for authentication and project setup. If `hoplite` is outside your daemon PATH, use a [command override](/docs/custom-providers#custom-binary) and keep `acp` in the arguments.
|
||||
|
||||
## Projects and the cloud workspace
|
||||
|
||||
Hoplite runs the agent in a cloud workspace. Your local files and Paseo's loopback MCP tools are not available in that cloud workspace.
|
||||
Hoplite runs the agent in a cloud workspace. Your local files and Paseo's loopback MCP tools are not available there.
|
||||
|
||||
Open a repository that is linked to a Hoplite project, or set `agents.providers.hoplite.env.HOPLITE_PROJECT_ID` to use one project everywhere. Without a linked repository or a pinned project, discovery reports `No Hoplite project`.
|
||||
|
||||
@@ -1,25 +1,25 @@
|
||||
---
|
||||
title: Hoplite
|
||||
description: 为 Paseo 安装和配置 Hoplite。
|
||||
description: 为 Paseo 安装并添加 Hoplite。
|
||||
nav: Hoplite
|
||||
---
|
||||
|
||||
# Hoplite {#hoplite}
|
||||
|
||||
通过 daemon 主机上的 Hoplite CLI,在 Paseo 中运行 Hoplite 的云端编程 Agent。
|
||||
Paseo 通过你已安装的 `hoplite` CLI 提供的 Agent Client Protocol(`hoplite acp`)运行 Hoplite 的云端编程 Agent。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
启动 Agent 前,请先在 Paseo 设置中添加 Hoplite。
|
||||
|
||||
1. 在 daemon 主机上安装 [Hoplite CLI](https://hoplite.sh/docs/cli)。
|
||||
2. 运行 `hoplite login`。
|
||||
3. 在 Paseo 中打开 **设置 → Hosts → 你的主机 → Providers**,选择 **+ Provider**,找到 **Hoplite** 并选择 **添加**。
|
||||
2. 在终端中运行 `hoplite login`。
|
||||
3. 在 Paseo 中打开 **设置 → Hosts → 你的主机 → Providers**,选择 **+ Provider**,找到 **Hoplite**,然后选择 **添加**。
|
||||
|
||||
Paseo 会启动 `hoplite acp`。认证和项目设置见 [Hoplite 的 ACP 指南](https://hoplite.sh/docs/cli/acp)。
|
||||
|
||||
如果 `hoplite` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers),并在参数中保留 `acp`。
|
||||
认证和项目设置见 [Hoplite 的 ACP 指南](https://hoplite.sh/docs/cli/acp)。如果 `hoplite` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers#custom-binary),并在参数中保留 `acp`。
|
||||
|
||||
## 项目和云端工作区 {#projects-and-the-cloud-workspace}
|
||||
|
||||
Hoplite 在云端工作区中运行 Agent。你的本地文件和 Paseo 的回环 MCP 工具在该云端工作区中不可用。
|
||||
Hoplite 在云端工作区中运行 Agent。你的本地文件和 Paseo 的回环 MCP 工具在那里不可用。
|
||||
|
||||
请打开一个关联了 Hoplite 项目的仓库,或者设置 `agents.providers.hoplite.env.HOPLITE_PROJECT_ID`,在所有地方使用同一个项目。如果既没有关联的仓库也没有固定的项目,发现过程会报告 `No Hoplite project`。
|
||||
|
||||
@@ -12,24 +12,30 @@ Paseo runs coding agents that you install and sign in to on your daemon host. Fo
|
||||
|
||||
## Native support
|
||||
|
||||
Paseo ships an integration for each of these agents.
|
||||
Paseo ships an integration for each of these agents. Most appear in Paseo automatically after you install and sign in to the CLI. Open a provider page for setup steps and defaults.
|
||||
|
||||
- [Antigravity](/docs/supported-providers/antigravity), runs through your installed `agy` CLI.
|
||||
- [Antigravity](/docs/supported-providers/antigravity), runs through your installed `agy` CLI over ACP.
|
||||
- [Claude Code](/docs/supported-providers/claude-code), Anthropic's coding agent.
|
||||
- [Codex](/docs/supported-providers/codex), OpenAI's workspace agent.
|
||||
- [fx](/docs/supported-providers/fx), Vercel Labs' coding agent.
|
||||
- [fx](/docs/supported-providers/fx), Vercel Labs' coding agent (add from Settings).
|
||||
- [GitHub Copilot](/docs/supported-providers/github-copilot), GitHub's AI pair programmer.
|
||||
- [Hoplite](/docs/supported-providers/hoplite), cloud coding agent.
|
||||
- [Hoplite](/docs/supported-providers/hoplite), cloud coding agent (add from Settings).
|
||||
- [Muse Code](/docs/supported-providers/muse-code), Meta's terminal coding agent.
|
||||
- [Oh My Pi](/docs/supported-providers/omp), multi-provider coding agent.
|
||||
- [Oh My Pi](/docs/supported-providers/omp), multi-provider coding agent (off by default).
|
||||
- [OpenCode](/docs/supported-providers/opencode), open-source coding assistant.
|
||||
- [Pi](/docs/supported-providers/pi), minimal terminal coding agent.
|
||||
|
||||
## More agents through ACP
|
||||
|
||||
Paseo runs any agent that speaks the [Agent Client Protocol](https://agentclientprotocol.com) (ACP). The in-app catalog lists the agents below.
|
||||
Paseo runs any agent that speaks the [Agent Client Protocol](https://agentclientprotocol.com) (ACP). The in-app catalog lists these agents.
|
||||
|
||||
To add one, open **Settings → Hosts → your host → Providers**, select **+ Provider**, find the agent, and choose **Add**. Entries that launch through `npx` or `uvx` need only that tool on your daemon host. For the other entries, install the CLI of the agent first. If the CLI is missing, the page of the provider says **Not installed**, and **Install** opens its install instructions.
|
||||
To add one from the catalog:
|
||||
|
||||
1. If the agent does not launch through `npx` or `uvx`, install its CLI on your daemon host.
|
||||
2. Open **Settings → Hosts → your host → Providers** in Paseo.
|
||||
3. Select **+ Provider**, find the agent, and select **Add**.
|
||||
|
||||
Entries that launch through `npx` or `uvx` need only that tool on your daemon host. If a CLI is missing, the provider page shows **Not installed**, and **Install** opens its install instructions.
|
||||
|
||||
- [Agoragentic](https://agoragentic.com), agent marketplace with 174+ AI capabilities.
|
||||
- [Amp](https://github.com/tao12345666333/amp-acp), frontier coding agent.
|
||||
|
||||
@@ -10,16 +10,16 @@ Paseo 运行由你在 daemon 主机上安装并登录的编程 Agent。关于 Pa
|
||||
|
||||
## 原生支持 {#native-support}
|
||||
|
||||
Paseo 为以下每个 Agent 都提供了集成。
|
||||
Paseo 为以下每个 Agent 都提供了集成。大多数 Agent 在你安装并登录 CLI 后会自动出现在 Paseo 中。打开对应 Provider 的页面可查看安装步骤和默认设置。
|
||||
|
||||
- [Antigravity](/docs/supported-providers/antigravity):通过你已安装的 `agy` CLI 运行。
|
||||
- [Antigravity](/docs/supported-providers/antigravity):通过你已安装的 `agy` CLI 经由 ACP 运行。
|
||||
- [Claude Code](/docs/supported-providers/claude-code):Anthropic 的编程 Agent。
|
||||
- [Codex](/docs/supported-providers/codex):OpenAI 的工作区 Agent。
|
||||
- [fx](/docs/supported-providers/fx):Vercel Labs 的编程 Agent。
|
||||
- [fx](/docs/supported-providers/fx):Vercel Labs 的编程 Agent(从设置中添加)。
|
||||
- [GitHub Copilot](/docs/supported-providers/github-copilot):GitHub 的 AI 结对编程助手。
|
||||
- [Hoplite](/docs/supported-providers/hoplite):云端编程 Agent。
|
||||
- [Hoplite](/docs/supported-providers/hoplite):云端编程 Agent(从设置中添加)。
|
||||
- [Muse Code](/docs/supported-providers/muse-code):Meta 的终端编程 Agent。
|
||||
- [Oh My Pi](/docs/supported-providers/omp):支持多家 Provider 的编程 Agent。
|
||||
- [Oh My Pi](/docs/supported-providers/omp):支持多家 Provider 的编程 Agent(默认关闭)。
|
||||
- [OpenCode](/docs/supported-providers/opencode):开源编程助手。
|
||||
- [Pi](/docs/supported-providers/pi):极简的终端编程 Agent。
|
||||
|
||||
@@ -27,7 +27,13 @@ Paseo 为以下每个 Agent 都提供了集成。
|
||||
|
||||
Paseo 可以运行任何使用 [Agent Client Protocol](https://agentclientprotocol.com)(ACP)的 Agent。应用内目录列出了以下 Agent。
|
||||
|
||||
要添加其中一个,请打开 **设置 → Hosts → 你的主机 → Providers**,选择 **+ Provider**,找到该 Agent 并选择 **添加**。通过 `npx` 或 `uvx` 启动的条目只需要 daemon 主机上有该工具。其他条目请先安装该 Agent 的 CLI。如果缺少 CLI,该 provider 的页面会显示 **未安装**,**安装** 会打开它的安装说明。
|
||||
从目录添加其中一个:
|
||||
|
||||
1. 如果该 Agent 不是通过 `npx` 或 `uvx` 启动的,请先在 daemon 主机上安装它的 CLI。
|
||||
2. 在 Paseo 中打开 **设置 → Hosts → 你的主机 → Providers**。
|
||||
3. 选择 **+ Provider**,找到该 Agent,然后选择 **添加**。
|
||||
|
||||
通过 `npx` 或 `uvx` 启动的条目只需要 daemon 主机上有该工具。如果缺少 CLI,Provider 页面会显示 **未安装**,选择 **安装** 会打开它的安装说明。
|
||||
|
||||
- [Agoragentic](https://agoragentic.com):拥有 174 种以上 AI 能力的 Agent 市场。
|
||||
- [Amp](https://github.com/tao12345666333/amp-acp):前沿的编程 Agent。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Muse Code
|
||||
description: Install and configure Muse Code for Paseo.
|
||||
description: Run Meta's Muse Code in Paseo with your installed muse CLI.
|
||||
nav: Muse Code
|
||||
order: 29
|
||||
category: Providers
|
||||
@@ -8,33 +8,42 @@ category: Providers
|
||||
|
||||
# Muse Code
|
||||
|
||||
Run Meta's terminal coding agent in Paseo with your existing Muse installation and credentials.
|
||||
Paseo runs Meta's Muse Code through your installed `muse` CLI (`muse serve`) over the Muse Session Protocol (MSP). It uses your existing Muse credentials and configuration.
|
||||
|
||||
## Getting started
|
||||
|
||||
Install Muse Code on the machine running the Paseo daemon:
|
||||
Muse Code is built into Paseo and enabled by default. Use Muse 1.3.0 or later (verified with 1.4.1).
|
||||
|
||||
```bash
|
||||
curl -fsSL https://dev.meta.ai/install.sh | sh
|
||||
muse login
|
||||
```
|
||||
1. Install Muse Code on your daemon host:
|
||||
|
||||
Use Muse 1.3.0 or newer. This integration was verified with 1.4.1. For API access, set
|
||||
`META_API_KEY` in the daemon's environment instead of logging in. See
|
||||
[provider environment overrides](/docs/custom-providers).
|
||||
```bash
|
||||
curl -fsSL https://dev.meta.ai/install.sh | sh
|
||||
```
|
||||
|
||||
In Paseo, select **Muse Code**, then choose a model, approval mode, and reasoning effort.
|
||||
Paseo runs `muse serve` and communicates over the Muse Session Protocol (MSP). Your Muse
|
||||
configuration determines the available models.
|
||||
2. Sign in with `muse login`, or set `META_API_KEY` in the daemon environment.
|
||||
3. In Paseo, choose **Muse Code** when you start an agent.
|
||||
|
||||
Your Muse configuration determines the available models. If `muse` is outside your daemon PATH or you need custom environment variables, see [Custom providers](/docs/custom-providers) and configure `agents.providers.muse`.
|
||||
|
||||
## Modes and skills
|
||||
|
||||
Approval modes control tool decisions separately from provider options. **Default** is the default mode.
|
||||
|
||||
- Available modes are **Default**, **Ask**, **Strict**, and **Full access**.
|
||||
- **Full access** approves escalated approval stages automatically and keeps your effective provider options.
|
||||
- Muse skills appear in the slash-command menu alongside `/compact`.
|
||||
|
||||
## Provider options
|
||||
|
||||
Paseo launches Muse with the sandbox disabled (`--disable-sandbox`) and workspace trust
|
||||
on (`--trust-workspace`). Muse can install packages using your npm cache and load project
|
||||
rules, skills, and configuration.
|
||||
By default, Paseo launches Muse with the sandbox disabled (`--disable-sandbox`) and workspace trust enabled (`--trust-workspace`). Muse can install packages with your npm cache and load project rules, skills, and configuration.
|
||||
|
||||
Set defaults for every Muse agent in `config.json` on the daemon machine under
|
||||
`agents.providers.muse.options`:
|
||||
| Option | Default | Effect |
|
||||
| ----------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `sandbox.enabled` | `false` | Enables Muse's filesystem and network sandbox. Its read-only home directory prevents npm from writing the default cache. |
|
||||
| `sandbox.network` | `"proxy-only"` | Sandbox network policy: `"proxy-only"`, `"restricted"`, or `"enabled"`. With sandbox disabled, Muse allows full network access. |
|
||||
| `trustWorkspace` | `true` | Lets Muse load project rules, skills, and configuration. |
|
||||
|
||||
To change defaults for every Muse agent, configure `agents.providers.muse.options` in `~/.paseo/config.json` on your daemon host:
|
||||
|
||||
```json
|
||||
{
|
||||
@@ -51,35 +60,11 @@ Set defaults for every Muse agent in `config.json` on the daemon machine under
|
||||
}
|
||||
```
|
||||
|
||||
You can also supply per-agent `providerOptions` when creating an agent. The daemon merges
|
||||
provider defaults with the per-agent options and delivers the effective `providerOptions`
|
||||
to Muse. See [provider options](/docs/sdk/provider-options) for configuration and creation.
|
||||
|
||||
Per-agent options are saved with the agent and reapplied when its Muse host opens on refresh
|
||||
or resume. Invalid values and unknown keys fail session creation with a `providerOptions`
|
||||
error.
|
||||
|
||||
| Option | Default | Effect |
|
||||
| ----------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `sandbox.enabled` | `false` | Enables Muse's filesystem and network sandbox. Its read-only home directory prevents npm from writing the default cache. |
|
||||
| `sandbox.network` | `"proxy-only"` | Sandbox network policy: `"proxy-only"`, `"restricted"`, or `"enabled"`. With sandbox disabled, Muse allows full network access. |
|
||||
| `trustWorkspace` | `true` | Lets Muse load project rules, skills, and configuration. |
|
||||
|
||||
Approval modes control tool decisions separately: **Default**, **Ask**, **Strict**, and
|
||||
**Full access**. Full access automatically allows escalated approval stages; it preserves
|
||||
the effective provider options. Skills appear in the slash-command menu, alongside `/compact`.
|
||||
You can also pass per-agent `providerOptions` when you create an agent. The daemon merges provider defaults with per-agent options and saves them with the agent for refresh or resume. Invalid values or unknown keys fail session creation with a `providerOptions` error. See [Provider options](/docs/sdk/provider-options) for details.
|
||||
|
||||
## Limitations in Muse 1.4.1
|
||||
|
||||
- **Paseo MCP tools are unavailable.** Muse drops the returned tool namespace before matching
|
||||
an MCP call. This upstream issue must be fixed in Muse before its agents can use Paseo tools.
|
||||
- **Compaction needs a model context limit.** If your endpoint does not report one, configure
|
||||
`context_compaction.provider_context_limit_tokens` in Muse for the selected model.
|
||||
- **Usage windows appear only when Muse reports them.** An empty `usage/read` response
|
||||
leaves subscription usage unavailable.
|
||||
- **Native subagents may need Muse's experimental SDK flag.** Set
|
||||
`MUSE_EXPERIMENTAL_SDK_ENABLED=on` in the provider environment if native subagent tools
|
||||
are missing. Linked child sessions appear only when Muse supplies `childSessionId`.
|
||||
|
||||
See [custom providers](/docs/custom-providers) to override the binary or environment under
|
||||
`agents.providers.muse`.
|
||||
- Paseo MCP tools are unavailable because Muse drops the returned tool namespace before matching an MCP call. This upstream issue must be fixed in Muse before Muse agents can use Paseo tools.
|
||||
- Compaction needs a model context limit. If your endpoint does not report one, configure `context_compaction.provider_context_limit_tokens` in Muse for the selected model.
|
||||
- Usage windows appear only when Muse reports them. An empty `usage/read` response leaves subscription usage unavailable.
|
||||
- If native subagent tools are missing, set `MUSE_EXPERIMENTAL_SDK_ENABLED=on` in the provider environment. Linked child sessions appear only when Muse supplies `childSessionId`.
|
||||
|
||||
@@ -1,31 +1,47 @@
|
||||
---
|
||||
title: Muse Code
|
||||
description: 为 Paseo 安装和配置 Muse Code。
|
||||
description: 使用已安装的 muse CLI 在 Paseo 中运行 Meta 的 Muse Code。
|
||||
nav: Muse Code
|
||||
---
|
||||
|
||||
# Muse Code {#muse-code}
|
||||
|
||||
使用你现有的 Muse 安装和凭据,在 Paseo 中运行 Meta 的终端编程 Agent。
|
||||
Paseo 通过你已安装的 `muse` CLI(`muse serve`)经由 Muse Session Protocol(MSP)运行 Meta 的 Muse Code。它使用你现有的 Muse 凭据和配置。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
在运行 Paseo daemon 的机器上安装 Muse Code:
|
||||
Muse Code 内置于 Paseo 且默认启用。请使用 Muse 1.3.0 或更高版本(已在 1.4.1 上验证)。
|
||||
|
||||
```bash
|
||||
curl -fsSL https://dev.meta.ai/install.sh | sh
|
||||
muse login
|
||||
```
|
||||
1. 在 daemon 主机上安装 Muse Code:
|
||||
|
||||
请使用 Muse 1.3.0 或更高版本。此集成已在 1.4.1 上验证。如需 API 访问,请在 daemon 的环境中设置 `META_API_KEY`,而不是登录。参见 [Provider 环境变量覆盖](/docs/custom-providers)。
|
||||
```bash
|
||||
curl -fsSL https://dev.meta.ai/install.sh | sh
|
||||
```
|
||||
|
||||
在 Paseo 中选择 **Muse Code**,然后选择模型、审批模式和推理强度。Paseo 运行 `muse serve`,并通过 Muse Session Protocol(MSP)通信。可用的模型由你的 Muse 配置决定。
|
||||
2. 运行 `muse login` 登录,或在 daemon 环境中设置 `META_API_KEY`。
|
||||
3. 在 Paseo 中启动 Agent 时选择 **Muse Code**。
|
||||
|
||||
可用的模型由你的 Muse 配置决定。如果 `muse` 不在 daemon 的 PATH 中,或需要自定义环境变量,请参见[自定义 Provider](/docs/custom-providers)并配置 `agents.providers.muse`。
|
||||
|
||||
## 模式和技能 {#modes-and-skills}
|
||||
|
||||
审批模式与 Provider 选项分开控制工具决策。**Default** 是默认模式。
|
||||
|
||||
- 可用模式包括 **Default**、**Ask**、**Strict** 和 **Full access**。
|
||||
- **Full access** 会自动批准升级的审批阶段,并保留生效的 Provider 选项。
|
||||
- Muse 技能会和 `/compact` 一起出现在斜杠命令菜单中。
|
||||
|
||||
## Provider 选项 {#provider-options}
|
||||
|
||||
Paseo 启动 Muse 时会禁用沙箱(`--disable-sandbox`)并开启工作区信任(`--trust-workspace`)。Muse 可以使用你的 npm 缓存安装软件包,并加载项目规则、技能和配置。
|
||||
默认情况下,Paseo 启动 Muse 时会禁用沙箱(`--disable-sandbox`)并启用工作区信任(`--trust-workspace`)。Muse 可以使用你的 npm 缓存安装软件包,并加载项目规则、技能和配置。
|
||||
|
||||
在 daemon 所在机器的 `config.json` 中,于 `agents.providers.muse.options` 下为所有 Muse Agent 设置默认值:
|
||||
| 选项 | 默认值 | 作用 |
|
||||
| ----------------- | -------------- | -------------------------------------------------------------------------------------------------- |
|
||||
| `sandbox.enabled` | `false` | 启用 Muse 的文件系统和网络沙箱。沙箱中的主目录是只读的,npm 无法写入默认缓存。 |
|
||||
| `sandbox.network` | `"proxy-only"` | 沙箱网络策略:`"proxy-only"`、`"restricted"` 或 `"enabled"`。禁用沙箱时,Muse 允许完全的网络访问。 |
|
||||
| `trustWorkspace` | `true` | 允许 Muse 加载项目规则、技能和配置。 |
|
||||
|
||||
要为所有 Muse Agent 更改默认值,请在 daemon 主机的 `~/.paseo/config.json` 中配置 `agents.providers.muse.options`:
|
||||
|
||||
```json
|
||||
{
|
||||
@@ -42,23 +58,11 @@ Paseo 启动 Muse 时会禁用沙箱(`--disable-sandbox`)并开启工作区
|
||||
}
|
||||
```
|
||||
|
||||
创建 Agent 时,你也可以提供每个 Agent 各自的 `providerOptions`。daemon 会把 Provider 默认值与每个 Agent 的选项合并,并把生效的 `providerOptions` 传给 Muse。配置和创建方法见 [Provider 选项](/docs/sdk/provider-options)。
|
||||
|
||||
每个 Agent 的选项会随 Agent 一起保存,并在刷新或恢复时打开其 Muse 主机时重新应用。无效的值和未知的键会使会话创建失败,并报告 `providerOptions` 错误。
|
||||
|
||||
| 选项 | 默认值 | 作用 |
|
||||
| ----------------- | -------------- | -------------------------------------------------------------------------------------------------- |
|
||||
| `sandbox.enabled` | `false` | 启用 Muse 的文件系统和网络沙箱。沙箱中的主目录是只读的,npm 无法写入默认缓存。 |
|
||||
| `sandbox.network` | `"proxy-only"` | 沙箱网络策略:`"proxy-only"`、`"restricted"` 或 `"enabled"`。禁用沙箱时,Muse 允许完全的网络访问。 |
|
||||
| `trustWorkspace` | `true` | 允许 Muse 加载项目规则、技能和配置。 |
|
||||
|
||||
审批模式单独控制工具决策:**Default**、**Ask**、**Strict** 和 **Full access**。Full access 会自动允许升级的审批阶段,并保留生效的 Provider 选项。技能会和 `/compact` 一起出现在斜杠命令菜单中。
|
||||
创建 Agent 时,你也可以传入每个 Agent 各自的 `providerOptions`。daemon 会将 Provider 默认值与每个 Agent 的选项合并,并随 Agent 保存,以便刷新或恢复时使用。无效的值或未知的键会使会话创建失败,并报告 `providerOptions` 错误。详情见 [Provider 选项](/docs/sdk/provider-options)。
|
||||
|
||||
## Muse 1.4.1 中的限制 {#limitations-in-muse-141}
|
||||
|
||||
- **Paseo MCP 工具不可用。** Muse 在匹配 MCP 调用之前丢弃了返回的工具命名空间。这是上游问题,必须先在 Muse 中修复,它的 Agent 才能使用 Paseo 工具。
|
||||
- **上下文压缩需要模型的上下文上限。** 如果你的端点不报告上限,请在 Muse 中为所选模型配置 `context_compaction.provider_context_limit_tokens`。
|
||||
- **只有 Muse 报告用量窗口时才会显示。** `usage/read` 返回空响应时,订阅用量将不可用。
|
||||
- **原生子 Agent 可能需要 Muse 的实验性 SDK 开关。** 如果缺少原生子 Agent 工具,请在 Provider 环境中设置 `MUSE_EXPERIMENTAL_SDK_ENABLED=on`。只有当 Muse 提供 `childSessionId` 时,关联的子会话才会出现。
|
||||
|
||||
要在 `agents.providers.muse` 下覆盖二进制文件或环境变量,请参见[自定义 Provider](/docs/custom-providers)。
|
||||
- Paseo MCP 工具不可用,因为 Muse 在匹配 MCP 调用前会丢弃返回的工具命名空间。此上游问题必须先在 Muse 中修复,Muse Agent 才能使用 Paseo 工具。
|
||||
- 上下文压缩需要模型的上下文上限。如果你的端点不报告上限,请在 Muse 中为所选模型配置 `context_compaction.provider_context_limit_tokens`。
|
||||
- 只有 Muse 报告用量窗口时才会显示。`usage/read` 返回空响应时,订阅用量不可用。
|
||||
- 如果缺少原生子 Agent 工具,请在 Provider 环境中设置 `MUSE_EXPERIMENTAL_SDK_ENABLED=on`。只有当 Muse 提供 `childSessionId` 时,关联的子会话才会出现。
|
||||
|
||||
@@ -8,26 +8,17 @@ category: Providers
|
||||
|
||||
# Oh My Pi
|
||||
|
||||
Run Oh My Pi (OMP) in Paseo with your existing `omp` installation and settings.
|
||||
Paseo runs Oh My Pi (OMP) through your installed `omp` CLI. It uses your existing credentials and settings.
|
||||
|
||||
## Getting started
|
||||
|
||||
1. Install [Oh My Pi](https://github.com/can1357/oh-my-pi) on your daemon host and make sure that `omp` runs in a terminal.
|
||||
Oh My Pi is built into Paseo and off by default.
|
||||
|
||||
1. Install [Oh My Pi](https://github.com/can1357/oh-my-pi) on your daemon host, and make sure that `omp` runs in a terminal.
|
||||
2. In Paseo, open **Settings → Hosts → your host → Providers** and turn on **Oh My Pi**.
|
||||
3. Choose **Oh My Pi** when you start an agent.
|
||||
|
||||
Oh My Pi is off by default. You can also turn it on in `~/.paseo/config.json`:
|
||||
|
||||
```json
|
||||
{
|
||||
"agents": {
|
||||
"providers": {
|
||||
"omp": { "enabled": true }
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
If `omp` is outside your daemon's PATH, use a [command override](/docs/custom-providers). To run a second OMP profile with its own settings, see [OMP profiles](https://github.com/getpaseo/paseo/blob/main/docs/custom-providers.md#omp-profiles-and-pi-compatible-forks) on GitHub.
|
||||
If `omp` is outside your daemon PATH, use a [command override](/docs/custom-providers#custom-binary). You can also enable `omp` in `~/.paseo/config.json` under `agents.providers.omp`. To run a second OMP profile with its own settings, see [OMP profiles](https://github.com/getpaseo/paseo/blob/main/docs/custom-providers.md#omp-profiles-and-pi-compatible-forks) on GitHub.
|
||||
|
||||
## Permission modes
|
||||
|
||||
|
||||
@@ -6,26 +6,17 @@ nav: Oh My Pi
|
||||
|
||||
# Oh My Pi {#oh-my-pi}
|
||||
|
||||
使用你现有的 `omp` 安装和设置,在 Paseo 中运行 Oh My Pi(OMP)。
|
||||
Paseo 通过你已安装的 `omp` CLI 运行 Oh My Pi(OMP)。它使用你现有的凭据和设置。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
Oh My Pi 内置于 Paseo,默认关闭。
|
||||
|
||||
1. 在 daemon 主机上安装 [Oh My Pi](https://github.com/can1357/oh-my-pi),并确认 `omp` 可以在终端中运行。
|
||||
2. 在 Paseo 中打开 **设置 → Hosts → 你的主机 → Providers**,启用 **Oh My Pi**。
|
||||
2. 在 Paseo 中打开 **设置 → Hosts → 你的主机 → Providers**,然后启用 **Oh My Pi**。
|
||||
3. 启动 Agent 时选择 **Oh My Pi**。
|
||||
|
||||
Oh My Pi 默认关闭。你也可以在 `~/.paseo/config.json` 中启用它:
|
||||
|
||||
```json
|
||||
{
|
||||
"agents": {
|
||||
"providers": {
|
||||
"omp": { "enabled": true }
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
如果 `omp` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers)。如需运行带有独立设置的第二个 OMP 配置,请参见 GitHub 上的 [OMP profiles](https://github.com/getpaseo/paseo/blob/main/docs/custom-providers.md#omp-profiles-and-pi-compatible-forks)。
|
||||
如果 `omp` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers#custom-binary)。你也可以在 `~/.paseo/config.json` 的 `agents.providers.omp` 下启用 `omp`。如需运行带有独立设置的第二个 OMP 配置,请参见 GitHub 上的 [OMP profiles](https://github.com/getpaseo/paseo/blob/main/docs/custom-providers.md#omp-profiles-and-pi-compatible-forks)。
|
||||
|
||||
## 权限模式 {#permission-modes}
|
||||
|
||||
|
||||
@@ -8,10 +8,12 @@ category: Providers
|
||||
|
||||
# OpenCode
|
||||
|
||||
Run OpenCode in Paseo with your existing `opencode` installation, credentials, and configuration.
|
||||
Paseo runs OpenCode through your installed `opencode` CLI. It uses your existing credentials and configuration.
|
||||
|
||||
## Getting started
|
||||
|
||||
OpenCode is built into Paseo and enabled by default.
|
||||
|
||||
1. Install [OpenCode](https://opencode.ai/) on your daemon host:
|
||||
|
||||
```bash
|
||||
@@ -21,13 +23,13 @@ Run OpenCode in Paseo with your existing `opencode` installation, credentials, a
|
||||
2. Connect OpenCode to a model provider, and make sure that `opencode` runs in a terminal.
|
||||
3. In Paseo, choose **OpenCode** when you start an agent.
|
||||
|
||||
If you use OpenCode v2, install version 2.0.10 or newer. Paseo rejects older v2 versions.
|
||||
If you use OpenCode v2, install version 2.0.10 or later. Paseo rejects older v2 versions.
|
||||
|
||||
If `opencode` is outside your daemon's PATH, use a [command override](/docs/custom-providers#custom-binary).
|
||||
If `opencode` is outside your daemon PATH, use a [command override](/docs/custom-providers#custom-binary).
|
||||
|
||||
## Modes
|
||||
|
||||
Paseo shows the agents of OpenCode as modes.
|
||||
Paseo shows OpenCode agents as modes.
|
||||
|
||||
| Mode | Effect |
|
||||
| ----- | ----------------------------------------------- |
|
||||
|
||||
@@ -6,10 +6,12 @@ nav: OpenCode
|
||||
|
||||
# OpenCode {#opencode}
|
||||
|
||||
使用你现有的 `opencode` 安装、凭据和配置,在 Paseo 中运行 OpenCode。
|
||||
Paseo 通过你已安装的 `opencode` CLI 运行 OpenCode。它使用你现有的凭据和配置。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
OpenCode 内置于 Paseo 且默认启用。
|
||||
|
||||
1. 在 daemon 主机上安装 [OpenCode](https://opencode.ai/):
|
||||
|
||||
```bash
|
||||
|
||||
@@ -8,24 +8,23 @@ category: Providers
|
||||
|
||||
# Pi
|
||||
|
||||
Run Pi in Paseo with your existing `pi` installation, credentials, and settings.
|
||||
Paseo runs Pi through your installed `pi` CLI. It uses your existing credentials and settings.
|
||||
|
||||
## Getting started
|
||||
|
||||
Pi is built into Paseo and enabled by default.
|
||||
|
||||
1. Install [Pi](https://pi.dev) on your daemon host.
|
||||
2. Connect Pi to a model provider, and make sure that `pi` runs in a terminal.
|
||||
3. In Paseo, choose **Pi** when you start an agent.
|
||||
|
||||
Pi appears in Paseo when the daemon can launch `pi`. If `pi` is outside your daemon's PATH, use a [command override](/docs/custom-providers#custom-binary).
|
||||
Pi appears in Paseo when the daemon can launch `pi`. If `pi` is outside your daemon PATH, use a [command override](/docs/custom-providers#custom-binary).
|
||||
|
||||
## Modes and sessions
|
||||
## Modes, sessions, and timeouts
|
||||
|
||||
- Pi has no permission modes, so Paseo shows no mode selector for a Pi agent.
|
||||
- Paseo can import sessions that you started in a terminal. It reads them from `~/.pi/agent/sessions`, or from the session directory that you configured in Pi.
|
||||
|
||||
## Timeouts
|
||||
|
||||
Paseo waits 60 seconds for Pi to answer a control request, such as a request for the model list. If Pi needs longer on your host, raise `rpcTimeoutMs` in [Provider options](/docs/custom-providers#provider-options).
|
||||
- Paseo waits 60 seconds for Pi to answer a control request, such as a request for the model list. If Pi needs longer on your host, raise `rpcTimeoutMs` in [Provider options](/docs/custom-providers#provider-options).
|
||||
|
||||
## See also
|
||||
|
||||
|
||||
@@ -6,24 +6,23 @@ nav: Pi
|
||||
|
||||
# Pi {#pi}
|
||||
|
||||
使用你现有的 `pi` 安装、凭据和设置,在 Paseo 中运行 Pi。
|
||||
Paseo 通过你已安装的 `pi` CLI 运行 Pi。它使用你现有的凭据和设置。
|
||||
|
||||
## 开始使用 {#getting-started}
|
||||
|
||||
Pi 内置于 Paseo 且默认启用。
|
||||
|
||||
1. 在 daemon 主机上安装 [Pi](https://pi.dev)。
|
||||
2. 为 Pi 配置模型 Provider,并确认 `pi` 可以在终端中运行。
|
||||
3. 在 Paseo 中启动 Agent 时选择 **Pi**。
|
||||
|
||||
daemon 能够启动 `pi` 时,Pi 就会出现在 Paseo 中。如果 `pi` 不在 daemon 的 PATH 中,请使用[命令覆盖](/docs/custom-providers#custom-binary)。
|
||||
|
||||
## 模式和会话 {#modes-and-sessions}
|
||||
## 模式、会话和超时 {#modes-sessions-and-timeouts}
|
||||
|
||||
- Pi 没有权限模式,所以 Paseo 不会为 Pi Agent 显示模式选择器。
|
||||
- Paseo 可以导入你在终端中启动的会话。它从 `~/.pi/agent/sessions` 读取,或者从你在 Pi 中配置的会话目录读取。
|
||||
|
||||
## 超时 {#timeouts}
|
||||
|
||||
Paseo 等待 Pi 响应控制请求(例如获取模型列表)的时间上限为 60 秒。如果 Pi 在你的主机上需要更长时间,请在 [Provider 选项](/docs/custom-providers#provider-options)中调高 `rpcTimeoutMs`。
|
||||
- Paseo 等待 Pi 响应控制请求(例如获取模型列表)的时间上限为 60 秒。如果 Pi 在你的主机上需要更长时间,请在 [Provider 选项](/docs/custom-providers#provider-options)中调高 `rpcTimeoutMs`。
|
||||
|
||||
## 另请参阅 {#see-also}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user