Skip to main content

To-do Fixer

to-do-fixer executes directory-backed tasks in fresh Codex sessions. It selects pending files randomly and processes them one at a time until the directory is empty or Codex reports a global usage or authentication limit.

Requirements

  • Python 3.10 or newer
  • Git
  • GitHub CLI (gh), authenticated when a repository must be cloned or created
  • An installed and authenticated codex CLI

Installation

From this directory:

python3 -m pip install .

Task format

Each non-hidden regular file directly inside the task directory is a pending task. The first line must be Repository: OWNER/REPO. The second line must be Type: goal or Type: task. The third line must start with Model: . A non-empty model overrides the Codex model for that execution; an empty value uses the default model from Codex configuration. Every remaining byte of UTF-8 text, beginning on the fourth line, is used as the Codex prompt. Goals and tasks use the same execution flow; the type and selected model are included in the run log.

Repository: kaizten/example-repository
Type: task
Model: gpt-6.1-sol
Implement the requested feature, run its tests, and update the documentation.

To use the configured default model, leave the value empty while retaining the required metadata line:

Model:

Repository clones are identified from their GitHub origin remote rather than from their directory name. If no local clone exists, the runner checks GitHub using the authenticated gh account. An existing repository is cloned into <repos-root>/<owner>/<repo>; a repository that returns HTTP 404 is created as private and then cloned there. Authentication, network, permission, clone-path collision, and multiple-local-clone errors cause the task to fail.

Usage

to-do-fixer

Tasks are read from ~/.to-do-fixer/tasks and repositories are searched recursively beneath ~ by default. Select other locations with:

to-do-fixer --tasks-directory ~/codex-tasks --repos-root ~/workspaces

If the selected task directory does not exist, the command prints a message, creates it and any missing parent directories, and then continues normally. An existing path that is not a directory remains an error.

Create the default task directory, including its parent directories, with:

to-do-fixer --create-tasks-directory

This initialization option must be used on its own and exits after ensuring the directory exists.

Codex runs sequentially with --approve-for-me, which uses automatic approval review with the workspace-write sandbox. A structured final response is required before a task is considered complete.

At startup and again when execution finishes, the command prints a task summary table with pending, done, failed, and total counts. The final table is also printed when execution stops early or is interrupted.

Completed tasks move into done/. Invalid, missing, ambiguous, blocked, or otherwise failed tasks move into failed/. Existing files in either directory are never overwritten. If Codex reaches a usage, quota, rate, credit, or authentication limit, the current task remains pending and the command stops.

Only one to-do-fixer process may use a task directory at a time. Pressing Ctrl-C stops the active Codex process and leaves its task pending.

Exit codes

Code Meaning
0 Every pending task was processed. Some may have moved to failed/.
1 Startup or configuration failed.
2 A global Codex limit or authentication failure stopped processing.
130 The user interrupted processing.

Development

python3 -m unittest discover -s tests -v
./build-package.sh

Metadata

Release files for to-do-fixer 0.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for to-do-fixer 0.0.3
File Size Uploaded Provenance Actions
to_do_fixer-0.0.3.tar.gz 13.0 kB Without provenance Details for to_do_fixer-0.0.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for to-do-fixer 0.0.3
File Interpreter ABI Platform Actions
to_do_fixer-0.0.3-py3-none-any.whl Python 3 none any Details for to_do_fixer-0.0.3-py3-none-any.whl

Total release size: 22.0 kB

Release files / to_do_fixer-0.0.3.tar.gz

Download URL to_do_fixer-0.0.3.tar.gz
Size 13.0 kB
Tags Source
SHA-256 checksum
How to use checksums
8a273c2859be25d29b7956db844aa698a176b90c8e3d9d1b8c3eb8e7798e46cd
BLAKE2b-256 checksum
How to use checksums
b339b0278fe49f508549507c0c1d58e8a47c4eb3abed0c4c3e55efc1e4a3ed99
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Release files / to_do_fixer-0.0.3-py3-none-any.whl

Download URL to_do_fixer-0.0.3-py3-none-any.whl
Size 9.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d9a05540668e980816e2b31a5e71b6ff4ef00da811696f4278cb17b7866eed82
BLAKE2b-256 checksum
How to use checksums
edacc27622da02f8a82119a0c91075505912174a27bb492d94c1e001ba74b4a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Security for to-do-fixer 0.0.3

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page