You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b1bc0cf
Browse filesBrowse the repository at this point in the historyBrowse files
|`void env types`| Regenerate .void/env.d.ts from env.ts |
31
-
|`void auth login`| Authenticate with Void |
31
+
|`void auth login`| Authenticate with the project’s saved destination, or choose one |
32
+
|`void account login`| Authenticate with a Void platform |
32
33
|`void cloudflare login`| Authenticate with Cloudflare through Void |
33
34
|`void platform install`| Install a company Void platform in Cloudflare |
34
35
|`void connect <url>`| Connect the CLI to a Void platform |
@@ -169,9 +170,23 @@ The deployment preference is saved in `.void/project.json`. Connecting to anothe
169
170
170
171
In a non-interactive shell, supply a URL or explicit target. Cloudflare requires usable credentials and an unambiguous account (`CLOUDFLARE_ACCOUNT_ID` when needed). For a Void platform, provide `VOID_TOKEN` with a matching `VOID_API_URL`, or reuse a valid origin-scoped keychain session. Use `void connect <url> --no-login` to save the verified connection without authenticating; this option is only available for Void platforms.
171
172
172
-
## Auth
173
+
## Authentication
173
174
174
-
### `void auth login`
175
+
`void auth login`, `void auth status`, and `void auth logout` use the destination
176
+
saved for the current project by `void init` or `void connect`. If no destination
177
+
is saved, interactive commands let you choose Cloudflare or a connected Void
178
+
platform. In a non-interactive shell, pass `--platform cloudflare|void` or use
179
+
the explicit `void cloudflare` and `void account` commands. Choosing a destination
180
+
for authentication does not change the project's deploy target.
181
+
182
+
`void auth whoami`, `void auth link`, and `void auth token` remain supported for
183
+
existing scripts. `whoami` follows the selected destination; `link` and `token`
184
+
are Void account operations. Prefer `void auth status`, `void account link`, and
185
+
`void account token` in new scripts.
186
+
187
+
## Void platform account
188
+
189
+
### `void account login`
175
190
176
191
Browser login through one of the platform's currently enabled methods. The token is saved in the operating-system keychain, scoped to the platform origin. Login fails closed when no keychain is available instead of writing the token to a plaintext file; headless environments use `VOID_TOKEN` from their secret manager.
This is optional if you already completed auth during `void connect` or the interactive `void init` flow.
184
199
185
-
### `void auth link [connection-id]`
200
+
### `void account link [connection-id]`
186
201
187
202
Link another enabled login method to your current account. Sign in again if your
188
203
session is no longer recent, complete the additional provider's browser login,
189
204
and confirm the displayed identity. With no connection ID, choose an enabled
190
205
method interactively. The optional dashboard exposes the same flow in **Account**.
191
206
192
-
### `void auth logout`
207
+
### `void account logout`
193
208
194
209
Removes saved credentials.
195
210
196
-
### `void auth whoami`
211
+
### `void account whoami`
197
212
198
213
Prints your current login.
199
214
200
-
### `void auth token`
215
+
### `void account token`
201
216
202
217
Copies your human auth token to the system clipboard. It is intended for
203
218
interactive troubleshooting and remains subject to login-method revocation. Do
@@ -1300,12 +1315,12 @@ Deploy-on-GitHub works from **any** Void login — Google, GitHub, or other SSO.
1300
1315
void github link
1301
1316
```
1302
1317
1303
-
Link your current Void account to a GitHub identity. Opens your browser to authorize Void on GitHub (a localhost + PKCE handshake, the same mechanics as `void auth login`), then binds that GitHub identity to the logged-in account. Requires an authenticated CLI (`void auth login` first).
1318
+
Link your current Void account to a GitHub identity. Opens your browser to authorize Void on GitHub (a localhost + PKCE handshake, the same mechanics as `void account login`), then binds that GitHub identity to the logged-in account. Requires an authenticated CLI (`void account login` first).
1304
1319
1305
1320
You normally don't need to run this directly — `void github install` runs the link automatically when your account has no GitHub identity yet. Run it on its own to link ahead of time, or to link a GitHub identity without installing the App.
1306
1321
1307
1322
::: warning Existing GitHub sign-in
1308
-
Void accounts cannot be merged. If the GitHub account you authorize is already linked to a different Void account, including one created through GitHub sign-in, `void github link` is refused with `This GitHub account is already linked to another Void account.` Run `void auth logout` and sign in to that existing account, or authorize a different GitHub account. The command is also refused if your current Void account is already linked to a different GitHub identity. Re-authorizing the GitHub account attached to your current Void account is allowed and reports `GitHub account already linked.`
1323
+
Void accounts cannot be merged. If the GitHub account you authorize is already linked to a different Void account, including one created through GitHub sign-in, `void github link` is refused with `This GitHub account is already linked to another Void account.` Run `void account logout` and sign in to that existing account, or authorize a different GitHub account. The command is also refused if your current Void account is already linked to a different GitHub identity. Re-authorizing the GitHub account attached to your current Void account is allowed and reports `GitHub account already linked.`
1309
1324
:::
1310
1325
1311
1326
### `void github install`
@@ -1334,7 +1349,7 @@ Join the GitHub App installations your organization already has. If a teammate i
1334
1349
1335
1350
In an interactive terminal you rarely need to run this yourself — `void github connect` runs the same join automatically when no active installations are linked to your account. Running `void github join` yourself matters mainly for non-interactive use (without a TTY, `void github connect` never opens a browser), or to link installations ahead of time.
1336
1351
1337
-
Requires an authenticated CLI (`void auth login` first) and organization-installation sharing enabled on your Void instance; when it is not enabled the command fails closed with a clear message. You can only join installations your GitHub authorization actually returns — you cannot name or join one you cannot access on GitHub.
1352
+
Requires an authenticated CLI (`void account login` first) and organization-installation sharing enabled on your Void instance; when it is not enabled the command fails closed with a clear message. You can only join installations your GitHub authorization actually returns — you cannot name or join one you cannot access on GitHub.
Copy file name to clipboardExpand all lines: packages/void/AGENTS.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,6 +58,8 @@ generated entries must preserve the module-boundary rules below.
58
58
59
59
-**Cloudflare session switching**: Explicit `void cloudflare login` forces a fresh browser sign-in, while automatic authentication reuses valid sessions. Adopted OAuth sessions persist the keyring preference so later compatible CLI logins update the same encrypted store. Environment API credentials block explicit browser login rather than masking it. Status reports identity/auth method and the pinned account separately; login never rewrites the project target. Keep credentials out of all diagnostics.
60
60
61
+
-**Authentication commands**: `void auth login|status|logout` follows the saved `.void/project.json` deployment platform, or prompts when unset; headless calls need `--platform` or an explicit command. `void account` always targets a Void platform account, and `void cloudflare` always targets Cloudflare. Keep `void auth whoami|link|token` as compatibility shortcuts; `link` and `token` belong only to Void accounts. Auth selection never changes the deployment preference.
62
+
61
63
-**Repeatable framework wrappers**: `generateWrapper` recognizes current and legacy wrapper entries and preserves the original application across `--skip-build` runs. Compile handlers before replacing the entry, stage the wrapper for an atomic rename, and copy a new original only after an actual new build. A missing or recursively wrapped original requires a rebuild; readiness alone cannot validate the application entry.
62
64
63
65
-**Framework queue delivery**: Native queue handlers receive the original `MessageBatch`; only managed HTTP delivery serializes it. The generated `/__void/queue` endpoint requires `__VOID_PROXY_TOKEN`, reconstructs `Date` timestamps and first-decision-wins ack/retry methods, and returns per-message decisions even if the consumer throws. Queue-only wrappers must also serve readiness.
Copy file name to clipboardExpand all lines: packages/void/skills/void/SKILL.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ dedicated Access applications or connect existing ones, including a separate
59
59
identity account. Protection setup verifies API/proxy coverage and uses scoped
60
60
service credentials for installation and CI. Use `platform config auth protection`
61
61
to show, enable, or disable protection; retain the company gate when probes fail.
62
-
Users link another enabled method with `void auth link [connection-id]` after
62
+
Users link another enabled method with `void account link [connection-id]` after
63
63
recent sign-in and explicit browser identity confirmation. For expired first-admin
64
64
codes, resume installation or repair completed provisioning. Lost-provider recovery
65
65
uses `platform config auth recover` with installation ownership, original recovery
@@ -79,6 +79,8 @@ For Void platform project access, use `void project team`: invite only an email
79
79
80
80
Use Void commands for every user-facing workflow. Never ask the user to install, authenticate, or run Wrangler directly. Say Cloudflare or Void instead, except when naming literal `wrangler.jsonc` / `wrangler.json` files or `WRANGLER_*` environment variables the user must inspect.
81
81
82
+
`void auth login|status|logout` follows the saved deploy destination or asks the user to choose; `void account` explicitly manages a Void platform account.
83
+
82
84
Use `void` in examples and commands in this skill. For first-time setup, prefer `void init` followed by `void deploy`; in an empty directory, install `void` first and let `void init` add the matching Pages adapter and starter dependencies with Vite+ as the default scaffold toolchain. In an existing app, `void init` configures Void in place by adding missing Vite scripts and creating or patching `vite.config.*` with `voidPlugin()`. For Cloudflare deployment, Void uses bundled tooling and secure browser OAuth; init or the first deploy saves the selected `account_id`, and `void cloudflare login|status|logout` manages the session; Void-managed deployment requires an explicitly connected platform. Use `void connect <url>` for an existing platform or `void platform install --plan` to preview a company control plane in the user's Cloudflare account. The core self-hosted platform excludes the dashboard, GitHub App, and build Containers; lifecycle commands are resumable and verify remote, Worker, and R2 ownership before mutations. `void platform disable` gates traffic through installation-owned routing storage and remains disabled through repair or upgrade; `void platform enable` explicitly restores traffic. Safe uninstall retains name-addressed Workers, R2, AI Gateway, external PostgreSQL, and zones for explicit manual cleanup. Direct Cloudflare deploys support native Void apps, static/SPA/SSG output, and Cloudflare builds from TanStack Start, React Router, vinext, SvelteKit, Nuxt, Analog, and Astro. They provision inferred resources, validate and apply migrations, require schema-declared server values in encrypted remote secret storage, upload and probe an immutable Worker Version, then activate and synchronize triggers. Native Void features are Workers Free-compatible by default; `void/sandbox` is an explicit exception because it uses Cloudflare Containers and therefore requires Workers Paid. A Sandbox deploy checks Containers access before provisioning/building, while apps without Sandbox perform no entitlement probe. Versions without preview URLs are staged at 0% and probed through workers.dev using a version override; the same safe fallback applies when Access blocks a generated preview alias but admits the stable Worker hostname. Set `CLOUDFLARE_WORKERS_SUBDOMAIN` in a fresh CI checkout, while local deploys cache it automatically. When Cloudflare Access protects `workers.dev`, use an admitted `CF_ACCESS_CLIENT_ID` / `CF_ACCESS_CLIENT_SECRET` service-token pair for CI, or a short-lived `CF_ACCESS_TOKEN` from `cloudflared` for an interactive local readiness probe. With Cloudflare saved in `.void/project.json`, secret, domain, project status/log/rollback, and remote database commands operate directly on the pinned Worker/account. Logs are a live tail. Rollback restores the selected version's saved schedules, queues, workflows, routes, and domains but never reverses database migrations; versions without complete trigger snapshots use code-only rollback and keep the current routes and schedules. On either deployment platform, auth-enabled `void deploy` preserves an existing `BETTER_AUTH_SECRET` or creates a persistent encrypted secret when missing; always use Void's deployment flow so it can manage that secret safely.
83
85
84
86
Use `void` and `@void/*` in code examples and package manifests.
@@ -110,7 +112,7 @@ If invoked without a concrete task, do a brief app status check and report:
0 commit comments