Skip to content
rjest
GitHub
intermediate 10 minutes

Inspect and reset the rjest daemon

jestd is observable by design. When a run behaves unexpectedly, these commands let you inspect and reset the daemon. The on-disk transform cache survives restarts, so resetting is cheap.

  1. 1

    Check daemon status

    See whether the daemon is running and what it is holding.

    $ npx rjest --daemon-status
  2. 2

    Stop the daemon

    Shut jestd down cleanly. The next run will boot a fresh one.

    $ npx rjest --daemon-stop
  3. 3

    Force a clean restart

    Restart the daemon in one step when it is stuck. The sled transform cache is preserved.

    $ npx rjest --daemon-restart

What survives a restart

  • ▸The blake3-keyed transform cache in sled persists on disk, so a restart does not throw away compiled output.
  • ▸Warm workers and the in-memory dependency graph are rebuilt on the next run — that is the one-time cold-start cost.

More guides in the index, or read the architecture to understand what the daemon is doing.