This release is a pre-release and may not be stable for production use.
Songe
A local model that sleeps.
You use your model as usual, through opencode, pi or any OpenAI-compatible tool. When your computer is idle and on power, Songe reads back what happened after each of the model's actions — the tool result, the error, your next message — and teaches the model to anticipate it. After a candidate passes the checks, the same model name serves that version. Nothing leaves your machine.
How it learns
The only new information a local model ever gets is what happened after it acted. Given that hindsight, the same model can usually tell what it should have done; without it, it can't. Songe closes that gap:
- Teacher: the original model, shown the conversation and what happened next.
- Student: the model with a small LoRA adapter, shown only the conversation.
- The student writes its own answers and the teacher scores them token by token (on-policy distillation, as in Google DeepMind's GKD). The student learns where it was wrong, in its own words, so it forgets little.
- It practises the moments where hindsight changes the teacher's mind most.
- It continues the current adapter with replay, rebuilding from the original base when experience is forgotten or the base, tools, or accumulated drift require it.
- A new version is served only if it is measurably better on conversations it never trained on and not measurably worse at general tasks. Otherwise nothing changes.
Songe never runs your tools at night. It only reads what already happened.
Requirements
- Apple Silicon with MLX, Linux with NVIDIA or AMD, or Windows with NVIDIA.
- A locally accessible model served by LM Studio, Ollama, llama.cpp, mlx-lm, or vLLM.
- Python 3.11 or later for pip installation; Homebrew supplies Python 3.12.
Memory and training support are measured on your machine. CPU-only machines can serve and record experience. Calibration must complete before learning starts.
Install
brew install sous-labs/tap/songe
pip install songe
songe init
songe init finds your model server and agents, shows a short facts list, and asks once. Use --show-diff for exact dependency commands and config diffs, or --yes to accept the plan in a script. It exposes your models through the Songe provider. Pick a model in your agent as usual; Songe follows each one you use. Training support and memory are measured during idle gaps. --model PATH optionally pre-enables a local base. Existing single-model installs retain their versions and undo history.
Choose Homebrew or pip, then run songe init. These release commands become
available after the first real PyPI release and creation of the Homebrew tap;
PyPI's 0.0.0.dev0 package only reserves the name.
| Platform | Dependencies | CI scope |
|---|---|---|
| macOS Apple Silicon | MLX and MLX-LM install automatically | Python 3.12 tests on main and v* tags; Metal tests skip when unavailable |
| Linux NVIDIA / AMD | init installs missing training dependencies in its private environment |
Ubuntu Python 3.11/3.12 CPU tests; GPU training unverified |
| Windows NVIDIA | init selects PyTorch wheels for the detected driver |
Portable locks and services implemented; Windows GPU validation required |
The default Linux/Windows install contains the proxy, store, CLI, web assets and Textual dependency without an ML framework. Init detects the accelerator and plans any missing training stack. CPU tests cover the Torch pipeline; accelerator and live server validation still require real hardware. See accelerator installation and CI limits.
Use
There is nothing to do. When you want to look:
songe # where things stand, in one block
songe open # now, next, models and learning results
songe models # learning levels, support reasons, and pending data
songe models MODEL off
songe models MODEL new
songe models MODEL all
songe undo MODEL # restore this model's previous version
Also: songe pause, songe resume, songe sleep --now, songe forget (delete what it has seen), songe uninstall.
The dashboard
songe open starts with now, next, and paused, followed by the Learning switch. They show the current model and work, measured progress and ETA when available, the next action and its condition, or a concrete waiting reason. The models table groups formats into one row with expandable files, followed by learning summaries and retained versions. Returning to a retained version loads and checks its weights before switching.
The browser paints the last state from session storage while fetching. Polls use ETags and separate status, models, learning, and versions revisions; unchanged sections retain their controls, focus, and expanded details. Static assets use content hashes and long-term caching. The dashboard is local.
What it changes on your machine
- Private data under the platform's application data directory: macOS
~/Library/Application Support/songe, Linux$XDG_DATA_HOME/songe, or Windows%LOCALAPPDATA%\songe. - LM Studio's models folder: a
songe/folder holding the current and previous learned versions. Your existing models are never touched. - opencode and pi: one added provider entry each, with a backup.
songe uninstallrestores them. - A per-user background service through launchd, systemd, or Windows Task Scheduler.
It sends no notifications and needs no account. songe uninstall --purge removes everything it created.
When it sleeps
Each model has three learning levels: off forwards and records without training; new (the default) learns only from exchanges recorded after that model's level was set; all also learns from earlier shared experience, including exchanges with other models. Switching back to new starts a fresh window. Scoring, on-policy sampling, training and held-out checks are per model. Songe trains one model at a time, choosing the most eligible pending experience, then the least recently trained. The GUI and TUI offer the same three choices. Existing on/off installs migrate to new/off while preserving versions and undo.
During learned idle gaps without proxy traffic, with adequate memory, power, a safe temperature, and new learnable experience. There is no daily time limit: Songe scores all new experience, trains the selected new pool once plus replay and anchors, then checks and switches the version if it passes. New data starts the next cycle; it never repeats a pool to fill time. The initial gap is ten minutes; later it follows your traffic history. The moment you come back it stops, saves its place, and continues later. A MacBook with its lid closed sleeps too, so learning waits for the next time it is open and idle.
Technical details, configuration and the development workflow: docs/DEVELOPMENT.md. Design and first principles: DESIGN.md.
Songe stops or unloads only work it started. Existing user model instances remain resident; learning waits when they leave too little memory. For llama.cpp and vLLM, init provisions a separate loopback endpoint for Songe’s own server. Before each learning slice, Songe sizes context, responses, logit chunks and serial microbatches from live memory and calibration. Observed pressure transitions set the RAM margin; the live guard remains the hard stop.
Metadata
Release files for songe 0.1.0a6
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 | Actions |
|---|---|---|---|---|
| songe-0.1.0a6.tar.gz | 611.2 kB | With provenance | Details for songe-0.1.0a6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| songe-0.1.0a6-py3-none-any.whl | Python 3 | none | any | Details for songe-0.1.0a6-py3-none-any.whl |
Total release size: 941.3 kB
Release files / songe-0.1.0a6.tar.gz
| Download URL | songe-0.1.0a6.tar.gz |
|---|---|
| Size | 611.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
936a2ab760b80b7560c8f710b8af02e900f52af87e165e872b5ba994f5d309fe
|
|
BLAKE2b-256 checksum How to use checksums |
abc8da77f38c76a2108eeef6b9e5e2cc343e95b198ecbd73dc277e8551c9f166
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 12, 2026.
Transparency logRelease files / songe-0.1.0a6-py3-none-any.whl
| Download URL | songe-0.1.0a6-py3-none-any.whl |
|---|---|
| Size | 330.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ae3fce0ee6a00230666f7c94ee33dd5f4e0c3429bb54728f79f1a5f7d8cecbbd
|
|
BLAKE2b-256 checksum How to use checksums |
c3d7aa623149b04d02f796c1643cf5b1719c78cdfe22e4d796af90f9471995d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 12, 2026.
Transparency logSecurity for songe 0.1.0a6
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
Both files in this release have been uploaded with provenance metadata.
Attestation for songe-0.1.0a6.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 Nov 12, 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.