Reference
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 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
helix chef is a local workflow and does not require Cloud authentication. It neither uploads a
project snapshot nor reads Cloud credentials. Use helix auth login separately only when you later
run a Cloud command.
What it does
- Installs the Helix skills (
npx skills add HelixDB/skills) and docs MCP. - Initializes a local project (
helix init local) with adevinstance on port6969, then starts it in-memory. - Writes
HELIX_CHEF_PROMPT.md(your build intent, or a Personal CRM default) and, for the default build, starter query files underexamples/— then seeds the data. - Detects an installed coding agent (Claude Code → OpenAI Codex → OpenCode → Cursor Agent), asks for a permission mode, and launches it against the build prompt.
- Opens the generated app at
http://localhost:3000once 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
Runninghelix chef in a terminal prompts first for:
HELIX_CHEF_PROMPT.md and used to drive the agent.
Next, choose a setup mode:
Examples
Related
helix init— initialize a project without agent setup.helix start— start a local instance.helix query— send dynamic JSON requests.