Self-improving AI Employees for everyone
Python ai-agentsai-employeeai-employeesassistantautonomous-agentsco-employeescompanygrok-botinstinctloop-agentsmuseown-your-datapersonalself-hosted
docs: the AWS deploy provider and the awsAction node across the docs
trohitgbe811a908166
diff --git a/CLAUDE.md b/CLAUDE.mdindex a3e4e3bf..6568ef85 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -40,6 +40,7 @@ This is a React Flow-based workflow automation platform implementing n8n-inspire| **[GitHub Service](./docs-internal/github_service.md)** | GitHub CLI integration — `githubAction` (repo_clone / pr_create / pr_list / pr_merge / issue_create / issue_list + `custom` passthrough; AI tool `github`). **Strict Stripe pattern: the gh CLI owns its own auth** — no token stored/injected by OpenCompany, no auth pre-flight (gh's own error surfaces), marker OAuth row for the modal badge, fieldless catalogue entry. Login = spawned `gh auth login --hostname github.com --git-protocol https --web` — source-verified: headless takes the `isInteractive=false` branch (no Press-Enter), prints one-time code + `github.com/login/device` URL on stderr; the modal shows the code via the generic `verificationCode` plumbing (`useCredentialPanel` → `OAuthConnect`). `login_env()` strips `GH_TOKEN`/`GITHUB_TOKEN` (login aborts otherwise). Success gate = `gh auth status` exit 0, then best-effort **`gh auth setup-git`** (official bridge — the future git node needs zero auth code). gh binary: **project-local, pooch-driven** (temporal `_install.py` idiom) — pinned release under `package_dir("gh")`, system gh never consulted (auth state still shared: gh config paths are user-level). Palette group `vcs`. || **[Cloudflare Service](./docs-internal/cloudflare_service.md)** | Cloudflare CLI integration — `cloudflareAction` (whoami / `search_commands` (`cf cli search`) / zones_list / DNS records list-create-edit-delete / `graphql_query` / `custom` passthrough; AI tool `cloudflare`) wrapping the official `cf` CLI (npm `[email protected]`, open beta — "the next version of Wrangler"). **Pin enforced, not just installed once**: `ensure_cf_cli` compares `core.js_runtime.installed_version("cf")` with the pin and re-runs `bun add` on a mismatch (clearing the login marker, since a new version may not see the old login). **Login = gh's device-flow shape**: `cf auth login --force --device --no-browser` prints a URL + one-time code on stderr that the handler relays to the modal (works from any machine; the old fixed-port-8877 loopback flow is `--no-device` only) — single flight (a repeat click returns the same code), install before any login (no invisible codes), never-kill-the-shim (killing bun's `cf.exe` launcher orphans the child), success gate = `cf auth whoami` JSON (`authenticated: true` — cf exits 0 in BOTH auth states). **cf contract traps**: destructive commands without `--force` print "Aborted." and **exit 0** (delete always passes it; `custom` turns it into an error); no `--account-id` flag on most commands (account = `CLOUDFLARE_ACCOUNT_ID`, from the `account_id` param — several accounts fail non-interactively without it); cf resolves a domain `--zone` only in the first page of the selected account, so the node resolves domains itself via `zones list --name`; no output-format flag (unknown flags rejected); cf reads `.env` files from its working directory and fails under bun on a `cloudflare.config.ts` found above it, so typed ops run from a neutral `<DATA_DIR>/cloudflare` (`custom` from the workspace) with `CF_DELEGATION=1` (otherwise bun lets cf hand off to another cached cf copy) and telemetry off. The optional `apiKey` field (an API token) rides `CLOUDFLARE_API_TOKEN` and beats the login; cf does NOT accept a Global API Key, so a `cfk_` key (with `cloudflare_email`) serves only `graphql_query`, which POSTs the official `client/v4/graphql` endpoint directly (no cf GraphQL command; the cf login's token never leaves the CLI) — needs `Account > Account Analytics > Read`. System cf never consulted. Palette group `deployment`. || **[Google Cloud Service](./docs-internal/gcloud_service.md)** | Google Cloud CLI integration — `gcloudAction` (auth/config/projects + set_project / Compute Engine instances list-start-stop-describe / Cloud Run deploy-list-describe / Cloud Storage ls-cp-rm / `custom` passthrough; AI tool `gcloud`) wrapping the official gcloud CLI (pinned versioned archive via pooch into `package_dir("gcloud")` — NOT npm; the Windows bundled-python zip keeps the legacy `google-cloud-sdk-` filename prefix, the `-cli-` spelling 404s, locked by test). CLI-opens-the-browser login variant (the pre-1.0 Cloudflare flow; gcloud picks a random loopback port — no fixed-port hazard) + the gh marker-token pattern; success gate = `gcloud auth list --filter=status:ACTIVE --format=json` non-empty (exit codes never trusted). **Config isolation divergence from gh**: every invocation pins `CLOUDSDK_CONFIG=<DATA_DIR>/gcloud/`, so terminal logins against the operator's global gcloud are deliberately NOT visible to the node. ADC note: node login mints gcloud USER creds only (CLI commands never read ADC); client-library code gets ADC via the `custom` op `auth application-default login` (lands isolated in the pinned dir). Cold install ~100 MB → login answers `pending: True` within the 22 s WS budget. Provider id `gcloud` is orthogonal to the Workspace `google` OAuth2 provider. Palette group `deployment`. |+| **[AWS Service](./docs-internal/aws_service.md)** | AWS integration over the official SDK — `awsAction` (whoami / EC2 instances list-describe-start-stop / S3 list-upload-download-delete / `call` for any operation of any AWS service by its boto3 method or API name / `list_operations` from the SDK's bundled models, with no credentials or network; AI tool `aws_action`; `awsServices` / `awsOperations` dropdown loaders). **The SDK, not the AWS CLI**: CLI v2 ships as an MSI / `.pkg` with no portable archive to pin on Windows or macOS, and its browser login (`aws login`) cannot run on a hosted server. `boto3` is a main server dependency imported only inside `nodes/aws/_sdk.py` (a clean-interpreter test locks that importing the plugin never loads it). Auth = an IAM access key pair in the encrypted store: `AwsCredential` (`ApiKeyCredential`, id `aws`) keeps the secret under the provider id plus `extra_fields` `aws_access_key_id` / `aws_region` (the Cloudflare companion-field pattern); `resolve()` also requires the ID, and the modal probe signs `sts:GetCallerIdentity`, so the ID must be saved before the secret validates. **No ambient credentials**: the pair is passed to every client explicitly, so environment variables, `~/.aws` and an instance profile on the server never authenticate a node. One cached, credential-free botocore session; client creation runs under a lock (botocore sessions are not thread-safe; ~5 ms per client once a service's model is loaded) and calls run in `asyncio.to_thread` with 10 s / 60 s timeouts and `standard` retries. `call` resolves the operation (with `difflib` suggestions) before any credential use and returns one page; responses are shaped the way the CLI prints them (no `ResponseMetadata`, ISO timestamps, base64 blobs, streaming bodies inline up to 1 MB). S3 transfers go through `coerce_file_param` / `write_media` and stop at `MEDIA_MAX_READ_BYTES` (25 MB); AWS errors become `NodeUserError` with code, message, request id and a hint. Tests run real botocore clients under `Stubber`. Unrelated to `company deploy --provider aws`, which drives the operator's own aws CLI. Palette group `deployment`. || **[TikHub Service](./docs-internal/tikhub_service.md)** | TikHub social-scraping integration — `tikhubAction` (`call` / `list_endpoints` / `fetch_url` / `account`; AI tool `tikhub_action`; palette group `scraper`, visible in normal mode) over the **official `tikhub` SDK** (`tikhub>=2.1.2,<3`, auto-generated from TikHub's `openapi.json`; ~1,100 methods across TikTok / Douyin / Instagram / YouTube / Twitter / Xiaohongshu / Bilibili / Kuaishou / Weibo / Reddit / Threads / LinkedIn / Zhihu). **The node is the "flattened CLI"**: one `call` op addressed by the SDK's own `resource.method` id (`douyin_web.fetch_one_video`, also `resource/method` or the `/api/v1/...` path) with **reflective `getattr` dispatch** and `inspect.signature(...).bind` pre-flight so unknown kwargs fail before any paid request; **nothing is vendored** — `endpoint_index()` introspects the installed SDK at runtime (resources = `AsyncResource` instance attrs, params = keyword-only signature, route from the docstring's ``GET /api/v1/...`` literal), cached per process, and feeds both `list_endpoints` and the `platform`-dependent dynamic `endpoint` dropdown (`tikhubEndpoints` loader; `all` returns no options, the LLM path stays free text). `tikhub` is imported lazily inside `_sdk.py` only (plugin imports with `sys.modules["tikhub"] = None`). `TikHubCredential` = bearer `ApiKeyCredential` with a declarative httpx probe against `/api/v1/tikhub/user/get_user_info` (never the unauthenticated health route); runtime key via `TikHubCredential.resolve` so a missing key yields the structured `PermissionDeniedError` envelope. SDK `TikHubError` subclasses map to `NodeUserError` (401 key rejected -> Credentials; 403 scope-or-balance -> `account`; 429 + `retry_after`; 400/422 with TikHub `detail`; 404; 5xx upstream after the SDK's own retries) and HTTP-200-with-in-body-`code >= 400` is raised too. **Flat `$0.001`/request tracking** (`pricing.json: api.tikhub` + `operation_map.tikhub`, `track_tikhub_usage` -> `api_usage_metrics`, only after a 2xx, never for `list_endpoints`). SDK drift is guarded by two contract tests (every `PLATFORMS` value matches a live resource; every backticked id in the skill resolves). || **[Discord Service](./docs-internal/discord_service.md)** | Discord bot integration — `discordSend` / `discordAction` (AI tools) + `discordReceive` / `discordInteraction` triggers. **discord.py owns the gateway, REST is plugin-owned** (nodes must work with no gateway, `discordAction` needs arbitrary routes, and the invalid-request guard is process-wide across accounts). **Multi-account rides the existing `session_id` credential column** — `_accounts.py` is the only file that knows `account_id -> "discord:<app_id>"`, `"default"` is the row the modal already writes, and `credential_customer_id` is deliberately NOT used (it is per-execution-context tenancy, so two nodes in one workflow could never target different bots). **`account_id` is in `server_controlled_fields`, which the framework enforces on every tool path** (`BaseNode.execute_as_tool` strips it in process, `NodeExecutor` restores the saved value on Temporal); `AccountScopedNode` strips it again as defence in depth, and only runs in process, since the per-type activity calls `execute` for an ActionNode. Attachments are metadata on the trigger and downloaded by `discordAction` (deployed triggers never run their node body). Interaction tokens never leave the server — the trigger emits an opaque ref. The interactions endpoint is a plugin router, not a `WebhookSource`: Discord's validation probe requires **401** (the generic intake raises 400) and the 3-second ACK deadline precludes awaiting `emit`. Rate limiting is reactive; the invalid-request guard is **process-global** because Cloudflare bans the source IP, not the token. || **[Sarvam AI Service](./docs-internal/sarvam_service.md)** | Sarvam AI (Indic-first). **`nodes/sarvam/` no longer exists** — every capability it served is now a *provider* inside an abstracted node: speech in `nodes/speech/`, and translate / transliterate / detect-language in `nodes/translate/`. What remains Sarvam-specific is `sarvamChatModel` (an **OpenAI-compat provider**: one `_COMPAT_PROVIDERS` entry + a JSON block, no provider subclass) under `nodes/model/`. **One stored key spans two auth styles** — the chat route takes `Authorization: Bearer` (what the openai SDK sends) while every other endpoint takes only `api-subscription-key`, so `SarvamCredential` declares the native header and every surface shares it. Introduces the generic **`supports_model_listing: false`** flag: Sarvam ships no `/v1/models` route, and unhandled that 404 becomes a `NodeUserError` that `AIService.fetch_models` re-raises *before* its curated fallback, breaking key validation and the model dropdown — so `OpenAIProvider.fetch_models` serves the curated list and probes with a one-token completion instead (defaults `true`; every other provider is untouched, locked by test). Also added generic **`Connection.request(files=)`** multipart support. |@@ -539,7 +540,7 @@ class CacheEntry(SQLModel, table=True):## Codebase Summary- **Hybrid architecture**: Python (FastAPI + Pydantic plugins) + React/TypeScript frontend + a bun-hosted Express sidecar for JS/TS code execution (bun is the only JavaScript runtime and package manager anything shipped needs; Node is dev/CI-only).-- **Backend NodeSpec is the single source of truth.** Plugins live in [`server/nodes/<group>/<plugin>/__init__.py`](./server/nodes/) (or a single `.py` inside a domain folder) and auto-register via `BaseNode.__init_subclass__`. Authoritative node count is `len(services.node_registry.NODE_METADATA)` after `import nodes`; never a file glob (`**/__init__.py` also matches group packages, and excluding `__init__.py` drops most plugins). Folders cover agent / model / android / google / microsoft / whatsapp / whatsapp_business / twitter / telegram / discord / social / email / search / scraper / document / code / filesystem / proxy / location / chat / text / scheduler / trigger / tool / utility / workflow / skill / context / vision / browser / speech / translate / stripe / vercel / github / cloudflare / gcloud.+- **Backend NodeSpec is the single source of truth.** Plugins live in [`server/nodes/<group>/<plugin>/__init__.py`](./server/nodes/) (or a single `.py` inside a domain folder) and auto-register via `BaseNode.__init_subclass__`. Authoritative node count is `len(services.node_registry.NODE_METADATA)` after `import nodes`; never a file glob (`**/__init__.py` also matches group packages, and excluding `__init__.py` drops most plugins). Folders cover agent / model / android / google / microsoft / whatsapp / whatsapp_business / twitter / telegram / discord / social / email / search / scraper / document / code / filesystem / proxy / location / chat / text / scheduler / trigger / tool / utility / workflow / skill / context / vision / browser / speech / translate / stripe / vercel / github / cloudflare / gcloud / aws.- **WebSocket-first frontend-backend communication.** Authoritative handler count is the size of the `MESSAGE_HANDLERS` dict in [`server/routers/websocket.py`](./server/routers/websocket.py) plus plugin-registered handlers via `services.ws_handler_registry`. Don't hand-maintain the count in this doc — it drifts on every plugin add.- **Plugin-first architecture (Wave 11).** One plugin = one authoring location (a folder rooted at `__init__.py`, or a single `.py` inside a domain folder). `services/handlers/` shrank from 12.8K → 1.1K LOC across 16 → 4 files. Live invariant total via `pytest --collect-only`.@@ -669,7 +670,7 @@ The project uses WebSocket as the primary communication method between frontend> The authoritative, per-node reference is the backend plugin registry plus the per-node "logic-flow" cards under [docs-internal/node-logic-flows/](./docs-internal/node-logic-flows/) (one card per node, grouped by category, with handles / params / outputs / side-effects / edge-cases). Live node list = the plugin registry (one folder per node under `server/nodes/<group>/`; read the total from `len(services.node_registry.NODE_METADATA)` rather than hardcoding it here — a bare `__init__.py` glob overcounts by also matching the group packages). Do NOT maintain a per-node catalogue here — it drifts on every plugin add.-Node groups (palette categories) are registered in [`server/nodes/groups.py`](./server/nodes/groups.py), 34 keys at time of writing: agent, ai, android, api, browser, chat, code, deployment, discord, document, email, filesystem, google, language, location, memory, microsoft, model, payments, proxy, scheduler, scraper, search, service, skill, social, text, tool, trigger, utility, vcs, whatsapp, whatsapp_business, workflow. Folder names are not palette keys: telegram and twitter nodes declare `social`, stripe declares `payments`, vercel / cloudflare / gcloud declare `deployment`, github declares `vcs`, the `context` node declares `memory`, `vision` declares `tool`, and speech and translate declare `language` (provider-abstracted `textToSpeech` / `speechToText` and `translateText` / `transliterateText` / `detectLanguage`; `nodes/sarvam/` was retired into them, and only `sarvamChatModel` under `nodes/model/` remains vendor-named). See [docs-internal/node-logic-flows/](./docs-internal/node-logic-flows/) for the card index.+Node groups (palette categories) are registered in [`server/nodes/groups.py`](./server/nodes/groups.py), 34 keys at time of writing: agent, ai, android, api, browser, chat, code, deployment, discord, document, email, filesystem, google, language, location, memory, microsoft, model, payments, proxy, scheduler, scraper, search, service, skill, social, text, tool, trigger, utility, vcs, whatsapp, whatsapp_business, workflow. Folder names are not palette keys: telegram and twitter nodes declare `social`, stripe declares `payments`, vercel / cloudflare / gcloud / aws declare `deployment`, github declares `vcs`, the `context` node declares `memory`, `vision` declares `tool`, and speech and translate declare `language` (provider-abstracted `textToSpeech` / `speechToText` and `translateText` / `transliterateText` / `detectLanguage`; `nodes/sarvam/` was retired into them, and only `sarvamChatModel` under `nodes/model/` remains vendor-named). See [docs-internal/node-logic-flows/](./docs-internal/node-logic-flows/) for the card index.## Backend Services@@ -1198,31 +1199,46 @@ bun run build## Production Deployment### Self-Deploy CLI (`company deploy`) — current path-One command provisions a login-gated OpenCompany VM on a cloud provider. Two stages: the-operator's **cloud CLI** (gcloud; the AWS Terraform module in `cli/terraform/aws/` is complete and validated on t3.micro, but the `providers/aws.py` CLI adapter is still a stub that exits 1) handles auth + project/region/zone resolution +-ADC verification + API enablement, then **Terraform** (`cli/terraform/gcp/`) owns all resources —-VM (new deployments use the `opencompany` resource id), firewall, artifact bucket (local `bun pm pack --quiet` source), service-account, and a cloud-init startup script that installs bun (`BUN_INSTALL=/usr/local`, official installer) + uv, `bun add -g`s the package,+One command provisions a login-gated OpenCompany VM on GCP or AWS. Two stages: the+operator's **cloud CLI** (`cli/commands/deploy/providers/gcp.py` / `aws.py`) handles auth and context: gcloud does+project/region/zone resolution + ADC verification + API enablement; the aws CLI checks the signed-in identity, resolves+the region (`--region`, `AWS_REGION`, `AWS_DEFAULT_REGION`, the CLI's configured region, then `us-east-1`), hands its+credentials to Terraform through `aws configure export-credentials` (so `aws login` sessions work) and refuses a region+without a default VPC. Then **Terraform** (`cli/terraform/<provider>/`, one shared variable set, so `up.py` writes one+tfvars shape) owns all resources. GCP: VM, firewall, artifact bucket (local `bun pm pack --quiet` source), service+account, and a GCE startup script (re-run on every boot) that installs bun (`BUN_INSTALL=/usr/local`, official installer) + uv, `bun add -g`s the package,provisions the Python side with `company provision` (a global add runs no lifecycle scripts; the shim knows its own package root, since where bun keeps global packages varies by platform) and runs-`company serve` under systemd — no Node, no npm on the VM. The AWS template instead delegates to `install.sh` as the login user and-points systemd at `$APP_HOME/.bun/bin/company` with a PATH `Environment=` line. Login gate = built-in auth (`VITE_AUTH_ENABLED=true`,+`company serve` under systemd — no Node, no npm on the VM. AWS: a security group and an EC2 instance whose cloud-init+script (first boot only) runs `install.sh` as the login user with a published release (`--source release` only) and+points systemd at `$APP_HOME/.bun/bin/company` with a PATH `Environment=` line; the module ignores `ami` and `user_data`+changes, so a later apply never replaces a running instance and deletes its disk. Each adapter names its default+`--machine-type` (`e2-standard-2` / `t3.micro`) and the `--source` values its module supports. Login gate = built-in auth (`VITE_AUTH_ENABLED=true`,`AUTH_MODE=single`) with the owner credential generated at deploy time and seeded on first boot.`build_app_env` (`cli/commands/deploy/_secrets.py`) also sets `DEPLOYMENT_MODE=cloud` on-deployed VMs and mints fresh `JWT_SECRET_KEY` / `SECRET_KEY` / `API_KEY_ENCRYPTION_KEY` per deploy.+deployed VMs and mints fresh `JWT_SECRET_KEY` / `SECRET_KEY` / `API_KEY_ENCRYPTION_KEY` per deploy; Temporal, the event+framework and `HOST` keep their `.env.template` values (Temporal on, as in the Docker image). A VM that installs 0.2.0 or+0.2.1 stops with "Project not built" (errors.md #25, fixed after 0.2.1), which is every AWS VM until the next release.++`--name` (default `opencompany`; 6-30 lowercase letters, digits and hyphens, because it is also a cloud resource id)+names a deployment: its state folder and its resource id. One machine drives one VM per name, and a name stays with+the provider that created it.```bashcompany deploy up --provider gcp --owner-email [email protected] # provision + install + print URL/creds-company deploy status # URL + /health-company deploy destroy # terraform destroy + clear state+company deploy up --provider aws --name acme-corp --owner-email [email protected]+company deploy status [--name acme-corp] # URL + /health+company deploy destroy [--name acme-corp] # terraform destroy + clear state```Key files: `cli/commands/serve.py` (single-port runtime: one supervised uvicorn process fronting API + WS + built SPA;the bun-hosted JS code-exec sidecar, WhatsApp and Temporal are backend-spawned on demand), `cli/commands/deploy/` (verbs, secrets, Terraform driver, provider CLI adapters),-`cli/terraform/gcp/` (HCL module + `startup.sh.tftpl`). Deployment state lives at-`<user-data>/deploy/opencompany/` (preserved by `company clean` — see `_OPENCOMPANY_KEEP`); only-`company deploy destroy` removes it. The deploy code is fully delinked from `company build` /+`cli/terraform/gcp/` and `cli/terraform/aws/` (HCL modules + `startup.sh.tftpl`). `prepare_workdir` copies only a+module's `*.tf` / `*.tftpl` files, so Terraform state or tfvars left in a module folder never reach a deployment.+Deployment state lives at `<DATA_DIR>/deploy/<name>/` (`~/.opencompany/deploy/opencompany/` by default); only+`company deploy destroy` removes it (`company clean` keeps a repo-local `.opencompany/deploy`, see `_OPENCOMPANY_KEEP`).+The deploy code is fully delinked from `company build` /`company clean` (lazy verb stubs in `cli/cli.py`; nothing in the build pipeline imports it).-For upgrades, `_state.py` also discovers pre-rebrand `deploy/machinaos/` state+For upgrades, `_state.py` also discovers pre-rebrand `deploy/machinaos/` state for the default nameunder the configured root, `~/.machina`, or `<repo>/.machina`. Such deploymentsretain their durable `machinaos` cloud/systemd id; changing it would causeTerraform replacement or strand live state. Fresh deployments use `opencompany`.diff --git a/docs-internal/node-logic-flows/cli_integrations/cloudflareAction.md b/docs-internal/node-logic-flows/cli_integrations/cloudflareAction.mdindex 5fb9eab0..91138dcc 100644--- a/docs-internal/node-logic-flows/cli_integrations/cloudflareAction.md+++ b/docs-internal/node-logic-flows/cli_integrations/cloudflareAction.md@@ -243,4 +243,5 @@ flowchart TD- **Skills using this as a tool**: [cloudflare-skill](../../../server/skills/cloudflare/cloudflare-skill/SKILL.md)- **Siblings**: [`gcloudAction`](./gcloudAction.md), [`vercelAction`](./vercelAction.md), [`githubAction`](./githubAction.md) - the same CLI-managed-auth pattern+- **Also in the deployment group**: [`awsAction`](./awsAction.md) (boto3 SDK with an IAM access key, no CLI)- **Architecture docs**: [Cloudflare Service](../../cloudflare_service.md), [Plugin System](../../plugin_system.md)diff --git a/docs-internal/node-logic-flows/cli_integrations/gcloudAction.md b/docs-internal/node-logic-flows/cli_integrations/gcloudAction.mdindex 5b3be241..de011d28 100644--- a/docs-internal/node-logic-flows/cli_integrations/gcloudAction.md+++ b/docs-internal/node-logic-flows/cli_integrations/gcloudAction.md@@ -191,4 +191,5 @@ flowchart TD- **Skills using this as a tool**: [gcloud-skill](../../../server/skills/gcloud/gcloud-skill/SKILL.md)- **Siblings**: [`cloudflareAction`](./cloudflareAction.md), [`githubAction`](./githubAction.md), [`vercelAction`](./vercelAction.md)+- **Also in the deployment group**: [`awsAction`](./awsAction.md) (boto3 SDK with an IAM access key, no CLI)- **Architecture docs**: [Google Cloud Service](../../gcloud_service.md)diff --git a/docs-internal/node-logic-flows/stripe/stripeReceive.md b/docs-internal/node-logic-flows/stripe/stripeReceive.mdindex 4a839bed..a9f27a08 100644--- a/docs-internal/node-logic-flows/stripe/stripeReceive.md+++ b/docs-internal/node-logic-flows/stripe/stripeReceive.md@@ -97,7 +97,7 @@ flowchart TDin-process event waiter, which serves a canvas Run and the deploy pathwithout Temporal: the deployment manager arms the in-process collectorinstead of a Temporal listener when no Temporal client is connected- (deployed VMs start with `TEMPORAL_ENABLED=false`) or the event framework+ (`TEMPORAL_ENABLED=false`, or Temporal not up yet) or the event frameworkis off. `StripeWebhookSource.handle` then calls`emit_stripe_event`, which reaches deployed listeners on Temporal. Theenvelope carries no `workflow_id`, so every deployment with the triggerdiff --git a/docs-internal/node_creation.md b/docs-internal/node_creation.mdindex 0ce616dd..9e4b2bef 100644--- a/docs-internal/node_creation.md+++ b/docs-internal/node_creation.md@@ -182,9 +182,9 @@ It is a single folder `server/nodes/<group>/<name>/` whose`credentials` / `task_queue` / `usable_as_tool` / `Params` / `Output`plus one `@Operation` method. That's the entire node (the folder alsoholds `icon.svg` / `meta.json`, which is why the folder is the canonical-shape; a bare `.py` inside a domain folder still works and 23 shipped+shape; a bare `.py` inside a domain folder still works and 20+ shippedplugins use it — stripe, telegram, discord, whatsapp, whatsapp_business,-translate, speech, github, vercel, cloudflare, gcloud; live list:+translate, speech, github, vercel, cloudflare, gcloud, aws, mcp; live list:`find server/nodes -mindepth 2 -maxdepth 2 -name "*.py" ! -name "_*" ! -name "__init__.py"`).On server restart it auto-registers, theNodeSpec is emitted at `/api/schemas/nodes/<type>/spec.json`, and itdiff --git a/docs-internal/plugin_system.md b/docs-internal/plugin_system.mdindex 73e17c9e..1830a7c6 100644--- a/docs-internal/plugin_system.md+++ b/docs-internal/plugin_system.md@@ -427,7 +427,7 @@ is an app.| `nodes/model/_credentials.py` | `OpenAI / Anthropic / Gemini / OpenRouter / Groq / Cerebras / DeepSeek / Kimi / Mistral / Xai / Sarvam / Ollama / LMStudio / OpenAICompatible` | api_key | One credential class per LLM provider, covering every agent-selectable provider and every standalone chat-model node (`ls server/nodes/model/*_chat_model`). Ollama / LM Studio store a local server URL; `OpenAICompatibleCredential` stores any number of named endpoints, each under its own `openai_compatible:<slug>` reference (RFC-0003); xAI is agent-selectable but has no standalone node; `SarvamCredential` also serves the speech / translate plugins. || `nodes/search/<name>/__init__.py` (inline) | `BraveSearch / Serper / Perplexity` | api_key | single-use search nodes |-This table is the Wave 11.E snapshot, not an inventory — later plugins (Stripe, Vercel, GitHub, Cloudflare, gcloud, WhatsApp, WhatsApp Business, Discord, Microsoft, ElevenLabs, Deepgram, DeepL, ...) each ship their own `_credentials.py`. Read the live set from `len(services.plugin.credential.CREDENTIAL_REGISTRY)`.+This table is the Wave 11.E snapshot, not an inventory — later plugins (Stripe, Vercel, GitHub, Cloudflare, gcloud, AWS, WhatsApp, WhatsApp Business, Discord, Microsoft, ElevenLabs, Deepgram, DeepL, ...) each ship their own `_credentials.py`. Read the live set from `len(services.plugin.credential.CREDENTIAL_REGISTRY)`.`GoogleCredential` exposes a `build_credentials()` classmethod thatreturns a `google.oauth2.credentials.Credentials` — hand-off to@@ -820,7 +820,7 @@ server/│ ├── skill/ # masterSkill (+ _expander.py; skill/simple_memory is an import shim —│ │ # the canonical simpleMemory plugin is nodes/tool/simple_memory/)│ └── ... # context / speech / translate / vision / discord / microsoft /-│ # whatsapp_business / stripe / vercel / github / cloudflare / gcloud —+│ # whatsapp_business / stripe / vercel / github / cloudflare / gcloud / aws —│ # `ls server/nodes` is the inventory; each group folder owns its│ # own _credentials.py (Wave 11.E.1), no central credentials package.└── services/diff --git a/docs/diagrams/how-it-works.svg b/docs/diagrams/how-it-works.svgindex 866ca6db..7cb7799b 100644--- a/docs/diagrams/how-it-works.svg+++ b/docs/diagrams/how-it-works.svg@@ -93,7 +93,7 @@<!-- Value band 1: integrations --><rect class="panel p-green" x="43" y="304" width="1714" height="78" rx="10"/><text class="h1" x="900" y="336" text-anchor="middle">Connect the apps you already use</text>- <text class="sub" x="900" y="364" text-anchor="middle">Gmail · Calendar · Drive · Sheets · Microsoft 365 · Telegram · WhatsApp · Discord · X · Stripe · GitHub · Vercel · Cloudflare · Google Cloud · browser · web search · Python · JavaScript + more</text>+ <text class="sub" x="900" y="364" text-anchor="middle">Gmail · Calendar · Drive · Sheets · Microsoft 365 · Telegram · WhatsApp · Discord · X · Stripe · GitHub · Vercel · Cloudflare · Google Cloud · AWS · browser · web search · Python · JavaScript + more</text><!-- Value band 2: local-first --><rect class="panel p-cyan" x="43" y="407" width="1714" height="92" rx="10"/>diff --git a/docs/diagrams/system-overview.svg b/docs/diagrams/system-overview.svgindex 67705c90..51cca7f9 100644--- a/docs/diagrams/system-overview.svg+++ b/docs/diagrams/system-overview.svg@@ -172,8 +172,8 @@<text class="sub" x="1540" y="577" text-anchor="middle">Apify actors, Crawlee, TikHub (social data)</text><rect class="box p-green" x="1340" y="610" width="400" height="62" rx="8"/>- <text class="h2" x="1540" y="633" text-anchor="middle">Dev + cloud CLIs</text>- <text class="sub" x="1540" y="653" text-anchor="middle">GitHub gh, Vercel, Cloudflare cf, Google Cloud gcloud</text>+ <text class="h2" x="1540" y="633" text-anchor="middle">Dev + cloud</text>+ <text class="sub" x="1540" y="653" text-anchor="middle">GitHub, Vercel, Cloudflare, Google Cloud CLIs; AWS SDK</text><rect class="box p-green" x="1340" y="688" width="400" height="62" rx="8"/><text class="h2" x="1540" y="711" text-anchor="middle">Payments</text>diff --git a/server/skills/GUIDE.md b/server/skills/GUIDE.mdindex d53df536..44f726d3 100644--- a/server/skills/GUIDE.md+++ b/server/skills/GUIDE.md@@ -20,6 +20,7 @@ server/skills/├── autonomous/ # Autonomous agent patterns│ code-mode-skill, agentic-loop-skill, progressive-discovery-skill,│ error-recovery-skill, multi-tool-orchestration-skill+├── aws/ # aws-skill (AWS SDK: EC2, S3, any API operation)├── cloudflare/ # cloudflare-skill (cf CLI)├── coding_agent/ # Code execution skills│ python-skill, javascript-skill, monty-skill, file-read-skill,