cgh-summarize
Frozen. 0.3.0 is the final release.
cgh[plugins]no longer installs it, it gets no new features, and it may be removed from the cgh repository later. Agents write better summaries than a small local model, at the moment they read a file:cgh artifact noteand theknowledge_recordMCP tool store them in cgh and cover this use case. It still installs by name (pip install cgh-summarize) and keeps working as described below.
Prose summaries of tracked files for cgh, written by a model running on your machine, on demand.
pip install cgh-summarize
cgh summarize status # detected backends, coverage
cgh summarize run # summarize the tracked files
cgh findings --key summary
cgh insights # cross-file patterns from the summaries
What changed in 0.3.0
- Nothing runs at index time. Earlier versions summarized files in
the background on every index. Summaries are now written only by an
explicit
cgh summarize run. - Local backends only. The agent CLI backends (
claude -p,gemini,codex,bob) are gone, and so is the egress gate that guarded them: no file content leaves the machine. An Ollama or OpenAI-compatible URL that is not loopback is never used.
Backends
| Backend | Runs |
|---|---|
ollama |
an Ollama daemon on a loopback URL, model is a config line |
openai |
an OpenAI-compatible server on a loopback URL (llama.cpp's llama-server, vLLM, LM Studio) |
structural |
cgh's own outline, no model at all |
backend = "auto" (default) picks the first available in that order.
Third-party plugins add backends through the summarize.backend
extension namespace; one that declares egress = "cloud" is skipped.
Configuration
[plugin.summarize]
# backend = "auto" # or ollama, openai, structural
# min_kb = 4 # skip files smaller than this
# language = "en"
# ollama_model = "qwen2.5:1.5b"
# ollama_url = "http://127.0.0.1:11434"
# openai_base_url = "" # e.g. http://127.0.0.1:8080/v1
# openai_model = ""
# openai_api_key_env = "OPENAI_API_KEY"
Re-summarize policy: when content changes, the old summary is carried forward while the drift stays under 30% of lines and fewer than 5 changes accumulated, then a fresh summary is produced.
Metadata
Release files for cgh-summarize 0.3.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 | |
|---|---|---|---|
| cgh_summarize-0.3.0.tar.gz | 15.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cgh_summarize-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.8 kB
Release files / cgh_summarize-0.3.0.tar.gz
| Download URL | cgh_summarize-0.3.0.tar.gz |
|---|---|
| Size | 15.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1101812e9d020d0ce862ee6a71b64339602f36a0c20bc1b373ac3f6af347468
|
|
BLAKE2b-256 checksum How to use checksums |
f5de6170b14a99397efef67d1701902612396763ca141202a108470d47ed4095
|
| 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 8, 2026.
Transparency logRelease files / cgh_summarize-0.3.0-py3-none-any.whl
| Download URL | cgh_summarize-0.3.0-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8523dcd5ec4cc71cc640e4bb05e3e327138fe910075768d3de2a93248334d90d
|
|
BLAKE2b-256 checksum How to use checksums |
6381c8d0b3c30c6ce13cbba99db3f7d1f79c90144150d41c578a1cafd2e545fe
|
| 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 8, 2026.
Transparency log