Task Agent 🤖
A prioritized, file-based task queue for autonomous agentic workers. This system uses a "Mission Control" approach to manage multiple agents working on git-tracked improvements across various branches and worktrees.
📂 System Architecture
The project follows a specific folder structure to manage the lifecycle of an improvement:
docs/issues/: The core queue.mission.usv: A prioritized list of issues using Unit Separator Value (\x1f) format. This serves as the source of truth for task priority.datapackage.json: Frictionless Data metadata for themission.usvschema.pending/: New issues awaiting triage or assignment.draft/: Issues currently being refined or planned.active/: Issues actively being worked on by an agent.completed/{year}/: Successfully implemented and verified improvements.
.gwt/: Git Worktree directory where active branches are checked out for isolated agent execution.
🛠️ Tooling: ta (Task Agent CLI)
The ta tool automates the transition of issues through the queue and manages the underlying git infrastructure.
Commands
| Command | Action |
|---|---|
ta next |
Displays the top prioritized issue from mission.usv. |
ta new |
Creates a new issue file and adds it to the queue. |
ta done |
Moves issue to completed/, removes it from the queue, and auto-commits the result. |
ta start <slug> |
Moves issue to active/, creates a git branch, and sets up a .gwt/ worktree. |
ta run <slug> |
Invokes the sidecar worker defined at .ta/worker to process an active issue. |
🚀 Workflow
- Prioritize: Use
ta new -t "Title"to add a task. - Review: Run
ta nextto see what is currently at the top of the queue. - Dispatch: (Planned) Run
ta start <slug>to prepare the workspace. - Execute: (Planned) The agent (Gemini CLI) processes the task in its isolated worktree via
ta run <slug>. - Finalize: Once verified,
ta donemoves the task to the finished state.
🤖 Gemini CLI Integration
By utilizing the Gemini CLI's headless mode, this system can orchestrate multiple agents simultaneously without requiring manual terminal management, significantly improving portability and scalability between Windows and WSL environments.
1 maintainer
Metadata
1 maintainer
Release files for task-agent 1.3.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 | |
|---|---|---|---|
| task_agent-1.3.1.tar.gz | 838.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| task_agent-1.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / task_agent-1.3.1.tar.gz
| Download URL | task_agent-1.3.1.tar.gz |
|---|---|
| Size | 838.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
50411fb790a2ecca4675aa4cedd7ebd2ec719ae9955c9c58a3fdb9929ee26c08
|
|
BLAKE2b-256 checksum How to use checksums |
b920bf103e8c013690d467e8edf9caefd4386f24948a3a99a3ec0a417b9ee050
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 28, 2026.
Transparency logRelease files / task_agent-1.3.1-py3-none-any.whl
| Download URL | task_agent-1.3.1-py3-none-any.whl |
|---|---|
| Size | 166.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3a8cebc7ea0a57e8878842da23a2a454224abaef6bed60c0bcfd260f78afbac
|
|
BLAKE2b-256 checksum How to use checksums |
53981ee07a75290b7db44b1a8b1f288602b23eff021872d55753374c1d45cfbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 28, 2026.
Transparency log
