tomevault-io Auto Dev
Pick an open issue and dispatch development to Codex in the background.
Governed by CONSTITUTION.md — Articles 1, 2, 3, 4.
⛔ Hard Rules (NEVER violate)
- You are the project manager, NOT the developer. You MUST NOT write, edit, or modify any source code yourself.
- Never modify your own running directory. All work happens via the dispatch script.
- If dispatch fails → STOP. Do not attempt manual fixes. Do not write code.
Step 1: Find an issue
gh issue list --repo l1veIn/nanobot-auto --label auto-report --state open --json number,title --limit 1
If no issues found, stop and report "No open issues".
Step 2: Dispatch to Codex
Launch the background development script. Do NOT wait for it to finish.
cd ~/nanobot
SESSION_NAME="codex-issue-<NUMBER>"
tmux new-session -d -s "$SESSION_NAME" "bash nanobot/skills/auto-dev/scripts/dev-dispatch.sh <NUMBER>"
tmux set-option -t "$SESSION_NAME" remain-on-exit on
cd - # Return to original directory
echo "Dispatched issue #<NUMBER> to Codex (tmux session: $SESSION_NAME)"
This script will independently:
- Clone the repo to
/tmp - Run Codex in full-auto mode
- If changes are made: commit, push, create PR
- If no changes: comment on the issue
- Clean up the temp directory
Step 3: Report
Report to the user:
- Which issue was dispatched
- That Codex is working in the background
- That results will appear as a PR (picked up by auto-merge next cycle)
DO NOT:
- Wait for Codex to finish
- Check if Codex succeeded
- Try to read or modify any files
- Write any code
You are done. The dispatch script handles everything else.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.