@aexhq/sdk 0.40.6 → 0.40.7

package/docs/concepts/subagents.md

@@ -1,88 +1,88 @@
----
-title: Subagents
-description: Delegate bounded sub-tasks to child agent runs with the subagent tool.
-icon: GitFork
----
-
-A run can delegate bounded sub-tasks to **child agent runs** with the built-in
-`subagent` tool. Delegation is agent-driven: the model decides to fan work out,
-each child is a real run with its own record, and the parent collects results
-as the children finish. There is no client-side parent/child API — lineage is
-session-internal.
-
-## How the tool works
-
-The agent calls `subagent` with a `prompt` and a `model` (both required), plus
-optional `system`, `provider`, `runtimeSize`, `timeout`,
-`includeBuiltinTools`, `tools` (builtin-tool names for the child), `skills`,
-and `files`. The call is **always async**: on a successful spawn it returns
-immediately with the child run id, and the parent keeps working while the child
-runs. When a child settles, the parent is notified in its loop, and it reads
-the child's status and captured outputs on demand with the companion
-`subagent_result` tool.
-
-Children inherit the parent's vaulted BYOK provider keys server-side — the
-child submission carries no secrets. Include a provider key for every provider
-your subagents may use when you open the parent session (a parent holding no
-key for the child's provider gets a clear `parent_missing_provider_key` tool
-error). See [Credentials](../credentials.md).
-
-## Depth and breadth limits
-
-Delegation is bounded by two server-enforced lineage limits:
-
-| Limit | Value | Behavior at the limit |
-| --- | --- | --- |
-| Max depth | **5** — the root run is depth 0 and may spawn down to depth 5; a depth-5 run may not spawn further | The spawn is rejected with a `depth_exceeded` tool error (the parent keeps running). |
-| Concurrent children per lineage root | **1000** live (non-terminal) descendants by default; hard platform ceiling **4096** | Further spawns are refused until a child settles. |
-
-The whole descendant subtree of one root shares a single depth and breadth
-budget, enforced server-side at every level — a grandchild spawn counts against
-the same root budget as a direct child. Values are mirrored in
-[Limits & quotas](../limits-and-quotas.md).
-
-## Where children run: `in-process` vs `container`
-
-By default a child runs **in-process**: it executes as a sibling agent process
-inside the parent's own machine, sharing the parent's CPU, memory, and
-lifetime. This is the platform default shipped today.
-
-- **No extra runtime cost.** The parent's machine is the billable unit, so
-  in-process children bill **$0 of additional runtime** — fan-out is priced by
-  the parent box, however many children it hosts. (Model-token spend is still
-  whatever each child's provider calls cost on your BYOK key.)
-- **Shared capacity.** N children share the parent's fixed CPU/memory. For
-  large fan-outs, size the parent up (`runtime`) rather than assuming each
-  child gets its own machine.
-- **Joined lifecycle.** The parent's terminal waits for its in-process children,
-  and their results are folded into the parent's per-child accounting. Platform
-  recovery re-spawns in-process children exactly once if the parent's machine
-  is replaced mid-run — settled children are never re-run.
-
-The escape valve is `host: "container"`: the child is dispatched to its **own
-isolated machine** with its own runtime size and its own runtime billing, and
-the parent does not host it. Use it when a child needs guaranteed capacity,
-isolation from the parent's filesystem/CPU, or a different machine size than
-the parent can share.
-
-## Lineage and observability
-
-Every child — in-process or container — is a first-class run record:
-
-- The parent's transcript logs each spawn with the child's run id.
-- Each child has its own status, typed event timeline, and captured outputs.
-  The child's events and outputs are readable by id
-  (`aex.sessions.outputs(id)` in the SDK, or the CLI's `aex events` /
-  `aex outputs`). Child runs are not served by the session read surface
-  today — `aex.sessions.get(id)` / `aex sessions` / the CLI's `aex status`
-  answer `not_found` for a child id.
-- The child's outputs are handed back to the parent via `subagent_result`, and
-  they remain independently downloadable after the lineage finishes.
-
-## Bounding delegation
-
-- Turn delegation off for a run by cherry-picking builtins without `subagent`
-  (see [Agent tools](agent-tools.md)) or setting `includeBuiltinTools: false`.
-- A per-session spend cap (`overrides.maxSpendUsd`) bounds the parent's spend.
-- The depth/breadth limits above are platform defaults and are not settable
-  per-session today.
+---
+title: Subagents
+description: Delegate bounded sub-tasks to child agent runs with the subagent tool.
+icon: GitFork
+---
+
+A run can delegate bounded sub-tasks to **child agent runs** with the built-in
+`subagent` tool. Delegation is agent-driven: the model decides to fan work out,
+each child is a real run with its own record, and the parent collects results
+as the children finish. There is no client-side parent/child API — lineage is
+session-internal.
+
+## How the tool works
+
+The agent calls `subagent` with a `prompt` and a `model` (both required), plus
+optional `system`, `provider`, `runtimeSize`, `timeout`,
+`includeBuiltinTools`, `tools` (builtin-tool names for the child), `skills`,
+and `files`. The call is **always async**: on a successful spawn it returns
+immediately with the child run id, and the parent keeps working while the child
+runs. When a child settles, the parent is notified in its loop, and it reads
+the child's status and captured outputs on demand with the companion
+`subagent_result` tool.
+
+Children inherit the parent's vaulted BYOK provider keys server-side — the
+child submission carries no secrets. Include a provider key for every provider
+your subagents may use when you open the parent session (a parent holding no
+key for the child's provider gets a clear `parent_missing_provider_key` tool
+error). See [Credentials](../credentials.md).
+
+## Depth and breadth limits
+
+Delegation is bounded by two server-enforced lineage limits:
+
+| Limit | Value | Behavior at the limit |
+| --- | --- | --- |
+| Max depth | **5** — the root run is depth 0 and may spawn down to depth 5; a depth-5 run may not spawn further | The spawn is rejected with a `depth_exceeded` tool error (the parent keeps running). |
+| Concurrent children per lineage root | **1000** live (non-terminal) descendants by default; hard platform ceiling **4096** | Further spawns are refused until a child settles. |
+
+The whole descendant subtree of one root shares a single depth and breadth
+budget, enforced server-side at every level — a grandchild spawn counts against
+the same root budget as a direct child. Values are mirrored in
+[Limits & quotas](../limits-and-quotas.md).
+
+## Where children run: `in-process` vs `container`
+
+By default a child runs **in-process**: it executes as a sibling agent process
+inside the parent's own machine, sharing the parent's CPU, memory, and
+lifetime. This is the platform default shipped today.
+
+- **No extra runtime cost.** The parent's machine is the billable unit, so
+  in-process children bill **$0 of additional runtime** — fan-out is priced by
+  the parent box, however many children it hosts. (Model-token spend is still
+  whatever each child's provider calls cost on your BYOK key.)
+- **Shared capacity.** N children share the parent's fixed CPU/memory. For
+  large fan-outs, size the parent up (`runtime`) rather than assuming each
+  child gets its own machine.
+- **Joined lifecycle.** The parent's terminal waits for its in-process children,
+  and their results are folded into the parent's per-child accounting. Platform
+  recovery re-spawns in-process children exactly once if the parent's machine
+  is replaced mid-run — settled children are never re-run.
+
+The escape valve is `host: "container"`: the child is dispatched to its **own
+isolated machine** with its own runtime size and its own runtime billing, and
+the parent does not host it. Use it when a child needs guaranteed capacity,
+isolation from the parent's filesystem/CPU, or a different machine size than
+the parent can share.
+
+## Lineage and observability
+
+Every child — in-process or container — is a first-class run record:
+
+- The parent's transcript logs each spawn with the child's run id.
+- Each child has its own status, typed event timeline, and captured outputs.
+  The child's events and outputs are readable by id
+  (`aex.sessions.outputs(id)` in the SDK, or the CLI's `aex events` /
+  `aex outputs`). Child runs are not served by the session read surface
+  today — `aex.sessions.get(id)` / `aex sessions` / the CLI's `aex status`
+  answer `not_found` for a child id.
+- The child's outputs are handed back to the parent via `subagent_result`, and
+  they remain independently downloadable after the lineage finishes.
+
+## Bounding delegation
+
+- Turn delegation off for a run by cherry-picking builtins without `subagent`
+  (see [Agent tools](agent-tools.md)) or setting `includeBuiltinTools: false`.
+- A per-session spend cap (`overrides.maxSpendUsd`) bounds the parent's spend.
+- The depth/breadth limits above are platform defaults and are not settable
+  per-session today.

package/docs/credentials.md

@@ -1,125 +1,125 @@
----
-title: Credentials
----
-
-# Credentials
-
-aex uses explicit, per-session credentials:
-
-- `AEX_API_KEY` authenticates the SDK or CLI to aex.
-- `apiKeys` carries BYOK provider keys for the model provider.
-- `McpServer.remote(..., { headers })` carries MCP auth when a remote MCP server needs it.
-- `environment.secrets` carries runtime secrets for your own code.
-
-Secrets never belong in reusable run config, files, prompts, or examples.
-
-## The client credential
-
-Pass your aex API key directly to the constructor — `new Aex(apiKey)` — or as
-the `apiKey` option:
-
-```ts
-import { Aex } from "@aexhq/sdk";
-
-const aex = new Aex(process.env.AEX_API_KEY!);          // preferred shorthand
-// equivalently:
-// const aex = new Aex({ apiKey: process.env.AEX_API_KEY! });
-```
-
-See [Authentication](authentication.md) for how keys are scoped, rotated, and
-issued during the beta.
-
-## Provider keys
-
-A session selects one upstream provider and must carry a BYOK key for it. Include
-additional provider keys only when subagents may use those providers.
-
-```ts
-const result = await aex.run({
-  model: Models.CLAUDE_HAIKU_4_5,
-  message: "Write a short report and save it as a file.",
-  apiKeys: {
-    anthropic: process.env.ANTHROPIC_API_KEY!
-  }
-});
-```
-
-Provider keys are used by the managed runtime for model calls. They are not saved
-as client defaults.
-
-## Runtime secrets
-
-Use `environment.secrets` for credentials your code needs at runtime. The value
-can be ephemeral with `Secret.value(...)` or a workspace secret reference with
-`Secret.ref(...)`.
-
-```ts
-import { Aex, Models, Secret } from "@aexhq/sdk";
-
-const aex = new Aex({ apiKey: process.env.AEX_API_KEY! });
-
-await aex.run({
-  model: Models.CLAUDE_HAIKU_4_5,
-  message: "Call https://api.example.com/v1/status with INTERNAL_API_TOKEN and summarize it.",
-  environment: {
-    secrets: {
-      INTERNAL_API_TOKEN: Secret.value(process.env.INTERNAL_API_TOKEN!)
-    },
-    networking: {
-      mode: "limited",
-      allowedHosts: ["api.example.com"]
-    }
-  },
-  apiKeys: { anthropic: process.env.ANTHROPIC_API_KEY! }
-});
-```
-
-Inside the run, use normal HTTP code for the service:
-
-```bash
-curl -sS \
-  -H "Authorization: Bearer $INTERNAL_API_TOKEN" \
-  https://api.example.com/v1/status
-```
-
-## Workspace secrets
-
-> **Availability note:** workspace-secret `Secret.ref(...)` injection requires
-> the next platform deploy — on the current hosted plane the referenced
-> variable can resolve empty inside the run. Per-run `Secret.value(...)`
-> secrets are unaffected.
-
-Store reusable values once, then reference them by name:
-
-```ts
-await aex.secrets.set({
-  name: "internal-api-token",
-  value: process.env.INTERNAL_API_TOKEN!
-});
-
-await aex.run({
-  model: Models.CLAUDE_HAIKU_4_5,
-  message: "Use INTERNAL_API_TOKEN for the status request.",
-  environment: {
-    secrets: {
-      INTERNAL_API_TOKEN: Secret.ref("internal-api-token")
-    }
-  },
-  apiKeys: { anthropic: process.env.ANTHROPIC_API_KEY! }
-});
-```
-
-Secret reads return metadata only; they never return the stored value.
-
-## Networking
-
-Networking is open by default within the platform's managed egress ceiling. Use
-`environment.networking.mode: "limited"` with `allowedHosts` when you want a
-run's own code to reach only named hosts. See [Networking](networking.md) for
-the two-layer enforcement model.
-
-## Explicit call-site rule
-
-There is no `defaultSecrets` and no client-held secret state. Each
-`openSession(...)` or `run(...)` call should show the provider keys, MCP auth, and
-runtime secrets needed for that call.
+---
+title: Credentials
+---
+
+# Credentials
+
+aex uses explicit, per-session credentials:
+
+- `AEX_API_KEY` authenticates the SDK or CLI to aex.
+- `apiKeys` carries BYOK provider keys for the model provider.
+- `McpServer.remote(..., { headers })` carries MCP auth when a remote MCP server needs it.
+- `environment.secrets` carries runtime secrets for your own code.
+
+Secrets never belong in reusable run config, files, prompts, or examples.
+
+## The client credential
+
+Pass your aex API key directly to the constructor — `new Aex(apiKey)` — or as
+the `apiKey` option:
+
+```ts
+import { Aex } from "@aexhq/sdk";
+
+const aex = new Aex(process.env.AEX_API_KEY!);          // preferred shorthand
+// equivalently:
+// const aex = new Aex({ apiKey: process.env.AEX_API_KEY! });
+```
+
+See [Authentication](authentication.md) for how keys are scoped, rotated, and
+issued during the beta.
+
+## Provider keys
+
+A session selects one upstream provider and must carry a BYOK key for it. Include
+additional provider keys only when subagents may use those providers.
+
+```ts
+const result = await aex.run({
+  model: Models.CLAUDE_HAIKU_4_5,
+  message: "Write a short report and save it as a file.",
+  apiKeys: {
+    anthropic: process.env.ANTHROPIC_API_KEY!
+  }
+});
+```
+
+Provider keys are used by the managed runtime for model calls. They are not saved
+as client defaults.
+
+## Runtime secrets
+
+Use `environment.secrets` for credentials your code needs at runtime. The value
+can be ephemeral with `Secret.value(...)` or a workspace secret reference with
+`Secret.ref(...)`.
+
+```ts
+import { Aex, Models, Secret } from "@aexhq/sdk";
+
+const aex = new Aex({ apiKey: process.env.AEX_API_KEY! });
+
+await aex.run({
+  model: Models.CLAUDE_HAIKU_4_5,
+  message: "Call https://api.example.com/v1/status with INTERNAL_API_TOKEN and summarize it.",
+  environment: {
+    secrets: {
+      INTERNAL_API_TOKEN: Secret.value(process.env.INTERNAL_API_TOKEN!)
+    },
+    networking: {
+      mode: "limited",
+      allowedHosts: ["api.example.com"]
+    }
+  },
+  apiKeys: { anthropic: process.env.ANTHROPIC_API_KEY! }
+});
+```
+
+Inside the run, use normal HTTP code for the service:
+
+```bash
+curl -sS \
+  -H "Authorization: Bearer $INTERNAL_API_TOKEN" \
+  https://api.example.com/v1/status
+```
+
+## Workspace secrets
+
+> **Availability note:** workspace-secret `Secret.ref(...)` injection requires
+> the next platform deploy — on the current hosted plane the referenced
+> variable can resolve empty inside the run. Per-run `Secret.value(...)`
+> secrets are unaffected.
+
+Store reusable values once, then reference them by name:
+
+```ts
+await aex.secrets.set({
+  name: "internal-api-token",
+  value: process.env.INTERNAL_API_TOKEN!
+});
+
+await aex.run({
+  model: Models.CLAUDE_HAIKU_4_5,
+  message: "Use INTERNAL_API_TOKEN for the status request.",
+  environment: {
+    secrets: {
+      INTERNAL_API_TOKEN: Secret.ref("internal-api-token")
+    }
+  },
+  apiKeys: { anthropic: process.env.ANTHROPIC_API_KEY! }
+});
+```
+
+Secret reads return metadata only; they never return the stored value.
+
+## Networking
+
+Networking is open by default within the platform's managed egress ceiling. Use
+`environment.networking.mode: "limited"` with `allowedHosts` when you want a
+run's own code to reach only named hosts. See [Networking](networking.md) for
+the two-layer enforcement model.
+
+## Explicit call-site rule
+
+There is no `defaultSecrets` and no client-held secret state. Each
+`openSession(...)` or `run(...)` call should show the provider keys, MCP auth, and
+runtime secrets needed for that call.

package/docs/defaults.md

@@ -1,64 +1,64 @@
----
-title: Defaults
----
-
-# Defaults
-
-These are the values aex applies when you **omit** the corresponding option on a
-run. Every value is mirrored from a single source-of-truth constant in the
-platform's limits module; this page is hand-maintained against those constants.
-If a value here ever disagrees with the constant, the constant wins.
-
-Each value below is named by its source-of-truth constant. The runtime-size
-presets are defined in the public
-[`packages/contracts/src/runtime-sizes.ts`](https://github.com/aexhq/aex/blob/main/packages/contracts/src/runtime-sizes.ts).
-For the hard ceilings and who can raise them, see
-[Limits & quotas](limits-and-quotas.md). For policy boundaries, see
-[Limits](limits.md).
-
-## Run
-
-| Option | Default | How to override | Source |
-| --- | --- | --- | --- |
-| `timeout` (run deadline) | 8 hours (also the ceiling) | Per-session via `overrides.timeout` (e.g. `"30m"`, `"2h"`). Values outside the run-timeout floor (1 minute) / ceiling (8 hours) are rejected with `RunConfigValidationError` before submission. | `RUN_DEFAULT_TIMEOUT_MS` |
-| `runtime` (machine size) | `shared-0.25x-1gb` — 0.25 vCPU, 1 GB | Per-session via `runtime` (use `Sizes.*` in TypeScript). | `RUN_DEFAULT_RUNTIME_SIZE` |
-| `overrides.maxSpendUsd` (per-session spend cap) | None — no spend cap (the session is still bounded by its `timeout` and any workspace-level cap) | Per-session via `overrides.maxSpendUsd` (a positive USD amount); the session is stopped once its spend would exceed the cap. | — |
-| `overrides.maxTurns` (agent iterations per run) | 20 (ceiling 200) | Per-session via `overrides.maxTurns` (a positive integer, clamped to the ceiling). | `RUN_DEFAULT_MAX_TURNS` |
-
-## Tools
-
-| Option | Default | How to override | Source |
-| --- | --- | --- | --- |
-| Per-call exec timeout | 30 minutes | Per-call via the tool call's `timeoutMs`. | `RUN_DEFAULT_EXEC_TIMEOUT_MS` |
-| `web_fetch` returned body | 500 KB (UTF-8) | Per-call via the tool's `max_bytes` argument. | `REQUEST_WEB_FETCH_DEFAULT_MAX_BYTES` |
-
-## MCP
-
-| Option | Default | How to override | Source |
-| --- | --- | --- | --- |
-| MCP connect timeout (register + initialize + discover) | 30 seconds | Per-port via `connectTimeoutMs`. | `RUN_DEFAULT_MCP_CONNECT_TIMEOUT_MS` |
-| MCP `tools/call` timeout | 30 minutes | Per-port via `callTimeoutMs`. | `RUN_DEFAULT_MCP_CALL_TIMEOUT_MS` |
-
-## Links (signed URLs and tickets)
-
-| Option | Default | How to override | Source |
-| --- | --- | --- | --- |
-| Output link / signed-URL TTL | 300 seconds (5 minutes) at the storage layer; `session.outputs().link(...)` defaults to `"1h"` | Per-call via `expiresSeconds` (storage) or `expiresIn` on `session.outputs().link` / `session.outputs().fetch`. | `REQUEST_PRESIGN_URL_DEFAULT_TTL_SECONDS` |
-| Event-stream connection ticket TTL | 60 seconds | Per-mint via the `ttlMs` argument. | `REQUEST_TICKET_DEFAULT_TTL_MS` |
-
-## Subagents
-
-| Option | Default | How to override | Source |
-| --- | --- | --- | --- |
-| Concurrent child runs per lineage root | 1000 (live, non-terminal child runs) | Platform default (subagents run in-process; no public per-run override). Hard ceiling 4096. | `RUN_DEFAULT_MAX_CONCURRENT_CHILD_RUNS` |
-| Max subagent depth | 5 | Platform default (subagents run in-process; no public per-run override). | `RUN_MAX_PUBLIC_SUBAGENT_DEPTH` |
-
-## Workspace
-
-| Option | Default | How to override | Source |
-| --- | --- | --- | --- |
-| Run submit rate (per minute) | 120 (`0` = disabled); past it `POST /runs` fails with `429 workspace_submit_rate_exceeded` | Per-plane via env `AEX_WORKSPACE_SUBMIT_RATE_PER_MIN`; per-workspace via support. | — |
-| Max concurrent runs | Plan-based: 5 live root runs (free), 50 (Pro), 200 (Team); hard ceiling 200 | Per-plan (upgrade) or per-workspace override via support, clamped to the ceiling. | `PLANS[planKey].maxConcurrentRuns` |
-| Monthly spend cap | $250 per UTC calendar month (`0` = unlimited) | Per-workspace override via support. | `WORKSPACE_DEFAULT_SPEND_CAP_USD` |
-| Per-workspace mutation rate limits (per minute) | run cancel 30, run delete 30, signed link 120, API key create 10, API key delete 30 | Per-plane via the matching `AEX_RATE_LIMIT_<ACTION>_PER_MINUTE` env var. | `WORKSPACE_RATE_LIMIT_DEFAULTS` |
-| Workspace storage cap | 500 GB (decimal) | Per-plane via env `AEX_WORKSPACE_STORAGE_CAP_BYTES`; admin workspaces are uncapped (not a customer entitlement). | `WORKSPACE_DEFAULT_STORAGE_CAP_BYTES` |
+---
+title: Defaults
+---
+
+# Defaults
+
+These are the values aex applies when you **omit** the corresponding option on a
+run. Every value is mirrored from a single source-of-truth constant in the
+platform's limits module; this page is hand-maintained against those constants.
+If a value here ever disagrees with the constant, the constant wins.
+
+Each value below is named by its source-of-truth constant. The runtime-size
+presets are defined in the public
+[`packages/contracts/src/runtime-sizes.ts`](https://github.com/aexhq/aex/blob/main/packages/contracts/src/runtime-sizes.ts).
+For the hard ceilings and who can raise them, see
+[Limits & quotas](limits-and-quotas.md). For policy boundaries, see
+[Limits](limits.md).
+
+## Run
+
+| Option | Default | How to override | Source |
+| --- | --- | --- | --- |
+| `timeout` (run deadline) | 8 hours (also the ceiling) | Per-session via `overrides.timeout` (e.g. `"30m"`, `"2h"`). Values outside the run-timeout floor (1 minute) / ceiling (8 hours) are rejected with `RunConfigValidationError` before submission. | `RUN_DEFAULT_TIMEOUT_MS` |
+| `runtime` (machine size) | `shared-0.25x-1gb` — 0.25 vCPU, 1 GB | Per-session via `runtime` (use `Sizes.*` in TypeScript). | `RUN_DEFAULT_RUNTIME_SIZE` |
+| `overrides.maxSpendUsd` (per-session spend cap) | None — no spend cap (the session is still bounded by its `timeout` and any workspace-level cap) | Per-session via `overrides.maxSpendUsd` (a positive USD amount); the session is stopped once its spend would exceed the cap. | — |
+| `overrides.maxTurns` (agent iterations per run) | 20 (ceiling 200) | Per-session via `overrides.maxTurns` (a positive integer, clamped to the ceiling). | `RUN_DEFAULT_MAX_TURNS` |
+
+## Tools
+
+| Option | Default | How to override | Source |
+| --- | --- | --- | --- |
+| Per-call exec timeout | 30 minutes | Per-call via the tool call's `timeoutMs`. | `RUN_DEFAULT_EXEC_TIMEOUT_MS` |
+| `web_fetch` returned body | 500 KB (UTF-8) | Per-call via the tool's `max_bytes` argument. | `REQUEST_WEB_FETCH_DEFAULT_MAX_BYTES` |
+
+## MCP
+
+| Option | Default | How to override | Source |
+| --- | --- | --- | --- |
+| MCP connect timeout (register + initialize + discover) | 30 seconds | Per-port via `connectTimeoutMs`. | `RUN_DEFAULT_MCP_CONNECT_TIMEOUT_MS` |
+| MCP `tools/call` timeout | 30 minutes | Per-port via `callTimeoutMs`. | `RUN_DEFAULT_MCP_CALL_TIMEOUT_MS` |
+
+## Links (signed URLs and tickets)
+
+| Option | Default | How to override | Source |
+| --- | --- | --- | --- |
+| Output link / signed-URL TTL | 300 seconds (5 minutes) at the storage layer; `session.outputs().link(...)` defaults to `"1h"` | Per-call via `expiresSeconds` (storage) or `expiresIn` on `session.outputs().link` / `session.outputs().fetch`. | `REQUEST_PRESIGN_URL_DEFAULT_TTL_SECONDS` |
+| Event-stream connection ticket TTL | 60 seconds | Per-mint via the `ttlMs` argument. | `REQUEST_TICKET_DEFAULT_TTL_MS` |
+
+## Subagents
+
+| Option | Default | How to override | Source |
+| --- | --- | --- | --- |
+| Concurrent child runs per lineage root | 1000 (live, non-terminal child runs) | Platform default (subagents run in-process; no public per-run override). Hard ceiling 4096. | `RUN_DEFAULT_MAX_CONCURRENT_CHILD_RUNS` |
+| Max subagent depth | 5 | Platform default (subagents run in-process; no public per-run override). | `RUN_MAX_PUBLIC_SUBAGENT_DEPTH` |
+
+## Workspace
+
+| Option | Default | How to override | Source |
+| --- | --- | --- | --- |
+| Run submit rate (per minute) | 120 (`0` = disabled); past it `POST /runs` fails with `429 workspace_submit_rate_exceeded` | Per-plane via env `AEX_WORKSPACE_SUBMIT_RATE_PER_MIN`; per-workspace via support. | — |
+| Max concurrent runs | Plan-based: 5 live root runs (free), 50 (Pro), 200 (Team); hard ceiling 200 | Per-plan (upgrade) or per-workspace override via support, clamped to the ceiling. | `PLANS[planKey].maxConcurrentRuns` |
+| Monthly spend cap | $250 per UTC calendar month (`0` = unlimited) | Per-workspace override via support. | `WORKSPACE_DEFAULT_SPEND_CAP_USD` |
+| Per-workspace mutation rate limits (per minute) | run cancel 30, run delete 30, signed link 120, API key create 10, API key delete 30 | Per-plane via the matching `AEX_RATE_LIMIT_<ACTION>_PER_MINUTE` env var. | `WORKSPACE_RATE_LIMIT_DEFAULTS` |
+| Workspace storage cap | 500 GB (decimal) | Per-plane via env `AEX_WORKSPACE_STORAGE_CAP_BYTES`; admin workspaces are uncapped (not a customer entitlement). | `WORKSPACE_DEFAULT_STORAGE_CAP_BYTES` |