invoke-toolkit

A set of extensions for rich output, more options in collection/config discovery through entry-points.

This extends the Collection from Invoke so it can create automatically collections.

invoke-toolkit

Features

Task discovery by namespace for extendable/composable CLIs
Discovery to plain old tasks.py (or any other name)
Local tasks discovery from local_tasks.py in the current directory
Integration with stand alone binaries for specific tasks
Task result caching with TTL support via diskcache (optional)
Future Download binaries

Do I need this package

If you have...

Used invoke for a while and...
Have a large tasks.py that needs to be modularized
Have a lot of copy/pasted code in multiple tasks.py across multiple repos.
Have exceeded the approach of a repository cloned as ~/tasks/ with more .py files that you want to manage.
Or you want to combine various tasks defined in multiple directories
You want to create a zipped (shiv) redistribute script for container environments like Kubernetes based CI environments with only requiring the Python interpreter.

Installation

pip install invoke-toolkit

Quick Start

Using Local Tasks

Create a local_tasks.py file in your project directory with your tasks:

from invoke_toolkit import task

@task()
def my_task(ctx):
    """Do something useful"""
    print("Hello from local tasks!")

Then run it with:

intk local.my-task

Local tasks are automatically discovered and added to the local namespace, allowing you to keep project-specific tasks separate from your main task collection.

Using Task Caching

Cache expensive task results with the cache parameter:

from invoke_toolkit import task

# Simple caching (no expiration)
@task(cache=True)
def expensive_task(ctx, param: str) -> str:
    """Results are cached across invocations."""
    return do_expensive_computation(param)

# Caching with TTL (1 hour)
@task(cache={"ttl": 3600})
def cached_task(ctx, name: str) -> dict:
    """Results cached for 1 hour."""
    return fetch_data(name)

# Caching with ignored arguments
@task(cache={"ttl": 600, "ignore_args": ["verbose"]})
def cached_with_options(ctx, query: str, verbose: bool = False) -> list:
    """Cache key ignores verbose flag."""
    return search(query, verbose=verbose)

Cache features:

Cache location is computed from git repository root + platformdirs
Debug logging (-d flag) shows cache hits/misses
Graceful degradation when diskcache is not installed

To enable caching, install with the cache extra:

pip install invoke-toolkit[cache]

Dynamic task defaults

Use Field when an argument default must be computed from the final task context or resolved from a URI. Explicit command-line values always take precedence.

Bind a resolver once, then reuse the resulting callable for scalar and file defaults. A local resolver always returns one string value per request. The resolver receives every URI using that callback and scheme in one batch.

from invoke_toolkit import Context, Field, FilePath, task


def resolve_bw(ctx: Context, requests: list) -> dict[str, str]:
    return {
        request.parameter: ctx.run("bw get password ...", hide=True).stdout.strip()
        for request in requests
    }


BitwardenField = Field(resolver=resolve_bw)
ExistingFile = FilePath(exists=True, dir_okay=False)


@task
def deploy(
    ctx: Context,
    password: str = BitwardenField(default="bw://PASSWORD_ID"),
    config: ExistingFile = BitwardenField(
        default="bw://CONFIG_ID", cleanup="task"
    ),
) -> None:
    ...

For str fields, the resolver string reaches the task unchanged. For Path or FilePath fields, Field.create_temporary_file() writes that string to a managed temporary file and passes its Path to the task. Override that method in a Field subclass to control file creation; resolvers do not return paths.

For omitted arguments, lookup precedence is explicit CLI/Python/call value, then INVOKE_<PARAMETER> environment value, then the resolved ctx.config value, then the declared Field default or factory. URI values from config use the same local or entry-point resolver dispatch as declared URI defaults.

Field(default_factory=callback) runs only if no higher-precedence value is available. Factories and resolvers never run during help, listing, or shell completion; Path/FilePath completion continues to work normally for explicit values.

Temporary Path files from resolver-bound Field instances are owned by invoke-toolkit. cleanup="pipeline" is the default and keeps the file through expanded pre/main/post execution; cleanup="task" removes it when that task returns. Cleanup runs after failures and cancellation.

Installed invoke_toolkit.field_resolver entry points remain supported for compatibility but issue a warning recommending a task-local resolver. Generate a resolver-only provider package with:

intk -x create.package --provider op

Provider packages expose no task collection. Providers return text only; for Path fields invoke-toolkit materializes and cleans the resulting temporary file according to that Field's cleanup lifetime.

Development

This project utilizes the pre-commit framework, make sure you run:

pre-commit install

With uvx:

uvx --with pre-commit-uv pre-commit install

License

invoke-toolkit is distributed under the terms of the MIT license.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

invoke_toolkit-0.0.66.tar.gz (183.0 kB view details)

Uploaded Aug 17, 2026 Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

invoke_toolkit-0.0.66-py3-none-any.whl (118.1 kB view details)

Uploaded Aug 17, 2026 Python 3

File details

Details for the file invoke_toolkit-0.0.66.tar.gz.

File metadata

Download URL: invoke_toolkit-0.0.66.tar.gz
Upload date: Aug 17, 2026
Size: 183.0 kB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for invoke_toolkit-0.0.66.tar.gz
Algorithm	Hash digest
SHA256	`98ff4a2bccb73db746850bce08ed543e8ec14ecf2eb9aa4affca6cb4ddb47b36`
MD5	`d31d010de372944b0f38d5aecd5ef534`
BLAKE2b-256	`f5e61d80560d7915069f27ec82ff609884fa01aac0bbab93dda03626dcd88a02`

See more details on using hashes here.

Provenance

The following attestation bundles were made for invoke_toolkit-0.0.66.tar.gz:

Publisher: publish-releases.yaml on D3f0/invoke-toolkit

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: invoke_toolkit-0.0.66.tar.gz
- Subject digest: 98ff4a2bccb73db746850bce08ed543e8ec14ecf2eb9aa4affca6cb4ddb47b36
- Sigstore transparency entry: 2498603369
- Sigstore integration time: Aug 17, 2026
Source repository:
- Permalink: D3f0/invoke-toolkit@c1e30fd6f4b369b13d93ab58132c6330ef9393d5
- Branch / Tag: refs/tags/v0.0.66
- Owner: https://github.com/D3f0
- Access: public
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: publish-releases.yaml@c1e30fd6f4b369b13d93ab58132c6330ef9393d5
- Trigger Event: release