Skip to main content
Reference
Create a new Helix project: helix init writes a helix.toml with either one local instance or one Helix Cloud database link. Local or Cloud.

Usage

Subcommands

Without a subcommand, the CLI prompts for the target in a terminal and creates a local dev instance in non-interactive shells.

Options

--path, --skills, and --no-skills can be passed before or after the subcommand.

helix init local

helix init cloud

Behavior

  • Fails if helix.toml already exists in the project directory.
  • Creates .helix/ for instance state and adds .helix/, .env, target/, and *.log to .gitignore when missing.
  • init local also writes examples/request.json and an AGENTS.md (never overwriting an existing one), and warns if Docker or Podman is unavailable.
  • Cloud init authenticates through the WorkOS session and resolves workspace, then project, then database as described in Cloud resource resolution. It ignores the link of any enclosing project.
  • Cloud init writes [project] id and workspace_id along with the [enterprise.<name>] link, so later Cloud commands in the directory need no flags.
  • It stores stable linkage only. It has no gateway URL (database endpoint) or query-auth options.
  • The skills install runs through npx; if it fails, the project is still created and the CLI prints a warning.

Examples