@standardagents/cli 0.15.3 → 0.17.0-next.a4b7340

package/README.md

@@ -20,9 +20,10 @@ The package is published publicly so this one-liner works without a prior npm
 login.
 
 This command will:
-- Open Standard Agents in your browser for GitHub sign-in, billing, GitHub App setup, and repo creation
-- Clone the created private GitHub repo into the directory where you ran the command
+- Open Standard Agents in your browser for login, billing, and platform repository setup
+- Clone the created platform-owned Artifact repository into the directory where you ran the command
 - Write `STANDARD_AGENTS_API_KEY`, `PLATFORM_ENDPOINT`, and `STANDARD_AGENTS_API_URL` to `.dev.vars`
+- Configure a repo-local Git credential helper that mints short-lived Artifacts tokens through the Standard Agents platform
 - Install dependencies with the detected package manager, start the local dev server, and open the local instance
 
 For local platform development, point the same command at your local platform API:
@@ -34,8 +35,10 @@ STANDARD_AGENTS_API_URL=https://platform.agentbuilder-platform.orb.local pnpm ex
 When testing unreleased workspace package changes, keep the same platform flow
 and add `STANDARDAGENTS_WORKSPACE=1`. With `pnpm`, the CLI rewrites the cloned
 project's generated `@standardagents/*` dependencies to local workspace links
-before installing. If you are running a packed or globally installed local CLI,
-also set `STANDARDAGENTS_WORKSPACE_ROOT` to the monorepo root:
+before installing, and the repo-local Git credential helper points at the
+current local CLI entry instead of `npx -y @standardagents/cli@latest`. If you
+are running a packed or globally installed local CLI, also set
+`STANDARDAGENTS_WORKSPACE_ROOT` to the monorepo root:
 
 ```bash
 STANDARDAGENTS_WORKSPACE=1 STANDARD_AGENTS_API_URL=https://platform.agentbuilder-platform.orb.local pnpm exec agents init
@@ -49,16 +52,16 @@ that serves locally packed packages in place of the unpublished npm registry
 packages. Use `-- --mode=workspace` or `-- --mode=npx` when you only need one
 side.
 
-After the GitHub publish workflow completes, run
+After release automation publishes the CLI and runtime packages, run
 `pnpm onboarding:verify:production` to exercise the real production one-liner
 against the npm registry without touching GitHub, Stripe, or the production
 platform. It runs `npx @standardagents/cli@latest init` against a fake platform
 API and requires the generated project to install `@standardagents/*` packages
-from npm. The publish workflow also runs this verifier after `publish-cli`.
-All Standard Agents package publishes must go through that workflow. The
-workflow publishes with public access, repairs package visibility if a scoped
-version already exists, sets the release dist-tag, and then runs the production
-onboarding verifier. Do not run manual npm publishes to test this flow.
+from npm.
+All Standard Agents package publishes must go through the approved release
+automation. The release path publishes with public access, repairs package
+visibility if a scoped version already exists, and sets the release dist-tag.
+Do not run manual npm publishes to test this flow.
 
 Use `agents init --local my-agent-project` for the legacy local-only template scaffold that does not create a platform repo or billing connection.
 
@@ -78,10 +81,24 @@ pnpm exec agents scaffold
 ```
 
 Adds Standard Agents to an existing Vite project. The command updates
-`package.json` with the current `@standardagents/builder` and
-`@cloudflare/vite-plugin` versions, wires the Vite and Wrangler config, creates
-the Worker entry point, and creates the `agents/` directory structure with
-documentation files.
+`package.json` with the current `@standardagents/builder` version, wires the
+`builder()` Vite plugin, and creates the `agents/` directory structure with
+documentation files. The builder plugin generates the Cloudflare Worker entry
+and binding config at build time.
+
+### Deploy From Artifacts Git
+
+Deployments are triggered by pushes to the platform-owned Artifacts repository:
+
+```bash
+git push origin main
+# or
+agents deploy
+```
+
+`agents deploy` is a convenience wrapper around `git push origin HEAD:<branch>`.
+It does not run a local build or upload bundles; the platform build runner
+deploys from the Artifacts push event.
 
 ### Install The AgentBuilder Skill
 
@@ -133,38 +150,18 @@ prints a markdown table containing the exact `model` strings to use in
 
 ## Manual Configuration
 
-If you prefer to configure manually, add the following to your `wrangler.jsonc`:
-
-```jsonc
-{
-  "durable_objects": {
-    "bindings": [
-      {
-        "name": "AGENT_BUILDER_THREAD",
-        "class_name": "DurableThread"
-      },
-      {
-        "name": "AGENT_BUILDER",
-        "class_name": "DurableAgentBuilder"
-      }
-    ]
-  },
-
-  "migrations": [
-    {
-      "tag": "v1",
-      "new_sqlite_classes": ["DurableThread", "DurableAgentBuilder"]
-    }
-  ]
-}
-```
+For new projects, manual Cloudflare configuration is not required. Add
+`builder()` to `vite.config.ts`; it injects the Cloudflare Vite plugin, Worker
+entry, assets config, Durable Object bindings, Worker Loader binding,
+compatibility flags, and migrations automatically.
 
 ## TypeScript Types
 
-To get proper TypeScript types for the bindings, regenerate your worker types:
+AgentBuilder generates project types when the dev server starts. For a focused
+type-generation pass, run:
 
 ```bash
-pnpm cf-typegen
+pnpm exec vite build
 ```
 
 This will update your `worker-configuration.d.ts` file with: