Loading...
RightNow Agent includes a persistent local chore queue. It uses the active configured model provider for model-backed steps and is independent of the removed local-model and GPU paths.
rightnow-pager chore add <request.json>
rightnow-pager chore run
rightnow-pager chore run --background
rightnow-pager chore status
rightnow-pager chore status --json
rightnow-pager chore pause
rightnow-pager chore resume
rightnow-pager chore cancel <id>
rightnow-pager chore retry <id>add accepts a JSON ChoreRequest. run drains eligible work until nothing else can start. Pause and cancel take effect at transaction boundaries. Resume does not start work by itself. Retry continues a failed chore from its last verified checkpoint.
The shipped profile does not set chore-queue keys, so parser defaults apply:
chore_queue_background = falsechore_queue_parallelism is unset and resolves to one worker.chore_queue_bounded_prompt_tokens is unset.chore_queue_heavy_background = falsefan_out_transactions = falseThe shipped profile performs no background chore execution and makes no parallel-speed claim.
A chore_queue_parallelism value above one requires a positive measured chore_queue_bounded_prompt_tokens, an active default model with a model_provider, and a context window on the model or provider. The context window must exceed the bounded prompt ceiling. Invalid combinations fail during queue setup.
Background heavy work also requires both background settings, confirmed AC power, and energy saver off. Foreground queue draining is separate. Parallel execution means concurrency across independent requests, not GPU batching or a provider-speed guarantee.