Skip to main content
For the complete documentation index optimized for AI agents, see llms.txt.
Bootstrap a first HelixDB app for a coding agent. helix chef installs agent context, scaffolds a local project, starts the local database, seeds starter data, writes a build prompt, and launches your coding agent to generate the app.

​
Usage

helix chef
helix cook is an alias for helix chef. The command takes no flags — it is fully interactive (and falls back to sensible defaults when run without a TTY).
helix chef uses npx, so Node.js/npm must be on PATH for the skills and docs-MCP install, and it needs Docker or Podman running to start the local database. It is intended for local development inside a coding-agent environment.

​
Authentication

The first interactive run signs you in to Helix Cloud through a GitHub device-code flow. This is used only to upload an optional, anonymized setup snapshot — the build itself does not require it.
  • Non-interactive (agents, CI, sandboxes): when stdin is not a TTY, helix chef skips the login automatically and proceeds without it. The snapshot upload is simply skipped.
  • Opt out in an interactive shell: set HELIX_SKIP_CLOUD_AUTH=1.
  • No-auth alternative: to scaffold without chef (and without any Cloud login), run helix init local → helix start dev → helix query dev --file … by hand.

​
What it does

  1. Installs the Helix skills (npx skills add HelixDB/skills) and docs MCP.
  2. Initializes a local project (helix init local) with a dev instance on port 6969, then starts it in-memory.
  3. Writes HELIX_CHEF_PROMPT.md (your build intent, or a Personal CRM default) and, for the default build, starter query files under examples/ — then seeds the data.
  4. Detects an installed coding agent (Claude Code → Codex → OpenCode), asks for a permission mode, and launches it against the build prompt.
  5. Opens the generated app at http://localhost:3000 once the agent’s frontend is running.
helix chef does not start a local dashboard — port 3000 is reserved for the Next.js app the agent builds.

​
Interactive mode

Running helix chef in a terminal prompts first for: 
What do you want to build?
Leave this blank to use the default Personal CRM build. If you provide an app idea, it is written into HELIX_CHEF_PROMPT.md and used to drive the agent. Next, choose a setup mode:
ModeBehavior
Automatic setupRuns every setup step with defaults.
Manual setupLets you choose the project path and confirm each setup step.

​
Examples

# Interactive setup
helix chef

# Skip the Cloud login (also implicit in non-interactive shells)
HELIX_SKIP_CLOUD_AUTH=1 helix chef

# Alias
helix cook