Skip to content
Set cost warnings and restore supported edits
On this page
DocumentationCode

Set cost warnings and restore supported edits

Cost warnings and file restoration are separate controls for supported Claude Code and Codex sessions. Neither should be interpreted as complete financial or repository rollback protection.

Availability variesSource reviewed 2026-09-06 · Rudr 0.34.0

Set a cost warning

  1. Expand Cost warning in the Code composer controls.
  2. Enter a USD threshold of at least $0.01, or leave it empty to disable warnings.
  3. Choose This execution session or Linked conversation for Scope.
  4. Review any optional stopping control and its limitations.
  5. Choose Save warning. The saved setting applies from the next turn.

Warnings occur at 80% and 100%. Missing or delayed usage coverage can delay them. Subscription equivalents and estimates are labeled separately from reported API costs.

Codex’s Stop Codex at the estimated threshold (best effort) can overshoot because usage reports lag execution. Claude’s native API budget flag is offered only for qualified CLI versions and API routes, and uses an estimate rather than invoice charges. Warnings alone do not enforce a spending cap.

Restore eligible edits after rewind

  1. After a supported conversation rewind, expand Restore files from the last rewind.
  2. Choose Preview file restoration.
  3. Inspect each file’s current checkpoint content, proposed restored content, and availability reason.
  4. Select only the files you intend to restore, then choose Restore selected files using the count shown by the button.
  5. Review the result in Files or Git.

Restoration requires verified full file preimages and matching checkpoints. Shell changes are excluded; native provider checkpoints are not automatically mapped. Restoring a file created by the agent can delete that file, as the preview explains. A truncated preview can still represent complete verified content used for the operation.

If restoration is unavailable or fails, refresh the preview and preserve current work. Do not substitute a whole-repository reset. See recorded usage and context/history.

Instructions have been reviewed against the application source; native setup and account walkthroughs remain to be verified. Platform and provider limitations are described above.

Set cost warnings and restore supported edits — Rudr