Skip to main content
An Entity can keep working between messages. Its daemon schedules memory work, inner-voice generation, autonomous wakes, and routines. Choose deliberately when that activity should use your model.

​
Pause model use

Select Pause inference below the conversation input. The control changes to Inference paused · Resume after the Entity acknowledges it.This pauses the shared Entity, including its Telegram conversations and background inference. Select Resume to allow model requests again. Other open spatial surfaces refresh their status automatically.
Pause cancels active model requests and blocks new chat and embedding requests at the shared inference provider. Scheduled heartbeat, consolidation, and automation entry points skip work while paused. The Entity keeps its identity and memory. The pause marker, .inference-paused, lives beside the Entity’s journal. It survives a restart when that directory is persistent. A deployment using an ephemeral disk must first configure durable storage.
Pause controls new runtime activity. It cannot reverse a tool action already completed or remove charges for requests a provider has already processed.

​
Stop a response or stop the process

For local process cleanup, inspect the targets first:
Then stop those local ngram processes:
This command operates on matching local ngram processes, not one selected Entity. The flags above preserve the separate gateway and Ollama processes.

​
Compact without starting over

Live context is the material sent to the model for the next turn. Durable memory is stored outside that context window. Compaction uses inference, so resume before requesting it. Short histories may have nothing to compact. If summarization fails, the runtime does not reset the conversation. Automatic compaction reports when it starts, completes, or fails in Telegram and spatial. The usage display is an estimate, not a provider billing meter. ngram currently assigns the OpenAI Astra route a 256,000-token application working budget. That is runtime policy, not a statement about the provider’s maximum context window or prices.

​
Reduce background usage

Use pause when you need a definite stop. For an Entity that should remain active, tune individual mechanisms in the configuration reference:
  • Increase autonomous wake intervals and reduce the hourly cycle cap.
  • Disable optional dream generation when you do not need it.
  • Review the inner-voice cadence, affect cycle, relational reflection, and consolidation schedule.
  • Disable or reschedule routines you no longer use.
autonomy.enabled: false disables the autonomous wake engine, but v1 also has a legacy initiative path and independent memory/body jobs. It is not the global inference switch. For a bounded first experiment, use uv run ngram ask rook "Hello". For a foreground conversation without the daemon, use uv run ngram talk rook.