pdd-cli 0.0.253__tar.gz → 0.0.255__tar.gz

pdd_cli-0.0.255/.gitignore

@@ -0,0 +1,309 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+*.vsix
+
+# setuptools-scm generated version file
+pdd/_version.py
+
+.tmp/
+.agentic_prompt*
+.agentic_output_*.txt
+agentic_fix_instructions.txt
+.cloud-image-hash
+examples/temp_split_dir/
+sync_order.sh
+
+staging_data_dump.json
+.pdd/core_dumps/*
+*_fixed.*
+
+.vscode/settings.json
+
+pdd/litellm_cache.sqlite/cache.db
+litellm_cache.sqlite/
+
+# Auto-deps lock files (created by filelock for concurrent access prevention)
+*.csv.lock
+
+# Cost tracking CSV (generated at runtime, should not be committed)
+pdd_cost.csv
+
+# Auto-deps default CSV (generated at runtime, should not be committed)
+deps.csv
+
+# Claude folder (ignore contents, but keep skills/)
+.claude/*
+!.claude/skills/
+
+# Test sync folder
+test_sync/
+
+# Vendored Python packages (created by pdd sync worktree setup)
+.pip_packages/
+
+
+# langchain cache
+.langchain.db
+*.pckl
+
+# C extensions
+*.so
+
+output/
+utils/mcp/manual_testing/
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+test-results/
+cover/
+staging/
+*.staging.log
+.staging_*
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+*.py.bak
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+.DS_Store
+
+# Ignore nested repositories
+edit-file-tool/
+
+staging/
+
+# Testmon cache
+.testmon*
+
+# Node.js
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+yarn.lock
+
+# Keep frontend build artifacts for pdd connect
+!pdd/frontend/dist/
+!pdd/frontend/lib/
+!pdd/frontend/package-lock.json
+
+# PDD internal directory (backups, locks, worktrees, etc.)
+.pdd/*
+!.pdd/
+!.pdd/meta/
+.pdd/meta/*.json
+!.pdd/meta/agentic_bug_orchestrator_python.json
+!.pdd/meta/agentic_bug_python.json
+!.pdd/meta/agentic_checkup_python.json
+!.pdd/meta/agentic_common_python.json
+!.pdd/meta/agentic_crash_python.json
+!.pdd/meta/agentic_e2e_fix_orchestrator_python.json
+!.pdd/meta/agentic_fix_python.json
+!.pdd/meta/agentic_update_python.json
+!.pdd/meta/agentic_verify_python.json
+!.pdd/meta/checkup_review_loop_python.json
+!.pdd/meta/commands_checkup_python.json
+!.pdd/meta/commands_prompt_python.json
+!.pdd/meta/prompt_lint_python.json
+!.pdd/meta/core_cloud_python.json
+!.pdd/meta/fix_code_loop_python.json
+!.pdd/meta/get_comment_python.json
+!.pdd/meta/get_test_command_python.json
+!.pdd/meta/git_update_python.json
+!.pdd/meta/llm_invoke_python.json
+!.pdd/meta/preprocess_python.json
+!.pdd/meta/summarize_directory_python.json
+!.pdd/meta/sync_determine_operation_python.json
+.pdd/meta/*_run.json
+# Issue #1006 follow-up: these two modules' tests pass quickly but
+# `pdd sync` runs >20 minutes on them in CI, hitting the auto-heal
+# 1200s timeout. Committing run-reports satisfies the released drift
+# detector's workflow-complete gate (no run_report → forced crash op)
+# until either the detector tolerates a "fix" fingerprint with no
+# run_report or the sync time on these orchestrators improves.
+!.pdd/meta/ci_drift_heal_python_run.json
+!.pdd/meta/agentic_change_orchestrator_python_run.json
+!.pdd/meta/metadata_sync_python_run.json
+Makefile.test-staging
+
+# Large model weights (HuggingFace clones)
+demos/3blue1brown/models/
+
+# Generated video outputs
+demos/3blue1brown/outputs/
+*.mp4
+
+# Infisical config (contains workspace/environment references)
+.infisical.json
+
+# --- Local Development Dependencies ---
+# Ignore locally installed/compiled packages and binaries.
+# These should be managed via requirements.txt or setup.py,
+# not tracked in version control to avoid OS compatibility issues.
+.local_pkgs/temp_workspace
+fake_test_output.py
+
+# Solver infrastructure artifacts
+.gh-wrapper/
+
+# Auto-heal CI workspace artifacts — must never be committed.
+# pdd-auto-heal[bot] writes these to its working directory and a workflow
+# accidentally staged them, leaking a GitHub installation token to PR #1211
+# (commit bebf874a4, since dropped). Keep these ignored repo-wide.
+github_token
+diff_base.txt
+modules.txt
+.loop/
+
+# Local PDD venv and debug artifacts
+pdd-env/
+error_log.txt

pdd_cli-0.0.255/.pdd/meta/llm_invoke_python.json

@@ -0,0 +1,11 @@
+{
+  "pdd_version": "0.0.253",
+  "timestamp": "2026-05-29T07:46:04.444006+00:00",
+  "command": "example",
+  "prompt_hash": null,
+  "code_hash": null,
+  "example_hash": null,
+  "test_hash": null,
+  "test_files": null,
+  "include_deps": null
+}

pdd_cli-0.0.255/.pdd/meta/sync_determine_operation_python.json

@@ -0,0 +1,11 @@
+{
+  "pdd_version": "0.0.254",
+  "timestamp": "2026-05-29T21:10:42.589757+00:00",
+  "command": "example",
+  "prompt_hash": null,
+  "code_hash": null,
+  "example_hash": null,
+  "test_hash": null,
+  "test_files": null,
+  "include_deps": null
+}

pdd_cli-0.0.255/PKG-INFO

@@ -0,0 +1,342 @@
+Metadata-Version: 2.4
+Name: pdd-cli
+Version: 0.0.255
+Summary: PDD (Prompt-Driven Development) Command Line Interface
+Author: Greg Tanaka
+Author-email: glt@alumni.caltech.edu
+License: MIT
+Project-URL: Homepage, https://github.com/promptdriven/pdd.git
+Project-URL: Repository, https://github.com/promptdriven/pdd.git
+Project-URL: Issue-Tracker, https://github.com/promptdriven/pdd/issues
+Keywords: prompt-driven development,code generation,AI,LLM,unit testing,software development
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.12
+Description-Content-Type: text/x-rst
+License-File: LICENSE
+Requires-Dist: GitPython==3.1.50
+Requires-Dist: Requests==2.34.2
+Requires-Dist: aiofiles==25.1.0
+Requires-Dist: click==8.4.1
+Requires-Dist: firecrawl-py==4.28.0
+Requires-Dist: firebase_admin==7.4.0
+Requires-Dist: httpx==0.28.1
+Requires-Dist: keyring==25.7.0
+Requires-Dist: keyrings.alt==5.0.2
+Requires-Dist: langchain<0.4,>=0.3.25
+Requires-Dist: langchain-anthropic<0.4,>=0.3.14
+Requires-Dist: langchain-community<0.4,>=0.3.25
+Requires-Dist: langchain-core<0.4,>=0.3.56
+Requires-Dist: langchain-mcp-adapters<0.2,>=0.1.0
+Requires-Dist: langgraph<0.4,>=0.3.0
+Requires-Dist: nest_asyncio==1.6.0
+Requires-Dist: numpy>=1.26.0
+Requires-Dist: pandas==3.0.3
+Requires-Dist: psutil>=7.0.0
+Requires-Dist: pydantic==2.13.4
+Requires-Dist: litellm[caching]<=1.82.6,>=1.80.0
+Requires-Dist: lxml>=5.0.0
+Requires-Dist: rich==15.0.0
+Requires-Dist: semver==3.0.4
+Requires-Dist: setuptools
+Requires-Dist: starlette>=0.37.2
+Requires-Dist: pytest==9.0.3
+Requires-Dist: pytest-cov==7.1.0
+Requires-Dist: boto3==1.43.14
+Requires-Dist: google-cloud-aiplatform>=1.3
+Requires-Dist: openai>=1.99.5
+Requires-Dist: pillow-heif==1.3.0
+Requires-Dist: Pillow==12.2.0
+Requires-Dist: textual
+Requires-Dist: python-dotenv==1.2.2
+Requires-Dist: PyYAML==6.0.3
+Requires-Dist: jsonschema==4.26.0
+Requires-Dist: z3-solver==4.16.0.0
+Requires-Dist: fastapi>=0.115.0
+Requires-Dist: uvicorn[standard]>=0.32.0
+Requires-Dist: websockets>=13.0
+Requires-Dist: watchdog>=4.0.0
+Requires-Dist: tiktoken>=0.7.0
+Requires-Dist: filelock>=3.12
+Provides-Extra: dev
+Requires-Dist: pytest-cov; extra == "dev"
+Requires-Dist: pytest-testmon; extra == "dev"
+Requires-Dist: pytest-xdist; extra == "dev"
+Requires-Dist: pytest-mock; extra == "dev"
+Requires-Dist: pytest-asyncio; extra == "dev"
+Requires-Dist: pytest-timeout; extra == "dev"
+Requires-Dist: build; extra == "dev"
+Requires-Dist: twine; extra == "dev"
+Dynamic: license-file
+
+.. image:: https://img.shields.io/pypi/v/pdd-cli.svg
+   :alt: PyPI version
+
+.. image:: https://img.shields.io/badge/Discord-join%20chat-7289DA.svg?logo=discord&logoColor=white&link=https://discord.gg/Yp4RTh8bG7
+   :alt: Join us on Discord
+   :target: https://discord.gg/Yp4RTh8bG7
+
+PDD: The Last Programming Language™
+====================================
+
+PDD (Prompt-Driven Development) is a prompt-native programming system. ``.prompt`` files are the human-authored source language; Python, TypeScript, Go, and other traditional languages are generated artifacts.
+
+PDD is the last programming language in this specific sense: developers author durable intent, constraints, examples, and tests, then compile that source into whatever implementation language the project needs. Code remains real and reviewable, but it is no longer the primary source of truth.
+
+The primary command is ``sync``, which automatically executes the complete PDD workflow loop—from dependency injection through code generation, testing, and verification. For most use cases, ``sync`` is the recommended starting point, as it intelligently determines what steps are needed and executes them in the correct order.
+
+.. image:: https://img.youtube.com/vi/5lBxpTSnjqo/0.jpg
+   :alt: Watch a video demonstration of PDD
+   :target: https://www.youtube.com/watch?v=5lBxpTSnjqo
+
+Why Choose Prompt-Driven Development?
+-------------------------------------
+
+*   **Tackle the Root Cause of Maintenance Costs**: Traditional development spends up to 90% of its budget on maintaining and modifying existing code. PDD addresses this by treating prompts—not code—as the primary source of truth. Instead of applying costly, complex patches, you update the high-level prompt and regenerate clean, consistent code.
+*   **Boost Developer Productivity & Focus**: PDD shifts your work from tedious, line-by-line coding to high-level system design. Its batch-oriented workflow (using commands like ``sync``) frees you from the constant supervision required by interactive AI assistants. You can define a task, launch the process, and focus on other priorities while the AI works in the background.
+*   **Maintain Control and Determinism**: Unlike agentic coders that can introduce unpredictable changes across a project, PDD gives you full control. You precisely define the context for every operation, ensuring that changes are targeted, deterministic, and safe. This is especially critical in large codebases, where unpredictable modifications can have cascading and destructive effects.
+*   **Enhance Code Quality and Consistency**: By using prompts as a single source of truth, PDD ensures your code, tests, and documentation never drift out of sync. This regenerative process produces a more reliable and understandable codebase compared to the tangled results of repeated patching.
+*   **Improve Collaboration**: Prompts are written in natural language, making them accessible to both technical and non-technical stakeholders. This fosters clearer communication and ensures the final product aligns with business requirements.
+*   **Reduce LLM Costs**: PDD's structured, batch-oriented nature is inherently more token-efficient and allows you to take advantage of significant discounts offered by LLM providers for batch processing APIs, making it a more cost-effective solution than many interactive tools.
+*   **Compile to Any Stack**: PDD does not ask teams to abandon Python, TypeScript, Java, Go, or C++. It treats those languages as targets emitted from a higher-level prompt source.
+
+
+Key Features
+------------
+
+*   **Automated `sync` Command**: A single command to automate the entire development cycle: from code generation and dependency management to testing and verification.
+*   **Cloud & Local Execution**: Run securely in the cloud with GitHub SSO (no API keys needed) or switch to local mode with the ``--local`` flag for full control.
+*   **Comprehensive Command Suite**: A full set of tools to ``generate``, ``test``, ``fix``, ``update``, and ``split`` your code and prompts.
+*   **Intelligent Testing**: Generate new unit tests, or improve existing ones by analyzing coverage reports to hit your desired targets.
+*   **Iterative Error Fixing**: Automatically find and correct errors in your code with commands like ``fix`` and ``crash``, which can loop until the issues are resolved.
+*   **Cost Tracking & Configuration**: Fine-tune AI model behavior with ``--strength`` and ``--temperature`` and track usage with optional cost reporting.
+*   **Cross-Language Support**: Work with Python, JavaScript, Java, C++, Go, and more, with automatic language detection from prompt filenames.
+
+
+Quick Installation
+------------------
+
+**Recommended: Using uv (Faster & Better Dependency Management)**
+
+We recommend installing PDD using the `uv <https://github.com/astral-sh/uv>`_ package manager for better dependency management and automatic environment configuration:
+
+.. code-block:: console
+
+   # Install uv if you haven't already
+   curl -LsSf https://astral.sh/uv/install.sh | sh
+
+   # Install PDD using uv tool install
+   uv tool install pdd-cli
+
+This installation method ensures:
+
+- Faster installations with optimized dependency resolution
+- Automatic environment setup without manual configuration
+- Proper handling of the PDD_PATH environment variable
+- Better isolation from other Python packages
+
+**Alternative: Using pip**
+
+If you prefer, you can install with pip:
+
+.. code-block:: console
+
+   pip install pdd-cli
+
+After installation, verify:
+
+.. code-block:: console
+
+   pdd --version
+
+You'll see the current PDD version.
+
+Getting Started with Examples
+-----------------------------
+
+To quickly see PDD in action, we recommend exploring the ``examples/`` directory in the project repository. It contains ready-to-use sample prompts and projects to help you get started.
+
+For instance, the ``handpaint`` example demonstrates how to generate a complete HTML canvas application from a single prompt. After cloning the repository, you can run it yourself:
+
+.. code-block:: console
+
+   # Navigate to the example directory
+   cd examples/handpaint/pdd/
+
+   # Run the sync command
+   pdd sync handpaint
+
+This will generate the full application based on the ``handpaint_html.prompt`` file.
+
+
+Advanced Installation Tips
+--------------------------
+
+
+**Virtual Environment**
+
+Create and activate a virtual environment, then install pdd-cli:
+
+.. code-block:: console
+
+   python -m venv pdd-env
+
+    # Activate environment
+    # On Windows:
+   pdd-env\Scripts\activate
+    # On Unix/MacOS:
+   source pdd-env/bin/activate
+
+    # Install PDD (with uv - recommended)
+   uv tool install pdd-cli
+    # OR with pip
+   pip install pdd-cli
+
+
+**Environment Variables**
+
+Optionally, add environment variables to your shell startup (e.g., ``.bashrc``, ``.zshrc``):
+
+.. code-block:: console
+
+   export PDD_AUTO_UPDATE=true
+   export PDD_GENERATE_OUTPUT_PATH=/path/to/generated/code/
+   export PDD_TEST_OUTPUT_PATH=/path/to/tests/
+
+Tab Completion
+~~~~~~~~~~~~~~
+Enable shell completion:
+
+.. code-block:: console
+
+   pdd install_completion
+
+Cloud vs Local
+--------------
+
+By default, PDD runs in cloud mode (currently waitlist), using GitHub SSO for secure access to AI models—no local API keys needed. If you want or need to run locally:
+
+.. code-block:: console
+
+   pdd --local generate my_prompt_python.prompt
+
+Be sure to configure API keys in your environment ahead of time:
+
+.. code-block:: console
+
+   export OPENAI_API_KEY=your_api_key_here
+   export ANTHROPIC_API_KEY=your_api_key_here
+   # etc.
+
+Basic Usage
+-----------
+
+All commands follow a standard pattern:
+
+.. code-block:: console
+
+   pdd [GLOBAL OPTIONS] COMMAND [COMMAND OPTIONS] [ARGS]...
+
+**Example – Sync**
+
+The ``sync`` command automates the entire PDD workflow for a given basename. It intelligently runs generation, testing, and fixing steps as needed, with real-time progress feedback.
+
+.. code-block:: console
+
+   pdd sync factorial_calculator
+
+**Example – Generate Code**
+
+Generate Python code from a prompt:
+
+.. code-block:: console
+
+   pdd generate factorial_calculator_python.prompt
+
+In cloud mode (no local keys required). Or locally if you prefer:
+
+.. code-block:: console
+
+   pdd --local generate factorial_calculator_python.prompt
+
+**Example – Test**
+
+Automatically create or enhance tests:
+
+.. code-block:: console
+
+   pdd test factorial_calculator_python.prompt src/factorial_calculator.py
+
+Use coverage analysis:
+
+.. code-block:: console
+
+   pdd test --coverage-report coverage.xml --existing-tests tests/test_factorial.py \
+       factorial_prompt.prompt src/factorial.py
+
+
+**Example – Fix Iteratively**
+
+Attempt to fix failing code or tests in multiple loops:
+
+.. code-block:: console
+
+   pdd fix --loop \
+       factorial_calculator_python.prompt src/factorial_calculator.py tests/test_factorial.py errors.log
+
+PDD will keep trying (with a budget limit configurable by ``--budget``) until tests pass or attempts are exhausted.
+
+Frequently Asked Questions (FAQ)
+--------------------------------
+
+**What's the main difference between PDD and using an AI chat assistant (agentic coder)?**
+
+Control and predictability. Interactive AI assistants can be unpredictable and make broad, unintended changes, which is risky in large codebases. PDD gives you full control. You define the exact context for every change, making the process deterministic and safe. PDD's batch-oriented workflow also frees you from constant supervision, boosting productivity.
+
+**What is "Cloud vs. Local" execution?**
+
+By default, PDD runs in cloud mode, using GitHub SSO for secure access to AI models—no local API keys needed. If you want or need to run locally, use the `--local` flag:
+
+.. code-block:: console
+
+   pdd --local generate my_prompt_python.prompt
+
+Be sure to configure API keys in your environment ahead of time:
+
+.. code-block:: console
+
+   export OPENAI_API_KEY=your_api_key_here
+   export ANTHROPIC_API_KEY=your_api_key_here
+   # etc.
+
+**Can I use PDD on an existing project?**
+
+Yes. PDD is designed for both new and existing projects. You can start by creating prompts for new features. For existing, manually written code, you can use the `pdd update` command to create a prompt file that reflects the current state of your code. This allows you to gradually bring parts of your existing codebase under the PDD methodology.
+
+**Do I need to be an expert prompt engineer?**
+
+Not at all. Effective prompts are more about clearly defining your requirements in natural language than about complex "engineering." If you can write a good specification or a clear bug report, you can write a good prompt. The goal is to describe *what* you want the code to do, not how to write it.
+
+**Is PDD really a programming language?**
+
+Yes, in the source-of-truth sense. A PDD program is the versioned prompt suite plus its includes, examples, tests, architecture metadata, and configuration. ``pdd sync`` compiles that source into conventional code and validates the result.
+
+
+Getting Help
+------------
+
+Use inline help to discover commands and options:
+
+.. code-block:: console
+
+   pdd --help
+   pdd generate --help
+   pdd fix --help
+   ...
+
+Happy Prompt-Driven Coding!