PhaseDrift

Install PhaseDrift

Install the signed release and connect your computer through your PhaseDrift account.

Set up with your agent

Let your agent install the local app and connect your project.

Open your project in your coding agent, then paste the prompt.

See the setup and skills

What you are installing

PhaseDrift is a local application with a browser dashboard. It includes the tracker, code analyzers and runtime. The phasedrift command connects a repository, controls tracking and opens its dashboard. Your code stays on your computer; your online account handles the subscription and optional synced history.

Install it yourself

Available for macOS on Apple Silicon, macOS on Intel, Linux (x64), Windows (x64).

The application includes its runtime and pinned analyzers. You do not need Bun or a separate desktop app. Git, Node.js and Perl are used by the analyzers.

macOS and Linux

curl -fsSL https://phasedrift.ai/install.sh | sh
export PATH="$HOME/.local/bin:$PATH"
phasedrift --version

To inspect the installer first, download it with curl -fsSL https://phasedrift.ai/install.sh -o phasedrift-install.sh, read the file, then run sh phasedrift-install.sh.

The installer checks the pinned archive checksum, public-key hash and verifier hash, then verifies the release signature before extracting anything. It installs under ~/.local and does not need administrator access.

Windows

In PowerShell, download and inspect the installer, then run it:

Invoke-WebRequest https://phasedrift.ai/install.ps1 -OutFile phasedrift-install.ps1
Get-Content ./phasedrift-install.ps1
./phasedrift-install.ps1
phasedrift --version

If your execution policy blocks the script, use the downloaded archive and the included runtime as shown below, or follow your organization’s approved script policy.

Connect your computer and project

This setup needs PhaseDrift 0.4.21 or later. Reinstall the current signed archive if phasedrift --version reports an earlier release; this minimum includes project check configuration and local MCP tools.

phasedrift login
phasedrift init --host codex --local-only
phasedrift doctor
phasedrift open

Run these inside your repository. login opens your PhaseDrift account. Sign in with your checkout email, confirm the connection code and choose Connect computer. No license key goes in your terminal or agent chat.

init connects your project and starts local tracking. The example selects Codex. Choose your actual host explicitly with --host opencode, --host claude-code, --host gemini-cli, --host cursor, or --host all; only selected hook-based hosts install their project hooks. --local-only pauses any existing hosted-history sync and turns off cloud report analysis while keeping local evidence on this computer. Omit both --local-only and --analysis only when you intend to preserve existing consent. open opens the dashboard. Run phasedrift status to find that project's dashboard again, or phasedrift scan to start a code scan.

Tracking runs in the background while the project tracker is running. After restarting Windows or Linux, run phasedrift restart in the project again to resume it with the same data. macOS also offers optional login startup through phasedrift service install.

Cloud report analysis and history uploads stay off until you separately enable them in Settings.

Download and verify manually

Download the signed local release.

Choose your computer. Your codebase and saved evidence stay there.

Keep the archive, manifest, signature, public key and verification script together. Run node verify-release.mjs ARCHIVE ARCHIVE.pub.pem before extracting. The pinned public-key SHA-256 is fb62c5e26289fbcce916ba9e05d821ae9d7f6c42f9d7faa99b00bd9e0219f29f.

From the extracted folder, install using the included runtime:

BUN_BE_BUN=1 ./dist/runtime --no-env-file scripts/install-cli.ts
export PATH="$HOME/.local/bin:$PATH"

On Windows, use PowerShell from the extracted folder:

$env:BUN_BE_BUN="1"
./dist/runtime.exe --no-env-file scripts/install-cli.ts
Remove-Item Env:BUN_BE_BUN
$env:PATH="$env:USERPROFILE/.local/bin;$env:PATH"

Already purchased and looking for the next step? Open your workspace or read Get set up.

On this page