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
TERMINAL PROJECT WORKBENCH · WINDOWS / MACOS / LINUX
Find the right project, see every repository state, then launch Codex, Claude Code, or your editor inside the correct context.
cdp api -Open codex
Your keyboard is not the bottleneck.
You remember paths, inspect repositories one by one, and restart tools. cdp compresses those fragments into one repeatable route.
PATH
Forget drive letters, parent folders, and exact names. Type a few letters and jump directly when there is one match.
cdp api
STATE
Dirty, untracked, ahead, behind, and last commit time arrive in one command.
cdp status --dirty
START
Enter the project first, then launch Codex, Claude, Gemini, VS Code, or Cursor.
cdp web -Open claude
Not a feature list. Executable routes.
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
A directory is not a development context.
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
The launcher is the final step, not the first. cdp establishes project identity and location before Codex, Claude, or Gemini starts.
PS C:\> cdp api -Open codex
api → my-api
C:\Work\my-api
local project root selected
branch: main / state: clean
approved setup applied
codex (cwd: C:\Work\my-api)
session starts in context
02 / TOOL BOUNDARY
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.
The v2.0 demo covers the status dashboard, direct jumps, workspaces, onEnter, Tab completion, and cross-platform support.
Open the demo video ↗Different shells. One project map.
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.
Choose your entry point.
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