Skip to main content

Hearth CLI — Project & Sprint Awareness System

Hearth CLI is a local project and sprint awareness tool for the terminal. It keeps a YAML registry of active work, calculates a lightweight cognitive-load signal, records context switches, and presents the same data through a Rich CLI and a Textual dashboard.

Created by Toshon Jennings.

The PyPI distribution is named hearth-cli; the installed command is hearth.

Install

Hearth CLI requires Python 3.11 or newer. Installing it as an isolated command-line tool is recommended:

pipx install hearth-cli

or:

uv tool install hearth-cli

You can also install it into an existing Python environment:

python -m pip install hearth-cli

First use

hearth add
hearth status
hearth dashboard

Hearth CLI starts with an empty registry. Its local data lives in ~/.config/hearth/ by default. Set HEARTH_DATA_DIR to use another directory.

Commands

  • hearth status shows project health, sprint capacity, and priority actions.
  • hearth sprint shows committed projects and cognitive-load guidance.
  • hearth switch <id> records a context switch and updates the project date.
  • hearth add registers a project interactively.
  • hearth add --from-json <json> registers a project non-interactively.
  • hearth edit <id> opens a project's YAML in $EDITOR.
  • hearth md writes PROJECTS.md in the Hearth CLI data directory.
  • hearth md --output <path> writes the report to a specific path.
  • hearth md --json prints the registry as structured JSON.
  • hearth agent-link <id> <type> <path> associates an agent log with a project.
  • hearth scan discovers candidate repositories directly under your home and ~/projects directories and asks before importing them.

Run hearth --help or hearth <command> --help for the complete interface.

Data and privacy

Hearth CLI is local-first. Registry data is stored as plain YAML and context-switch history is appended to a plain JSON Lines file. It does not encrypt those files or send them to a remote service. Protect the data directory with normal filesystem permissions and full-disk encryption if it contains sensitive project information.

Development

uv sync --extra dev
uv run pytest
uv build

License

Hearth CLI is source-available proprietary software. Personal, educational, and internal operational use is permitted with named credit. Reselling it, charging for access to it, including it in a paid product or service, or otherwise monetizing Hearth CLI requires a separate written commercial agreement with Toshon Jennings. See LICENSE for the complete terms.

Release files for Hearth-CLI 1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for Hearth-CLI 1.0.1
File Size Uploaded
hearth_cli-1.0.1.tar.gz 23.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for Hearth-CLI 1.0.1
File Interpreter ABI Platform
hearth_cli-1.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 52.5 kB

Release files / hearth_cli-1.0.1.tar.gz

Download URL hearth_cli-1.0.1.tar.gz
Size 23.7 kB
Tags Source
SHA-256 checksum
How to use checksums
9984f5472eec4031f39db8cd6e3303d1e77366958bd140fb9211cc31ee951f92
BLAKE2b-256 checksum
How to use checksums
870df45b1c7f3293e408a021d39baddeee8c7cce0338abdd556f9060cf73d391
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 14, 2026.

Transparency log

Release files / hearth_cli-1.0.1-py3-none-any.whl

Download URL hearth_cli-1.0.1-py3-none-any.whl
Size 28.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
89df964c663b51258e6aac397a95a8bde80207951f49a7d449f3730d1fe91b60
BLAKE2b-256 checksum
How to use checksums
bb654e2e078c20ee3880e3bef101520edd861fe8f94ce3a8066c797d3c1fc85d
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 14, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page