grimoire-kit
Grimoire installs into your repository and gives you, for the code you delegate to agents (Claude Code, Copilot), a local dashboard, tasks, project memory and an evidence check.
Website · Manual (in French) · Version française
uv tool install grimoire-kit # or: pipx install grimoire-kit
grimoire init . --lite -y # sets up the current repository, light profile (no service)
grimoire standard init . --profile governed # makes the evidence check blocking
The five tools
The dashboard
A local web page that gathers the Grimoire projects on your machine and their tasks. Started from a project, it adds that project and opens on it; it does not start sessions, that stays in your editor.
grimoire cockpit start # starts in the background and opens the browser
Tasks
Each piece of work becomes a task with an acceptance criterion. A session takes a task and hands its work back to you for review.
grimoire task add "Fix the CSV export" -a "pytest tests/test_export.py passes" --ready
Project memory
What the project decided carries over from one session to the next. Memory belongs to each project; in the light profile it needs no service.
grimoire memory remember "We keep SQLite while the volume allows it"
Evidence check
Before a task changes state, Grimoire checks that its evidence exists: a test run, a written
review, a produced file. It refuses for real in the governed profile and warns elsewhere;
either way, it names what is missing.
grimoire standard gate check # tells which evidence is missing, if any
Install
Start small and enable only what the project needs. Updating goes through a backup and a preview; anything that needs your call is proposed instead of applied.
grimoire upgrade-flow run # guided update, backup first
Under the hood
The manual is in French.
- Getting started · Command reference
- Project memory · Evidence check · Updating
- Hosts, surface by surface
- Repository architecture · Changelog
Contributing
Issues and change proposals are welcome. The path (environment, tests, contribution rules) is in CONTRIBUTING.md. A change to a command updates its reference page in the same commit.
License
MIT — see LICENSE.
Metadata
Release files for grimoire-kit 3.73.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 |
|---|---|---|---|---|
| grimoire_kit-3.73.0.tar.gz | 10.3 MB | With provenance | Details for grimoire_kit-3.73.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| grimoire_kit-3.73.0-py3-none-any.whl | Python 3 | none | any | Details for grimoire_kit-3.73.0-py3-none-any.whl |
Total release size: 20.9 MB
Release files / grimoire_kit-3.73.0.tar.gz
| Download URL | grimoire_kit-3.73.0.tar.gz |
|---|---|
| Size | 10.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ac3a8aff7c61b6b5f14fd6dd1d0dcd881f185b2615e270451b5b1496da02e65
|
|
BLAKE2b-256 checksum How to use checksums |
38b50001818d32cb2727fef19a07d94277964d44730e4007624a9cb1db1214ec
|
| 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 Oct 28, 2026.
Transparency logRelease files / grimoire_kit-3.73.0-py3-none-any.whl
| Download URL | grimoire_kit-3.73.0-py3-none-any.whl |
|---|---|
| Size | 10.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec3a54f2bfc20705d1a6917e899fb9587b37442765c1776cffdc06be99437bd3
|
|
BLAKE2b-256 checksum How to use checksums |
eb1222ae6da1ab2b5175fd27a9d59927d8b4efcc70edf6b654c2ee4412f4c8ca
|
| 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 Oct 28, 2026.
Transparency logSecurity for grimoire-kit 3.73.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 grimoire_kit-3.73.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 28, 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.