py-harness
Four jobs on your laptop: ask, write a test, fix a bug, add
one small function. Only touches the folder you point at. Daily work
is py-harness plus Ollama llama3.1:8b. Not everyday-ready.
Site: yauhenbichel.github.io/py-harness.
Run it
python3 -m venv .venv && source .venv/bin/activate
pip install py-harness-cli
The command is py-harness. The PyPI name is py-harness-cli because
py-harness collides with another package. Do not pip install py-harness or pip install pyharness.
Sample project — clone, then cd demo/orders. Do not brief this
repository.
git clone https://github.com/YauhenBichel/py-harness.git
cd py-harness/demo/orders
py-harness brief
py-harness ask "what does compute_total return?"
py-harness run "find the NameError and fix it"
Activate .venv in every new terminal. If the shell says
command not found: py-harness, it is not active. Daily work needs
ollama pull llama3.1:8b. From a clone,
python3 scripts/run/install.py is the editable install.
ask never writes. run writes, then runs the tests. The NameError
sample is built into the tool (no model). Another folder:
py-harness ask ~/app "what does add return?".
Start · Commands · Contributing · Security
What it looks like
Replay: asciinema play docs/media/pip-demo.cast.
A longer session (8B ask): docs/media/live-demo.gif.
Full log: Live demo.
VS Code — py-harness editors vscode, then Tasks: Run Task.
Replay: asciinema play docs/media/vscode-demo.cast.
VS Code.
Cursor — py-harness editors cursor --allow-writes, then chat or Tasks.
Replay: asciinema play docs/media/cursor-demo.cast.
Cursor.
Scores
One laptop. 29 Aug–5 Sep 2026. Not everyday-ready.
| What I tried | Result |
|---|---|
| 0.5B as daily work | 0 / 4 vibe, 0 / 2 parse |
Four Start commands on demo/orders |
0 / 4, then 4 / 4 after the harness |
| Same bench, code must run | 8B 6–9 / 9; 7B coder 7 / 9; 30B timeout |
| Same-night daily (write tests, clamp, sum × 3) | 8B 9 / 9, 7B coder 7 / 9. Keep the 8B |
| Extra 7B–8B on disk | Empty-VRAM SWE daily clamp: first generate 180s. Not a score |
| A real repository (4,580 files) | reading works; writing 1 / 12 |
The long table: Experiments. Every score: Results. Which tags timed out: Hub models.
More
| If you want | Go here |
|---|---|
| What each folder is | Folders |
| Tests | PYTHONPATH=src python -m unittest discover -s tests -q |
| 0.5B style prior | YauhenBichel/python-vibe-0.5b |
| Train / serve / API | Commands |
| A first issue | good first issue |
Vulnerabilities: a public GitHub issue. Do not paste live keys.
Contributors
Thank you to everyone who has helped py-harness.
Yauhen Bichel |
Mark Xian |
Itzsaurav |
svkzn |
Aditya |
Huangshuo Kuang |
The list is filled by Contributors from GitHub commits (bots omitted). Contributor graph · good first issue
1 maintainer
Metadata
1 maintainer
Release files for py-harness-cli 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| py_harness_cli-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for py_harness_cli-0.3.1-py3-none-any.whl |
Release files / py_harness_cli-0.3.1-py3-none-any.whl
| Download URL | py_harness_cli-0.3.1-py3-none-any.whl |
|---|---|
| Size | 210.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3890b14da331b06def25390fa998e8a7fc51cc6d03c139a3786f32448cb089b
|
|
BLAKE2b-256 checksum How to use checksums |
b9252286451596a89a62c5520ccbe68b4a140aba7e94355160c0270982c3294a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Security for py-harness-cli 0.3.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
