limitless-tools 0.1.0

Library and CLI to fetch Limitless lifelogs and store locally

limitless_tools

A Python 3.11+ library and CLI to fetch and store Limitless lifelogs locally as JSON. Built with TDD and clean, extensible architecture.

Tested on macOS (14.x) and Ubuntu 22.04; Windows support is planned.

• PRD: docs/PRD.md
• Default data dir: ~/limitless_tools/data/lifelogs (configurable)

Quick start

1. Create a virtual environment and install dev dependencies:

python3 -m venv .venv
source .venv/bin/activate
python3 -m pip install --upgrade pip
pip install -r requirements-dev.txt

Prefer pip install -e ".[dev]" if you want an editable install with all contributor tooling in one step.

2. Configure environment (copy .env.example to .env and fill in values or export env vars):

export LIMITLESS_API_KEY=your_api_key
# export LIMITLESS_API_URL=https://api.limitless.ai
# export LIMITLESS_DATA_DIR=~/limitless_tools/data/lifelogs

3. Run tests:

python3 -m pytest -q

4. Fetch lifelogs (saves JSON files under the data dir):

python3 -m limitless_tools.cli.main fetch \
  --limit 10 \
  --direction desc \
  --include-markdown \
    --include-headings

Installation (macOS/Linux)

Install from PyPI (after 0.1.0 ships) with:

pip install limitless-tools
# or install it into an isolated environment:
pipx install limitless-tools

For contributor tooling plus an editable install:

pip install -e ".[dev]"

For local development you can keep an editable install around and run the console script directly:

pip install -e .
limitless --help

Windows support is planned, but the release artifacts are currently smoke-tested on macOS (Sonoma) and Ubuntu LTS only.

Configuration

• Example config file: config.toml.example in this repo.
  • Default user path: ~/limitless_tools/config/config.toml
  • Copy and edit: mkdir -p ~/limitless_tools/config && cp config.toml.example ~/limitless_tools/config/config.toml
  • Or pass a custom file with --config /path/to/config.toml.
• You can also write/update the config via CLI:

python -m limitless_tools.cli.main configure \
  --api-key YOUR_API_KEY \
  --data-dir ~/limitless_tools/data/lifelogs \
  --output-dir ~/limitless_tools/exports \
  --timezone UTC \
  --batch-size 50

Notes: You can define multiple profiles (e.g., [default], [work]) and select with --profile work. Precedence: CLI flags > environment variables > config file > built‑in defaults.

Supported platforms

• Verified locally on macOS Sonoma (arm64) and Ubuntu 22.04 (x86_64) via CI + smoke tests.
• Wheel/venv smoke tests run as part of the release checklist (scripts/release_check.sh).
• Windows support is on the roadmap; we’re tracking path/timezone quirks before advertising it as fully supported.

Notes

• Uses pagination with sensible defaults. See docs/PRD.md for detailed requirements and roadmap.
• TDD-first: tests are single-assert and documented for clarity.

CLI at a glance

• limitless fetch --limit 10 --direction desc — fetch the latest entries with markdown/headings by default.
• limitless sync --date 2025-11-01 --timezone UTC — incremental sync that updates index.json and sync state.
• limitless list --date 2025-11-01 --json — list indexed lifelogs filtered by date and starred status.
• limitless search --query "meeting notes" --regex — search titles and markdown with regex or fuzzy matching.
• limitless export-markdown --limit 5 / --date YYYY-MM-DD --combine — print or write markdown exports.
• limitless export-csv --date 2025-11-01 --output /tmp/lifelogs.csv — dump metadata (add --include-markdown to include body content).

Error handling & exit codes

• Network failures (including timeouts) are retried when safe and surface as concise ApiError messages (HTTP 429 with Retry-After hints, or Request timed out …).
• Local persistence issues (e.g., unwritable data dir) become StorageError/StateError with the offending path in the context.
• The CLI wraps those exceptions in friendly stderr output so you see a single Error: … line instead of a Python traceback; pass -v/--verbose to capture the stack trace in logs if needed.
• Exit codes: 0 success, 1 operational/service errors, 2 validation/config problems (e.g., invalid timezone, missing --date when using --combine), 130 for Ctrl+C aborts.
• Errors also drive JSON logging via --verbose, so CI logs include structured context without leaking secrets.

Documentation

• Usage guide: docs/USAGE.md
• PRD & roadmap: docs/PRD.md
• Audio research: docs/AUDIO.md
• Task tracker: docs/TASKS.md

Links

• Changelog: CHANGELOG.md
• Contributing & workflow: CONTRIBUTING.md
• Security policy: SECURITY.md

Code quality

• Ruff: a fast Python linter that aggregates many checks (pycodestyle/pyflakes/isort/pyupgrade) in one tool. It keeps the codebase consistent and catches common issues early.
• mypy: static type checker for Python. It enforces type hints to reduce runtime errors and improve maintainability.

Run locally:

ruff check .
mypy limitless_tools

Release checks

Use scripts/release_check.sh before tagging a release. It runs ruff, mypy, pytest, builds sdist/wheel, validates with twine check, and performs a fresh virtualenv smoke test of the wheel on macOS/Linux. Override the Python interpreter via PYTHON_BIN=/path/to/python scripts/release_check.sh if needed.

Security & Privacy

• No unexpected egress: the HTTP client enforces a base URL allowlist (default: api.limitless.ai, localhost, 127.0.0.1).
  • Extend with LIMITLESS_URL_ALLOWLIST="host1,host2" or bypass with LIMITLESS_ALLOW_UNSAFE_URLS=1 if you explicitly need it.
• Log redaction: secret‑like fields (e.g., api_key, X-API-Key, authorization, token, password, secret) are redacted as [REDACTED] in structured logs.
• Secret scanning: a detect-secrets pre‑commit hook and baseline are included.
  • Install hooks: pre-commit install
  • Run locally: pre-commit run --all-files