Task (cade-task)
Task is a light CLI wrapper around Reminders.app (reminders-cli) with sane defaults to remove friction from GTD.
Quick Start
Install
Install with pipx:
pipx install cade-task
Or with uv:
uv tool install cade-task
More install options available.
Set your project directory
Export TASK_PROJECT_DIR for your shell environment:
export TASK_PROJECT_DIR="${HOME}/awesome_stuff"
Go
$ task list
Tasks
┌───────┬──────────────────────────────────────────────────────┐
│ Index │ Task │
├───────┼──────────────────────────────────────────────────────┤
│ 0 │ Refactor code, all of it │
│ 1 │ Add testing to generator │
│ │ TODO: handle empty API responses (src/client.py:57) │
│ │ PERF: cache parsed reminders output (cade_task/lib.py:91) │
└───────┴──────────────────────────────────────────────────────┘
task list shows both Reminders tasks and TODO-style comments discovered in the current project. Supported markers include TODO:, FIXME:, ISSUE:, HACK:, TIP:, INFO:, PERF:, TEST:, WARN:, XXX:, and BUG:.
Check out usage or --help for more commands.
Caveats
- Task wraps Keith Smiley’s reminders-cli. Task is intended as a backend-agnostic wrapper that standardizes use without being tied to a specific implementation— I don’t want to retrain muscle memory if a new killer app comes along.
License
This project is distributed under an MIT license, see LICENSE for more information.
Made it this far? You deserve a hug.
Metadata
Release files for cade-task 0.5.1
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 |
|---|---|---|---|---|
| cade_task-0.5.1.tar.gz | 99.9 kB | Without provenance | Details for cade_task-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cade_task-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for cade_task-0.5.1-py3-none-any.whl |
Total release size: 110.2 kB
Release files / cade_task-0.5.1.tar.gz
| Download URL | cade_task-0.5.1.tar.gz |
|---|---|
| Size | 99.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2bca4fa83aef6023e75f3707ce92bc1c358409d14e8c73893c1c9d11c86e7a99
|
|
BLAKE2b-256 checksum How to use checksums |
a69216dee25d6331a35956911fd3e173b72bd286fda941033caa16c58b577340
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / cade_task-0.5.1-py3-none-any.whl
| Download URL | cade_task-0.5.1-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
698f6cfe512b4335cc9983991c53cd7a15ff94c0d6c6639e141cbea7d7209ffa
|
|
BLAKE2b-256 checksum How to use checksums |
a60400ce9063436cc9d0b846780e08b166f9b9b6f12c9126aebc4d32c1102578
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for cade-task 0.5.1
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.