symphony-orchestrator 0.2.1 → 0.2.2
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.md +37 -0
- package/apps/frontend/dist/assets/{index-CH9z-EYd.js → index-_dUsDQpW.js} +6 -6
- package/apps/frontend/dist/index.html +1 -1
- package/package.json +1 -1
- package/vendor/symphony-darwin-arm64 +0 -0
- package/vendor/symphony-darwin-x64 +0 -0
- package/vendor/symphony-linux-x64 +0 -0
- package/vendor/symphony-win32-x64.exe +0 -0
package/README.md
CHANGED
|
@@ -77,6 +77,43 @@ with `medium` reasoning:
|
|
|
77
77
|
}
|
|
78
78
|
```
|
|
79
79
|
|
|
80
|
+
PI is not a prerequisite. If you have the `pi` CLI installed and authenticated, you can use it as an
|
|
81
|
+
Agent Harness instead of Codex for selected Stage Agents. Define an `agents.pi` harness and point each
|
|
82
|
+
stage that should use PI at that harness with `harness`:
|
|
83
|
+
|
|
84
|
+
```json
|
|
85
|
+
{
|
|
86
|
+
"agents": {
|
|
87
|
+
"codex": {
|
|
88
|
+
"kind": "codex",
|
|
89
|
+
"command": "codex exec",
|
|
90
|
+
"model": "gpt-5.5",
|
|
91
|
+
"reasoningEffort": "medium"
|
|
92
|
+
},
|
|
93
|
+
"pi": {
|
|
94
|
+
"kind": "pi",
|
|
95
|
+
"command": "pi --model <model> --thinking <reasoning> --print --no-session",
|
|
96
|
+
"model": "openai/gpt-5.5",
|
|
97
|
+
"reasoningEffort": "medium"
|
|
98
|
+
}
|
|
99
|
+
},
|
|
100
|
+
"stageAgents": {
|
|
101
|
+
"enabled": true,
|
|
102
|
+
"stages": [
|
|
103
|
+
{
|
|
104
|
+
"states": ["Todo", "To-Do", "In progress", "In Progress"],
|
|
105
|
+
"agent": "engineer",
|
|
106
|
+
"harness": "pi"
|
|
107
|
+
}
|
|
108
|
+
]
|
|
109
|
+
}
|
|
110
|
+
}
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
When the `agents` object is present, each configured Stage Agent should select an existing Agent
|
|
114
|
+
Harness with `harness` unless its `agent` name also matches a harness name. PI readiness checks require
|
|
115
|
+
the `pi` executable on `PATH` and provider authentication for the configured model.
|
|
116
|
+
|
|
80
117
|
If setup is incomplete, the Terminal Console still starts and prints Readiness Gaps with remediation
|
|
81
118
|
steps. Dispatch remains disabled until those gaps are resolved.
|
|
82
119
|
|