accrue-ui
Run-observability dashboard for accrue enrichment pipelines: watch a run live cell-by-cell, inspect any cell's prompt and response, triage failures, and track cost — all from the JSONL run log accrue emits.
Status: early release. 0.1.0 is the first published version; the dashboard is built issue-by-issue, so expect gaps — see the issues.
Install
pip install accrue-ui
Then point it at a run log:
accrue-ui .accrue/runs/2026-08-20a.jsonl
accrue 1.4 and later ship an accrue watch handoff that opens the same
dashboard:
accrue watch .accrue/runs/2026-08-20a.jsonl
From accrue 1.4.1 there is a one-line form that installs both:
pip install 'accrue[ui]'
Requires Python 3.10+ and a run log — write one with
pipeline.run(..., run_log=True).
Retrying failed rows
Point the dashboard at the pipeline that produced the run and the triage tab's retry buttons go live — one click re-runs just the failed cells (everything else is served from the run's checkpoint) and the grid heals in place:
# attr is a zero-arg callable returning (pipeline, data)
accrue-ui .accrue/runs/2026-08-20a.jsonl --pipeline enrich:target
# ...or the Pipeline itself, with the data alongside it
accrue-ui .accrue/runs/2026-08-20a.jsonl --pipeline enrich:pipeline --data enrich:rows
Run it from the same directory the pipeline ran in, so the retry resolves
the same checkpoint. Without --pipeline the buttons stay disabled and say
why.
Development
pip install -e ".[dev]"
pytest
ruff check .
No-build frontend
The frontend (accrue_ui/static/) is plain ES modules served as-is:
Preact + HTM + signals, vendored and pinned under
accrue_ui/static/vendor/ (see VERSIONS.md there). There is no build
step, no node toolchain, and no npm — ever. See CLAUDE.md for the full
conventions.
Related
- accrue — the pipeline engine whose run log this dashboard consumes.
Metadata
Release files for accrue-ui 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 | Provenance | Actions |
|---|---|---|---|---|
| accrue_ui-0.1.0.tar.gz | 134.4 kB | With provenance | Details for accrue_ui-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| accrue_ui-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for accrue_ui-0.1.0-py3-none-any.whl |
Total release size: 235.8 kB
Release files / accrue_ui-0.1.0.tar.gz
| Download URL | accrue_ui-0.1.0.tar.gz |
|---|---|
| Size | 134.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7094fde25d3255dcb656bbe5bc6ae84f022e9bf516e109080163613b86627a87
|
|
BLAKE2b-256 checksum How to use checksums |
e302dc229564d204254ebf694d312300cb0e8226d6175b26583ce707d5d69ac8
|
| 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 Sep 11, 2026.
Transparency logRelease files / accrue_ui-0.1.0-py3-none-any.whl
| Download URL | accrue_ui-0.1.0-py3-none-any.whl |
|---|---|
| Size | 101.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dcaf405bbaf6f8522d8907173ddf3849f99057a1ae9c3974a194a1b07e4d5afc
|
|
BLAKE2b-256 checksum How to use checksums |
0fc631d9287a410b87fc3ca1093e657a7f852482021f0d961b8f4724b943b1b8
|
| 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 Sep 11, 2026.
Transparency logSecurity for accrue-ui 0.1.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
Both files in this release have been uploaded with provenance metadata.
Attestation for accrue_ui-0.1.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 Sep 11, 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.