Reference

rescile-ce CLI Reference

Complete CLI reference for rescile-ce global options and subcommands serve, save, diff, bootstrap, and mod.

Edit this page on GitHub

CLI Reference

The rescile-ce binary provides several subcommands for managing and serving your graph.

Synopsis:

rescile-ce [GLOBAL OPTIONS] <COMMAND>

Global Options

  • -d, --data-dir <DIR>: The root directory for your data files. Defaults to ./data.
  • --module <PATH_OR_URL>: Load a module. Can be used multiple times.
  • --module-params <PARAMS>: Semicolon-separated key=value params available in all templates.
  • --debug-build[=<SELECTORS>]: Enable module/graph-build debug logging. Filter by passing a comma-separated selector list (e.g. network,bafin). No value enables full build tracing.
  • --debug-runtime[=<LEVEL>]: Enable core runtime server/action logs (default level: debug).
  • --debug-proxy[=<LEVEL>], --debug-vault[=<LEVEL>], --debug-graphql[=<LEVEL>], --debug-mcp[=<LEVEL>], --debug-runner[=<LEVEL>], --debug-auth[=<LEVEL>]: Enable debug logs for the named runtime component (default level: debug).
  • --remove-orphaned-assets: Remove unconnected assets from the final graph.
  • --writeonce-keys <KEYS>: Comma-separated property keys that avoid overwrites (default: created).
  • --max-loop <N>: Max stabilization loop iterations (default: 8).
  • --git-client <CLIENT>: Git client (auto, gh, git, internal).
  • --no-progress: Disable the interactive spinner and print plain log lines. Useful for CI pipelines or when copying output from the terminal.

Subcommands

serve

Builds the graph and starts the Web UI and GraphQL server.

  • --port <PORT>: Listening port (default: 7600).
  • --listen <IP>: Listener IP address (default: 127.0.0.1).
  • --agent-port <PORT>: Optional gRPC port for agent runners.
  • --keep-action-logs <DAYS>: Number of days to persist action execution logs (default: 7). Use 0 to keep logs forever. Old log files are pruned on startup.
  • --ctx-url-controller <URL>: Override the controller URL exposed in the rescile_endpoints template parameter (env: RESCILE_CTX_URL_CONTROLLER).
  • --ctx-url-mcp <URL>: Override the MCP URL exposed in the rescile_endpoints template parameter (env: RESCILE_CTX_URL_MCP).
  • --ctx-url-vault <URL>: Override the Vault URL exposed in the rescile_endpoints template parameter (env: RESCILE_CTX_URL_VAULT).
  • --init: Run the bootstrap step before serving (copy/merge starter files from loaded modules).
  • --bootstrap-policy <POLICY>: Default bootstrap policy (once, append, merge, replace, skip) for assets that do not declare their own. Only used together with --init.

save <FILE>

Builds the graph and dumps the raw in-memory representation to a JSON file.

  • --init: Run the bootstrap step before saving (copy/merge starter files from loaded modules).
  • --bootstrap-policy <POLICY>: Default bootstrap policy (once, append, merge, replace, skip) for assets that do not declare their own. Only used together with --init.

diff <FILE>

Builds the current graph and compares its structure against an older, saved graph JSON file.

bootstrap

Explicitly copies starter asset and input files from loaded modules into the local data/ directory. This is the only place where module assets/inputs are copied into a project; there is no implicit auto-copy during normal graph builds.

  • --module <NAME>: Restrict copying to the named module. If omitted, all loaded modules are considered.
  • --diff: Print what would be copied or merged without writing any files.
  • --force: Overwrite existing local files instead of preserving them.
  • --bootstrap-policy <POLICY>: Default bootstrap policy (once, append, merge, replace, skip) for assets that do not declare their own.

CSV files are merged according to each asset’s bootstrap_policy (default merge): new rows are appended, existing rows keep their non-empty cells, and missing columns are backfilled from the module CSV or from column default/template values. Input JSON files are copied only if they do not already exist unless --force is used.

See Bootstrapping a Project for details and examples.

update [VERSION]

Checks for and safely installs in-place updates for rescile-ce.

generate-schema

Generates a .schema.json file from the local data dir module. Infers resources, properties, relations, and capabilities from assets, models, and action files.

  • [RESOURCES]: comma-separated list of resources to include.
  • --output <FILE>: write the generated schema to a file (stdout if omitted).
  • --schema-id <ID>: override schema id (default: module name).
  • --schema-version <VERSION>: override schema version (default: module version).

See Schema Validation — Generating a Schema for details.

validate

Validates the current workspace against central schemas.

  • --schema <URL_OR_PATH>: Use only this schema source; ignore schemas declared in module.toml. Can be used multiple times.
  • --strict-schemas: Treat schema validation warnings as hard errors and validate CSV cell values against schema types.
  • --init: Run the bootstrap step before validating (copy/merge starter files from loaded modules).
  • --bootstrap-policy <POLICY>: Default bootstrap policy (once, append, merge, replace, skip) for assets that do not declare their own. Only used together with --init.

See Schema Validation for details.

mod <lock|check|update|fetch|check-schema>

Dependency management commands. See Module Dependencies.

mod check-schema --schema <URL_OR_PATH> --strict-schemas validates loaded modules against the given schema sources.