TaskManager.exe
Version-controlled task management for AI agents. Agents use familiar file editing tools; versioning and sync happen transparently via jj (jujutsu).
Problem
AI agents using file-based task systems lose work when:
- Multiple agents edit the same file
- Context resets mid-task and overwrites with stale state
- No history to recover from
- Agents go in circles - after context reset, they repeat mistakes because they don't know what was already tried
Installation
Requires Python 3.11+ and jj.
pipx install taskmanager-exe
# or
uvx taskmanager-exe
Quick Start
# Initialize in your repo
taskman init
# Install MCP server config
taskman install-mcp claude # or: cursor, codex
# Install Claude Code skills (optional)
taskman install-skills
To create a worktree (from main repo):
taskman wt my-feature # creates worktrees/my-feature/ + clones .agent-files
To add .agent-files to an existing worktree (recovery):
taskman wt # clones .agent-files into current directory
How It Works
Agent
│
├── Edit tool ────────► .agent-files/ (jj repo)
│ (file ops) │
│ push/pull
├── MCP Server ───────────────┼──────────────────►
│ (batch/sync) ▼
│ .agent-files.git/ (bare origin)
└── Skills ───────────────────┘
(CLI wrapper)
- Agents edit files with their normal Edit tool
- jj auto-snapshots every change (no explicit commit needed)
- MCP tools or Skills handle sync and history queries
- Bare git origin serializes concurrent access across worktrees
CLI Commands
taskman init # create .agent-files.git/ + .agent-files/
taskman wt <name> # create worktree (from main repo)
taskman wt # add .agent-files to existing worktree
taskman install-mcp <agent> # install MCP config (claude, cursor, codex)
taskman install-skills # install skill files to ~/.claude/commands/
taskman uninstall-mcp <agent> # remove MCP config
taskman uninstall-skills # remove skill files
taskman describe <reason> # create named checkpoint
taskman sync <reason> # full sync: describe + fetch + rebase + push
taskman history-diffs <file> <start> [end] # diffs across revision range
taskman history-batch <file> <start> [end] # file content at each revision
taskman history-search <pattern> [file] [limit] # search history
taskman stdio # run MCP server (stdio transport)
MCP Tools
When installed via taskman install-mcp, these tools are available:
| Tool | Description |
|---|---|
describe(reason) |
Create named checkpoint |
sync(reason) |
Full sync workflow |
history_diffs(file, start, end) |
Aggregate diffs across range |
history_batch(file, start, end) |
File content at all revisions |
history_search(pattern, file, limit) |
Search history for pattern |
Skills
When installed via taskman install-skills, these Claude Code skills are available:
| Skill | Description |
|---|---|
/continue |
Resume work - pull + read STATUS.md |
/handoff |
Mid-task handoff - sync + detailed context |
/complete |
Task done - sync + archive |
/describe <reason> |
Create named checkpoint |
/sync <reason> |
Full sync workflow |
/history-diffs <file> <start> [end] |
Diffs across range |
/history-batch <file> <start> [end] |
File content at revisions |
/history-search <pattern> [--file] [--limit] |
Search history |
Skills wrap the CLI and work without MCP support.
Direct jj Commands
Agents can also use jj directly for simple operations:
jj status # current state
jj log # view history
jj diff # see changes
jj restore --from <rev> <file> # restore file from revision
Task File Structure
.agent-files/
STATUS.md # Task index, session state
LONGTERM_MEM.md # Architecture (months+)
MEDIUMTERM_MEM.md # Patterns, gotchas (weeks)
tasks/
TASK_<slug>.md # Individual tasks
_archive/ # Completed tasks
Sync Model
Sync at task boundaries:
/continue- session start, pull latest state/handoff- mid-task, push with detailed context/complete- task done, push and archive
On conflict, agent resolves with Edit tool, then syncs again.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for taskmanager-exe 0.6.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 | |
|---|---|---|---|---|
| taskmanager_exe-0.6.1.tar.gz | 38.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| taskmanager_exe-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.2 kB
Release files / taskmanager_exe-0.6.1.tar.gz
| Download URL | taskmanager_exe-0.6.1.tar.gz |
|---|---|
| Size | 38.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b16995e336a57676edfe202758d5f1f7216c3ad38560505425d0ec5b41beefe
|
|
BLAKE2b-256 checksum How to use checksums |
9c1e245bfb5f6597ab3fd7de9fa4fe4cf2dfc9eb5ff7b793dbb34451914a3913
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 17, 2026.
Transparency logRelease files / taskmanager_exe-0.6.1-py3-none-any.whl
| Download URL | taskmanager_exe-0.6.1-py3-none-any.whl |
|---|---|
| Size | 50.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2961e42afa8d3b46d7bbeccb2a75b4bc7c5b74de34bbdab196a14e8799dd0c67
|
|
BLAKE2b-256 checksum How to use checksums |
d67a0d208454fc6f3d88401a7d379849b2dad98829ea9b24cc8519450f136c30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 17, 2026.
Transparency logSecurity for taskmanager-exe 0.6.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for taskmanager_exe-0.6.1.tar.gz
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 Jun 17, 2026.
Transparency logA 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.
