@wardby/cli 0.5.2 → 0.5.3

package/help/coding-packages.md

@@ -3,7 +3,7 @@ id: coding-packages
 title: Approve packages for coding agents
 summary: Let Codex coding workers install vetted npm and PyPI dependencies through Wardby's registry proxy.
 audience: operator
-tags: [coding-agents, packages, npm, pypi, supply-chain, refusals, lockfile]
+tags: [coding-agents, packages, npm, pypi, supply-chain, refusals, lockfile, extras, pip-extras]
 appliesTo: >=0.2.1
 ---
 
@@ -35,8 +35,37 @@ if its own checks failed. A package reachable only through a refused one is
 refused too, so a high-severity advisory deep in a toolchain blocks every run
 that installs it.
 
+## PyPI extras
+
+A PyPI entry may name extras, as pip does: `psycopg[binary]`,
+`uvicorn[standard]>=0.30`. An extra allows only the dependencies that
+package's own metadata declares under that extra (for `psycopg[binary]`, the
+`psycopg-binary` wheel); a bare `psycopg` entry follows no extra, so
+`psycopg-binary` is refused with `wardby_package_not_allowed`. A plain entry
+follows no extras at all, its own or its dependencies': a plain `fastapi`
+whose metadata asks for `uvicorn[standard]` gets bare `uvicorn` only. Extras a
+dependency line names are followed only below an entry that names extras
+(`fastapi[standard]`), once the proxy has served that parent's metadata: if
+an extra's packages are still refused with `403 wardby_package_not_allowed`,
+name the extra on the allowlist directly (`uvicorn[standard]`). Every
+safeguard still applies to what an extra adds. Extras need the coding proxy
+and control plane on the same Wardby version: a proxy from before extras
+support cannot load an allowlist with a `name[extra]` entry, so every registry
+request of that run fails; and once a profile stores an extras entry, do not
+downgrade below the release that added extras.
+
+The quickstart's coding step offers the packages a local repository declares
+(`package.json`, `pyproject.toml` including its build-system packages,
+`requirements*.txt`, keeping Python extras such as `psycopg[binary]`) as
+`local-builder`'s allowlist after asking, or with `--allow-repo-packages` in a non-interactive
+run. See [Local repositories](local-repositories.md).
+
+> Re-running the quickstart replaces `local-builder`'s package allowlist with
+> what the repository declares (or empties it), discarding any packages you
+> added with `update_agent`; re-add them after a re-run.
+
 Review agents see the pull request's CI results in `repo_pr_read` and are
 told to trust CI over the sandbox's **Tests**.
 
 Read [`docs/coding-packages.md`](../docs/coding-packages.md) for allowlist
