You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Chinese documentation: [README_CN.md](./README_CN.md).
14
14
-`Result/PushData`
15
15
-`Log/Debug`, `Log/Info`, `Log/Warn`, `Log/Error`
16
16
- Runtime input injection from `input_schema.json` defaults, `--input`, or `--json`
17
-
- Run input validation for required `input_schema.json` fields before the worker starts
17
+
- Run input validation for required fields and declared value types in `input_schema.json` before the worker starts
18
18
- Platform environment variables:
19
19
-`ChromeWs`
20
20
-`CDP_ENDPOINT` / `BROWSER_WS_ENDPOINT`
@@ -93,7 +93,7 @@ Validation checks:
93
93
94
94
CoreClaw installs dependencies from `requirements.txt`, `package.json`, or `go.mod` after upload. The CLI therefore rejects workers that rely on locally installed SDK packages but do not declare those packages for the cloud installer.
95
95
96
-
At run time, the CLI also validates the actual input assembled from defaults, `--input`, or `--json`. If a field marked `"required": true` is missing or empty, the command fails before creating run artifacts or starting the worker, matching CoreClaw's form-level launch behavior.
96
+
At run time, the CLI also validates the actual input assembled from defaults, `--input`, or `--json`. If a field marked `"required": true` is missing or empty, or if a declared input field has the wrong JSON type, the command fails before creating run artifacts or starting the worker, matching CoreClaw's form-level launch behavior.
97
97
98
98
CoreClaw's docs describe `output_schema.json` for upload-ready projects, but the current platform still accepts older workers without it. The CLI treats a missing `output_schema.json` as a warning, not a blocker. Local `export.ndjson` keeps the full raw result rows when no output schema exists.
99
99
@@ -128,7 +128,7 @@ The run starts a local CoreClaw SDK gRPC server on `127.0.0.1:20086`, then execu
128
128
129
129
Use `--timeout-ms` to cap the whole worker process and `--idle-timeout-ms` to stop a worker that has stopped producing output but still has open Node/Python/Go handles. Durations accept milliseconds, `s`, or `m`.
130
130
131
-
If the input schema marks a field as required, local runs require a non-empty value for that field. Use `--input input.json` or `--json '{"field":"value"}'` when the schema does not provide a default.
131
+
If the input schema marks a field as required, local runs require a non-empty value for that field. Declared fields must also match their schema type, for example `integer` must be an integer, `boolean` must be a boolean, and `array` must be a JSON array. Use `--input input.json` or `--json '{"field":"value"}'` when the schema does not provide a default.
132
132
133
133
Use `--min-results` for real worker smoke tests. Some existing workers can exit with code `0` after logging an upstream or browser error, so result count is the reliable success gate.
0 commit comments