dekk
Make project CLIs runnable with one config and zero manual activation.
Install
pipx install dekk
Fallback:
python -m pip install --upgrade dekk
Minimal Setup
dekk install ./tools/cli.py
If .dekk.toml is missing, dekk install and dekk wrap create a starter
file from the repo context first.
Explicit template-driven setup is still available:
dekk init --example conda
eval "$(dekk activate --shell bash)"
Optional (no activation after this):
dekk wrap myapp ./tools/cli.py
Worktree-safe default:
dekk install ./tools/cli.py # no shell rc PATH edits by default
dekk install ./tools/cli.py --update-shell
Project Command Routing
All project commands go through dekk <appname>, which finds the nearest
.dekk.toml and runs with cwd set to that project root:
dekk myapp # project-aware help
dekk myapp --help
dekk myapp server --port 8080
dekk myapp build
dekk myapp test
This is worktree-friendly by default:
dekkwalks up from your current directory to find the nearest.dekk.toml- the app name must match
[project].name - the command runs with
cwdset to that project root, not whatever nested directory you happened to be in - activation is scoped to that project config before the command runs
That means dekk myapp server works correctly from a repo root, a nested
subpackage, or a separate Git worktree for the same project, without relying
on global shell state.
Built-in Project Tools
Built-in tools (setup, agents, worktree) are project-scoped — they require
the app name so dekk knows which project context to use:
dekk myapp setup
dekk myapp agents init
dekk myapp agents generate --target all
dekk myapp worktree create feature-x --base main
dekk myapp worktree list
Why the app name? Because dekk resolves paths from your current directory.
The app name selects the project (validates against [project].name in
.dekk.toml), and all paths resolve relative to that project root. This
makes every command worktree-safe — it works correctly from any checkout.
Agents
Source of truth: .agents/
dekk myapp agents init
dekk myapp agents generate --target all
dekk myapp agents clean --target codex
dekk myapp agents install # optional (installs Codex skills to ~/.codex/skills)
Generated files: AGENTS.md, CLAUDE.md, .cursorrules, .github/copilot-instructions.md, .agents.json
Worktrees
dekk myapp worktree create feature-x --base main
dekk myapp worktree list
dekk myapp worktree remove feature-x
dekk myapp worktree prune
Worktrees with .dekk.toml get automatic environment setup on creation.
Auto-scaffolded as an agent skill via dekk myapp agents init for git repos.
Inheriting Tools in Downstream CLIs
CLIs built with dekk.Typer can also inherit these tools directly,
useful when worktree isolation is not a concern:
from dekk import Typer
app = Typer(
name="myapp",
auto_activate=True,
add_doctor_command=True,
add_version_command=True,
add_worktree_command=True,
add_agents_command=True,
)
Docs
- Getting Started
- .dekk.toml Specification
- Real-World Examples — annotated configs from carts and apxm
- Agent Workflows
- Worktree Management
1 maintainer
Metadata
1 maintainer
Release files for dekk 1.11.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dekk-1.11.5.tar.gz | 290.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dekk-1.11.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 508.6 kB
Release files / dekk-1.11.5.tar.gz
| Download URL | dekk-1.11.5.tar.gz |
|---|---|
| Size | 290.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e17800e936874d231ce960bbfcb4090fa07f95cef544670bfd498a6c7189e26f
|
|
BLAKE2b-256 checksum How to use checksums |
c959f62e75452fc3326ee2a82b03514277ab061ddfb62cd6089a138a268f6407
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 May 26, 2026.
Transparency logRelease files / dekk-1.11.5-py3-none-any.whl
| Download URL | dekk-1.11.5-py3-none-any.whl |
|---|---|
| Size | 217.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e079aed547b002a32aa11e60731f0a8d69f234358b22796605b7b55ab30b1c31
|
|
BLAKE2b-256 checksum How to use checksums |
28f540ffe497f1b9e9b47195c184e14435da274427a8d971d041a977783f55a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 May 26, 2026.
Transparency log
