Rift / Public alpha
alpha*Be here for the first chapter.
Rift is open to everyone. Bring your coding agent, put it to work, and help us iron out issues and shape what comes next.
No invitation or account needed. Free and open source. No telemetry in the CLI.
curl -fsS https://storage.googleapis.com/rift-e59ea04337d9/v1.3.1-alpha/install.sh | shWindows (PowerShell)
irm 'https://storage.googleapis.com/rift-e59ea04337d9/v1.3.1-alpha/install.ps1' | iex
v1.3.1-alpha · Free and open source. Already installed? Run rift update.
Do more.
With less.
Recall preview / 1h
No CLI telemetry.
01 / Why an open alpha
Real work.
Better answers.
80%
Less repeated
input context
An indicative example: of 100,000 input-context tokens, Rift avoids 80,000 repeated tokens and delivers 20,000. Illustrative, not measured savings or a guarantee of billing reductions.
The alpha is available for anyone to try. It is an early release with rough edges, and the point is to learn: fix issues, gather feature feedback, and understand what Rift does well in real projects. The examples on this page are illustrative, not measured results from alpha users.
01
Find the rough edges.
Put Rift through the work you actually do. Reproducible bug reports help us make capture, Recall, and the dashboard more reliable.
02
Shape the next features.
Tell us what gets in your way and what would make Rift more useful. Real workflows help us choose what to build next.
03
Put claims to the test.
We want evidence from real projects before making broad claims. Share results if you choose; savings will vary with the work, agent, and context.
04
Build in public.
Read the source, open an issue, or contribute on GitHub. Rift is free to install and available under the Apache-2.0 license.
02 / What to try
Less repetition.
More understanding.
Start with one project and a supported agent: Claude Code, Codex, or Antigravity. Use your normal workflow, then explore what Rift recorded.
Keep the story.
Follow supported coding-agent sessions, changes, and checkpoints in a local record alongside your project.
Carry context forward.
Help an agent reuse useful context instead of reading the same material again. See where Recall helps in your own work.
See the work clearly.
Inspect agent activity, recorded token usage, and cost estimates. Help us find the views and signals that are useful day to day.
03 / Your data, your choice
Your feedback.
Shared by you.
A little history, at a glance. Character density traces an example month of events, sessions, and checkpoints.
The Rift CLI has no telemetry or automatic usage reporting. Your captured sessions and usage records stay on your machine. Installing the alpha does not send us your code, prompts, or session history.
We learn from what you choose to share: an issue, a feature request, a diagnostic report, or observations about your own results. Nothing is submitted automatically, and you can use Rift without sending feedback.
Want to report a problem? Run rift doctor --report, review its output, and share it with reproduction steps. Use non-sensitive examples and leave out credentials, private code, and customer data.
Downloads and update checks use the network. Your coding agent follows its own provider’s data policies. This website’s analytics are covered by our privacy policy.
04 / Start here
One project.
Your everyday workflow.
Install Rift, follow the quickstart, and see how it fits. Help us make the next release more useful.