@1claw/openapi-spec 0.59.10 → 0.61.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 +39 -1
- package/openapi.json +4249 -8
- package/openapi.yaml +2747 -94
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# @1claw/openapi-spec (v0.
|
|
1
|
+
# @1claw/openapi-spec (v0.61.0)
|
|
2
2
|
|
|
3
3
|
> ⭐ **Star [1clawAI/agent-templates](https://github.com/1clawAI/agent-templates)** — ready-to-run agent templates wired to 1Claw. It is our single starred repo.
|
|
4
4
|
|
|
@@ -42,6 +42,44 @@ openapi-generator generate \
|
|
|
42
42
|
import spec from "@1claw/openapi-spec/openapi.json";
|
|
43
43
|
```
|
|
44
44
|
|
|
45
|
+
## What's in the spec (v0.61.0)
|
|
46
|
+
|
|
47
|
+
Additive only — no path or parameter renames, so generated clients keep compiling.
|
|
48
|
+
|
|
49
|
+
- **Fleet management** — `GET /v1/platform/apps/{appId}/fleets/{template_id}`
|
|
50
|
+
and `/agents`; `POST .../bulk-patch`, `.../rollout`, `.../pause`. Four new
|
|
51
|
+
schemas: `FleetSummaryResponse`, `ListFleetAgentsResponse`, `FleetAgent`,
|
|
52
|
+
`FleetRolloutResponse`.
|
|
53
|
+
- **Two things the descriptions state deliberately**, because a client that
|
|
54
|
+
guesses either wrong causes damage at cohort scale: read
|
|
55
|
+
`bulk_patchable_fields` off the fleet summary rather than hard-coding it (it
|
|
56
|
+
excludes guardrails and capability flags and may narrow further), and expect
|
|
57
|
+
`job_id` to be `null` for a dry run.
|
|
58
|
+
- **`spec_hash` on `PlatformTemplateResponse`** — distinguishes a template
|
|
59
|
+
version bump that changed nothing from one that did.
|
|
60
|
+
- New nullable fields use 3.1 union types (`type: [string, "null"]`) rather
|
|
61
|
+
than the 3.0 `nullable:` keyword the rest of the file still uses.
|
|
62
|
+
|
|
63
|
+
## What's in the spec (v0.59.10)
|
|
64
|
+
|
|
65
|
+
Additive only — no path or parameter renames, so generated clients keep compiling.
|
|
66
|
+
|
|
67
|
+
- **Browser device management** — `GET /v1/browser/devices` and
|
|
68
|
+
`DELETE /v1/browser/devices/{id}`. Revoked devices are listed rather than
|
|
69
|
+
hidden; revocation is what makes a leaked `bb_` bridge credential stop working.
|
|
70
|
+
- **The fill request gained four required fields** — `form_path`, `field_names`,
|
|
71
|
+
`redirect_chain` and `current_generation` on
|
|
72
|
+
`POST /v1/agents/{id}/browser/fills`. They were optional and the server filled
|
|
73
|
+
them in when absent, which turned three of its own policy checks off. A request
|
|
74
|
+
missing any of them is refused with a 400 naming them. Send
|
|
75
|
+
`current_generation` as the generation observed *now*: the same value as
|
|
76
|
+
`generation` makes the staleness check compare a value to itself.
|
|
77
|
+
- **`POST /v1/vaults` documents 409** for a duplicate name, and what 400 covers
|
|
78
|
+
(empty, or over 255 characters). Both were 500s. `CreateVaultRequest.name`
|
|
79
|
+
carries the real constraints.
|
|
80
|
+
- **`POST /v1/runtimes/{id}/chat` documents 503** — the runtime's last start
|
|
81
|
+
failed under 120s ago and is not being retried yet.
|
|
82
|
+
|
|
45
83
|
## What's in the spec (v0.59.4)
|
|
46
84
|
|
|
47
85
|
### Platform connection expansion (v0.59.4)
|