Skip to main content
pdd setup is the required first step after installing PDD. It detects available agentic CLI tools, discovers API keys, configures the model list, optionally creates a .pddrc, runs a live model test, and prints a summary. The wizard can be re-run at any time to add providers, update keys, or change settings.

Usage

pdd setup
pdd setup takes no arguments or flags. It is fully interactive.

The 6-step setup wizard

1

Detect agentic CLI tools

Scans PATH for supported agentic CLI tools: Claude Code (claude), Gemini CLI (gemini), and Codex CLI (codex). Offers installation instructions and API key configuration if none are found.At least one of the following is required for agentic commands:
ToolInstallAPI key
Claude Codenpm install -g @anthropic-ai/claude-codeANTHROPIC_API_KEY
Gemini CLInpm install -g @google/gemini-cliGOOGLE_API_KEY or GEMINI_API_KEY
Codex CLInpm install -g @openai/codexOPENAI_API_KEY
2

Scan for API keys

Searches for API keys across .env, ~/.pdd/api-env.*, and the current shell environment. If no keys are found, prompts you to enter one.
3

Configure models from llm_model.csv

Selects appropriate models from the bundled data/llm_model.csv reference file based on your available API keys. The CSV contains top models (ELO ≥ 1400) across all LiteLLM-supported providers, with columns for provider, model identifier, cost, ELO rating, API key name, and reasoning capabilities.
4

Create .pddrc (optional)

Offers to create a .pddrc project configuration file. Recommended for multi-context projects such as monorepos.
5

Test the first available model

Makes a real LLM call with the first available model to verify the API key and model configuration are working correctly.
6

Print summary

Displays a structured summary of detected CLIs, configured API keys, selected models, and the test result.

After setup: source the API environment file

After the wizard completes, source the generated API environment file so your keys take effect in the current terminal session:
source ~/.pdd/api-env.zsh
New terminal windows load the keys automatically. You only need to source manually for the current session after running pdd setup.

Re-running setup

pdd setup can be re-run at any time to:
  • Add a new provider or API key.
  • Switch to a different agentic CLI tool.
  • Update the model configuration after adding new keys.
  • Regenerate or update .pddrc.
pdd setup

Setup banner

If you skip pdd setup after installation, the first time you run another pdd command, it will detect missing setup files and display a reminder banner. The banner is suppressed once ~/.pdd/api-env exists or when your project already provides credentials via .env or .pdd/.
pdd setup installs shell tab completion automatically. If you need to refresh the completion script without re-running the full setup wizard, run pdd install_completion directly.
  • pdd connect — Launch the web interface after completing setup.
  • pdd auth — Authenticate with PDD Cloud separately from local API key setup.

Build docs developers (and LLMs) love