@rtrvr-ai/rover 2.2.0 → 2.3.0

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 CHANGED
@@ -281,7 +281,7 @@ If you enable `tools.web.scrapeMode: 'on_demand'`, use a site key capability pro
281
281
 
282
282
  See [full configuration reference](https://github.com/rtrvr-ai/rover/blob/main/docs/INTEGRATION.md#configuration-reference).
283
283
 
284
- ## Public Agent Tasks
284
+ ## Public Agent Tasks (ATP)
285
285
 
286
286
  Rover-enabled sites expose two public entrypoints:
287
287
 
@@ -312,6 +312,7 @@ The returned task URL is the canonical resource:
312
312
  - `GET` + `Accept: application/x-ndjson` for CLI-friendly streaming
313
313
  - `POST { "input": "..." }` for continuation when the task asks for more input
314
314
  - `DELETE` to cancel
315
+ - a `workflow` URL when the task belongs to an aggregated multi-site workflow
315
316
 
316
317
  Task creation may also return browser handoff URLs:
317
318
 
@@ -320,13 +321,26 @@ Task creation may also return browser handoff URLs:
320
321
 
321
322
  The task URL remains canonical; receipt links are only a browser handoff layer over that same task.
322
323
 
323
- The response also includes an `open` URL for browser attach.
324
-
325
324
  - `Prefer: execution=browser` keeps execution browser-first
326
325
  - `Prefer: execution=cloud` is the explicit browserless path today
327
326
  - `Prefer: execution=auto` prefers browser attach first; delayed cloud auto-promotion is a follow-up robustness phase
328
327
 
329
- Rover deep links like `?rover=` and `?rover_shortcut=` remain the simple browser-first entrypoints; `/v1/tasks` is the machine-oriented protocol.
328
+ Rover deep links like `?rover=` and `?rover_shortcut=` remain the simple browser-first entrypoints; `/v1/tasks` is the machine-oriented protocol. Cross-site workflows and handoffs extend that same public contract rather than replacing it.
329
+
330
+ ### Cross-site workflows and handoffs
331
+
332
+ Public tasks can delegate to Rover on another Rover-enabled site without leaving the same protocol surface.
333
+
334
+ - `POST /v1/tasks/{id}/handoffs` creates a child task on another site
335
+ - `GET /v1/workflows/{id}` returns aggregated workflow state or stream
336
+ - child tasks inherit the same workflow lineage as the parent
337
+
338
+ Receiving sites must explicitly opt in through Workspace/site config:
339
+
340
+ - `aiAccess.enabled = true`
341
+ - `aiAccess.allowDelegatedHandoffs = true`
342
+
343
+ By default, handoffs carry a structured summary rather than the full transcript or tool trace.
330
344
 
331
345
  ## Rover V2 Runtime Endpoints
332
346