EdgeSpark CLI commands reference

Run edgespark --help for a list of all commands, or edgespark <command> --help for detailed options and flags.

Account and project setup

Command	Description
`edgespark login`	Start browser-based authentication and store local credentials
`edgespark whoami`	Show the current authenticated user
`edgespark logout`	Clear stored credentials
`edgespark init <name> —agent <name>`	Create a new EdgeSpark project and write the matching instructions file
`edgespark init <name> —agent <name> -t <src>`	Initialize from a template — official shorthand, `github:owner/repo`, tarball URL, SSH URL, or local path

edgespark init now scaffolds a root project with server/, web/, configs/, and edgespark.toml. Install dependencies separately in server/ and web/ after scaffolding. --agent is required. The current mappings are:

claude writes CLAUDE.md
gemini writes GEMINI.md
codex writes AGENTS.md
Any other agent name also writes AGENTS.md

That means values such as copilot, cursor, opencode, amp, devin, aider, windsurf, cline, continue, antigravity, kiro, or your own custom agent name all currently scaffold AGENTS.md.

Local development

Command	Description
`edgespark dev`	Start the local dev server on `http://localhost:7775`
`edgespark dev --port <number>`	Run the dev server on a different port
`edgespark dev --reset`	Wipe `.edgespark/state/` before starting so seed data and migrations re-run

Deploy

Command	Description
`edgespark deploy`	Build and deploy your project to its current default environment
`edgespark deploy --dry-run`	Run deployment validation before a real deploy

Custom domains

See the custom domains guide for the end-to-end flow.

Command	Description
`edgespark domain add <hostname>`	Register a hostname against the current project and print the DNS records to publish
`edgespark domain verify <hostname>`	Poll until the domain is active or the timeout is reached (default `15m`, configurable with `--timeout`)
`edgespark domain status <hostname>`	One-shot read of activation, EdgeSpark routing, TLS status, and any pending DNS records
`edgespark domain list`	List every custom domain on the current project
`edgespark domain remove <hostname>`	Detach a hostname from the current project

New projects currently expose one default production environment. Public staging and promote workflows are coming soon, so they are intentionally not documented here yet.

Logs

Command	Description
`edgespark log tail`	Stream real-time logs from your current default environment

Pull platform-managed files

Command	Description
`edgespark pull`	Pull platform-managed schema and SDK types together
`edgespark pull schema`	Pull system-managed database tables into `server/src/__generated__/`
`edgespark pull types`	Pull SDK type declarations for `edgespark` imports
`edgespark pull types --check`	Check whether generated SDK types are stale without writing files

Use edgespark pull to refresh everything that EdgeSpark generates for you. It does not replace your app schema workflow in server/src/defs/. For your own tables, use edgespark db generate and edgespark db migrate.

Database

Command	Description
`edgespark db generate`	Generate migration files from `server/src/defs/db_schema.ts`
`edgespark db generate —name <name>`	Generate a named migration
`edgespark db migrate`	Apply pending migrations to the project database
`edgespark db migrate --confirm-dangerous`	Apply pending migrations that include destructive SQL
`edgespark db check`	Validate the local migration chain before deploy
`edgespark db studio`	Open Drizzle Studio against the project database
`edgespark db studio —port <port>`	Run Drizzle Studio on a custom port
`edgespark db studio —host <host>`	Bind Drizzle Studio to a custom host
`edgespark db sql "<query>"`	Run an ad-hoc SQL query against the project database
`edgespark db sql "<query>" --confirm-dangerous`	Allow destructive DML such as `DELETE` after explicit confirmation

edgespark db sql is for reads and ad-hoc DML. DDL such as CREATE TABLE, ALTER TABLE, and DROP TABLE is blocked. Use the migration workflow instead.

Storage

Command	Description
`edgespark storage apply`	Apply bucket declarations from `server/src/defs/storage_schema.ts`
`edgespark storage apply --confirm-dangerous`	Confirm bucket removals before applying
`edgespark storage bucket list`	List synced storage buckets
`edgespark storage bucket list --desc`	Include bucket descriptions in the output

Secrets

Command	Description
`edgespark secret list`	List secret names only
`edgespark secret set <keys…>`	Register one or more secret keys and open a secure page for entering values
`edgespark secret delete <keys…>`	Delete one or more secret keys

edgespark secret set never sends secret values through the terminal, agent context, or third-party LLM APIs such as Anthropic, Google, or OpenAI. The CLI only registers key names, then opens a secure EdgeSpark browser URL where the human owner enters the values directly.

Vars

Command	Description
`edgespark var list`	List configured environment variables
`edgespark var set <entries…>`	Set one or more plain env vars in `KEY=VALUE` form
`edgespark var delete <keys…>`	Delete one or more env vars by key

Auth configuration

Command	Description
`edgespark auth get`	Show the current auth configuration
`edgespark auth get --json`	Show the current auth configuration as JSON
`edgespark auth pull`	Pull auth config into `configs/auth-config.yaml`
`edgespark auth apply`	Apply `configs/auth-config.yaml` to the project

edgespark auth apply updates the project config, but you should still run edgespark deploy before expecting auth changes to affect your live app.

CLI installation

How to install and authenticate the EdgeSpark CLI.

Deploy and test loop

How to use edgespark deploy and edgespark log tail in the development loop.

The deploy pipeline

What happens at each step when you run edgespark deploy.

Declarative workflow

How repo-authored schema, pull commands, and generated types fit together.

CLI

SDK

Platform

Account and project setup

Local development

Deploy

Custom domains

Logs

Pull platform-managed files

Database

Storage

Secrets

Vars

Auth configuration

See also

CLI installation

Deploy and test loop

The deploy pipeline

Declarative workflow

​Account and project setup

​Local development

​Deploy

​Custom domains

​Logs

​Pull platform-managed files

​Database

​Storage

​Secrets

​Vars

​Auth configuration

​See also

CLI installation

Deploy and test loop

The deploy pipeline

Declarative workflow

Account and project setup

Local development

Deploy

Custom domains

Logs

Pull platform-managed files

Database

Storage

Secrets

Vars

Auth configuration

See also