@abelxiaoxing/cadence 2.0.36 → 2.0.38
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.de.md +4 -4
- package/README.es.md +4 -4
- package/README.fr.md +4 -4
- package/README.ja.md +4 -4
- package/README.ko.md +4 -4
- package/README.md +11 -9
- package/README.pt-BR.md +4 -4
- package/README.ru.md +4 -4
- package/README.zh-CN.md +12 -10
- package/THIRD_PARTY_NOTICES.md +9 -1
- package/agents/design-explorer.md +4 -2
- package/agents/diagnosis-worker.md +5 -2
- package/agents/implementation-worker.md +19 -12
- package/docs/conversation-mode.md +46 -18
- package/docs/reuse-and-distribution.md +1 -1
- package/docs/service-management.md +35 -9
- package/package.json +16 -8
- package/src/agent-browser/labeled-rule.ts +74 -0
- package/src/agent-browser/session-navigator.ts +214 -0
- package/src/agent-browser/source.ts +174 -0
- package/src/agent-browser/transcript-content.ts +442 -0
- package/src/agent-browser/transcript-pane.ts +324 -0
- package/src/agent-panel-cadence.ts +147 -628
- package/src/agent-panel-model.ts +34 -267
- package/src/agent-panel.ts +139 -437
- package/src/cadence-instructions.ts +8 -7
- package/src/cadence-mode.ts +30 -9
- package/src/change-tools.mjs +268 -0
- package/src/coordinator-tools.mjs +44 -16
- package/src/git-environment.d.mts +2 -0
- package/src/git-environment.mjs +24 -0
- package/src/image-content.mjs +7 -28
- package/src/index.ts +1 -1
- package/src/native-build.ts +1 -1
- package/src/native-workflow-history.ts +20 -3
- package/src/operator-cli.mjs +18 -11
- package/src/research-scan.mjs +393 -0
- package/src/research-tools.mjs +406 -342
- package/src/sdk-worker.mjs +42 -55
- package/src/service/contracts/core.ts +0 -1
- package/src/service/contracts/workbench.ts +21 -19
- package/src/service/contracts/workflow.ts +283 -16
- package/src/service/coordination.ts +7 -0
- package/src/service-cli.mjs +652 -149
- package/src/service-host.mjs +2745 -1137
- package/src/worker-capture.mjs +24 -1
- package/src/worker-public.mjs +19 -2
- package/src/worker-redaction.mjs +11 -0
- package/src/worker-toolkit.mjs +157 -0
- package/src/worker-workspace.d.mts +13 -0
- package/src/worker-workspace.mjs +48 -0
- package/src/workspace.ts +4 -24
- package/web/dist/assets/cadence.css +1 -1
- package/web/dist/assets/cadence.js +18 -17
- package/web/dist/manifest.json +7 -7
package/README.de.md
CHANGED
|
@@ -46,7 +46,7 @@ Port und Token liegen in `~/.pi/agent/cadence/.env`; wer das Token hat, kann dei
|
|
|
46
46
|
3. Sende einmal `/cadence [Ziel]`.
|
|
47
47
|
Dieses Gespräch bleibt im Cadence-Modus; kläre Anforderungen mit normalen Nachrichten.
|
|
48
48
|
4. Prüfe den vollständigen Plan und klicke **Implement this plan**.
|
|
49
|
-
Implementierung, Checks,
|
|
49
|
+
Implementierung, Checks, automatische Fehlerbehebung und die vereinbarte lokale Lieferung laufen automatisch.
|
|
50
50
|
5. Verfolge den Fortschritt im Gespräch; die Protokolle der Subagenten öffnest du über das Dock **Subagents** unten links.
|
|
51
51
|
Aktualisieren und Abschluss beenden den Modus nicht.
|
|
52
52
|
**Exit Cadence** beendet nur den Modus; **Cancel workflow — request stop** fordert den Abbruch an.
|
|
@@ -57,7 +57,7 @@ No live Pi terminal is required for the browser conversation workflow.
|
|
|
57
57
|
|
|
58
58
|
Gib einmal `/cadence <Ziel>` ein und führe danach ein normales Gespräch.
|
|
59
59
|
Cadence untersucht das Projekt, klärt Entscheidungen und erstellt einen Plan.
|
|
60
|
-
Nach ausdrücklicher Planfreigabe folgen Implementierung, Prüfungen,
|
|
60
|
+
Nach ausdrücklicher Planfreigabe folgen Implementierung, Prüfungen, automatische Fehlerbehebung und die vereinbarte lokale Integration automatisch.
|
|
61
61
|
|
|
62
62
|
Der Modus bleibt für dieses Gespräch aktiv, auch nach Abschluss eines Ziels.
|
|
63
63
|
Zum Verlassen `exit cadence` eingeben; dadurch wird laufende Arbeit nicht abgebrochen.
|
|
@@ -90,7 +90,7 @@ Ihre tatsächlichen Ergebnisse bleiben von der automatischen Agent-Prüfung getr
|
|
|
90
90
|
```sh
|
|
91
91
|
cadence server status
|
|
92
92
|
cadence server restart # nach einem Upgrade oder einer .env / models.json-Änderung
|
|
93
|
-
cadence server upgrade
|
|
93
|
+
cadence server upgrade
|
|
94
94
|
cadence server stop # bleibt registriert und startet beim nächsten Boot oder Login erneut
|
|
95
95
|
cadence server uninstall # vor npm uninstall -g ausführen
|
|
96
96
|
```
|
|
@@ -103,7 +103,7 @@ Linux-Root- und benannte Dienste, entfernter HTTPS-Zugang und Wiederherstellung
|
|
|
103
103
|
## Entwicklung
|
|
104
104
|
|
|
105
105
|
Pi kann auch ein lokales Checkout oder ein gepacktes Tarball laden: Füge seinen absoluten oder relativen Pfad zu Pís `packages` hinzu, oder versuche `pi -e ./cadence`.
|
|
106
|
-
Cadence
|
|
106
|
+
Cadence benötigt Pi 1.5.0 oder einen kompatiblen 1.x-Host; Entwicklungs-Pins und getestete Laufzeiten sind keine universellen Kompatibilitätsversprechen.
|
|
107
107
|
|
|
108
108
|
```sh
|
|
109
109
|
bun install
|
package/README.es.md
CHANGED
|
@@ -46,7 +46,7 @@ El puerto y el token están en `~/.pi/agent/cadence/.env`; cualquiera con el tok
|
|
|
46
46
|
3. Envía `/cadence [objetivo]` una vez.
|
|
47
47
|
Esta conversación permanece en modo Cadence; aclara los requisitos con mensajes normales.
|
|
48
48
|
4. Revisa el plan completo y pulsa **Implement this plan**.
|
|
49
|
-
La implementación, comprobaciones,
|
|
49
|
+
La implementación, comprobaciones, recuperación automática y entrega local acordada son automáticas.
|
|
50
50
|
5. Sigue el progreso en la conversación; abre los registros de los subagentes desde el panel **Subagents** abajo a la izquierda.
|
|
51
51
|
Recargar o terminar un objetivo no desactiva el modo.
|
|
52
52
|
**Exit Cadence** sale del modo; **Cancel workflow — request stop** solicita cancelar el trabajo.
|
|
@@ -57,7 +57,7 @@ No live Pi terminal is required for the browser conversation workflow.
|
|
|
57
57
|
|
|
58
58
|
Escribe `/cadence <objetivo>` una sola vez y continúa conversando normalmente.
|
|
59
59
|
Cadence investiga el proyecto, aclara decisiones y prepara un plan.
|
|
60
|
-
Tras aprobarlo explícitamente, implementa, verifica, realiza
|
|
60
|
+
Tras aprobarlo explícitamente, implementa, verifica, realiza recuperación automática y entrega la integración local acordada.
|
|
61
61
|
|
|
62
62
|
El modo permanece activo durante toda la conversación, incluso al terminar un objetivo.
|
|
63
63
|
Usa `exit cadence` para salir; salir no cancela el trabajo aceptado.
|
|
@@ -90,7 +90,7 @@ Sus resultados reales se mantienen separados de la revisión automática del age
|
|
|
90
90
|
```sh
|
|
91
91
|
cadence server status
|
|
92
92
|
cadence server restart # después de una actualización o un cambio de .env / models.json
|
|
93
|
-
cadence server upgrade
|
|
93
|
+
cadence server upgrade
|
|
94
94
|
cadence server stop # permanece registrado y vuelve a iniciar en el próximo arranque o inicio de sesión
|
|
95
95
|
cadence server uninstall # ejecutar antes de npm uninstall -g
|
|
96
96
|
```
|
|
@@ -103,7 +103,7 @@ Los servicios raíz de Linux y con nombre, el acceso HTTPS remoto y la recuperac
|
|
|
103
103
|
## Desarrollo
|
|
104
104
|
|
|
105
105
|
Pi también puede cargar un checkout local o un tarball empaquetado: añade su ruta absoluta o relativa a `packages` de Pi, o prueba `pi -e ./cadence`.
|
|
106
|
-
Cadence
|
|
106
|
+
Cadence requiere Pi 1.5.0 o un host 1.x compatible; los pines de desarrollo y los tiempos de ejecución probados no son promesas de compatibilidad universales.
|
|
107
107
|
|
|
108
108
|
```sh
|
|
109
109
|
bun install
|
package/README.fr.md
CHANGED
|
@@ -46,7 +46,7 @@ Le port et le jeton se trouvent dans `~/.pi/agent/cadence/.env` ; quiconque poss
|
|
|
46
46
|
3. Envoyez une fois `/cadence [objectif]`.
|
|
47
47
|
Cette conversation reste en mode Cadence ; précisez les besoins par des messages ordinaires.
|
|
48
48
|
4. Lisez le plan complet et cliquez sur **Implement this plan**.
|
|
49
|
-
L’implémentation, les vérifications,
|
|
49
|
+
L’implémentation, les vérifications, la reprise automatique et la livraison locale convenue sont automatiques.
|
|
50
50
|
5. Suivez la progression dans la conversation ; ouvrez les traces des sous-agents depuis le panneau **Subagents** en bas à gauche.
|
|
51
51
|
Actualiser ou terminer un objectif ne quitte pas le mode.
|
|
52
52
|
**Exit Cadence** quitte le mode ; **Cancel workflow — request stop** demande l’annulation.
|
|
@@ -57,7 +57,7 @@ No live Pi terminal is required for the browser conversation workflow.
|
|
|
57
57
|
|
|
58
58
|
Saisissez `/cadence <objectif>` une seule fois, puis poursuivez la conversation normalement.
|
|
59
59
|
Cadence étudie le projet, clarifie les décisions et prépare un plan.
|
|
60
|
-
Après votre approbation explicite, il réalise les modifications, vérifications,
|
|
60
|
+
Après votre approbation explicite, il réalise les modifications, vérifications, reprise automatique et intégration locale convenues.
|
|
61
61
|
|
|
62
62
|
Le mode reste actif pendant toute la conversation, même après la fin d’un objectif.
|
|
63
63
|
Saisissez `exit cadence` pour quitter ; cela n’annule pas le travail accepté.
|
|
@@ -90,7 +90,7 @@ Leurs résultats restent distincts de la revue automatique par un Agent.
|
|
|
90
90
|
```sh
|
|
91
91
|
cadence server status
|
|
92
92
|
cadence server restart # après une mise à niveau ou un changement de .env / models.json
|
|
93
|
-
cadence server upgrade
|
|
93
|
+
cadence server upgrade
|
|
94
94
|
cadence server stop # reste enregistré et redémarre au prochain boot ou connexion
|
|
95
95
|
cadence server uninstall # à exécuter avant npm uninstall -g
|
|
96
96
|
```
|
|
@@ -103,7 +103,7 @@ Les services racine Linux et nommés, l'accès HTTPS distant et la récupératio
|
|
|
103
103
|
## Développement
|
|
104
104
|
|
|
105
105
|
Pi peut aussi charger un checkout local ou une archive tarball packagée : ajoutez son chemin absolu ou relatif aux `packages` de Pi, ou essayez `pi -e ./cadence`.
|
|
106
|
-
Cadence
|
|
106
|
+
Cadence nécessite Pi 1.5.0 ou un hôte 1.x compatible ; les versions figées de développement et les temps d'exécution testés ne sont pas des promesses de compatibilité universelles.
|
|
107
107
|
|
|
108
108
|
```sh
|
|
109
109
|
bun install
|
package/README.ja.md
CHANGED
|
@@ -58,7 +58,7 @@ pi install "$(npm root -g)/@abelxiaoxing/cadence"
|
|
|
58
58
|
3. 一度だけ `/cadence [目標]` を送信します。
|
|
59
59
|
この会話は Cadence モードを維持し、その後は通常のメッセージで要件を明確にできます。
|
|
60
60
|
4. 完全な計画を確認し、**Implement this plan** を押します。
|
|
61
|
-
|
|
61
|
+
実装、検証、障害からの自動復旧、合意したローカル納品が自動で進みます。
|
|
62
62
|
5. 同じ会話で進捗を確認し、サブエージェントの記録は左下の **Subagents** パネルから開きます。
|
|
63
63
|
再読み込みや目標完了でもモードは維持されます。
|
|
64
64
|
**Exit Cadence** はモード終了のみ、**Cancel workflow — request stop** は作業のキャンセル要求です。
|
|
@@ -69,7 +69,7 @@ No live Pi terminal is required for the browser conversation workflow.
|
|
|
69
69
|
|
|
70
70
|
`/cadence <目標>` を一度入力した後は、通常の会話を続けます。
|
|
71
71
|
Cadence がプロジェクトを調査し、必要な判断を確認して計画を作ります。
|
|
72
|
-
|
|
72
|
+
計画への明示的な承認後は、実装・検証・自動復旧・合意したローカル統合を自動で進めます。
|
|
73
73
|
|
|
74
74
|
目標が完了しても、この会話では Cadence モードを維持します。
|
|
75
75
|
終了するには `exit cadence` と入力します。
|
|
@@ -105,7 +105,7 @@ WebUI のフォルダピッカーも同じ方法でプロジェクトを開く
|
|
|
105
105
|
```sh
|
|
106
106
|
cadence server status
|
|
107
107
|
cadence server restart # アップグレードや .env / models.json の変更後
|
|
108
|
-
cadence server upgrade
|
|
108
|
+
cadence server upgrade
|
|
109
109
|
cadence server stop # 登録は保持され、次の起動またはログイン時に再び起動する
|
|
110
110
|
cadence server uninstall # npm uninstall -g の前に実行
|
|
111
111
|
```
|
|
@@ -121,7 +121,7 @@ Linux ルートおよび名前付きサービス、リモート HTTPS アクセ
|
|
|
121
121
|
|
|
122
122
|
Pi はローカル checkout やパックされた tarball も読み込める。
|
|
123
123
|
その絶対または相対パスを Pi の `packages` に追加するか、`pi -e ./cadence` を試す。
|
|
124
|
-
Cadence
|
|
124
|
+
Cadence には Pi 1.5.0 または互換性のある 1.x ホストが必要。
|
|
125
125
|
開発用のピンとテスト済みのランタイムは、普遍的な互換性の約束ではない。
|
|
126
126
|
|
|
127
127
|
```sh
|
package/README.ko.md
CHANGED
|
@@ -56,7 +56,7 @@ pi install "$(npm root -g)/@abelxiaoxing/cadence"
|
|
|
56
56
|
3. `/cadence [목표]`를 한 번 전송하세요.
|
|
57
57
|
이 대화는 Cadence 모드를 유지하며 이후에는 일반 메시지로 요구사항을 구체화합니다.
|
|
58
58
|
4. 전체 계획을 확인하고 **Implement this plan**을 누르세요.
|
|
59
|
-
구현, 검사,
|
|
59
|
+
구현, 검사, 자동 복구 및 합의한 로컬 전달을 자동으로 진행합니다.
|
|
60
60
|
5. 같은 대화에서 진행 상황을 확인하고, 서브에이전트 기록은 왼쪽 아래 **Subagents** 패널에서 여세요.
|
|
61
61
|
새로고침이나 목표 완료로 모드가 꺼지지 않습니다.
|
|
62
62
|
**Exit Cadence**는 모드만 종료하고, **Cancel workflow — request stop**은 작업 취소를 요청합니다.
|
|
@@ -67,7 +67,7 @@ No live Pi terminal is required for the browser conversation workflow.
|
|
|
67
67
|
|
|
68
68
|
`/cadence <목표>`를 한 번 입력한 다음 평소처럼 대화하세요.
|
|
69
69
|
Cadence가 프로젝트를 조사하고 결정 사항을 확인한 뒤 계획을 만듭니다.
|
|
70
|
-
명시적으로 계획을 승인하면 구현, 검증,
|
|
70
|
+
명시적으로 계획을 승인하면 구현, 검증, 자동 복구 및 합의한 로컬 통합을 자동으로 진행합니다.
|
|
71
71
|
|
|
72
72
|
목표가 완료되어도 이 대화는 Cadence 모드를 유지합니다.
|
|
73
73
|
`exit cadence`로 종료할 수 있으며, 종료는 이미 승인된 작업을 취소하지 않습니다.
|
|
@@ -102,7 +102,7 @@ WebUI 폴더 선택기도 같은 방법으로 프로젝트를 엽니다.
|
|
|
102
102
|
```sh
|
|
103
103
|
cadence server status
|
|
104
104
|
cadence server restart # 업그레이드나 .env / models.json 변경 후
|
|
105
|
-
cadence server upgrade
|
|
105
|
+
cadence server upgrade
|
|
106
106
|
cadence server stop # 등록은 유지되고 다음 부팅 또는 로그인 시 다시 시작
|
|
107
107
|
cadence server uninstall # npm uninstall -g 전에 실행
|
|
108
108
|
```
|
|
@@ -118,7 +118,7 @@ Linux 루트 및 이름 지정 서비스, 원격 HTTPS 액세스, 복구에는 [
|
|
|
118
118
|
|
|
119
119
|
Pi는 로컬 체크아웃이나 패킹된 tarball도 로드할 수 있습니다.
|
|
120
120
|
그 절대 또는 상대 경로를 Pi의 `packages`에 추가하거나, `pi -e ./cadence`를 시도하세요.
|
|
121
|
-
Cadence는 Pi
|
|
121
|
+
Cadence는 Pi 1.5.0 또는 호환되는 1.x 호스트가 필요합니다.
|
|
122
122
|
개발 고정 버전과 테스트된 런타임은 보편적인 호환성 약속이 아닙니다.
|
|
123
123
|
|
|
124
124
|
```sh
|
package/README.md
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
[English](README.md) · [简体中文](README.zh-CN.md) · [日本語](README.ja.md) · [한국어](README.ko.md) · [Deutsch](README.de.md) · [Français](README.fr.md) · [Español](README.es.md) · [Português (Brasil)](README.pt-BR.md) · [Русский](README.ru.md)
|
|
4
4
|
|
|
5
5
|
Cadence turns [Pi](https://www.npmjs.com/package/@earendil-works/pi-coding-agent) into a conversation-driven engineering workflow.
|
|
6
|
-
Enter `/cadence [goal]`, align the
|
|
6
|
+
Enter `/cadence [goal]`, align the expected delivery through conversation, then let the persistent owner implement, recover and verify it.
|
|
7
7
|
The optional WebUI supports the same persistent conversation workflow without a live Pi terminal, alongside ordinary chat and readonly retained history.
|
|
8
8
|
|
|
9
9
|
## Why Cadence
|
|
@@ -11,9 +11,9 @@ The optional WebUI supports the same persistent conversation workflow without a
|
|
|
11
11
|
- **Work outlives the window.**
|
|
12
12
|
Tasks run in a background service: closing the terminal, quitting Pi or leaving the browser tab only detaches, and either client can reattach to the same run.
|
|
13
13
|
- **Nothing is edited before you approve.**
|
|
14
|
-
|
|
14
|
+
Cadence first investigates readonly and proposes a readable delivery agreement; files change only after you confirm its goal, scope and permitted actions.
|
|
15
15
|
- **Results you can trust.**
|
|
16
|
-
Subagent output, real check runs and
|
|
16
|
+
Subagent output, real check runs and independent Agent review stay separate: model prose or a "Done" never counts as a passed check, and failed, canceled and unknown outcomes stay distinct.
|
|
17
17
|
- **Complete history.**
|
|
18
18
|
Conversation workflows retain sanitized transcripts and actual process results; legacy task history also provides exact search and Markdown/NDJSON export.
|
|
19
19
|
- **One link for everything.**
|
|
@@ -21,7 +21,7 @@ The optional WebUI supports the same persistent conversation workflow without a
|
|
|
21
21
|
- **One history with the terminal.**
|
|
22
22
|
Browser conversations are the project's Pi sessions: continue a terminal session in the browser or a browser one with `/resume`, and read Pi's branches in either place.
|
|
23
23
|
|
|
24
|
-
Cadence is a trusted assistant, **not a sandbox**: its agents
|
|
24
|
+
Cadence is a trusted assistant, **not a sandbox**: its agents use host tools in the approved checkout or worktree, so use it on code you can review and recover.
|
|
25
25
|
|
|
26
26
|
## Install
|
|
27
27
|
|
|
@@ -47,7 +47,7 @@ The port and token live in `~/.pi/agent/cadence/.env`; anyone with the token can
|
|
|
47
47
|
Saved model preferences are reused on Send; choose once if none is available.
|
|
48
48
|
3. Send `/cadence [goal]` once to enter Cadence in this conversation; continue with normal messages to investigate and clarify requirements.
|
|
49
49
|
4. Review the complete inline plan and click **Implement this plan** (or send `按计划实施`).
|
|
50
|
-
The owner implements,
|
|
50
|
+
The owner implements, diagnoses failures, adjusts the route, updates approved project knowledge and verifies delivery without routine reconfirmation.
|
|
51
51
|
5. Follow actual progress and local merge results in the conversation; open any subagent's full context from the lower-left **Subagents** dock.
|
|
52
52
|
Refresh and completion keep Cadence on; **Exit Cadence** only exits the mode, while **Cancel workflow — request stop** requests cancellation.
|
|
53
53
|
|
|
@@ -58,8 +58,10 @@ Choose a vision-capable model; see [image input](docs/conversation-mode.md#image
|
|
|
58
58
|
|
|
59
59
|
Enter `/cadence <goal>` once in any trusted project's Pi conversation.
|
|
60
60
|
Continue with normal messages: Cadence investigates, consolidates questions and develops a readable plan with you.
|
|
61
|
-
After explicit
|
|
62
|
-
|
|
61
|
+
After one explicit delivery approval it automatically implements, recovers, reviews and verifies within the agreed boundary.
|
|
62
|
+
Each approved local delivery gets a named branch and one stable worktree that preserves partial work, then merges back into the displayed original branch.
|
|
63
|
+
Mode entry/research create no Git resources; approved local commits/merge never imply a remote push.
|
|
64
|
+
Relevant project documents are injected into workers and updated from verified lessons, without a separate knowledge-management command.
|
|
63
65
|
|
|
64
66
|
**Completing a goal leaves the conversation in Cadence mode.**
|
|
65
67
|
No repeated command is needed.
|
|
@@ -92,7 +94,7 @@ Their actual outcomes remain separate from automatic Agent review.
|
|
|
92
94
|
```sh
|
|
93
95
|
cadence server status
|
|
94
96
|
cadence server restart # after an upgrade or a .env / models.json change
|
|
95
|
-
cadence server upgrade # npm
|
|
97
|
+
cadence server upgrade # detected Pi/npm/Bun install: fetch, install and restart
|
|
96
98
|
cadence server stop # stays registered and starts again at the next boot or login
|
|
97
99
|
cadence server uninstall # run before npm uninstall -g
|
|
98
100
|
cadence doctor # what is left over or recently recovered; --fix for the rest
|
|
@@ -108,7 +110,7 @@ Linux root and named services, remote HTTPS access and automatic recovery are co
|
|
|
108
110
|
## Development
|
|
109
111
|
|
|
110
112
|
Pi can also load a local checkout or packed tarball: add its absolute or relative path to Pi's `packages`, or try `pi -e ./cadence`.
|
|
111
|
-
Cadence
|
|
113
|
+
Cadence requires Pi 1.5.0 or a compatible 1.x host; development pins and tested runtimes are not universal compatibility promises.
|
|
112
114
|
|
|
113
115
|
```sh
|
|
114
116
|
bun install
|
package/README.pt-BR.md
CHANGED
|
@@ -46,7 +46,7 @@ A porta e o token ficam em `~/.pi/agent/cadence/.env`; qualquer pessoa com o tok
|
|
|
46
46
|
3. Envie `/cadence [objetivo]` uma vez.
|
|
47
47
|
Esta conversa permanece no modo Cadence; esclareça os requisitos com mensagens normais.
|
|
48
48
|
4. Revise o plano completo e clique em **Implement this plan**.
|
|
49
|
-
Implementação, verificações,
|
|
49
|
+
Implementação, verificações, recuperação automática e entrega local acordada são automáticos.
|
|
50
50
|
5. Acompanhe o progresso na conversa; abra os registros dos subagentes no painel **Subagents**, no canto inferior esquerdo.
|
|
51
51
|
Atualizar a página ou concluir um objetivo não desativa o modo.
|
|
52
52
|
**Exit Cadence** sai do modo; **Cancel workflow — request stop** solicita o cancelamento.
|
|
@@ -57,7 +57,7 @@ No live Pi terminal is required for the browser conversation workflow.
|
|
|
57
57
|
|
|
58
58
|
Digite `/cadence <objetivo>` uma vez e continue conversando normalmente.
|
|
59
59
|
O Cadence investiga o projeto, esclarece decisões e prepara um plano.
|
|
60
|
-
Após aprovação explícita, executa a implementação, verificações,
|
|
60
|
+
Após aprovação explícita, executa a implementação, verificações, recuperação automática e integração local acordada.
|
|
61
61
|
|
|
62
62
|
O modo permanece ativo durante toda a conversa, mesmo após concluir um objetivo.
|
|
63
63
|
Digite `exit cadence` para sair; sair não cancela trabalho aceito.
|
|
@@ -90,7 +90,7 @@ Os resultados reais permanecem separados da revisão automática do agente.
|
|
|
90
90
|
```sh
|
|
91
91
|
cadence server status
|
|
92
92
|
cadence server restart # após um upgrade ou uma alteração de .env / models.json
|
|
93
|
-
cadence server upgrade
|
|
93
|
+
cadence server upgrade
|
|
94
94
|
cadence server stop # permanece registrado e inicia de novo no próximo boot ou login
|
|
95
95
|
cadence server uninstall # executar antes de npm uninstall -g
|
|
96
96
|
```
|
|
@@ -103,7 +103,7 @@ Serviços root e nomeados do Linux, acesso HTTPS remoto e recuperação estão c
|
|
|
103
103
|
## Desenvolvimento
|
|
104
104
|
|
|
105
105
|
O Pi também pode carregar um checkout local ou um tarball empacotado: adicione seu caminho absoluto ou relativo aos `packages` do Pi, ou experimente `pi -e ./cadence`.
|
|
106
|
-
O Cadence
|
|
106
|
+
O Cadence requer Pi 1.5.0 ou um host 1.x compatível; fixações de desenvolvimento e tempos de execução testados não são promessas universais de compatibilidade.
|
|
107
107
|
|
|
108
108
|
```sh
|
|
109
109
|
bun install
|
package/README.ru.md
CHANGED
|
@@ -46,7 +46,7 @@ pi install "$(npm root -g)/@abelxiaoxing/cadence"
|
|
|
46
46
|
3. Один раз отправьте `/cadence [цель]`.
|
|
47
47
|
Разговор остаётся в режиме Cadence; уточняйте требования обычными сообщениями.
|
|
48
48
|
4. Проверьте полный план и нажмите **Implement this plan**.
|
|
49
|
-
Реализация, проверки,
|
|
49
|
+
Реализация, проверки, автоматическое восстановление и согласованная локальная интеграция выполняются автоматически.
|
|
50
50
|
5. Следите за ходом работы в разговоре; записи субагентов открываются из панели **Subagents** слева внизу.
|
|
51
51
|
Обновление страницы и завершение цели не выключают режим.
|
|
52
52
|
**Exit Cadence** выходит из режима; **Cancel workflow — request stop** запрашивает отмену работы.
|
|
@@ -57,7 +57,7 @@ No live Pi terminal is required for the browser conversation workflow.
|
|
|
57
57
|
|
|
58
58
|
Введите `/cadence <цель>` один раз и продолжайте обычный диалог.
|
|
59
59
|
Cadence исследует проект, уточняет решения и составляет план.
|
|
60
|
-
После явного одобрения он автоматически выполняет реализацию, проверки,
|
|
60
|
+
После явного одобрения он автоматически выполняет реализацию, проверки, автоматическое восстановление и согласованную локальную интеграцию.
|
|
61
61
|
|
|
62
62
|
Режим сохраняется на весь диалог, даже после завершения цели.
|
|
63
63
|
Команда `exit cadence` выходит из режима, но не отменяет принятую работу.
|
|
@@ -90,7 +90,7 @@ cadence project open /absolute/new-project --create
|
|
|
90
90
|
```sh
|
|
91
91
|
cadence server status
|
|
92
92
|
cadence server restart # после обновления или изменения .env / models.json
|
|
93
|
-
cadence server upgrade
|
|
93
|
+
cadence server upgrade
|
|
94
94
|
cadence server stop # остаётся зарегистрированной и снова запускается при следующей загрузке или входе
|
|
95
95
|
cadence server uninstall # выполнить перед npm uninstall -g
|
|
96
96
|
```
|
|
@@ -103,7 +103,7 @@ Uninstall удаляет только определение службы; пр
|
|
|
103
103
|
## Разработка
|
|
104
104
|
|
|
105
105
|
Pi также может загрузить локальный checkout или упакованный tarball: добавьте его абсолютный или относительный путь в `packages` Pi, или попробуйте `pi -e ./cadence`.
|
|
106
|
-
Cadence
|
|
106
|
+
Cadence требует Pi 1.5.0 или совместимый хост 1.x; фиксированные версии разработки и протестированные среды выполнения не являются универсальными обещаниями совместимости.
|
|
107
107
|
|
|
108
108
|
```sh
|
|
109
109
|
bun install
|
package/README.zh-CN.md
CHANGED
|
@@ -12,7 +12,7 @@ Cadence 把 [Pi](https://www.npmjs.com/package/@earendil-works/pi-coding-agent)
|
|
|
12
12
|
- **批准之前不会修改任何文件。**
|
|
13
13
|
任务先只读分析并提出一个可读的计划;只有在你确认那个确切计划之后,文件才会被修改。
|
|
14
14
|
- **结果可信。**
|
|
15
|
-
|
|
15
|
+
子代理输出、真实的检查运行和独立 Agent 审查彼此独立:模型的文字或一句“Done”都不算检查通过,失败、取消和未知结果保持相互区分。
|
|
16
16
|
- **完整历史。**
|
|
17
17
|
新工作流保留脱敏后的子代理记录与实际进程结果;旧任务历史另支持精确搜索及 Markdown/NDJSON 导出。
|
|
18
18
|
- **与终端共用一份历史。**
|
|
@@ -20,7 +20,7 @@ Cadence 把 [Pi](https://www.npmjs.com/package/@earendil-works/pi-coding-agent)
|
|
|
20
20
|
- **一个链接涵盖一切。**
|
|
21
21
|
WebUI(桌面和手机,英文与简体中文)还承载普通的 Pi 对话,并可在项目间切换,每个项目都有自己的 owner 和历史。
|
|
22
22
|
|
|
23
|
-
Cadence
|
|
23
|
+
Cadence 是一个受信任的助手,**不是沙箱**:它的代理在获批的 checkout 或 worktree 中使用宿主工具,所以请只在你能够审阅和恢复的代码上使用它。
|
|
24
24
|
|
|
25
25
|
## 安装
|
|
26
26
|
|
|
@@ -43,18 +43,19 @@ pi install "$(npm root -g)/@abelxiaoxing/cadence"
|
|
|
43
43
|
如果丢失了链接,`cadence token-link --reveal` 会再次打印它。
|
|
44
44
|
2. 用右下角的文件夹按钮明确选择项目。
|
|
45
45
|
发送时复用已保存的模型偏好;没有可用偏好时只需选择一次。
|
|
46
|
-
3. 输入一次 `/cadence [目标]`,当前对话进入持续 Cadence
|
|
46
|
+
3. 输入一次 `/cadence [目标]`,当前对话进入持续 Cadence 模式;之后正常对话,调查项目并澄清影响交付的关键问题。
|
|
47
47
|
4. 查看完整计划,点击**按此计划实施**或发送 `按计划实施`。
|
|
48
|
-
|
|
48
|
+
后台自动实施、诊断故障、调整路线、维护项目知识并验证交付,普通内部问题无需再次确认。
|
|
49
49
|
5. 在同一对话查看真实进度和合并结果;子代理的完整上下文从左下角**子代理**面板打开。
|
|
50
50
|
刷新、完成目标后仍保持 Cadence;**退出 Cadence**不取消后台工作,**取消工作流 — 请求停止**才请求取消。
|
|
51
51
|
|
|
52
52
|
### 在终端中:一次进入,持续对话
|
|
53
53
|
|
|
54
54
|
在任意已信任项目的 Pi 对话里输入一次 `/cadence <目标>`,之后正常对话即可。
|
|
55
|
-
Cadence
|
|
56
|
-
|
|
57
|
-
|
|
55
|
+
Cadence 自动调查仓库和项目知识,只澄清真正影响结果的问题,并生成包含目标、验收、范围、环境准备和本地交付方式的约定。
|
|
56
|
+
确认后输入 `按计划实施`,系统自主实施、诊断、接续部分成果和调整技术路线;没有固定修复轮数或总交付时长配额,真实验证后再交付。
|
|
57
|
+
每个获批的 Git 交付创建一个命名任务分支和稳定 worktree,在其中持续实施、恢复和维护项目知识,审查与验证后合回约定中的原分支。
|
|
58
|
+
进入模式和只读研究不会创建 Git 资源;不会默认推送、发布或部署。
|
|
58
59
|
非 Git 项目可选择直接工作副本交付,不执行提交或合并。
|
|
59
60
|
|
|
60
61
|
**完成任务后,这个对话仍然保持 Cadence 模式,不需要再次输入 `/cadence`。**
|
|
@@ -63,7 +64,8 @@ Cadence 自动调查仓库、汇总需要你决定的问题,并与你反复对
|
|
|
63
64
|
|
|
64
65
|
日常原生使用可按需启动或复用本地项目 owner,**无需安装系统服务或先进入项目管理器**。
|
|
65
66
|
模型偏好记在 `~/.pi/agent/cadence/settings.json`,跨项目复用,不复制 Pi 凭据。
|
|
66
|
-
|
|
67
|
+
项目知识优先维护在已有工程文档中,`.cadence/project.md` 作为简洁索引;相关内容在工作者启动时按需注入,交付时自动沉淀已验证经验。
|
|
68
|
+
隔离 worktree 不会自动复制依赖或凭据,必要的准备命令会列入确认。
|
|
67
69
|
|
|
68
70
|
详细边界见 [对话模式](docs/conversation-mode.md)。
|
|
69
71
|
`/cadence-history [运行 ID]` 提供只读诊断、运行详情和已有任务历史,不创建或执行任务,也不启动服务。
|
|
@@ -90,7 +92,7 @@ cadence project open /absolute/new-project --create
|
|
|
90
92
|
```sh
|
|
91
93
|
cadence server status
|
|
92
94
|
cadence server restart # 升级或修改 .env / models.json 之后
|
|
93
|
-
cadence server upgrade # npm
|
|
95
|
+
cadence server upgrade # 识别 Pi/npm/Bun 安装:下载、安装并重启
|
|
94
96
|
cadence server stop # 保持注册状态,并在下次启动或登录时再次启动
|
|
95
97
|
cadence server uninstall # 在 npm uninstall -g 之前运行
|
|
96
98
|
```
|
|
@@ -103,7 +105,7 @@ Linux root 与命名服务、远程 HTTPS 访问和恢复见[服务管理](docs/
|
|
|
103
105
|
## 开发
|
|
104
106
|
|
|
105
107
|
Pi 也可以加载本地 checkout 或打包的 tarball:把其绝对或相对路径加到 Pi 的 `packages`,或试试 `pi -e ./cadence`。
|
|
106
|
-
Cadence
|
|
108
|
+
Cadence 要求 Pi 1.5.0 或兼容的 1.x 宿主;开发用的固定版本和已测试运行时不是通用的兼容性承诺。
|
|
107
109
|
|
|
108
110
|
```sh
|
|
109
111
|
bun install
|
package/THIRD_PARTY_NOTICES.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
This package adapts narrow lifecycle evidence from the reviewed reference repository `gotgenes/pi-packages` (MIT), commit `a1ee2255b81cb540f88d233112e868ca91fe7846`, package `packages/pi-subagents`.
|
|
4
4
|
Only FIFO settlement, cancellation cleanup, legal state transitions, and born-complete session disposal invariants informed this implementation.
|
|
5
|
-
The adapted invariants are re-expressed in this package's own code and tests; no reference code
|
|
5
|
+
The adapted invariants are re-expressed in this package's own code and tests; that historical adaptation shipped no reference code verbatim.
|
|
6
6
|
|
|
7
7
|
The complete MIT license text of the referenced package is bundled at `licenses/pi-subagents-MIT.txt`.
|
|
8
8
|
|
|
@@ -11,6 +11,14 @@ The complete MIT license text of the referenced package is bundled at `licenses/
|
|
|
11
11
|
| FIFO settlement of queued work | gotgenes/pi-packages @ a1ee2255 | packages/pi-subagents (state/queue semantics) |
|
|
12
12
|
| Cancellation cleanup and born-complete disposal | gotgenes/pi-packages @ a1ee2255 | packages/pi-subagents (session lifecycle) |
|
|
13
13
|
|
|
14
|
+
## Native agent session browser
|
|
15
|
+
|
|
16
|
+
`src/agent-browser/session-navigator.ts`, `transcript-pane.ts`, `transcript-content.ts` and `labeled-rule.ts` adapt the readonly session browser from `gotgenes/pi-packages`, commit `52854c12d590142e61a4f6a6947be9084035300d`, `packages/pi-subagents/src/ui/{session-navigator,transcript-content,labeled-rule}.ts` (MIT).
|
|
17
|
+
The browser's transcript pane, per-message renderer, incremental content cache, paging/follow behavior and labeled chrome are reused code, not merely UI inspiration.
|
|
18
|
+
Cadence replaces upstream agent/file sourcing with its existing readonly event feed and supplies a live Pi list with stable selection and per-agent reading positions.
|
|
19
|
+
No upstream executor, manager, steering, stopping or persisted-run reader is included.
|
|
20
|
+
`provenance/agent-browser-reuse.json` records exact source hashes, local paths and adaptations; the complete upstream MIT license is preserved in `licenses/pi-subagents-MIT.txt`.
|
|
21
|
+
|
|
14
22
|
## Bundled browser dependencies, icons and fonts
|
|
15
23
|
|
|
16
24
|
`licenses/bundled-web.txt` preserves the full actual emitted dependency notices, including React/DOM/scheduler, react-icons and Feather, unified/Markdown/HTML utilities, highlight.js, KaTeX and vis-timeline's embedded vendor versions.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: design-explorer
|
|
3
|
-
description: Readonly
|
|
3
|
+
description: Readonly research and independent Agent review for an explicit Cadence goal
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Design Explorer
|
|
@@ -14,4 +14,6 @@ Your plan is advisory, not permission to edit.
|
|
|
14
14
|
Do not change files, run shell commands, delegate editing, mutate Git, install software, clean consumer data or publish.
|
|
15
15
|
Do not invoke workflow commands or approve your own work.
|
|
16
16
|
Never reveal credentials, private diagnostics or session transcripts.
|
|
17
|
-
Return
|
|
17
|
+
Return the requested format with references and unresolved questions.
|
|
18
|
+
For automatic review, judge the current candidate against immutable acceptance and real check evidence; the initial technical route is not an additional requirement.
|
|
19
|
+
Automatic Agent review is never human review.
|
|
@@ -11,7 +11,10 @@ Compare plausible causes and describe evidence that would falsify each one.
|
|
|
11
11
|
Report unavailable collectors, missing reproduction evidence and uncertainty explicitly.
|
|
12
12
|
|
|
13
13
|
Do not repair files, run shell commands, mutate Git, install software, clean consumer material, publish or delegate editing.
|
|
14
|
-
A
|
|
14
|
+
A repair suggestion is not editing authority.
|
|
15
|
+
In an already approved delivery, return the owner-requested structured diagnosis and in-scope remaining assignments; the service may dispatch them under the original approval.
|
|
16
|
+
Do not ask for routine reconfirmation or redefine acceptance.
|
|
15
17
|
Never expose credentials, private diagnostics or session transcripts.
|
|
16
|
-
Return
|
|
18
|
+
Return the requested report format with supporting evidence and concrete next steps.
|
|
19
|
+
Distinguish a failed method from a genuinely unavailable in-scope route.
|
|
17
20
|
Do not claim a successful check, certified result or applied repair from source inspection alone.
|
|
@@ -1,20 +1,27 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: implementation-worker
|
|
3
|
-
description: One
|
|
3
|
+
description: One editing attempt within an approved, service-owned adaptive delivery
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Implementation Worker
|
|
7
7
|
|
|
8
|
-
|
|
9
|
-
Read
|
|
10
|
-
|
|
11
|
-
|
|
8
|
+
Complete the assigned remaining work in the owner-selected working copy using ordinary host tools.
|
|
9
|
+
Read the injected project knowledge, applicable project instructions, adjacent implementation and tests first.
|
|
10
|
+
Make the smallest complete change and reuse existing helpers before introducing new abstractions.
|
|
11
|
+
Inspect existing outputs before editing: previous attempts and predecessors may already have completed useful work.
|
|
12
|
+
Preserve those outputs and unrelated user edits; do not restart the plan or rerun clean-start preconditions.
|
|
12
13
|
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
14
|
+
The initial technical route may change within the approved goal, explicit decisions, acceptance and assigned write paths.
|
|
15
|
+
Resolve ordinary implementation problems yourself.
|
|
16
|
+
If a route fails, report concrete evidence and remaining work so the owner can diagnose, split or revise the route.
|
|
17
|
+
Never weaken requirements or tests to manufacture success.
|
|
17
18
|
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
The
|
|
19
|
+
Do not mutate Git, install software, copy profiles or credentials, delete consumer state, publish, deploy or invoke workflow commands.
|
|
20
|
+
Do not spawn workers or retry the whole work session.
|
|
21
|
+
The service owns delegation and recovery.
|
|
22
|
+
These are host tools, not a sandbox or automatic rollback system.
|
|
23
|
+
|
|
24
|
+
After all work, use `cadence_report` to submit completed or blocked with a concrete summary of actual changes and remaining gaps, then give a short final answer.
|
|
25
|
+
Do not call another tool after the report unless you submit a new report afterwards.
|
|
26
|
+
Your report and native exit are not passing checks or delivery approval: the owner runs real checks and independent readonly Agent review.
|
|
27
|
+
For knowledge assignments, update existing topic owners with source-backed facts and useful verification guidance, preserving human text; never turn speculation or raw session history into project rules.
|