Saddlefit fits an agent's harness to one compact model, on your own tasks. It adds what fixes failures, drops what stops helping, and proves each change on tasks the tutor never saw.
The model's weights never change; only the files around it do: system prompt, skills, tool
guidance, tool scripts, loop settings, reasoning mode and an EXPERIENCE.md of lessons.
Status: pre-alpha. Built milestone by milestone; see the milestones and the spec.
Three loops
- Fast — during a task. When the task's own check fails, the student probes a few harness variants locally and keeps what passes; the finding goes on probation in a journal.
- Middle — overnight. A tutor diagnoses training failures and proposes one change at a time; it is accepted only if it wins on repeated runs over held-out tasks, and pruned by ablation once it stops paying for its context.
- Slow — every few weeks. Statistics on accepted changes become a ranked playbook, gated by an A/B test, until a compact local tutor can take over.
The fast loop in detail
The middle loop in detail
The slow loop in detail
What counts as a compact model
An open-weight model that runs on one consumer machine and meets all four conditions
(saddlefit doctor checks them):
- Memory — at 4-bit, weights plus a 32k-token context fit in 24 GB or less.
- Active size — at most about 10B parameters active per token (a 30B-A3B MoE qualifies).
- Speed — roughly 20 tokens per second or more on the target machine.
- Tool use — reliable tool calls, natively or through constrained JSON output.
| Tier | What it is | Typical hardware |
|---|---|---|
| S | dense, 1–4B | 8–16 GB laptops, CPU only |
| M | dense, 4–10B, or a looped model | 16–18 GB Macs, GPUs with 8–12 GB |
| L | MoE, up to ~35B total and ~5B active | 32–36 GB Macs, 24 GB GPUs |
Quickstart
Requires Python 3.12+, Docker and a local model runner such as Ollama.
uv tool install saddlefit
cd your-python-project
saddlefit init --model qwen3:8b
saddlefit doctor
saddlefit tasks mine
saddlefit baseline
saddlefit fit
saddlefit report
Every command also accepts --json.
Where it comes from
The middle loop follows AutoSaddler; the fast loop and the improver that improves itself follow Harness². What Saddlefit adds is the focus on one compact local model, measured on your own tasks, with a harness that stays small.
See the spec, Part D for sources and a fuller comparison.
Documentation
- Specification — the build contract
- Architecture
- Architecture decision records
- Contributing
- Security policy
License
Metadata
Release files for saddlefit 0.2.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 | Provenance | |
|---|---|---|---|---|
| saddlefit-0.2.0.tar.gz | 130.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| saddlefit-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 288.9 kB
Release files / saddlefit-0.2.0.tar.gz
| Download URL | saddlefit-0.2.0.tar.gz |
|---|---|
| Size | 130.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3c171cb565232076d2e3c9af3ea17949761659b66a1f1fbbfbe773ea5d97e12
|
|
BLAKE2b-256 checksum How to use checksums |
b41a666f75aea0de6c34f12f4e6423b58b84194096cb470e9dbd2205a6d9cf88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 22, 2026.
Transparency logRelease files / saddlefit-0.2.0-py3-none-any.whl
| Download URL | saddlefit-0.2.0-py3-none-any.whl |
|---|---|
| Size | 158.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
928a5edbea3d633924b02c9ed7290ba48a9fab9c29d0a54685043612882018b9
|
|
BLAKE2b-256 checksum How to use checksums |
0d2e1459f2b5438be90f43dbed7a82283a4e0c938f5e5cc4cfc70cdec7f1d38c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 22, 2026.
Transparency logSecurity for saddlefit 0.2.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for saddlefit-0.2.0.tar.gz
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 Oct 22, 2026.
Transparency logA 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.