@standardagents/skill 0.45.5 → 0.45.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@standardagents/skill",
-  "version": "0.45.5",
+  "version": "0.45.7",
   "private": false,
   "publishConfig": {
     "access": "public",

package/skills/agentbuilder/SKILL.md

@@ -781,7 +781,7 @@ By default, `runCode()` executes the `default` export with no args. Use `execute
 - **`state.context`** is in-memory scratch data for the *current execution*. It is not durable across thread restarts and should not be used for invocation or subagent creation arguments. For durable structured state, use `state.getValue` / `state.setValue`.
 - **`state.getValue` / `state.setValue`** are durable per-thread JSON storage. Use them for small structured state; use files for larger content or artifacts.
 - **`state.env` / `state.envType` / `state.setEnv`** are for runtime configuration and secrets. `state.env(name)` resolves thread -> account -> instance -> agent -> prompt. `state.envType(name)` returns `'secret'` by default; `'text'` means the value may be shown in tool output. `state.setEnv(name, value, { type: 'text' | 'secret' })` writes thread-scoped env and propagates to active descendants. Omit `type` only when preserving the existing type is intentional; new keys default to secret.
-- **`state.runCode`** runs JavaScript or TypeScript in an isolated Dynamic Worker sandbox. The sandbox does not receive `ThreadState`, env, files, network, or host globals implicitly. Pass exact capabilities through `imports`, `globals`, `modules`, and `execute`. It executes exported values/functions; code such as `console.log(fibonacci(5))` can log, but it must still `export default ...` or export a named function/value for the host to receive a result.
+- **`state.runCode`** runs JavaScript or TypeScript in an isolated Dynamic Worker sandbox. The sandbox does not receive `ThreadState`, env, files, network, or host globals implicitly. Pass exact capabilities through `imports`, `globals`, `modules`, and `execute`. It executes exported values/functions; code such as `console.log(fibonacci(5))` can log, but it must still `export default ...` or export a named function/value for the host to receive a result. The sandbox memory limit is 128 MB; `memoryLimitBytes` cannot lower it, and a higher value is clamped to it.
 - **`state.scheduleEffect`** runs a named effect after a delay. It survives restarts. This is your cron, your queue, and your retry timer all in one.
 - **`state.invokeTool` vs `state.queueTool`** — `invokeTool` runs synchronously and returns the result; `queueTool` schedules the call to run later in the normal tool-call flow. Prefer `queueTool` when the model should see the result as a regular tool call.
 - **`state.notifyParent`** — for children whose relationship sets `parentCommunication: 'explicit'`, this is the main way the child talks to the parent. Use it sparingly; every delivered notification interrupts the parent. If there is no parent, nothing is queued externally.
@@ -871,7 +871,7 @@ PromptDefinition
   model                  ModelName                       references agents/models/<name>
   includeChat            boolean (default false)         pass full chat history to this LLM step
   includePastTools       boolean (default false)         include tool calls and results in later requests
-  parallelToolCalls      boolean (default false)         allow multiple tool calls per turn
+  parallelToolCalls      boolean (provider default)      allow multiple tool calls per turn
   toolChoice             'auto' | 'none' | 'required'    tool calling strategy (default 'auto')
   requiredSchema         ZodSchema                       validate args when called as a tool
   variables              VariableDefinition[]            declared text/secret variables
@@ -1139,7 +1139,7 @@ Undeclared thread-only env keys are treated as write-only secrets when scanned f
 
 ## Platform terms
 
-If `git push` prints lines that start with `remote: Standard Agents:`, the platform stored the push but started no build. Tell the user what the lines say. For the terms notice, the user runs `npx @standardagents/cli terms accept`. An acceptance starts no build: the command lists the deploy that waits and starts it (with `--agree`, with no second question). To start it later, run `npx @standardagents/cli builds retry` on the pushed branch.
+If `git push` prints lines that start with `remote: Standard Agents:`, the platform stored the push but started no build. Tell the user what the lines say. For the terms notice, the user runs `npx @standardagents/cli@latest terms accept`. An acceptance starts no build: the command lists the deploy that waits and starts it (with `--agree`, with no second question). To start it later, run `npx @standardagents/cli@latest builds retry` on the pushed branch.
 
 The platform can ask an account member to accept updated terms.
 
@@ -1168,7 +1168,8 @@ new yes.
 
 Add `--json` for stable output; a code 2 result holds the command in
 `accept_command`. Exit codes: 0 success, 1 failure, 2
-confirmation needed, 3 not signed in (the user runs `login` or `git-login`).
+confirmation needed, 3 not signed in (the user runs
+`npx @standardagents/cli@latest login`, the one sign-in command, in any directory).
 After acceptance the command lists each deploy that started.
 
 ---
@@ -1189,9 +1190,10 @@ destination.
 
 ### `agents diag` (CLI)
 
-All subcommands accept `--endpoint <instance-url>` and `--token <api-key>`
-(defaults: `$STANDARD_AGENTS_INSTANCE_URL` / `$STANDARD_AGENTS_INSTANCE_TOKEN`,
-falling back to `http://localhost:5173` for local dev). The token must belong
+All subcommands read `$STANDARD_AGENTS_INSTANCE_URL` and
+`$STANDARD_AGENTS_INSTANCE_TOKEN` (falling back to `http://localhost:5173` for
+local dev). Set the token in the environment: `--token <api-key>` is accepted,
+but an argument is visible to other users in the process list. The token must belong
 to a user with the `logs` permission (admin keys qualify; customer `api`-role
 keys do not).
 
@@ -1204,6 +1206,15 @@ agents diag tail 050d96f1             # live-tail the log stream — are bytes f
 agents diag revive 050d96f1           # run a watchdog check NOW: finalize + resume
 ```
 
+Every subcommand accepts `--json`: stdout then holds one JSON document
+(`diag tail --json` prints one frame per line), and errors go to stderr. A
+failure exits 1 and prints `{ "error": { "code", "message", "status",
+"request_id" } }`. `diag threads` reports how many threads it could not read
+(`unreadable` in JSON); `diag threads --stuck` exits 1 when it could not read
+every thread. Exit 0 means the scan was complete, not that the instance is
+healthy: read the returned threads to see whether any are stuck. `diag tail`
+exits 1 when the stream closes abnormally.
+
 ### Interpretation guide
 
 - `diag instance` → `builder version` answers "is the fix deployed?" without
@@ -1234,7 +1245,7 @@ All three are gated by the `logs` permission on hosted deployments.
 
 ## After a push
 
-A project on Standard Agents hosting deploys from git: the platform builds each pushed commit. A push that git accepts is not a deploy, and the build can fail after the push. Check every push with the CLI. The commands use the project key in `.dev.vars`, or the account sign-in from `agents login`; `agents rollback` and `agents redeploy` need that sign-in. Each command accepts `--json` and never prompts.
+A project on Standard Agents hosting deploys from git: the platform builds each pushed commit. A push that git accepts is not a deploy, and the build can fail after the push. Check every push with the CLI. The commands use the project key in `.dev.vars`, or the account sign-in from `npx @standardagents/cli@latest login`, which is saved once for the machine; `agents rollback` and `agents redeploy` need that sign-in. Each command accepts `--json` and never prompts.
 
 ```bash
 agents deploy                              # push, then follow the build; exits 0 only when the commit was deployed
@@ -1260,8 +1271,8 @@ Without a global install, use `npx @standardagents/cli@latest <command>`.
 | 0 | Done. For a wait: the commit was deployed. | None. |
 | 1 | The build failed, or the platform refused the request. | Read `agents builds logs`. |
 | 2 | The command line, the checkout, or the named build is not usable. | Read the message. |
-| 3 | Not signed in, or the command needs an account sign-in. | Ask the user to run `agents login`. |
-| 4 | The platform needs the terms accepted before it builds. | Ask the user to run `npx @standardagents/cli terms accept`. It starts the refused build after the acceptance; `npx @standardagents/cli builds retry` starts it later. |
+| 3 | Not signed in, or the command needs an account sign-in. | Ask the user to run `npx @standardagents/cli@latest login`. |
+| 4 | The platform needs the terms accepted before it builds. | Ask the user to run `npx @standardagents/cli@latest terms accept`. It starts the refused build after the acceptance; `npx @standardagents/cli@latest builds retry` starts it later. |
 | 5 | The time limit passed while the build was still in progress. | Run `agents builds status --wait` again, or raise `--timeout <seconds>`. |
 
 Only a person can sign in or accept the terms. Do not try to do either for the user.
@@ -1275,16 +1286,15 @@ When you edit `agents/`, `prompts/`, `handlers/`, `models/`, `tools/`, `hooks/`,
 Validation order:
 
 1. Read `package.json` and prefer project scripts if they exist.
-2. Refresh Cloudflare types:
-   - use `pnpm cf-typegen` if that script exists
-   - otherwise run `npx wrangler types`
-3. Regenerate Standard Agents Builder types by starting the dev server:
+2. Generate the project's types by starting the dev server. This is the only type-generation command:
    - usually `pnpm dev`, `npm run dev`, or equivalent
+   - the dev server writes `.agents/types.d.ts` and `.agents/virtual-module.d.ts` when it starts, and again after each change under `agents/`; the type checker fails while they are missing
+   - do not run `wrangler types`: a generated project has no Wrangler config, because the `builder()` plugin generates the Cloudflare configuration
    - do not run the `build` script of a generated project; it stops with a message on purpose, because builds run on the Standard Agents platform
-4. Run the project's type checker:
-   - prefer `pnpm type-check` / `npm run type-check` if present
+3. Run the project's type checker:
+   - prefer the project's script: `pnpm typecheck` / `npm run typecheck` in a generated project, or `type-check` if that is the script name
    - otherwise use the installed checker directly: `pnpm exec vue-tsc --build`, `pnpm exec tsc -b`, or `pnpm exec tsc --noEmit`
-5. If any validation step cannot run, state exactly what is missing.
+4. If any validation step cannot run, state exactly what is missing.
 
 ## Hosting