life-cli
Life accountability CLI. Task tracking + ephemeral Claude personas that hold you accountable.
When you talk to life, you're spawning a Claude agent with your full task context and explicit behavioral rules.
Perfect for:
- Accountability that matches your ADHD, not against it
- Responding to directness, not encouragement
- Task tracking that actually works
Quick Start
poetry install
life --help
Usage
Dashboard
# Show all tasks, momentum, and current assessment
life
Task Management
# Add task (atomic strings only)
life task "thing"
life task "thing" --focus
life task "thing" --due 2025-12-01
# Add habit (daily wellness/maintenance, checkable)
life habit "hydrate"
# Add chore (recurring maintenance, checkable)
life chore "dishes"
# Mark done (fuzzy match)
life done "partial match"
# Check habit or chore (fuzzy match)
life check "partial match"
# Toggle focus (max 3 active)
life focus "partial"
# Remove task
life rm "partial"
# Set/view operational context
life context "Relationship: Crisis. Wedding: 52 days."
life context # view current
# Direct SQL for power users
life sql "SELECT * FROM tasks WHERE focus = 1"
# List all tasks with IDs
life list
Spawn Personas
When you pass a natural language message (not a known command), life spawns an ephemeral Claude agent with full task context and CLI access.
# Default: Roast identity (harsh accountability)
life "been coding for 8 hours straight"
# Pepper identity (optimistic enablement)
life pepper "just finished the presentation"
# Kim identity (methodical analysis)
life kim "should I refactor the auth module?"
Each persona has distinct behavioral constitution. See Personas below.
Personas
Ephemeral Claude agents with different behavioral constitutions. See docs/personas for details.
| Persona | Use When | Style |
|---|---|---|
| roast | You need gatekeeping. Procrastinating on critical tasks. Hiding behind code work. | Harsh accountability. No enablement. |
| pepper | You're paralyzed by perfectionism. Overwhelmed. Need permission to move forward. | Optimistic catalyst. Celebrate progress. |
| kim | Spiraling into speculation. Need procedural clarity. Overthinking. | Methodical. Facts-based. Stable. |
Categories
- Task: Project work with due dates. Mark done when complete.
- Habit: Daily wellness (hydrate, exercise, sleep). Checkable daily. Never "complete."
- Chore: Recurring maintenance (dishes, laundry). Checkable daily. Never "complete."
Metadata
Release files for life-cli 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 |
|---|---|---|---|---|
| life_cli-0.1.0.tar.gz | 18.4 kB | Without provenance | Details for life_cli-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| life_cli-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for life_cli-0.1.0-py3-none-any.whl |
Total release size: 41.2 kB
Release files / life_cli-0.1.0.tar.gz
| Download URL | life_cli-0.1.0.tar.gz |
|---|---|
| Size | 18.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
278a8b2f8f5cd14e5c4cf94eb6fb2d8c97d433faa17fdbd01b14ca9e526ff44a
|
|
BLAKE2b-256 checksum How to use checksums |
9db8871be4b00949ba5f6af34fdae07d418164c53fac7884e5102e023edb514b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.12.10 Darwin/24.5.0
|
Release files / life_cli-0.1.0-py3-none-any.whl
| Download URL | life_cli-0.1.0-py3-none-any.whl |
|---|---|
| Size | 22.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fccd85499702c5f7cbfffcc5c86d7a6d3b910957a49290f865f21c70b327e38f
|
|
BLAKE2b-256 checksum How to use checksums |
2d6ea7a2c99464708118b177d3ef5649b3cf91e8d683bbd28245391e93070891
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.12.10 Darwin/24.5.0
|
Security for life-cli 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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.