Rift

Agent setup

Connect the coding tools you already use. Set up each project once, then work with your agent as usual.

Browse guides Agent setup

# Supported agents

The alpha supports capture and Recall for Claude Code, Codex, and Antigravity. Install and sign in to your agent before setting up Rift. Rift does not supply an AI model or replace your agent's subscription.

Rift may detect Gemini CLI, Cursor, Copilot CLI, OpenCode, Factory Droid, or Ollama, but those integrations are not yet wired in this release. Detection alone does not mean sessions are captured. Unsupported integrations are left untouched.

# Connect a project

  1. Open the project's Git directory in your terminal and run rift.
  2. Review the detected agents and proposed setup. Confirm the integrations you want to use.
  3. Restart your agent so it loads the project configuration.
  4. Approve trust and hook prompts inside the agent when asked. Rift does not grant those permissions for you.
  5. Start a task, then use rift doctor if activity does not appear.

For direct command-line setup, run rift init. To change your defaults for future projects, run rift install. Existing projects have their own settings.

# Project settings

From the dashboard, press s or open Settings. Review capture options, Recall, and integration status for the selected project. Changes apply to that project, so check the selected name before making an adjustment.

You can disable a supported agent's capture integration without deleting recorded history:

terminal
rift disable --agent claude-code
rift enable --agent claude-code

Use codex or antigravity instead for the other supported agents. To initialize capture without Recall, use rift init --no-recall. See Recall & savings for switching Recall itself on or off.

Rift reports configuration conflicts instead of overwriting files it cannot safely manage. Follow the finding in rift doctor rather than deleting another tool's settings.

# Worktrees and clones

Linked Git worktrees appear under their project in the picker. If a worktree is missing activity, check it from a terminal in that worktree:

terminal
rift worktree status
rift worktree list

If it needs adoption, run rift worktree adopt there to connect it to the project's enabled integrations. A fresh clone on another machine needs setup on that machine, even when the repository already contains Rift configuration.

Read the privacy guide before enabling capture for a project with sensitive material.