Recall & savings

# What to expect

Recall helps supported agents avoid reading the same context repeatedly. When a file is read again, Rift can return changed lines or a note that it is unchanged. A first read of a large file can start with an outline. Repeated command output can be shortened while retaining useful errors, warnings, and test summaries.

Use your agent normally after project setup. A fresh project or a task that reads everything only once may have little to reuse. Benefits depend on the task, agent, repeated context, and recorded activity; there is no guaranteed savings percentage.

# Inspect your results

rift recall status
rift savings
rift savings --last 7d

Use Recall status to check integration state, and savings to inspect reported avoided context. The trailing windows are 24h, 7d, and 30d. You can also inspect the dashboard's Recall summary and open the viewer to look at recorded recalls.

For a window that starts at a particular time, use a UTC timestamp:

rift savings --since 2026-11-01T00:00:00Z

If you intentionally want a fresh evaluation period for this project, run rift savings reset. It changes the start of the reporting period and keeps captured history. Record that boundary when comparing results.

# Read the numbers

• Recorded tokens describe activity Rift observed. An empty or unknown value is different from measured zero.
• Avoided context describes context Rift reports saving in its own view of the work. It is not an independently verified provider invoice.
• Dollar estimates depend on available model prices and assumptions. They do not establish the amount your provider charged or refunded.
• Time windows must match for comparisons. Short windows do not reach back past a reporting period you explicitly reset.

The illustrative graphics on the site explain the idea; they are not benchmarks or results collected from alpha users.

# Control Recall

Use Project Settings to review the features enabled for a project. From your terminal, you can disable or re-enable Recall:

rift recall disable
rift recall init

Disabling Recall removes its managed integration entries and keeps its recorded data. Restart your agent after changing integration settings. Disabling an agent's capture is a separate action described in agent setup.

# Share useful feedback

The CLI has no telemetry. We cannot see these results unless you choose to share them. If you want to help evaluate the alpha, describe the task type, agent and version, reporting period, and relevant results. Keep private source, prompts, paths, and credentials out of public reports.

Unexpected behavior? Start with troubleshooting and share a minimal example when possible.