TERMINAL PROJECT WORKBENCH · WINDOWS / MACOS / LINUX

Stop navigating. Start shipping.

Find the right project, see every repository state, then launch Codex, Claude Code, or your editor inside the correct context.

  • Fuzzy-search straight to the project root
  • See every repository state in one view
  • Launch an AI CLI or editor in one step
ROUTE READY cdp v2.2.0
cd E:\Work\Client Projects\VeryLongName\backend cd ..\..\..\SideProjects\tooling git status → cd → open → restart context
PS C:\> cdp api -Open codex
Destination
my-api
Branch
main
State
clean
Launch
codex

Your keyboard is not the bottleneck.

Rebuilding context before every session is.

You remember paths, inspect repositories one by one, and restart tools. cdp compresses those fragments into one repeatable route.

PATH

Long paths are baggage, not knowledge.

Forget drive letters, parent folders, and exact names. Type a few letters and jump directly when there is one match.

cdp api

STATE

Fifty repositories should not mean fifty checks.

Dirty, untracked, ahead, behind, and last commit time arrive in one command.

cdp status --dirty

START

The tool launched. The context did not.

Enter the project first, then launch Codex, Claude, Gemini, VS Code, or Cursor.

cdp web -Open claude

Not a feature list. Executable routes.

One entry point for project context.

LIVE ROUTE PowerShell 7

Lock onto a destination from anywhere.

PS C:\> cdp

56 projects · type to filter · enter to warp

> my-api    C:\Work\my-api

✓ destination locked · C:\Work\my-api

ARRIVAL The current shell is now at the project root

A directory is not a development context.

Route the AI CLI into the right project.

cdp resolves a named project, enters its local path, applies approved project setup, and starts the tool with the correct working directory.

01 / AI CLI ROUTE

One command replaces the context checklist.

The launcher is the final step, not the first. cdp establishes project identity and location before Codex, Claude, or Gemini starts.

  • Project query resolves against your explicit project map
  • OS-specific path profile selects the local root
  • Approved onEnter setup runs before the launcher
  • The AI CLI inherits the intended working directory
AI SESSION ROUTE
  1. 01 RESOLVE PS C:\> cdp api -Open codex api → my-api
  2. 02 ENTER C:\Work\my-api local project root selected
  3. 03 PREPARE branch: main / state: clean approved setup applied
  4. 04 LAUNCH codex (cwd: C:\Work\my-api) session starts in context
READY The AI CLI starts where the work actually lives.

02 / TOOL BOUNDARY

Directory memory and project orchestration solve different jobs.

Use zoxide or autojump for arbitrary visited directories. Use cdp when a named project, repository state, and launcher must travel together.

Tool What it knows Repository overview AI CLI launch
zoxide / autojump Visited directory paths Not built in Not built in
cdp Named projects + local path profiles cdp status cdp api -Open codex

Complementary by design: fast directory recall on one side, repeatable project context on the other.

Skip the claims. Watch the terminal.

From repository overview to AI CLI launch.

The v2.0 demo covers the status dashboard, direct jumps, workspaces, onEnter, Tab completion, and cross-platform support.

Open the demo video ↗
cdp / live proof REAL PRODUCT CAPTURE

Different shells. One project map.

Four routes merge into one workbench.

PowerShell and bash / zsh share the same configuration shape. Windows paths convert automatically when entering WSL, so there is no second project list to maintain.

  • Windows PowerShell 5.1 / 7
  • WSL · bash / zsh
  • Linux · bash / zsh
  • macOS · zsh / bash
SHARED DESTINATION ~/.cdp/projects.json

Choose your entry point.

Your next command goes straight to cdp.

No build tools required. Pick a platform, copy the command, then run `cdp doctor` to verify the environment.

Install the module from PowerShell Gallery, then install fzf.

Install-Module -Name cdp -Scope CurrentUser
winget install fzf
Import-Module cdp
cdp doctor