everyapp 0.3.0-rc.2 → 0.3.0-rc.4

package/skills/everyapp/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: everyapp
-description: Create, run, deploy and manage private web apps on Cloudflare with everyapp (Every App). Use before running any everyapp command, to deploy an app, set a secret, query its database, check the Gateway, or answer any "how do I" question about Every App.
+description: Create, run, deploy and manage private web apps on Cloudflare with everyapp (EveryApp). Use before running any everyapp command, to deploy an app, set a secret, query its database, check the Gateway, or answer any "how do I" question about EveryApp.
 ---
 
 everyapp: self-hosted platform for private web apps on Cloudflare. While
 publishing is paused the command is `pnpm everyapp` (never `npx everyapp`),
-run from the Every App checkout or from an app's directory (its package.json
+run from the EveryApp checkout or from an app's directory (its package.json
 links the CLI).
 
 Docs: two worlds. The user docs (https://everyapp.com/docs) are short and
@@ -13,7 +13,9 @@ for the person. The agent docs are yours: https://everyapp.com/llms.txt
 lists every page with a one-line summary; a page is Markdown at its URL
 plus .md (https://everyapp.com/docs/agent/manifest.md); in a checkout they
 are landing-page/content/agent/*.md. Pages: setup (driving setup for a
-person, every handoff), cli (every command and flag), json (the --json
+person, every handoff), apps (the open apps: each one's id, repository,
+install command, every setting and whether it needs R2), cli (every
+command and flag), json (the --json
 protocol), errors (every code and its fix), troubleshooting (by symptom),
 status (the report, every line, and its fixes in order), manifest
 (everyapp.config.ts), identity (headers, token, env, SDK), secrets
@@ -21,7 +23,11 @@ status (the report, every line, and its fixes in order), manifest
 email, events (webhooks, email alerts, the signature, every event type,
 emit()), mcp (tools, connector, OAuth), deploy (the pipeline, what the policy
 check refuses), providers (API providers: the catalog, registering one,
-a spec's fields), access (Cloudflare Access), workspace (the workspace from
+a spec's fields), access (Cloudflare Access), signin (sign-in providers:
+Continue with Google, Microsoft, GitHub, Apple, Cloudflare or SSO; every
+setting, the signin commands), ai (the Gateway's default model
+provider: the order, `ai default|show|list`, AI Gateway in front, what an
+app writes), workspace (the workspace from
 the terminal and from an AI client: every command and every tool), gateway
 (everything a Gateway offers: apps vs MCP apps vs the compact MCP surface,
 people, groups and caps, the CLI by job, what to suggest next, other MCP
@@ -29,8 +35,10 @@ servers), build (the build-every-app skill as a page), patterns (its
 example-patterns index), repo/* (security model, capabilities, runbooks).
 Step-by-step setup of each
 integration (the Gateway, Access, email, DataForSEO, Context, OpenRouter,
-OpenAI, Workers AI, Google, Microsoft 365, Slack; every catalog provider by
-id in setup/providers.md): setup/README.md beside this file.
+OpenAI, Workers AI, the default model provider (setup/ai.md) and Cloudflare
+AI Gateway (setup/ai-gateway.md), Google, Microsoft 365, Slack; every
+catalog provider by id in setup/providers.md): setup/README.md beside this
+file.
 Answering "how do I": fetch the page for the subject and answer from it
 with the exact command or manifest field, naming the page. A failed
 command: look its code up on errors (anchor: the code, lowercased) before
@@ -55,8 +63,8 @@ scope sets (google-workspace, microsoft-365, slack) is listed with
 scopes: [...] and held to them; after a schema change run pnpm run
 db:generate; a value only dev needs goes in .dev.vars, never in git (dev
 page). The way back: the first row of the app's sidebar (or of its page
-header when it has no sidebar) is a muted "‹ Every App" link to
-GATEWAY_URL (aria-label "Back to Every App"), above the app's own name,
+header when it has no sidebar) is a muted "‹ EveryApp" link to
+GATEWAY_URL (aria-label "Back to EveryApp"), above the app's own name,
 so every app on the Gateway reads the same; put nothing else about the
 Gateway in the footer.
 
@@ -107,11 +115,15 @@ Data:    pnpm everyapp db migrate (local)   pnpm everyapp db query "<sql>" [--lo
          (a production write stops with CONFIRMATION_REQUIRED: add --yes only
          if the user said so). pnpm everyapp db restore --json undoes the last
          deploy's migrations (and every write since): only when the user asks.
-Postgres: an app with resources.hyperdrive or migrations.dialect "postgresql"
-         reads POSTGRES_DATABASE_URL (and <BINDING>_ORIGIN_URL) from
-         .everyapp/secrets.env, which the user writes; never print, commit or
-         ask for its values in chat. deploy runs drizzle-kit migrate before
-         the upload.
+Postgres: any Postgres with a URL (Neon, Supabase, …) goes through Hyperdrive:
+         resources.hyperdrive, database.provider "postgres", migrations.dialect
+         "postgresql" (manifest page, #postgres). The deploy reads
+         POSTGRES_DATABASE_URL (and <BINDING>_ORIGIN_URL) from
+         .everyapp/secrets.env, which the user writes (configure doesn't);
+         never print, commit or ask for its values in chat. Without it deploy
+         stops HYPERDRIVE_ORIGIN_MISSING (data.variables, data.file) and status
+         names it under the app. deploy runs drizzle-kit migrate before the
+         upload. Turso is libSQL: app secrets, not Hyperdrive.
 Secrets: pnpm everyapp configure <app> --json   sets up an app: every setting its
          manifest declares, each where it is held (an AI key or a capability's
          client on the Gateway, once for every app; the app's own secrets on
@@ -248,7 +260,7 @@ Tools:   an app's AI tools are defineTools() in src/tools.ts; the Gateway
          http://<app-id>.localhost:8787/mcp) and snapshots them at deploy.
          How to write, connect and debug them: mcp.md beside this file.
 Wipe:    pnpm everyapp teardown --account-id <id> --dry-run --json   deletes
-         EVERYTHING Every App made in one Cloudflare account (the Gateway too):
+         EVERYTHING EveryApp made in one Cloudflare account (the Gateway too):
          only on a dedicated test account the user names, never one they use.
          Always --dry-run --json first and show the user data.plan. It needs
          EVERYAPP_TEST_ACCOUNTS=<id> and CLOUDFLARE_API_TOKEN scoped to that
@@ -270,16 +282,19 @@ Security: the Gateway signs people in and passes identity to the app in a
          against the list there. No CI job and no API key: the review runs
          where you run. Fix what it finds, or say in the pull request why a
          finding is a false positive. What the Gateway promises and what an
-         app must do itself: docs/threat-model.md in the Every App checkout
+         app must do itself: docs/threat-model.md in the EveryApp checkout
          (https://everyapp.com/docs/agent/repo/threat-model).
 
 Only a person can: approve the Cloudflare login, open the owner link, pick
 a workers.dev subdomain, pay for Workers Paid, buy a domain. Interactive
 setup optionally offers browser deployment: a Yes/No prompt (default No),
 then a hidden Cloudflare API token prompt. Never ask for its value in chat.
-It then offers Cloudflare Access (Yes by default; the team name asked for
-when the account has none); under --json neither is asked, and --yes
-answers No to both.
+It then puts Cloudflare Access in front by default (asked at a terminal,
+Yes by default; the team name asked for when the account has none); under
+--json or --yes it goes on without a question when the account can (a Zero
+Trust team exists, the Cloudflare login is an owner or admin), else the
+warning ACCESS_SETUP_SKIPPED says why and names access on; --no-access
+leaves it off. --yes answers No to browser deployment.
 Handing off: stop, tell the person in one or two lines what to do (the
 action's url and code, what to click, what to come back with), and resume
 with data.rerun when they say it is done. Two more only a person can do:

package/skills/everyapp/mcp.md

@@ -159,8 +159,10 @@ Workspace tools (Gateway connector only; every admin action of the UI, listed
          `everyapp_workspace_apps`, `everyapp_workspace_app_set`,
          `everyapp_workspace_app_access`, `everyapp_workspace_app_access_set`,
          `everyapp_workspace_app_cap`, `everyapp_workspace_cap_default`,
-         `everyapp_workspace_usage`,
-         `everyapp_workspace_activity`, `everyapp_workspace_rename`, and the
+         `everyapp_ai_show` (any member), `everyapp_ai_default`,
+         `everyapp_workspace_usage`, `everyapp_workspace_activity`,
+         `everyapp_workspace_audit` (the audit log: who did what, 90 days),
+         `everyapp_workspace_rename`, and the
          events tools `everyapp_workspace_events`, `everyapp_workspace_events_add`
          (a generated signing secret comes back once, in that answer: it opens
          nothing on the Gateway, so the person stores it in the receiver now),
@@ -190,8 +192,17 @@ Provider tools (Gateway connector only; one audit row per call like the
          never a replace of a row that is there) and
          `everyapp_provider_remove` (`{ id }`: refuses a built-in, a row
          whose key is set, and a row an app lists). A hosted Gateway hides
-         both writers. No key is ever set through a tool: `everyapp secret
-         set NAME` from the terminal. Full reference:
+         both writers. `everyapp_provider_add` also takes `{ preset }`, an
+         OAuth preset (github-oauth, notion-oauth, …; the list tool's
+         `presets`) or a built-in client (google-workspace), and answers
+         the redirect URI to register at the provider's console. Every
+         member gets `everyapp_provider_connections` (their own connected
+         accounts; `all: true` the organization's, owners and admins) and
+         `everyapp_provider_disconnect` (their own; owners and admins
+         anyone's or the organization's). Connecting is a browser flow at
+         `<gateway>/connect/<provider>`, never a tool. No key, client or
+         token ever passes through a tool: `everyapp secret set NAME` from
+         the terminal, or Admin → Providers. Full reference:
          /docs/agent/mcp#provider-tools.
 Sign-in provider tools (Gateway connector only, owners and admins, reads):
          `everyapp_signin_list` (Manage workspace → Sign-in: each sign-in
@@ -264,8 +275,11 @@ snapshot yet shows no hint (its tools load on first use).
 Scripts and anything that takes a header: a personal access token. In the
 Gateway open **Admin** (the sidebar footer's **Manage workspace**; owners and
 admins only), tab **Tokens**, heading **Personal access tokens**, button
-**New token**: a name, **All my apps** or one app, an expiry (default
-90 days). The token is `epat_…`, shown once, read & write. Send it as
+**New token**: a name, an access level (**Read only**, the default:
+`mcp:read`; **Read & write**: `mcp:write`; **Full access**: `*`, with a
+warning), **All my apps** or one app (the one app is the default when there
+is one), an expiry (default 30 days). The token is `epat_…`, shown once.
+Send it as
 `Authorization: Bearer epat_…` to `https://<gateway>/mcp` (a token made for one
 app sees that app alone):
 
@@ -284,7 +298,7 @@ deactivating a person ends all of theirs; tokens are revoked on Admin, Tokens.
 
 Other servers worth having beside the Gateway's (Cloudflare's API server for
 the owner, read before write; nothing else): [setup/gateway.md](setup/gateway.md),
-"Optional: MCP servers worth having beside Every App". Offer one in a line;
+"Optional: MCP servers worth having beside EveryApp". Offer one in a line;
 never add it unasked.
 
 ## Troubleshooting
@@ -310,7 +324,7 @@ Admin (a connection made with **Only these apps** needs a reconnect to add one).
 expired or revoked token, a bearer that isn't `epat_` on an app host, the token
 of a revoked connection); its body depends on the surface. On
 `https://<gateway>/mcp` with OAuth on: an empty body and
-`WWW-Authenticate: Bearer realm="OAuth", resource_metadata="…/.well-known/oauth-protected-resource/mcp", scope="mcp:read"`
+`WWW-Authenticate: Bearer realm="OAuth", resource_metadata="…/.well-known/oauth-protected-resource/mcp", scope="mcp:read mcp:write"`
 (`error="invalid_token"` added when a token was sent); a revoked connection's
 token gets `{"error":"invalid_token","error_description":"This connection was revoked or lost its access. Connect again."}`.
 On `https://<app-host>/mcp` (where the manifest sets `mcp`), and on the Gateway with OAuth off:

package/skills/everyapp/security-review.md

@@ -8,7 +8,7 @@ by the agent that made the change, with no CI job and no API key.
 ## The app boundaries
 
 What the review looks for (what the Gateway promises and what the app must
-do itself is the threat model, `docs/threat-model.md` in the Every App
+do itself is the threat model, `docs/threat-model.md` in the EveryApp
 checkout, served at https://everyapp.com/docs/agent/repo/threat-model):
 
 - A route, server function or tool that reads who the user is from anything

package/skills/everyapp/setup/README.md

@@ -21,6 +21,8 @@ click when they have to do something themselves.
 | OpenRouter                                    | [openrouter.md](openrouter.md)         | `OPENROUTER_API_KEY`                                                            | OpenSEO, Open CRM, agentic-inbox                                        |
 | OpenAI                                        | [openai.md](openai.md)                 | `OPENAI_API_KEY`, `AI_PROXY_EXTRA_ROUTES`                                       | apps listing the `openai` provider                                      |
 | Workers AI                                    | [workers-ai.md](workers-ai.md)         | `WORKERS_AI_API_TOKEN` (`CLOUDFLARE_ACCOUNT_ID` is set by `everyapp setup`)     | agentic-inbox (optional)                                                |
+| The default model provider (any one key)      | [ai.md](ai.md)                         | one provider's key (OpenRouter first); the choice with `everyapp ai default`    | every app whose manifest says `ai: { chat: true }` (agentic-inbox, OpenCRM) |
+| Cloudflare AI Gateway in front of the models  | [ai-gateway.md](ai-gateway.md)         | `AI_GATEWAY_ID` (set by `everyapp ai gateway on`; optional `AI_GATEWAY_API_KEY`) | every AI provider call, once it is on                                   |
 | Google (Gmail, Calendar, Search Console and Analytics) | [google.md](google.md)        | `GOOGLE_WORKSPACE_CLIENT_ID`, `GOOGLE_WORKSPACE_CLIENT_SECRET`                  | Open CRM                                                                |
 | Microsoft 365 (Outlook mail and calendar)     | [microsoft-365.md](microsoft-365.md)   | `MICROSOFT_365_CLIENT_ID`, `MICROSOFT_365_CLIENT_SECRET`                        | Open CRM                                                                |
 | Slack (OAuth client)                          | [slack.md](slack.md)                   | `SLACK_CLIENT_ID`, `SLACK_CLIENT_SECRET`                                        | Open CRM                                                                |
@@ -49,8 +51,23 @@ whole spec, hint and smoke request included, and its setting is set like
 any Gateway setting (`pnpm everyapp secret set <NAME>`, which first names
 the provider and the hosts its key goes to).
 
+An OAuth provider (GitHub, Notion, Linear, GitLab, Atlassian, HubSpot,
+Zoom, Dropbox, Spotify, X, or any custom one; the agent docs'
+`providers` page, "OAuth providers") has no file either: `pnpm everyapp
+provider presets` lists what can be added, `pnpm everyapp provider add
+--oauth <preset>` adds it and prints the redirect URI the person registers
+at the provider's console (`https://<gateway>/connect/<id>/callback`) and
+the two settings to set, `pnpm everyapp secret set <ID>_CLIENT_ID
+<ID>_CLIENT_SECRET` (an owner or admin may paste them in Manage workspace →
+Providers instead). Only a person can make the OAuth app at the provider
+and approve a consent; after the client is set, each member connects their
+own account under Connected accounts in the account menu. Google,
+Microsoft 365 and Slack below are the same: their files set the client,
+and the same client serves both the app-driven flow those files describe
+and the Gateway-owned one.
+
 Which integrations a person needs: the apps they deploy decide. The four
-Every App apps (OpenSEO, OpenCRM, OpenAnalytics, Agentic Inbox) are
+EveryApp apps (OpenSEO, OpenCRM, OpenAnalytics, Agentic Inbox) are
 installed from their GitHub releases by [gateway.md](gateway.md)'s last
 step, each unless the person skips it; the keys they then ask for are the
 files below. From any

package/skills/everyapp/setup/access.md

@@ -15,10 +15,14 @@ team lacks it), an allow policy with every member's and invitee's email, two
 Access applications, and the three Gateway settings, in one run. At the end
 the person has Access's login before the Gateway, MCP clients, the Gateway's
 `/health` and each app's public routes still reachable without it, and
-optionally no passwords. A person running `pnpm everyapp setup` at a
-terminal is offered the same by setup itself ("Put Cloudflare Access in
-front of your Gateway?", Yes by default); under `--json` nobody is, so the
-offer is yours, after the owner exists. This
+optionally no passwords. `pnpm everyapp setup` does the same by
+default once the owner exists: a person at a terminal is asked ("Put
+Cloudflare Access in front of your Gateway?", Yes by default); under
+`--json` or `--yes` it goes on without a question when the account can (a
+Zero Trust team exists, the Cloudflare login is an owner or admin of the
+Gateway), and otherwise the warning `ACCESS_SETUP_SKIPPED` says why and
+names `access on`: then the offer is yours. `setup --no-access` leaves it
+off. This
 is the "outer ring" of `docs/runbooks/cloudflare-access.md`; the other way,
 a "Continue with Company SSO" button, is
 the runbook's "OIDC sign-in" and isn't covered here.
@@ -127,9 +131,9 @@ one-time PIN expires 10 minutes after it is sent.
 | `ACCESS_HOSTED`                                                                                                     | a hosted Gateway ignores Access                                                                                                                                                                                                                                       | not available there                                                                                                                                                                                                                                                                                              |
 | `ACCESS_SESSION_INVALID`, `ACCESS_EMAIL_INVALID`, `ACCESS_DOMAIN_INVALID`                                           | a flag's value                                                                                                                                                                                                                                                        | durations like `720h` or `2h30m`, a full address, the part after the `@`                                                                                                                                                                                                                                         |
 | warning `ACCESS_EMAIL_NOT_INVITED`                                                                                  | `--email` names someone without an account; the Gateway refuses them                                                                                                                                                                                                  | invite them in **Manage workspace → Users**                                                                                                                                                                                                                                                                      |
-| warning `ACCESS_IDP_UNVERIFIED_EMAILS`                                                                              | a generic OIDC or SAML provider lets people pick their own email; `on` leaves it off the Every App applications                                                                                                                                                       | nothing, unless the person wants it allowed anyway: then they allow it in the dashboard, knowing the risk (runbook: "Verified emails")                                                                                                                                                                           |
+| warning `ACCESS_IDP_UNVERIFIED_EMAILS`                                                                              | a generic OIDC or SAML provider lets people pick their own email; `on` leaves it off the EveryApp applications                                                                                                                                                       | nothing, unless the person wants it allowed anyway: then they allow it in the dashboard, knowing the risk (runbook: "Verified emails")                                                                                                                                                                           |
 | warning `ACCESS_ONE_APPLICATION`                                                                                    | one Access application covers both hosts                                                                                                                                                                                                                              | kept and updated; an app host's Access cookie is then a Gateway login too                                                                                                                                                                                                                                        |
-| warning `ACCESS_FOREIGN_DESTINATION`                                                                                | the application also covers something that isn't Every App's                                                                                                                                                                                                          | kept as found; `access off` won't delete that application                                                                                                                                                                                                                                                        |
+| warning `ACCESS_FOREIGN_DESTINATION`                                                                                | the application also covers something that isn't EveryApp's                                                                                                                                                                                                          | kept as found; `access off` won't delete that application                                                                                                                                                                                                                                                        |
 | warning `ACCESS_INLINE_POLICIES`                                                                                    | the application has policies of its own, so the shared policy can't attach                                                                                                                                                                                            | the person makes them reusable in the dashboard, or manages it there                                                                                                                                                                                                                                             |
 | warning `ACCESS_ROUTE_NOT_EXPRESSIBLE`, `ACCESS_TOO_MANY_PUBLIC_ROUTES`                                             | a public route stays behind Access: no Access pattern for it (one `*` per path segment), or past the 25 overrides per host the command allows (the runbook's limit; Cloudflare's account limits page lists none)                                                      | people signed in still reach it; merge routes under one prefix                                                                                                                                                                                                                                                   |
 | warning `ACCESS_APP_OUTSIDE_BASE`                                                                                   | the app's host isn't one label under `<app base domain>`, so the apps' application on `*.<app base domain>` doesn't cover it: Access isn't in front of that app at all (the Gateway still signs people in there); merging routes changes nothing                      | the person moves the app under the base domain, or makes an Access application for that host by hand in **Zero Trust → Access controls → Applications**                                                                                                                                                          |
@@ -146,7 +150,7 @@ one-time PIN expires 10 minutes after it is sent.
 | MCP clients get an HTML login page                                                                                  | a bypass is missing                                                                                                                                                                                                                                                   | `pnpm everyapp access on --json`                                                                                                                                                                                                                                                                                 |
 | teammates can't log in at Access at all                                                                             | the team's only provider is Sign in with Cloudflare, restricted to the account's members                                                                                                                                                                              | `pnpm everyapp access on --json` adds the one-time PIN beside it, on the applications too                                                                                                                                                                                                                        |
 | Access's forbidden page after **Sign in with Cloudflare**                                                           | the person's Cloudflare account email isn't a Gateway member (`ACCESS_LOGIN_NOT_MEMBER`)                                                                                                                                                                              | use **Send login code** with the Gateway address, or invite the Cloudflare one                                                                                                                                                                                                                                   |
-| `ACCESS_IDP_ANY_CLOUDFLARE_ACCOUNT` from `on` or `show`                                                             | a Cloudflare provider's **Restrict to account members** is off; `on` leaves it off the Every App applications (the PIN alone signs people in)                                                                                                                         | the person turns it on: Zero Trust → Settings → Authentication → the provider; then `pnpm everyapp access on --json` allows it                                                                                                                                                                                   |
+| `ACCESS_IDP_ANY_CLOUDFLARE_ACCOUNT` from `on` or `show`                                                             | a Cloudflare provider's **Restrict to account members** is off; `on` leaves it off the EveryApp applications (the PIN alone signs people in)                                                                                                                         | the person turns it on: Zero Trust → Settings → Authentication → the provider; then `pnpm everyapp access on --json` allows it                                                                                                                                                                                   |
 | the 51st person is blocked by Access                                                                                | the Free plan's 50 seats                                                                                                                                                                                                                                              | the person removes inactive users (Zero Trust → **Team & Resources → Users** → **Action → Remove users**; `cf zero-trust seats edit` does it from the shell, only when they ask), or pays                                                                                                                        |
 | `EMAIL_PASSWORD_SIGN_IN=false` changes nothing                                                                      | no owner has linked Access yet (no log line for it: `pnpm everyapp access show --json` still lists the owner in `data.linkPending`), or Access isn't configured (`access.config_problem` in the logs)                                                                 | an owner signs in through Access once; or fix the settings                                                                                                                                                                                                                                                       |
 | locked out: nobody passes Access                                                                                    | the policy or the one-time PIN is wrong at Cloudflare's edge; the Worker's settings can't let anyone in                                                                                                                                                               | when the person asks: `pnpm everyapp access off --json --yes` (deletes the two applications too); or the person fixes the policy, or deletes the applications, in **Zero Trust → Access controls → Applications**                                                                                                |

package/skills/everyapp/setup/ai-gateway.md

@@ -0,0 +1,117 @@
+# Cloudflare AI Gateway in front of the model providers
+
+Cloudflare AI Gateway is a proxy for model calls in the Gateway's own
+Cloudflare account: a log of every call, caching, rate limits, retries
+and a spend view, at `https://gateway.ai.cloudflare.com/v1/<account>/<gateway>/…`.
+It has no models of its own and never replaces a provider's key: with it
+on, every call the Gateway makes to an AI provider that has an AI Gateway
+slug (OpenRouter, OpenAI, Anthropic, Groq, Mistral, Workers AI) goes
+through it with the provider's own key still on the call; Gemini and
+Cohere go direct (Cloudflare documents no form for their OpenAI-shaped
+paths). It changes no app and no manifest. At the end the person has an
+AI Gateway named `everyapp` in their account, `AI_GATEWAY_ID` on the
+Gateway, and every model call showing up in the AI Gateway dashboard.
+
+## Settings
+
+| NAME                 | Required or optional                               | What it holds                                                                                           |
+| -------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
+| `AI_GATEWAY_ID`      | optional (set by `pnpm everyapp ai gateway on`)    | the AI Gateway's id, its name in the dashboard (`everyapp`); with `CLOUDFLARE_ACCOUNT_ID`, which `everyapp setup` set |
+| `AI_GATEWAY_API_KEY` | optional, only for an authenticated gateway         | an AI Gateway token with Run permission, sent as `cf-aig-authorization: Bearer <token>`                  |
+
+The Gateway sends the gateway token only to `gateway.ai.cloudflare.com`
+and, for Workers AI, `api.cloudflare.com` with `cf-aig-gateway-id`. Apps
+can't set `cf-aig-*` headers: the proxy strips them.
+
+## Costs and plans
+
+As of October 2026: AI Gateway is included with a Cloudflare account on
+every plan, with logs kept per plan (Workers Free: 100,000 logs per
+gateway; Paid: 10 million) and no per-request charge of its own; the
+provider's prices are unchanged (BYOK: the provider's key is the
+provider's bill). Unified Billing (paying providers through Cloudflare
+credits) is not used: the Gateway always sends the provider's key, and
+`cf-aig-no-wholesale` is not needed because a key on the request wins.
+
+## Only a person can
+
+- Decide to turn it on (it adds a hop and a log of every prompt's
+  metadata, never the prompt itself unless logging of payloads is turned
+  on in the dashboard).
+- Create a gateway token in the dashboard when they want an
+  authenticated gateway, and paste it into the terminal.
+- Turn on caching, rate limits or payload logging in the AI Gateway
+  dashboard: the Gateway sends no `cf-aig-*` options; the gateway's own
+  settings apply to every call.
+
+## Before you start
+
+1. `pnpm everyapp status --json`: `data.installed` and `data.claimed`
+   true; otherwise [gateway.md](gateway.md) first.
+2. `pnpm everyapp ai show --json`: `done.data.aiGateway.on` false means
+   it isn't on; `done.data.via` says `direct`. At least one model
+   provider configured ([ai.md](ai.md)) so there is something to front.
+3. The Cloudflare login the CLI uses can create AI Gateways in the
+   account (the account owner's login, or a token with AI Gateway Write).
+
+## Steps
+
+1. **Turn it on**: `pnpm everyapp ai gateway on --json`. The CLI finds or
+   creates an AI Gateway named `everyapp` in the Gateway's account
+   (`--id <name>` for another name, or one the person made already) and
+   sets `AI_GATEWAY_ID` on the Gateway. `done.data` is `{ id, url,
+   created }`. From the Gateway's next request every slugged provider
+   call goes through it.
+2. **Authenticated gateway (optional).** In the dashboard, AI → AI
+   Gateway → the gateway → Settings → Authenticated Gateway: on; create
+   an AI Gateway token (Run permission). Then from the person's
+   terminal: `pnpm everyapp secret set AI_GATEWAY_API_KEY` (the value by
+   pipe or prompt, never on the command line). Without the token on an
+   authenticated gateway every model call answers 401 from AI Gateway.
+3. Nothing else: no app changes, no key moves.
+
+## Verify
+
+1. `pnpm everyapp ai show --json`: `done.data.aiGateway` is `{ on: true,
+   id: "everyapp" }` and `done.data.via` is `ai-gateway`.
+2. Make one model call in an app (ask Agentic Inbox's agent something),
+   then open the dashboard: AI → AI Gateway → `everyapp` → Logs shows
+   the request with the provider's name.
+3. Manage workspace → Usage still counts the call under its provider:
+   AI Gateway adds a hop, not a provider.
+
+## If it fails
+
+- `ai gateway on` fails with a Cloudflare error: the login can't create
+  AI Gateways (a scoped token without AI Gateway Write); use the
+  account owner's login, or make the gateway in the dashboard and run
+  `ai gateway on --id <its name>`.
+- A model call answers 401 after turning it on: the gateway is
+  authenticated and `AI_GATEWAY_API_KEY` isn't set (step 2) or is wrong
+  (rotate it).
+- A model call answers 404 or 400 from `gateway.ai.cloudflare.com`: a
+  provider path AI Gateway doesn't serve the way the catalog recorded
+  it (the entry's `aig` block; `landing-page/content/agent/ai.md` lists
+  each). `pnpm everyapp ai gateway off` sends everything direct again
+  while it is looked at.
+- Calls work but don't appear in the dashboard: the provider has no
+  slug (Gemini, Cohere) and went direct.
+
+## Rerun, rotate, remove
+
+- `ai gateway on` again is safe: it finds the existing gateway and
+  rewrites the same id.
+- Rotate the gateway token in the dashboard, then `pnpm everyapp secret
+  set AI_GATEWAY_API_KEY` again.
+- `pnpm everyapp ai gateway off` unsets `AI_GATEWAY_ID`: every call goes
+  direct from the next request; the AI Gateway resource and its logs
+  stay in the account (delete it in the dashboard). `pnpm everyapp secret
+  unset AI_GATEWAY_API_KEY` removes the token.
+
+## Sources
+
+- https://developers.cloudflare.com/ai-gateway/ (overview; provider
+  pages under usage/providers/; authentication under
+  configuration/authentication/; the header glossary), read 2026-10-25.
+- https://everyapp.com/docs/agent/ai (in the checkout
+  `landing-page/content/agent/ai.md`): how each provider is fronted.

package/skills/everyapp/setup/ai.md

@@ -0,0 +1,139 @@
+# The default model provider
+
+An app that says `ai: { chat: true }` in its manifest (Agentic Inbox,
+OpenCRM's research agent) takes whichever chat model the Gateway's
+operator made the default, through `/api/ai/default/…`; it never names a
+provider. One key, set once, makes every such app work. This file sets
+that one key and, when the person wants a particular provider or model,
+the choice. At the end the person has one model provider's key on the
+Gateway, `pnpm everyapp ai show` saying what the default resolves to,
+and every app that needs "a chat model" open.
+
+## Settings
+
+| NAME                                                     | Required or optional                         | What it holds                                                                                              |
+| -------------------------------------------------------- | -------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
+| one provider's key (`OPENROUTER_API_KEY` first in the order) | required by every app whose manifest says `ai.chat` | the provider's key as its file says ([openrouter.md](openrouter.md), [workers-ai.md](workers-ai.md), [openai.md](openai.md), or [providers.md](providers.md) under `anthropic`, `groq`, `mistral`, `gemini`) |
+| the choice (`pnpm everyapp ai default <provider>[/<model>]`) | optional                                     | which provider (and model) the default is; without it the order decides                                     |
+
+The order the Gateway resolves the default in, the first whose settings
+are set: `openrouter` (one key, many models, the price in every answer),
+`workers-ai` (no provider account: the Gateway's own Cloudflare token;
+weaker models), `openai`, `anthropic`, `groq`, `mistral`, `gemini`. The
+operator's choice wins over the order. Cloudflare AI Gateway is never
+the default: it fronts whichever provider resolves
+([ai-gateway.md](ai-gateway.md)).
+
+## Costs and plans
+
+The provider's: OpenRouter is prepaid in USD at the providers' own
+prices ([openrouter.md](openrouter.md)); Workers AI bills the Cloudflare
+account per token ([workers-ai.md](workers-ai.md)); the others each have
+a plan of their own, named in their section of
+[providers.md](providers.md). The model the Gateway fills in when an app
+names none is a cheap capable one per provider (OpenRouter
+`anthropic/claude-haiku-5.5`, Workers AI
+`@cf/meta/llama-4-scout-17b-16e-instruct`, OpenAI `gpt-6-luna`, Groq
+`openai/gpt-oss-20b`, Mistral `mistral-small-latest`, Gemini
+`gemini-3.1-flash-lite`); `pnpm everyapp ai default <provider>/<model>`
+picks another. Usage by provider and model is on Manage workspace →
+Usage and in `pnpm everyapp workspace usage --json` (`byModel`).
+
+## Only a person can
+
+- Open an account with the provider and buy credits or add a card.
+- Create the key there and paste it into the terminal (the value never
+  goes through the chat or the command line).
+- Decide the provider and model when the shipped order isn't what they
+  want (a model they trust, a region, a budget).
+
+## Before you start
+
+1. `pnpm everyapp status --json`: `data.installed` and `data.claimed`
+   true; otherwise [gateway.md](gateway.md) first.
+2. Whether this file applies: an app in `data.apps[]` whose `setup.unmet`
+   has a setting with `kind: "ai-default"` (label "A chat model (…)"),
+   or whose `setup.settings` lists one. Its `names` is the key the order
+   asks for first and its `hint` names the alternatives. No such app:
+   nothing to do here; an app that pins a provider is that provider's
+   file.
+3. `pnpm everyapp ai show --json`: `done.data.configured` false means no
+   provider is set yet; `done.data.provider` and `done.data.settings`
+   say which key the default would use; `done.data.candidates[]` lists
+   every provider with `configured`.
+
+## Steps
+
+1. **Pick the provider with the person.** Default to OpenRouter unless
+   they say otherwise: it is one key for every model and the only one
+   whose spend the Gateway counts in dollars. Workers AI when they want
+   no provider account at all. A single vendor when they already have a
+   key there.
+2. **Set that provider's key**, by its own file: [openrouter.md](openrouter.md)
+   (`OPENROUTER_API_KEY`), [workers-ai.md](workers-ai.md)
+   (`WORKERS_AI_API_TOKEN`), [openai.md](openai.md) (`OPENAI_API_KEY`),
+   or the provider's section of [providers.md](providers.md)
+   (`ANTHROPIC_API_KEY`, `GROQ_API_KEY`, `MISTRAL_API_KEY`,
+   `GEMINI_API_KEY`). Each ends with `pnpm everyapp secret set <NAME>`,
+   the value from the person's terminal, or `pnpm everyapp configure
+   <app id>`, which asks for exactly the one key the app's `ai-default`
+   setting names.
+3. **Store the choice when it isn't the order's.** The first configured
+   provider of the order is the default by itself; nothing to store when
+   it is OpenRouter and the person is happy with its model. Otherwise:
+   `pnpm everyapp ai default <provider>` (`groq`), or with a model,
+   `pnpm everyapp ai default openrouter/anthropic/claude-sonnet-5.5`
+   (the provider id up to the first slash, the model after it). `pnpm
+   everyapp ai default off` clears it. Each change queues the
+   `ai.default_changed` event.
+4. **Optionally put AI Gateway in front**: [ai-gateway.md](ai-gateway.md)
+   (`pnpm everyapp ai gateway on`), for logs, caching and limits on
+   every model call; it changes no app and no key.
+
+## Verify
+
+1. `pnpm everyapp ai show --json`: `done.data.configured` true,
+   `done.data.provider` the one the person picked (or the order's
+   first), `done.data.model` the model that will be filled in,
+   `done.data.via` `ai-gateway` once the gateway is on, else `direct`.
+2. `pnpm everyapp status --json`: every app that said `ai.chat` has
+   `setup.ready` true and no `ai-default` setting in `setup.unmet`.
+3. In the app: a chat answer arrives (Agentic Inbox: open a thread and
+   ask the agent; OpenCRM: run research on a company). Manage workspace
+   → Usage → By provider shows the provider and, under it, the model.
+
+## If it fails
+
+- `ai_default_not_configured` in an app's error (503): no provider's
+  key is set, or the chosen one's isn't. The message names the key;
+  step 2. `pnpm everyapp ai show` says the same with `configured: false`.
+- `AI_DEFAULT_INVALID` from `ai default`: the id isn't a provider the
+  Gateway knows, is an API provider (Stripe), has no OpenAI-shaped chat
+  route (Cohere: an app pins it under `providers`), or is `ai-gateway`
+  (turn it on with `ai gateway on` and pick a model provider). The
+  message names the candidates.
+- `ai_route_not_allowed` on the default route: the app called something
+  other than chat completions or embeddings; it lists the provider under
+  `providers` for that.
+- `model_not_allowed` never comes from the default route; an app seeing
+  it pinned a provider and limited `ai.models`.
+- A provider's own error (401, 429, a model name it doesn't serve): the
+  provider's file, "If it fails".
+
+## Rerun, rotate, remove
+
+- Rerunning any step is safe: `ai default` overwrites the choice, a key
+  set again replaces the old one on the next request.
+- Rotate a key as its provider's file says; the default resolves to the
+  same provider.
+- Remove the choice with `pnpm everyapp ai default off`; remove a key
+  with `pnpm everyapp secret unset <NAME>`, after which the order moves
+  to the next configured provider, or apps that need the default show
+  "Needs setup" again.
+
+## Sources
+
+- https://everyapp.com/docs/agent/ai (in the checkout
+  `landing-page/content/agent/ai.md`): the route, the order, the
+  commands and their `--json`, the event.
+- `packages/sdk/src/internal/aiDefault.ts`: the resolution rule.

package/skills/everyapp/setup/context.md

@@ -54,12 +54,12 @@ As of October 2026 (context.dev/pricing and docs.context.dev/account):
 2. **Person:** Sign up, or sign in. Page: https://www.context.dev/signup. Type their email in **Email** and click **Continue** (an email sign-up sets a password and asks them to verify the address by email), or pick Google or GitHub under "or continue with" (no verification step). Continuing accepts the Terms of Service and Privacy Policy. An existing account signs in from "Already have an account? Sign in" (https://context.dev/login). It worked when the dashboard opens.
 
    Alternative, only with their say-so (it registers a key in their name): Context.dev's agent flow (context.dev/auth.md, read today, not run). Everything in one shell, with `EMAIL` set to the address they gave (an existing account's email, when they have one). Register:
-   `reg=$(jq -n --arg email "$EMAIL" '{type:"service_auth",login_hint:$email,api_key_name:"Every App Gateway",client_name:"everyapp setup"}' | curl -sS -X POST https://www.context.dev/agent/identity -H 'Content-Type: application/json' -d @-); printf '%s' "$reg" | jq '{claim, offer}'`
+   `reg=$(jq -n --arg email "$EMAIL" '{type:"service_auth",login_hint:$email,api_key_name:"EveryApp Gateway",client_name:"everyapp setup"}' | curl -sS -X POST https://www.context.dev/agent/identity -H 'Content-Type: application/json' -d @-); printf '%s' "$reg" | jq '{claim, offer}'`
    Show them `claim.verification_uri` and `claim.user_code` in full, and that both expire in `claim.expires_in` seconds (600: ten minutes). If the response has `offer`, say it includes 1,000 extra credits (deadline `offer.claim_by`); promise nothing otherwise. A 429 `rate_limit_exceeded` from the registration means stop, no retry: step 3 instead. They open the link, enter the 6-digit code, and sign up or sign in with that email (a password sign-up also verifies the address). Then poll every `claim.interval` seconds, for ten minutes at most, until the key arrives or an error ends it, and pipe the key straight in (README's "a command produced it"); `claim_token` is read from `$reg` in the same shell, never typed (it is short-lived and not the key):
    `CLAIM=$(printf '%s' "$reg" | jq -r .claim_token); INTERVAL=$(printf '%s' "$reg" | jq -r '.claim.interval // 5'); for i in $(seq 1 120); do r=$(curl -sS -X POST https://www.context.dev/oauth2/token -d "grant_type=urn:workos:agent-auth:grant-type:claim&claim_token=$CLAIM"); e=$(printf '%s' "$r" | jq -r '.error // empty'); case "$e" in '') break;; authorization_pending) ;; slow_down) sleep 10;; *) printf '%s' "$r" | jq '{error, error_description}'; break;; esac; sleep "$INTERVAL"; done; printf '%s' "$r" | jq -e .access_token >/dev/null && printf '%s' "$r" | jq -r .access_token | pnpm everyapp secret set CONTEXT_API_KEY --json`
    `authorization_pending` means they haven't finished (`email_verification_required`: the address isn't verified yet); `expired_token` means the ten minutes passed: register again, only with their agreement; `invalid_grant` means stop and show its `error_description`. When the loop ends without a key, nothing is set and the printed error says why (none printed: curl itself failed). Never print `$r`: the key is in it. This replaces steps 3 and 4: go to Verify (nobody but the Gateway holds the key now, so its smoke check is skipped; 1 and 3 there are the check).
 
-3. **Person:** Create the key. Page: https://context.dev/dashboard/api-keys. Create a new key with the page's button (its label isn't in the docs); if the dialog shows the key once, copy it before closing. Keep **Full access** (the default; it covers the Data APIs the apps use and the usage read the smoke check uses), or choose **Restricted** with Data APIs = Use and "Account logs, usage, and browser profiles" = Read. Name it "Every App Gateway" when the form asks (renaming later needs a paid plan). It worked when the key is listed on that page. A Free organization holds at most two keys: with two there already, delete one they no longer use (whether a disabled key still counts toward the two isn't in the docs), or use the agent flow above, which needs no button.
+3. **Person:** Create the key. Page: https://context.dev/dashboard/api-keys. Create a new key with the page's button (its label isn't in the docs); if the dialog shows the key once, copy it before closing. Keep **Full access** (the default; it covers the Data APIs the apps use and the usage read the smoke check uses), or choose **Restricted** with Data APIs = Use and "Account logs, usage, and browser profiles" = Read. Name it "EveryApp Gateway" when the form asks (renaming later needs a paid plan). It worked when the key is listed on that page. A Free organization holds at most two keys: with two there already, delete one they no longer use (whether a disabled key still counts toward the two isn't in the docs), or use the agent flow above, which needs no button.
 
 4. **Person, then You:** Put it on the Gateway. README's first way (the key is on a screen they are looking at): they open a second terminal in the `every-app` folder and run `pnpm everyapp configure crm` (or `pnpm everyapp configure openseo`; no `--json`: with it nothing prompts), which asks for this key among the app's other unset settings (for OpenSEO it is optional: Yes to `Set the N optional settings too?` (`Set the optional setting too?` for one), then `CONTEXT_API_KEY (Enter to skip)`; once an app is ready, its menu `Everything <app> needs is set. Change one?` lists it), or `pnpm everyapp secret set CONTEXT_API_KEY` for just this one. The prompt is hidden (`CONTEXT_API_KEY`, under lines saying what it is for and where it comes from; `secret set` asks `Value for CONTEXT_API_KEY`); they paste, press Enter, and see `Set CONTEXT_API_KEY on the Gateway` (configure then says `crm is ready.` or what the app still needs, and `Live now. No deploy needed.`; `secret set` ends `Live now on <gateway host>. No deploy needed.`). Nothing is exported afterwards, so offer the smoke check (Verify 2, 0 credits) in that same terminal: the hidden read (README's third way: `read -rs CONTEXT_API_KEY && export CONTEXT_API_KEY`, paste, Enter), Verify 2's curl, they tell you its last line (200) and `credits_remaining`, then `unset CONTEXT_API_KEY`; declined, the app (Verify 3) is the check. README's third way from the start, when they read it in hidden instead (never a typed `export …=`, which the shell history keeps; run the smoke check below first): `pnpm everyapp configure <app id> --from-env --json`, whose `done` event has `data.set` `["CONTEXT_API_KEY"]` and `data.changed.gateway.names`, or `pnpm everyapp secret set CONTEXT_API_KEY --from-env CONTEXT_API_KEY --json`, whose `done` event has `data.gateway.names` `["CONTEXT_API_KEY"]`; then `unset CONTEXT_API_KEY`. Never on a command line, never in the chat (a key seen in the chat gets rotated: step 3 again). Wait for "done".
 

package/skills/everyapp/setup/dataforseo.md

@@ -112,7 +112,7 @@ value is set.
    Confirm the email if asked: until it is confirmed the API answers 40104.
    When it worked, the dashboard at app.dataforseo.com opens and shows a $1
    balance. Already registered: sign in at https://app.dataforseo.com. Ran
-   elsewhere: an OpenSEO deployed outside Every App held the base64 form of
+   elsewhere: an OpenSEO deployed outside EveryApp held the base64 form of
    the same credential, which works unchanged here (step 4's note), and if
    that deployment whitelisted its server's IP on API Access, the list has
    to be emptied (step 2). Wait for "I'm in".
@@ -197,7 +197,7 @@ value is set.
    (`https://<gateway host>/?setup=openseo`) means a required setting is
    still unset: Verify 1 says which. OpenSEO shows one message for a
    missing key and a rejected one alike: "DataForSEO isn't set up on your
-   Every App gateway yet, or rejected the key it holds. An owner or admin
+   EveryApp gateway yet, or rejected the key it holds. An owner or admin
    sets it with pnpm everyapp secret set DATAFORSEO_API_KEY." Tell them apart with
    `pnpm everyapp secret list --json`: `DATAFORSEO_API_KEY` absent from
    `data.gateway.names` means step 4 did not land (behind the Gateway's
@@ -227,7 +227,7 @@ value is set.
 | `SECRET_SEVERAL_NAMES`                                                             | `--from-env` or a pipe with more than one name                                                                         | One name per call                                                                                                             |
 | `SECRET_EMPTY`                                                                     | The `--from-env` variable is empty or not exported in that shell                                                       | The hidden read (README's third way) in that same terminal first, then rerun                                                  |
 | A browser opening OpenSEO is sent to `https://<gateway host>/?setup=openseo`; any other request gets 503 with the body `{"error":"app_needs_setup","app":"openseo"}` | The Gateway's setup gate: a required setting of OpenSEO is still unset (this key or the OpenRouter one; Context is optional) | `data.app.setup.command`, `pnpm everyapp configure openseo` (step 4), then Verify 1                                  |
-| `integration_not_configured` (503, header `x-everyapp-error`)                      | The Gateway holds no `DATAFORSEO_API_KEY`; OpenSEO shows it as "DataForSEO isn't set up on your Every App gateway yet, or rejected the key it holds. An owner or admin sets it with pnpm everyapp secret set DATAFORSEO_API_KEY." (behind the setup gate the app doesn't open in this state) | Steps 4 and 5; check the name's spelling in `data.gateway.names`                                                 |
+| `integration_not_configured` (503, header `x-everyapp-error`)                      | The Gateway holds no `DATAFORSEO_API_KEY`; OpenSEO shows it as "DataForSEO isn't set up on your EveryApp gateway yet, or rejected the key it holds. An owner or admin sets it with pnpm everyapp secret set DATAFORSEO_API_KEY." (behind the setup gate the app doesn't open in this state) | Steps 4 and 5; check the name's spelling in `data.gateway.names`                                                 |
 | `capability_not_requested` (403)                                                   | The deployed manifest does not list `capabilities.dataforseo`                                                          | OpenSEO's does; a fork must add it to `everyapp.config.ts` and deploy again                                                   |
 | `integration_path_not_allowed` (403)                                               | The app called an account-wide path (`appendix/user_data`, `appendix/webhook_resend`, `tasks_ready`, `id_list`, `errors`) | By design: one key serves every app. Check balance and limits from the terminal (Verify 2)                                 |
 | `integration_method_not_allowed` (405)                                             | A method other than GET or POST                                                                                        | DataForSEO reads with GET and POST only                                                                                       |

package/skills/everyapp/setup/email.md

@@ -278,7 +278,7 @@ recipient address (20 on a hosted Gateway) and 5,000 a day per Gateway.
    is `false`).
 3. The provider alone, Cloudflare, with the person's yes (one counted
    email, unless `to` is a verified destination address):
-   `cf email-sending send --body '{"from":"noreply@<your domain>","to":"<address>","subject":"Every App test","text":"It works."}'`
+   `cf email-sending send --body '{"from":"noreply@<your domain>","to":"<address>","subject":"EveryApp test","text":"It works."}'`
    sends without the Gateway. It arriving means the provider is done and a
    failed invite is the Gateway's side (its settings; the logs below). A
    refusal is the REST API's numeric code (`10203` sending disabled,