@myapihq/cli 2.16.3 → 2.17.0

package/dist/commands/container.js

@@ -11,6 +11,7 @@ export const EXPOSES = [
     'GET /container/orgs/{org_id}/containers',
     'GET /container/orgs/{org_id}/containers/{id}',
     'DELETE /container/orgs/{org_id}/containers/{id}',
+    'PATCH /container/orgs/{org_id}/containers/{id}',
     'POST /container/orgs/{org_id}/containers/{id}/deploy',
     'GET /container/orgs/{org_id}/containers/{id}/logs',
     'GET /container/orgs/{org_id}/containers/{id}/revisions',
@@ -28,6 +29,7 @@ export const SCHEMA = {
     'max-instances': 'number',
     port: 'number',
     env: 'string',
+    unset: 'string',
     tail: 'number',
     scope: 'string',
     'no-promote': 'boolean',
@@ -587,6 +589,18 @@ Examples:
   myapi container create --name api --port 8080
   myapi container create --name nightly --type job --cron "0 3 * * *"
   myapi container create --name queue-worker --type worker --memory 1Gi`,
+    'env': `myapi container env <id> --env KEY=VALUE[,K2=V2] [--unset KEY3[,KEY4]] [--org <id>] [--json]
+
+Change environment variables on a container that already exists, and roll a new
+revision on the SAME image so they take effect. No rebuild, and the container
+keeps its URL, its scoped key and its custom domain.
+
+This is a MERGE. Variables you do not name keep their values, so adding one
+entry to an allowlist does not mean resending every secret. --unset removes.
+
+Examples:
+  myapi container env c-123 --env ALLOWED=a@x.com,b@y.com
+  myapi container env c-123 --env LOG_LEVEL=debug --unset LEGACY_FLAG`,
     'deploy': `myapi container deploy <id> <image-ref> [--org <id>] [--json]
        myapi container deploy <id> --source <dir|tar.gz> [--org <id>] [--json]
 
@@ -673,6 +687,7 @@ Subcommands:
   deploy <id> <image>  Ship a pre-built image (or --source <dir|tar> to build) and go live
                        (--smoke to verify before promoting; --no-promote to hold it back)
   domain <id> <domain> Bind a custom domain (--remove to unbind)
+  env <id>             Change environment variables (merge; rolls a new revision)
   get <id>             Inspect a container
   list                 List containers in your org
   logs <id>            Show recent runtime logs (--tail <n>, --scope all) — see build-logs for build failures
@@ -691,8 +706,59 @@ All commands accept --org <id> (or set default: myapi config set-org <id>).`);
             info(`Unknown subcommand: ${subcommand}. Run "myapi container --help" for the list.`);
         return;
     }
+    /**
+     * `myapi container env <id> --env K=V[,K2=V2] [--unset K3[,K4]]`
+     *
+     * Until 2026-08-19 the only way to change a variable was to delete the
+     * container and create another, losing the URL, the scoped key and the custom
+     * domain. The skill said to do exactly that, and a customer went through three
+     * generations of one container in a week because of it.
+     */
+    async function envCmd(id, flags) {
+        const config = requireConfig();
+        const orgId = requireOrg(flags, config, 'myapi container env <id> --env K=V [--unset K2]');
+        if (!id)
+            error('Missing id.\nUsage: myapi container env <id> --env KEY=VALUE[,K2=V2] [--unset KEY3[,KEY4]]');
+        const env = {};
+        if (typeof flags.env === 'string') {
+            const parsed = _parseEnv(flags.env);
+            if (typeof parsed === 'string')
+                error(parsed);
+            Object.assign(env, parsed);
+        }
+        if (typeof flags.unset === 'string') {
+            for (const k of flags.unset.split(',').map(s => s.trim()).filter(Boolean))
+                env[k] = null;
+        }
+        if (Object.keys(env).length === 0) {
+            error('Nothing to change. Pass --env KEY=VALUE to set one, or --unset KEY to remove one.\n' +
+                'This is a merge: variables you do not name keep their values.');
+        }
+        info('› Updating environment…');
+        const res = await sdkContainer.updateContainerEnv(config.api_key, orgId, id, env);
+        if (flags.json) {
+            printJson(res);
+            return;
+        }
+        if (res.set?.length)
+            info(`  set:     ${res.set.join(', ')}`);
+        if (res.removed?.length)
+            info(`  removed: ${res.removed.join(', ')}`);
+        // Say plainly whether the running container has the new values, because
+        // "stored" and "live" are different states and only one of them is what the
+        // caller asked for.
+        if (res.applied) {
+            success(`Redeployed on the same image — the new values are live${res.revision ? ` (${res.revision})` : ''}.`);
+        }
+        else {
+            info('  Stored. This container has no deployment yet, so the values apply on your first deploy.');
+        }
+        if (res.env)
+            info(`  ${Object.keys(res.env).length} variable(s) now set: ${Object.keys(res.env).sort().join(', ')}`);
+    }
     switch (subcommand) {
         case 'create': return create(args[0], flags);
+        case 'env': return envCmd(args[0], flags);
         case 'build-logs': return buildLogs(args[0], flags);
         case 'deploy': return deploy(args[0], args[1], flags);
         case 'list': return list(flags);

package/dist/sdk-container.test.js

@@ -144,12 +144,16 @@ describe('container.getContainerLogs', () => {
     });
 });
 describe('container.EXPOSES', () => {
-    it('covers the 11 container endpoints', () => {
+    it('covers the 12 container endpoints', () => {
         expect(container.EXPOSES).toEqual([
             'POST /container/orgs/{org_id}/containers',
             'GET /container/orgs/{org_id}/containers',
             'GET /container/orgs/{org_id}/containers/{id}',
             'DELETE /container/orgs/{org_id}/containers/{id}',
+            // Added 2026-08-19. Env is the one create-time setting that is NOT
+            // immutable: PATCH merges the map and rolls a revision on the same
+            // image, so the container keeps its URL, scoped key and custom domain.
+            'PATCH /container/orgs/{org_id}/containers/{id}',
             'POST /container/orgs/{org_id}/containers/{id}/deploy',
             // Added 2026-07-28. Promote and rollback are ONE endpoint: naming a
             // revision promotes it, omitting one rolls back to the previous ready

package/dist/skills/my-api-hq/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: my-api-hq
-version: 1.2.0
+version: 1.2.1
 description: >
   Auth, organizations, and billing hub. Start here to get an api_key and org_id — every other service depends on both.
 triggers: [api key, account, organization, org, billing, balance, topup, credits, setup, defaults, brand, sync brand, doctor, health check, is my org healthy]
-checksum: sha256-ef7057aa3584c43f852415f25ca5d023ee372c8d00f915a5da68a5e70634e2b2
+checksum: sha256-b4eef3d505e92f2b9fe8dfa45b74d4221e3c646947ebfe8961aa5a2445bfa139
 ---
 
 # MyApiHQ
@@ -34,27 +34,29 @@ An anonymous account can upgrade at any time via `myapi account link <email>`
 | Command | What it does |
 |---|---|
 | `myapi account setup` | Interactive setup: creates account, generates api_key, sets defaults |
-| `myapi status` | Single-screen orientation: account + every resource in the default org. Start here when you don't know what already exists |
+| `myapi status` | Single-screen orientation: account + every resource in the default org. Start here when you don't know what exists |
 | `myapi account whoami` | Show current account, default org/funnel, balance, free-tier usage |
-| `myapi account link [email]` | Upgrade anonymous account to registered (or add a second session) |
+| `myapi account link [email]` | Upgrade anonymous account to registered (or add a session) |
 | `myapi account switch [index]` | Switch active account |
+| `myapi account import-key` | Import an API key non-interactively (CI, Docker) |
+| `myapi account registrant <set\|get\|clear>` | WHOIS contact info `domain register` requires (ICANN) |
 | `myapi org list` | List all orgs (`*` marks the default) |
 | `myapi org create --name "..."` | Create a new org (`--yes` auto-sets as default) |
 | `myapi org get [id]` | Inspect one org (defaults to current default) |
 | `myapi org update [id]` | Update fields (name, tagline, description, business-sector, logo-url) |
-| `myapi org delete <id>` | Delete an org and cascade (funnels included). Verify the target with `myapi org get <id>` first; asks for confirmation — `--yes` required in non-interactive runs |
-| `myapi org sync-brand <domain>` | Scrape a live site and auto-fill brand info |
+| `myapi org delete <id>` | Delete an org and cascade (funnels included). Verify with `myapi org get <id>` first; `--yes` required non-interactively |
+| `myapi org sync-brand <domain>` | Scrape a live site to auto-fill brand info |
 | `myapi keys list / create / revoke <id>` | Manage API keys (alias `myapi account api-keys`) |
 | `myapi billing balance` | Check balance |
 | `myapi billing topup <amount>` | Top up by dollar amount |
 | `myapi billing history` | Recent transactions |
-| `myapi billing usage [--period month|30d]` | Spend rolled up by service (this month, or trailing 30d) |
-| `myapi billing spend-cap [<amount> | clear] [--period month|day]` | Set/show/clear the account-level spend ceiling (IAM Layer 2) |
-| `myapi billing auto-recharge [show \| set \| disable]` | Keep the wallet funded automatically — off-session refill when balance drops below a threshold, bounded by a monthly cap |
+| `myapi billing usage [--period month|30d]` | Spend rolled up by service (month or trailing 30d) |
+| `myapi billing spend-cap [<amount> | clear] [--period month|day]` | Set/show/clear the account-level spend ceiling |
+| `myapi billing auto-recharge [show \| set \| disable]` | Keep the wallet funded — off-session refill when balance drops below a threshold, capped monthly |
 | `myapi account mailing-address ["<address>"]` | Get or set the account's CAN-SPAM mailing address (required for email send) |
 | `myapi config set-org <id>` / `set-funnel <id>` / `set-domain <name>` | Set CLI defaults |
-| `myapi install-skills` | Install agent skill files into ~/.claude/, ~/.gemini/, ~/.cursor/ |
-| `myapi doctor [--verbose] [--json]` | Org-wide health check: per-slot config/integrity findings + DNS/HTTP probes |
+| `myapi install-skills` | Install agent skills into ~/.claude/, ~/.gemini/, ~/.cursor/ |
+| `myapi doctor [--verbose] [--json]` | Org-wide health check: config/integrity findings + DNS/HTTP probes |
 <!-- generated:end -->
 
 ## Examples

package/dist/skills/my-container-api/SKILL.md

@@ -1,21 +1,21 @@
 ---
 name: my-container-api
-version: 1.0.0
+version: 1.1.0
 description: >
   Run containers on demand — long-running services, background workers, and scheduled jobs. The heavier-duty sibling of edge functions, for native deps and long execution.
 triggers: [container, cloud run, dynamic app, custom domain app, service, worker, scheduled job, deploy container, docker image]
-checksum: sha256-a5aabfe95b85f1e6ceb2b9254441183d540e81f888cefbdcf302385b95db2fd0
+checksum: sha256-0a83428114cbc7065d1a4db4f8a0cf39ff965c51acac78f5eeff159345a08da2
 ---
 
 # MyContainerAPI
 
-A container runs a pre-built image on managed cloud infrastructure. Three types: a **service** (HTTP server, scales to zero), a **worker** (always-on background process), or a **job** (runs to completion — the only type that takes a cron schedule). Containers are the heavier-duty sibling of edge functions (`myapi fn`) — use them for native dependencies, long execution, or a full dynamic app.
+A container runs a pre-built image on managed cloud infrastructure. Three types: a **service** (HTTP server, scales to zero), a **worker** (always-on background process), or a **job** (runs to completion — the only type that takes a cron schedule).
 
 ## Capabilities
 <!-- llm:start -->
 The lifecycle is **create → deploy → (optionally) bind a custom domain**.
 
-- `create` registers the container and issues a **scoped API key**, returned once. The running container receives it as the `MYAPI_KEY` env var, so your code calls other MyAPI slots with no token handling. Deploy rotates this key.
+- `create` registers the container and issues a **scoped API key**, returned once. The container gets it as `MYAPI_KEY`, so your code calls other MyAPI slots with no token handling. Deploy rotates this key.
 - `deploy` takes **either** a pre-built image reference **or** a source
   directory. `--source ./dir` tars the directory, builds it server-side
   (typically ~4 minutes) and deploys the result — **no Docker on your machine,
@@ -53,12 +53,12 @@ it, so the probe would never reach your container.
 
 ### Custom domains (dynamic apps)
 
-`myapi container domain <id> <domain>` binds a custom domain to a **deployed** container, served over HTTPS automatically. This is the path for a dynamic backend on a real domain — distinct from `my-funnel-api`, which serves static sites.
+`myapi container domain <id> <domain>` binds a custom domain to a **deployed** container, over HTTPS automatically. The path for a dynamic backend on a real domain — unlike `my-funnel-api`, which serves static sites.
 
 Get it right:
 
 - **Deploy first.** Binding a domain to a container that has never deployed fails (422) — there is nothing running to route to.
-- **Register the parent domain first.** The domain's MyAPI-managed parent must already be registered via `my-domain-api`. Binding `app.synthesisdaily.com` requires `synthesisdaily.com` registered in MyAPI; otherwise 422.
+- **Register the parent domain first** via `my-domain-api`. Binding `app.synthesisdaily.com` requires `synthesisdaily.com` registered in MyAPI; otherwise 422.
 - **One domain per container.** Re-binding, or binding a hostname already taken, fails (409).
 - `--remove` unbinds. `myapi container get <id>` shows the bound `custom_domain`.
 <!-- llm:end -->
@@ -127,8 +127,13 @@ way that looks like an application bug.
 - **Any 5xx from your code is replaced by an edge HTML error page.** A JSON
   error envelope will not reach the caller. Return a 4xx if the reason has to
   survive.
-- **`--env`, `--cpu`, `--memory`, `--max-instances` and `--cron` are set at
-  `create` and cannot be changed by `deploy`.** Recreate to change them.
+- **`--cpu`, `--memory`, `--max-instances` and `--cron` are set at `create` and
+  cannot be changed by `deploy`.** Recreate to change those.
+- **`--env` CAN be changed after create**, with `container env` — a merge
+  (`--unset` removes) that rolls a new revision on the same image, keeping the
+  URL, the scoped key and the custom domain. Do NOT recreate to edit a variable:
+  this page said to for months, and it cost one customer three generations of
+  the same container in a week.
 
 ### Keeping a service warm
 
@@ -167,4 +172,4 @@ reply  { "success": true, "data": …, "error": null, "meta": {…} }
 
 Run `myapi container --help` for the full flag reference.
 
-**End-to-end example:** `examples/authenticated-app/` in github.com/myapihq/myapi walks the full seam — hosted login → token verification → per-user KV record → deployed container. Every constraint it hits is in **Runtime constraints** above.
+**End-to-end example:** `examples/authenticated-app/` in github.com/myapihq/myapi walks the full seam — hosted login → token verification → per-user KV record → deployed container.

package/dist/skills/my-crm-api/SKILL.md

@@ -1,15 +1,15 @@
 ---
 name: my-crm-api
-version: 1.0.0
+version: 1.0.1
 description: >
   The canonical store of engaged contacts + companies for an org. Auto-ingests from inbound webhooks via a configurable dot-path. Fixed lifecycle_stage enum (cold | warm | qualified | customer | churned). Append-only event timeline with reserved kinds. Soft delete + restore. Promote-from-Goldfox closes the discovery → engagement loop.
 triggers: [crm, contact, company, lead, engagement, pipeline, lifecycle, qualified, customer, webhook ingest, promote]
-checksum: sha256-3f840c8d7205d6a3eacc7c2be3ba2580a52a1964c085af241fd9ad67d48e19b6
+checksum: sha256-285ad94b1266588d103119ec139f11f0d19831bcbfd12779130f9fbeaf7f33f5
 ---
 
 # MyCRMAPI
 
-The store that closes the funnel. Today's loop without CRM: discover people (Goldfox) → save audience → send email → track pixel → form-fill via webhook → … nothing. People who *engage* live nowhere. CRM is where they land — automatically.
+The store that closes the funnel. Without CRM the loop ends nowhere: discover people (Goldfox) → audience → email → pixel → form-fill via webhook → … nothing. People who *engage* live nowhere. CRM is where they land.
 
 ## Capabilities
 <!-- llm:start -->
@@ -55,7 +55,7 @@ Agents cannot write events directly — the closed enum is intentional. For cust
 ### Auto-ingest
 
 Today (v1):
-- **Webhook**: configurable per endpoint via `crm_email_path` — a JSON dot-path. Default `"email"` ingests `{"email":"x@y.com"}`. For Stripe, set `data.object.customer_email`; for GitHub, `sender.email`. Empty string disables ingest for that endpoint.
+- **Webhook**: set per endpoint via `crm_email_path`, a JSON dot-path. Default `"email"` ingests `{"email":"x@y.com"}`. For Stripe, set `data.object.customer_email`; for GitHub, `sender.email`. Empty string disables ingest.
 
 Coming next (backend wiring in progress):
 - **Email**: every `myapi email message send` writes `email_sent`; opens/clicks fire `email_opened`/`email_clicked`
@@ -63,19 +63,19 @@ Coming next (backend wiring in progress):
 
 If a contact doesn't exist for the matched email, it's auto-created with `source=` matching the originating service. The contact's company is auto-linked by email domain (creates the company on first sight).
 
-**Missing lead? Check `myapi webhook deliveries` before concluding it never arrived.** A deadlock under concurrent ingest could drop the contact *after* the form returned success to the visitor (fixed 2026-07-27). Raw payloads were always stored, so the delivery is there even when the contact isn't.
+**Missing lead? Check `myapi webhook deliveries` before concluding it never arrived.** A deadlock under concurrent ingest could drop the contact *after* the form returned success (fixed 2026-07-27). Raw payloads are always stored, so the delivery is there even when the contact isn't.
 
 ### Soft delete + restore
 
-`myapi crm contacts delete <id>` sets `deleted_at` but **retains the event timeline**. By default soft-deleted contacts are excluded from search — pass `--include-deleted` to see them. Restore with `myapi crm contacts restore <id>`.
+`myapi crm contacts delete <id>` sets `deleted_at` but **keeps the event timeline**. By default soft-deleted contacts are excluded from search — pass `--include-deleted` to see them. Restore with `myapi crm contacts restore <id>`.
 
 ### Goldfox enrichment (deferred)
 
-A contact promoted from Goldfox carries a `goldfox_person_id`. In v2 the GET response will join live, embedding the row as `goldfox_person`; today that field is null. Goldfox-only fields are not yet filterable in CRM search.
+A contact promoted from Goldfox carries a `goldfox_person_id`. In v2 the GET response will embed the row as `goldfox_person`; today it is null. Goldfox-only fields are not yet searchable.
 
 ### Search filter — re-engagement semantics
 
-`--max-last-engagement-days N` returns contacts last engaged *more than* N days ago, and intentionally **includes contacts with no engagement at all** (promoted-but-never-emailed Goldfox leads) — the natural targets of a re-engagement campaign. To separate "never tried" from "tried and went cold," layer `--origin goldfox` or post-filter the JSON.
+`--max-last-engagement-days N` returns contacts last engaged *more than* N days ago, and intentionally **includes contacts with no engagement at all** (promoted-but-never-emailed Goldfox leads) — the natural targets of a re-engagement campaign. `--min-last-engagement-days N` is its complement: engaged *within* N days. `--company-id <id>` narrows to one company. To separate "never tried" from "tried and went cold," layer `--origin goldfox`.
 
 ### Failure modes
 
@@ -98,13 +98,13 @@ A contact promoted from Goldfox carries a `goldfox_person_id`. In v2 the GET res
 | `myapi crm contacts update <id> [--stage ...] [...]` | Patch fields. Stage change emits `stage_changed` event |
 | `myapi crm contacts delete <id>` | Soft delete (events retained) |
 | `myapi crm contacts restore <id>` | Restore a soft-deleted contact |
-| `myapi crm contacts promote <goldfox_person_id>` | Idempotent Goldfox → CRM promotion |
+| `myapi crm contacts promote <goldfox_person_id>` | Idempotent Goldfox → CRM promote |
 | `myapi crm contacts events <id> [--kind ...]` | Timeline (newest first), filter by kind |
 
 ### Companies
 | Command | What it does |
 |---|---|
-| `myapi crm companies list / search / create / get / update / delete / restore` | Same shape as contacts |
+| `myapi crm companies list / search / create / get / update / delete / restore` | Same shape as contacts. `--domain` filters search, `--name` sets display name |
 | `myapi crm companies promote <domain>` | Goldfox company id IS its domain — pass the domain |
 
 <!-- generated:end -->

package/dist/skills/my-email-api/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: my-email-api
-version: 1.0.0
+version: 1.0.1
 description: >
   Send transactional and bulk email from your own domain. Create mailboxes, send/receive messages, generate AI templates, and manage warmup.
 triggers: [email, mailbox, send email, transactional email, template, warmup, inbox, outbox, ses, sender reputation]
-checksum: sha256-98aedd0274a450fdd68a2d0cfe3a8af33520c58b2ce6e7cfaee7840fd5526aa6
+checksum: sha256-18f539fc12dd9e9e8f2abecf518aa1ee70741f85cc26ba0a6a941b9c29d537d8
 ---
 
 # MyEmailAPI
@@ -24,7 +24,7 @@ A registered domain via **mydomainapi** is the prerequisite — mailboxes need a
 <!-- generated:start -->
 | Namespace | Subcommands | Purpose |
 |---|---|---|
-| `email mailbox` | `create`, `list`, `activate-sending` | Create and manage mailboxes |
+| `email mailbox` | `create`, `list`, `delete`, `activate-sending`, `set-forwarding`, `clear-forwarding` | Create and manage mailboxes |
 | `email message` | `send`, `status`, `sent`, `inbox`, `outbox`, `get` | Transactional send + read |
 | `email warmup` | `start`, `stats`, `pause`, `resume`, `stop` | IP/domain warmup for sending reputation |
 | `email template` | `generate`, `list`, `get`, `preview`, `edit`, `send-test`, `delete` | AI-generated HTML templates |
@@ -60,6 +60,22 @@ myapi email warmup stats --address hello@yourdomain.com
 ```
 <!-- llm:end -->
 
+## Flags worth knowing
+
+| Flag | Where | What it does |
+|---|---|---|
+| `--username` + `--domain` | `mailbox create` | Alternative to the positional `<user@domain>` |
+| `--filter unassigned` | `mailbox list` | Orphaned mailboxes — those whose domain is gone |
+| `--html` | `message send` | Send an HTML body instead of `--body` plain text |
+| `--template-id` + `--template-vars` | `message send` | Send a stored template with a JSON var map, instead of a body |
+| `--name` | `template generate` | Alternative to the positional `<name>` |
+| `--per-day` | `warmup start` | Cap the daily volume the ramp climbs to |
+| `--emails`, `--quick` | `verify bulk` | Addresses inline rather than on stdin; skip the catch-all probe |
+
+Forwarding keeps the original: `set-forwarding <user@domain> <forward-to@domain>`
+copies every inbound message to an external address and leaves it in the mailbox.
+`clear-forwarding <user@domain>` stops it.
+
 ## Notes
 
 - A mailbox is uniquely identified by its address (`username@domain`).

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@myapihq/cli",
   "license": "Apache-2.0",
-  "version": "2.16.3",
+  "version": "2.17.0",
   "description": "MyAPI command-line interface",
   "repository": {
     "type": "git",
@@ -46,7 +46,7 @@
     "lint:skills:strict": "node scripts/copy-skills.js && node scripts/lint-skills.js --strict"
   },
   "dependencies": {
-    "@myapihq/sdk": "^2.16.3"
+    "@myapihq/sdk": "^2.17.0"
   },
   "devDependencies": {
     "@types/node": "^25.6.0",