Files
paseo/public-docs/why.zh-CN.md
T
Mohamed Boudra bd15e40e94 Serve paseo.sh in Simplified Chinese (#7373)
* feat(website): serve paseo.sh in Simplified Chinese

Every page of the website now has a Simplified Chinese version under
/zh-CN: the interface, docs, blog posts, comparison pages, legal pages,
all changelog releases and the homepage mockup. English URLs are unchanged.

The URL alone decides the language. There is no browser-language redirect
and no stored preference, because either would have to redirect the
unprefixed English URLs that people share and search engines index.
Internal links carry the page's language instead, and hreflang alternates
point Chinese search results at /zh-CN.

Translated headings pin the English anchor with {#id}, so section links
work in both languages. content-translations.test.ts fails when a page
has no translation or a translation's headings drift from the English.
Changelog releases and plugin listings without a translation render
whole in English under a notice, so a release never waits on one.

Plugin manifests and the registry gain optional translations and
OVERVIEW.zh-CN.md fields; older clients and registries ignore them.

* feat(website): replace the native language select with an EN/ZH menu

The header showed an OS-native select whose popup did not match the site.
The trigger now shows the language abbreviated (EN, ZH) and opens a menu in
the app's dropdown style that names each language in itself, with its name
in the page language underneath. Rows are real links to the same page in
that language; arrows, Escape, outside presses and taps behave as a menu
button, and the menu keeps itself on screen when a narrow header pushes the
trigger toward an edge.

Also drops the stray space after the full-width comma in the Chinese
homepage subtitle.

* docs(website): translate main's new docs and 0.12.0 release notes

Main added Keep run workspaces to the schedules docs, rewrote plugin icons
around inline SVG, and promoted 0.12.0 with new entries. Bring the Chinese
pages and changelog in line so no section falls back to English.

* fix(server): leave plugin listing translations to the registry

The daemon rejected manifests whose translations the registry would refuse,
so a plugin main installs could fail to load here. Paseo never reads
translations; the registry validates them at publish. Docs now say which
checks are automated at publish and which are human review.

* docs(plugins): describe the registry's final overview translation discovery

* style(server): format manifest test

* test(app): measure sidebar rows one at a time

After a reload the developer error toast appears while expectVerticalOrder
measures every row at once. Each concurrent boundingBox runs the toast
locator handler, and only one of them resumes, so the poll timed out on
every attempt since #7424. Measuring sequentially keeps one action in flight.

* test(app): return sidebar row measuring to main

#7480 hides the developer toast instead of running a locator handler, so
measuring the rows concurrently no longer races it. Reverts 41ac23016.

* test(app): wait for the compact shell before opening compact Changes

The shell survives the breakpoint, so right after the resize the wide
Explorer could still be visible: the test skipped the Explorer toggle and
the tab then disappeared, or toggled at the wrong time. Wait for the
compact-shell marker, as the composer helpers do since #7424.

* docs(website): translate main's plugin file panel docs

* test(app): edit the code font size after the font family remount

A committed appearance change remounts the settings screen through
AppearanceStyleBoundary, and the new form starts from the stored size.
Filling the size before that remount lost the edit in CI.

* docs(website): translate main's client/ui import docs

Follows #7474: one /client/ui entry, StreamedText instead of useRevealedText,
SettingsGroup dropped from the settings table, and the new
'UI imports in v0.13' migration section.

* test(app): wait for the previous layout's file panel picker to leave

After a resize the old layout's picker animates out while the new one is
already mounted, so the Use button matched two elements and the strict
locator failed. Wait for the shell's layout and a single picker first.
2026-10-21 13:13:03 +07:00

3.0 KiB
Raw Blame History

title, description, nav
title description nav
为什么选择 Paseo? 一个完整的 Agent 开发环境,用于运行编程 Agent、编辑文件、审查改动和测试你的工作。 为什么选择 Paseo?

为什么选择 Paseo?

Paseo 是一个完整的 Agent 开发环境。你可以运行编程 Agent、编辑文件、审查 diff 和 PR,并用终端和内置的桌面浏览器测试你的应用。对于由 Agent 驱动的开发,Paseo 可以替代你的 IDE:在一个应用里把任务从第一条提示词一路推进到审查和测试。

在一个工作区中开发

打开桌面应用,选择一个项目和一个 Agent,然后开始工作。对话、编辑器、终端、diff 和浏览器以分栏的形式放在一起。运行你的应用、检查结果、让 Agent 修改,都不用离开工作区。

桌面应用支持 macOS、Windows 和 Linux。它会自动启动和管理本地 daemon。

并行运行任务

为相互独立的任务分配各自的 worktree 和分支。同时运行多个 Agent,检查每份 diff,测试每个实现,再决定合并哪个。你可以为每个任务使用同一个 Provider,也可以为每个任务选择不同的 Provider 和模型。

配置工作区脚本,为每个 worktree 在不同端口上启动开发服务器。试试并行开发工作流。

使用你的 Agent 和工具

Paseo 运行你已经在用的编程 Agent,沿用你的订阅、凭据、配置、技能和 MCP 服务器。你的 Agent 使用你机器上的文件和工具。参见支持的 Provider。

你可以口述任务,或使用语音模式。语音转文字和文字转语音默认在本地运行,也可以在设置中选择云端 Provider。

在另一台设备上继续

daemon 持有正在运行的 Agent 和工作区。桌面应用在本地连接它;移动端、网页端和 CLI 客户端连接到同一个环境。这种分离让你可以在另一台设备上继续工作,或者把环境运行在服务器上。

你可以完全在笔记本电脑上使用 Paseo,也可以在需要时连接另一台机器。原生的 iOS 和 Android 应用让你在手机上使用 Agent、文件、终端和 diff。内置浏览器在桌面应用中运行。你可以直接连接你的设备,也可以通过可选的端到端加密中继连接。

自动化并扩展你的工作流

为 Agent 提供 Paseo 工具,让它们创建 worktree、启动其他 Agent、发送提示词并收集结果。使用 CLI 或 TypeScript SDK 自动化 Agent 和工作区操作。

插件可以添加 Provider、工作区面板、命令和工作流。Hub 把外部事件连接到在你机器上运行的 Agent。

Paseo 基于 Apache-2.0 开源,没有遥测和跟踪,也不需要 Paseo 账号。