Jules Planner
A Python package and GitHub Action for integrating Jules architecture planning into your development workflow.
Overview
This package simplifies interfacing with the Jules API from GitHub Actions. It allows you to automatically generate architecture and implementation plans for issues and pull requests directly within GitHub.
Installation
pip install jules-planner
Usage
As a GitHub Action
This package is designed to be used primarily within a GitHub Actions workflow.
-
Set up secrets:
JULES_API_KEY: Your Jules API key (Get it from Jules Settings).GITHUB_TOKEN: Automatically provided by GitHub Actions.
-
Create a workflow file: (e.g.,
.github/workflows/jules-plan.yml)name: Jules Architecture Planning on: issue_comment: types: [created] permissions: contents: read issues: write pull-requests: write jobs: plan: if: contains(github.event.comment.body, '@jules plan') runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v3 - name: Set up Python uses: actions/setup-python@v4 with: python-version: '3.10' - name: Install Jules Planner run: pip install jules-planner - name: Generate Plan env: JULES_API_KEY: ${{ secrets.JULES_API_KEY }} GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: jules-planner
As a Python Library
You can also use the client directly in your Python scripts:
from jules_planner import JulesPlanner
planner = JulesPlanner(
api_key="your-api-key",
repo_owner="owner",
repo_name="repo"
)
# ... use planner methods ...
Configuration
The CLI tool expects the following environment variables:
JULES_API_KEY: Required. Your Jules API key.GITHUB_REPOSITORY: The repository name inowner/repoformat (automatically set in GitHub Actions).GITHUB_EVENT_PATH: Path to the event payload file (automatically set in GitHub Actions).GITHUB_TOKEN: GitHub token for API access (automatically set in GitHub Actions).
License
MIT
Metadata
Release files for jules-planner 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| jules_planner-0.1.0.tar.gz | 10.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jules_planner-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.4 kB
Release files / jules_planner-0.1.0.tar.gz
| Download URL | jules_planner-0.1.0.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
415f9b5c13d2e89921668c28634690ef248be4f3440f1eb0b5b2106650850ffc
|
|
BLAKE2b-256 checksum How to use checksums |
d6b0a0cd8ae4133d703e78d05ffcabf67dc69eafd19e5ae408a274f76fbcd09d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 30, 2025.
Transparency logRelease files / jules_planner-0.1.0-py3-none-any.whl
| Download URL | jules_planner-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4cea9d53428f43a3960eda3a9a68a4a971327e4ce3d20709d7ec78aa718ee586
|
|
BLAKE2b-256 checksum How to use checksums |
36506e000f3db69246c4009fe16bff52923901278fc8e7c0537c399ea586ba4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 30, 2025.
Transparency log