causet dev

causet dev is a real, shipped command. It is a local compile-and-watch loop, not a hot-reload server — it does not push IR to a running fork automatically. Deploying still requires causet deploy (or release + deploy apply/activate).

What it does

  1. Reads your CLI context (causet context show)
  2. Compiles the runtime directory once
  3. Prints platform, application, fork, runtime/query URLs, and (if signed in) the dashboard URL
  4. Unless --once is set, watches .causet/.yaml/.yml files under the runtime directory and recompiles on change
causet dev
causet dev --runtime ./concert-app --fork sandbox
causet dev --once

Flags

FlagDescription
--runtime <path>Runtime directory to compile and watch (default: .)
--fork <fork>Fork to develop against (default: CLI context)
--onceCompile once and exit — no file watching
--interval <seconds>File poll interval in seconds (default: 2)
--out <path>Compiler output directory (default: dist)

Local loop vs. deploy

causet dev only recompiles locally on your machine. To make a change visible to a fork’s live traffic, run the normal deploy path (or the causet deploy golden path) after your DSL is ready:

causet dev --once
causet deploy --fork main --runtime . --full

See Deployments for the full apply/activate lifecycle.

What is Causet?