webloti/task-folder-router-for-codex — explained in plain English
Analysis updated 2026-05-18
Automatically route labeled Codex tasks like client: acme into their own isolated project subfolder
Keep unrelated Codex tasks from writing files into the same shared workspace root
Continue the same subproject across multiple separate Codex tasks using a shared folder label
Check whether a Codex workspace's router installation is set up correctly without changing files
| webloti/task-folder-router-for-codex | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | Python | Python | Python |
| Last pushed | — | 2022-11-22 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 2/5 | 2/5 | 4/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Needs Python 3.8 or newer and a Codex workspace that allows project hooks.
Task Folder Router for Codex is a small template that helps keep the AI coding assistant Codex organized when it is used for many unrelated tasks inside a single workspace. Without it, every task Codex runs tends to write files into the same root folder, which can quickly get messy once you are juggling several different projects or clients at once. This tool watches for a label at the start of a new Codex task, such as project, client, site, or app, followed by a name, and automatically creates or reuses a matching subfolder for that task to work inside. By default the router runs in a mixed mode: tasks that do not start with a recognized label continue to work in the main workspace root exactly as before, while labeled tasks get routed into their own isolated subfolder, such as clients acme inc or projects my dashboard. Names are automatically converted into safe folder names, and only labels you have explicitly configured are accepted, so the tool cannot be tricked into creating arbitrary folders from unexpected input. The project is explicit about its limits: it does not read the contents of your projects, does not send any data anywhere, and does not commit, push, deploy, or install anything on its own. Installation involves cloning the template once into a separate tools folder and then running a Python installer script against each individual Codex workspace where you want the router active, which asks you which labels you want to allow. Once installed, the workspace contains a small hooks file and a router configuration file that tell Codex which folder to use for each new task. A companion doctor script lets you check whether a workspace's setup is correct without changing anything. The project requires Python 3.8 or newer and a Codex setup that supports project hooks. It is released under the MIT license.
A template that automatically routes labeled Codex AI coding tasks into their own isolated subfolders inside a shared workspace.
Mainly Python. The stack also includes Python, JSON.
Free to use, modify, and distribute, including commercially, as long as the MIT copyright notice is kept.
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.