-syntax, package-policy controls, lockfile behavior, and refusal errors.
+syntax (including [PyPI extras](../docs/coding-packages.md#pypi-extras)), package-policy controls, lockfile behavior, and refusal errors.

package/help/creating-agents.md

@@ -59,6 +59,20 @@ separately; a missing one fails the run itself at dispatch, not
 `create_agent`/`update_agent`. See [Models and pricing](models.md) and
 [Model not available](errors/model-unavailable.md).
 
+## Run it on a schedule
+
+Give an agent a cron schedule with `set_schedule` (`agentId`, `schedule` such
+as `0 6 * * 1`, and `timezone`), and turn it off with `disable_schedule`. A
+coding agent needs a `codingProfile.defaultTask` first, since a scheduled run
+has no one to pass a task. A native agent's system prompt is its task. Trigger
+the agent once with `trigger_agent` and check the result before scheduling it.
+
+Schedules fire only while a Wardby scheduler runs: `wardby serve`, or
+`wardby scheduler` next to `wardby mcp`. On a quickstart install, start
+`npx @wardby/cli@latest scheduler` from the project directory and keep it
+running; the MCP server your assistant starts never fires schedules. See
+[Operate managed agents](operating-agents.md).
+
 ## Decision checklist
 
 Choose a native agent when all of these are true:

package/help/deploy-gke.md

@@ -11,8 +11,9 @@ appliesTo: >=0.2.1
 
 The supported Google Cloud deployment creates a GKE Autopilot cluster, private
 Cloud SQL for PostgreSQL, Artifact Registry, HTTPS Gateway, Google Secret
-Manager synchronization, and isolated gVisor-backed **Codex** coding-worker
-pods. It also applies namespace RBAC and default-deny network policies.
+Manager synchronization, and isolated gVisor-backed coding-worker pods for
+Codex and Claude Code. It also applies namespace RBAC and default-deny network
+policies.
 
 Use a dedicated billed project, a hostname you control, remote Terraform state,
 and a GitHub App installed only on repositories that agents need. Review
@@ -37,9 +38,32 @@ already write the tables and columns it adds (such as per-model usage for
 [cost attribution](cost-attribution.md), or a run's live turn count). Until the
 grants are applied, the coding proxy's writes are refused and coding runs fail.
 
-Claude Code's two-container executor is currently Docker-only; Kubernetes
-coding workers use the Codex path. Configure an identity provider and GitHub
-App before allowing people to use the public endpoint.
+The Kubernetes launcher runs Codex and Claude Code coding workers; a Claude
+Code pod adds a tool-runner sidecar with its own image. Configure an identity
+provider and GitHub App before allowing people to use the public endpoint.
+
+## Plan it with your assistant
+
+If you are an assistant connected to Wardby over MCP and the user asked to plan
+a GKE deployment, produce a written plan; do not create cloud resources. Read
+[Choose a deployment target](deployment-targets.md) first and confirm GKE is
+the right target. Then ask for, one at a time, and record:
+
+1. The Google Cloud project (dedicated, with billing) and region, and who
+   holds the IAM roles to apply Terraform.
+2. The public hostname and who controls its DNS.
+3. The identity provider for people signing in (see
+   [Configure identity and privileged access](identity-and-access.md)).
+4. The GitHub App: which repositories it is installed on (see
+   [Connect GitHub repositories](github.md)).
+5. Which coding providers the agents use (Codex, Claude Code or both), and
+   which provider keys and worker images that needs.
+6. Where Terraform state lives, and the monthly cloud budget and alerts.
+7. Optional: Jira.
+
+The plan lists those answers, the ordered steps above with the values filled
+in, the commands the user will run themselves, and the open questions. Point
+the user to the full guide below for every step.
 
 Follow the complete, ordered guide at
 [`docs/getting-started-gke.md`](../docs/getting-started-gke.md). It includes

package/help/deployment-targets.md

@@ -19,9 +19,9 @@ Wardby has one local path and two production-ready deployment shapes:
   identity provider. The Compose and Caddy configuration is a reference
   baseline, not a managed platform.
 - **Google Kubernetes Engine Autopilot:** the supported Google Cloud path. It
-  provisions GKE, private-IP Cloud SQL, Artifact Registry, isolated Codex
-  workers, HTTPS Gateway, and GCP-native secret and network controls. See
-  [Deploy on GKE](deploy-gke.md).
+  provisions GKE, private-IP Cloud SQL, Artifact Registry, isolated Codex and
+  Claude Code workers, HTTPS Gateway, and GCP-native secret and network
+  controls. See [Deploy on GKE](deploy-gke.md).
 
 AWS is supported as a portable runtime target and has a Bedrock Claude adapter,
 but Wardby does not ship a native AWS deployment module. Other cloud providers

package/help/getting-started.md

@@ -30,6 +30,11 @@ Claude Code. Run `wardby doctor` afterwards to verify the local installation.
   Review that branch with
   `trigger_agent {"agentId": "<reviewer id>", "review": {"branch": "wardby/run-<run id>"}}`.
   You need Docker and an OpenAI key (Codex) or an Anthropic key (Claude Code).
+  For a Python project (a root `pyproject.toml`, `setup.py`, `setup.cfg`,
+  `Pipfile` or `requirements*.txt`), the builder gets a Node + Python 3.12
+  workspace and can run `pytest`. Quickstart also offers the packages the
+  repository declares as the builder's package allowlist, so it can install
+  them (`--allow-repo-packages` in a non-interactive run).
   See [Use local git repositories](local-repositories.md).
 - **B. A coding agent that opens GitHub pull requests.** Do A first. Then
   install a GitHub App on the repository (Contents and Pull requests: read and
@@ -42,6 +47,20 @@ Claude Code. Run `wardby doctor` afterwards to verify the local installation.
   with webhooks, link a native agent to the repository with the `pull_request`
   trigger, and open a pull request. See [Code review agents](code-review-agents.md).
 
+- **D. Another language (Go, Java, Rust…).** Do A with Codex, then build a
+  worker image with that toolchain on the base image `wardby doctor` prints,
+  and set the builder's `codingProfile.workerImageRef`. Ask your assistant
+  "Help me build a Wardby worker image for Go"; it follows
+  [Build a custom worker image](build-worker-image.md). Codex agents only.
+
+The quickstart ends with a menu of next steps to ask your assistant: run the
+builder and reviewer, allow more packages, build a worker image, schedule an
+agent, set up an architecture reviewer and keeper (see
+[Set up an architecture agent](architecture-agent.md), which has a
+local-repository variant), or plan a GKE deployment
+([Deploy on GKE](deploy-gke.md)). Each names the help article the assistant
+follows.
+
 The full step-by-step guide is "Choose what to set up next" in
 [`docs/getting-started.md`](../docs/getting-started.md).
 

package/help/local-repositories.md

@@ -135,14 +135,42 @@ then:
   `CODING_CLAUDE_WORKER_IMAGE` plus `CODING_CLAUDE_TOOL_RUNNER_IMAGE`, override
   them with your own digests;
 - starts the coding proxy and runs the coding preflight;
+- detects Python projects: if the repository's committed root holds
+  `pyproject.toml`, `setup.py`, `setup.cfg`, `Pipfile` or a `requirements*.txt`,
+  `local-builder` gets a Node + Python 3.12 workspace (`toolchain: node-python`)
+  for Codex and Claude Code, with `pytest` and `ruff`, so it can run the tests.
+  The images come from `CODING_WORKER_IMAGE_NODE_PYTHON_3_12` (Codex) and
+  `CODING_CLAUDE_TOOL_RUNNER_IMAGE_NODE_PYTHON_3_12` (Claude Code); set them to
+  override. If this version has no Python image, quickstart says so and the
+  builder uses the Node workspace (it can edit but not run Python tests). Other
+  languages need a bring-your-own image via `workerImageRef`, which is
+  Codex-only today: Claude Code agents cannot use a custom toolchain yet. See
+  the BYO worker images guide in the long-form docs;
 - finds the repository: a trusted folder that is a git repository, or the
   repositories directly inside a trusted folder (hidden folders are skipped).
   With several it asks which to use; non-interactively it uses the first in
   sorted order and prints the choice. Re-run with `--trust <repo>` to pick
   another: folders passed on a run take precedence over saved ones;
+- offers the packages the repository declares (`package.json` dependencies,
+  `pyproject.toml` dependencies including optional groups and Poetry, with
+  Poetry's legacy `[tool.poetry.dev-dependencies]`, the `[build-system]
+requires` build packages (or `setuptools` and `wheel` when there is no
+  `[build-system]` table), and
+  `requirements*.txt`, read from the committed root) as `local-builder`'s
+  package allowlist: names without versions (Python extras such as
+  `psycopg[binary]` are kept), up to 200 per ecosystem. It lists them
+  and asks "Allow local-builder to install these packages through Wardby's
+  registry? [Y/n]"; every registry safeguard still applies. If you decline, or
+  run non-interactively without `--allow-repo-packages`, the allowlist stays
+  empty: add packages later with `update_agent` and
+  `codingProfile.packageAllowlist`. A re-run replaces the allowlist with what
+  the repository declares now. A manifest quickstart cannot read is skipped
+  with a note. See [Approve packages for coding agents](coding-packages.md);
 - creates `local-builder` (a coding agent, $2 budget) and `local-reviewer`
-  (a review agent, $1 budget) for the repository and prints the two
-  `trigger_agent` calls to try; and
+  (a review agent, $1.50 budget, on Claude Sonnet 5 or `gpt-5.6-terra` by
+  default, with the thorough review prompt quoted in
+  [Set up an architecture agent](architecture-agent.md#reviewer-system-prompt))
+  for the repository and prints the two `trigger_agent` calls to try; and
 - if the repository has no `.wardby/services.yaml`, offers a starter one with
   PostgreSQL and/or Redis. It is committed to the branch
   `wardby/quickstart-services` without touching your working tree. Merge that
@@ -151,11 +179,14 @@ then:
   branch" is whichever branch is checked out when quickstart runs.
 
 Flags: `--coding` (run the step), `--no-coding` (skip it), `--trust <dir>`
-(repeatable), `--coding-provider codex|claude-code` and
-`--starter-services postgres,redis|none`. In `--non-interactive` mode the step
+(repeatable), `--coding-provider codex|claude-code`,
+`--starter-services postgres,redis|none` and `--allow-repo-packages` (or
+`--no-allow-repo-packages`). In `--non-interactive` mode the step
 only runs with `--coding`, and it needs at least one `--trust`. `doctor` and
 `status` report the trusted folders, worker image, coding proxy and each local
-agent's repository, and `down` stops the proxy with the database.
+agent's repository, and `down` stops the proxy with the database. Quickstart
+ends with a menu of next things to ask your assistant, each naming the help
+article it follows; see [Get started](getting-started.md).
 
 ## Errors
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wardby/cli",
-  "version": "0.5.2",
+  "version": "0.5.3",
   "description": "Self-hosted control plane for budget-guarded AI agents.",
   "license": "Apache-2.0",
   "homepage": "https://github.com/wardby/wardby#readme",
@@ -56,6 +56,7 @@
     "format:check": "prettier --check .",
     "build:vendor": "node scripts/build-sandbox-vendor.mjs",
     "build:help": "tsx src/help/build.ts",
+    "sync:reviewer-prompt": "tsx src/quickstart/sync-reviewer-prompt.ts",
     "build:viewer-schemas": "tsx src/viewer/build-schemas.ts",
     "build": "npm run build:vendor && PRISMA_HIDE_UPDATE_MESSAGE=1 prisma generate && tsc -p tsconfig.build.json && npm run build:help",
     "prepare": "npm run build:vendor && PRISMA_HIDE_UPDATE_MESSAGE=1 prisma generate",
@@ -110,7 +111,7 @@
     "gpt-tokenizer": "^2.5.0",
     "jose": "^6.2.12",
     "node-html-parser": "^9.0.3",
-    "openai": "^4.67.0",
+    "openai": "7.30.0",
     "papaparse": "^5.7.0",
     "pg": "8.23.0",
     "pino": "^9.14.0",