agents-relay 2.0.185 → 2.0.186
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 +5 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -250,11 +250,12 @@ Every model-backed task declares a durable output with `--output task-pr` or `--
|
|
|
250
250
|
For Codex and ChatGPT, **correlated worker events are authoritative lifecycle inputs**, not a separate durable store. Event publication uses the canonical Neo `events-bus` surface (`events__publish` for sandboxed/hosted workers, or `NEO_EVENTS_EMIT` for direct local workers); Agents Relay subscribes, validates correlation, applies graph transitions, persists results in RelayStore, and projects them to GitHub. Relay publishes `task.process.launched` only after successful adapter launch; `task.started` is worker-owned and must be a new, correlated start acknowledgement. Codex publishes `task.process.exited` when its synchronous runtime exits, while ChatGPT publishes `task.process.async_exited` after its one-shot submission runtime exits; neither substitutes for `task.completed`, `task.failed`, `task.blocked`, or `task.cancelled`. The executing agent must publish exactly one correlated terminal event. Relay persists the matching durable state only from that terminal event. Model-backed tasks require an event bus and time out explicitly if no terminal event arrives.
|
|
251
251
|
|
|
252
252
|
External execution uses the single global `webhelm` executable installed by the
|
|
253
|
-
WebHelm
|
|
254
|
-
|
|
255
|
-
|
|
253
|
+
WebHelm Skill. Before starting Relay, install that Skill through the agent's
|
|
254
|
+
normal Skill mechanism and follow the setup instructions in its own
|
|
255
|
+
`SKILL.md`. The Skill can live in any directory; its installer links the
|
|
256
|
+
global `webhelm` command to the Skill's launcher. Relay calls
|
|
256
257
|
`webhelm platform profile chatgpt` before browser workspace initialization.
|
|
257
|
-
|
|
258
|
+
Relay does not discover Skill directories or invoke a separate runtime.
|
|
258
259
|
|
|
259
260
|
The ChatGPT adapter uses Relay's `agents/chatgpt-worker.agent.md` lifecycle contract. A new worker uses `webhelm platform run chatgpt new-thread --session-id SESSION_ID --config <file>` in a caller-owned Session. This is a regular persistent ChatGPT thread, which supports the connected Neo MCP in the verified account. Relay closes the Session after submission, but the ChatGPT thread remains in history. Existing-thread review and handoff continue through `new-turn`. File paths are included in the worker message for Neo MCP reading; they are not uploaded as browser attachments. Submission receipts retain `status: submitted`; the event bus owns task completion.
|
|
260
261
|
|