Codex Autopilot

Codex Autopilot

Multi-model AI coding orchestration via tmux + launchd on macOS.

Overview

Codex Autopilot runs a watchdog loop that orchestrates multiple AI coding sessions in tmux. It features intelligent task routing — frontend tasks (UI, components, H5) are routed to Gemini CLI (1M context window, superior design aesthetics), while backend tasks (API, database, deployment) go to Codex CLI. The watchdog detects idle sessions, auto-nudges them, handles permission prompts, dispatches tasks from a priority queue, and sends notifications via Discord/Telegram. The same stack can be driven by an OpenClaw or Hermes-style orchestration layer for queue dispatch, PR follow-up, and workspace maintenance.

Multi-Model Architecture

Tasks are automatically classified by keywords and routed to the appropriate model. Frontend tasks fall back to Codex if Gemini is unavailable.

Installation

git clone https://github.com/imwyvern/AIWorkFlowSkill.git ~/.autopilot
cd ~/.autopilot
cp config.yaml.example config.yaml
# Edit config.yaml with your project paths, Telegram bot token, and Discord channels

Dependencies

• macOS with launchd (for scheduled execution)
• tmux — session multiplexer for Codex windows
• Codex CLI (codex) — OpenAI's coding agent
• python3 — for state cleanup and PRD verification scripts
• yq — YAML processor for config parsing
• jq — JSON processor for state management
• bash 4+ — for associative arrays in scripts

Install dependencies via Homebrew:

brew install tmux yq jq

Recommended Codex Alias

For unattended tmux sessions, the production default is a full-permission Codex invocation:

echo "alias codex='command codex --yolo'" >> ~/.zshrc
source ~/.zshrc

If you prefer explicit invocation per session, use command codex --yolo directly instead of the alias.

launchd Setup

Use install.sh to register the launchd plist:

./install.sh

This creates a LaunchAgent that runs the watchdog on a configurable interval.

Core Components

watchdog.sh

Main loop engine. On each tick:

1. Iterates through configured project tmux windows
2. Captures current Codex output via codex-status.sh
3. Determines if session is active, idle, or stuck
4. Dispatches appropriate action (nudge, permission grant, task from queue)
5. Enforces cooldowns, daily send limits, and loop detection

codex-status.sh

Captures and analyzes tmux pane content. Detects:

• Codex activity state (working / idle / waiting for permission)
• Permission prompts requiring approval
• Context compaction signals
• Error states and crashes

tmux-send.sh

Sends keystrokes or text to a specific tmux window. Handles:

• Typing text into Codex prompt
• Pressing Enter/keys for permission approval
• Verification polling to confirm send succeeded

autopilot-lib.sh

Shared function library used by all scripts:

• Telegram notification helpers
• File locking primitives
• Timeout and retry logic
• Logging utilities
• State file read/write

autopilot-constants.sh

Defines status constants used across scripts (e.g., STATUS_ACTIVE, STATUS_IDLE, STATUS_PERMISSION).

task-queue.sh

Task queue manager. Supports:

• Enqueuing tasks for specific projects
• Dequeueing next task based on priority
• Task status tracking (pending/running/done/failed)

discord-notify.sh

Sends formatted notifications to Discord channels via webhook. Supports project-channel routing defined in config.yaml.

test-agent.sh

Built-in CI/CD that runs on every commit. Evaluates test suites, tracks coverage, and auto-enqueues bugfix tasks when tests fail.

commit → watchdog detects → test-agent evaluate
  ├─ all pass → review clean → enqueue coverage tasks for low-coverage files
  └─ failures → parse log → auto-enqueue "fix(test): ..." bugfix task
       └─ 1h cooldown per file (prevents retry loops)

Triggers:

• on_commit_evaluate — every new commit
• on_review_clean — after code review passes
• nightly — scheduled full evaluation (default 02:30)

Coverage ratchet: global coverage must not regress; weekly +1% target, capped at 90%.

Other Scripts

Configuration

Edit config.yaml (copy from config.yaml.example). Key sections:

Timing Thresholds

active_threshold: 120    # seconds — Codex considered "working"
idle_threshold: 360      # seconds — Codex considered "idle", triggers nudge
cooldown: 120            # minimum seconds between sends to same project

Safety Limits

max_daily_sends_total: 200   # global daily send cap
max_daily_sends: 50          # per-project daily cap
max_consecutive_failures: 5  # pause project after N failures
loop_detection_threshold: 3  # detect repeated output loops

Multi-Project Scheduler

scheduler:
  strategy: "round-robin"    # or "priority"
  max_sends_per_tick: 1
  inter_project_delay: 5     # seconds between project sends

Project Directories

project_dirs:
  - "~/project-alpha"
  - "~/project-beta"

Gemini Frontend Routing

gemini:
  default_window: "gemini-h5"        # Default tmux window for frontend tasks
  project_windows:
    youxin: "gemini-youxin"          # Per-project Gemini window overrides

Frontend task detection keywords: 页面, 组件, 样式, UI, 前端, H5, 小程序, 界面, frontend, component, style, page, layout

Discord Channel Routing

discord_channels:
  my-project:
    channel_id: "123456789"
    tmux_window: "my-project"
    project_dir: "/path/to/project"

Telegram Notifications

telegram:
  bot_token: "YOUR_BOT_TOKEN"
  chat_id: "YOUR_CHAT_ID"
  status_interval: 1800

Usage

Adding a Project

1. Start a Codex CLI session in a named tmux window:

   tmux new-window -t autopilot -n my-project
   # In the new window, cd to project and run codex
   

2. Add the project path to config.yaml under project_dirs

3. Optionally create projects/my-project/tasks.yaml for task queue:

   project:
     name: "My Project"
     dir: "~/my-project"
     enabled: true
     priority: 1
   tasks:
     - id: "feature-x"
       name: "Implement feature X"
       prompt: |
         Implement feature X per the spec in docs/feature-x.md
   

Manual Operations

# Check status of all projects
./scripts/monitor-all.sh

# Manually nudge a specific project
./scripts/auto-nudge.sh my-project

# Send a command to a tmux window
./scripts/tmux-send.sh my-project "codex exec 'fix the tests'"

# Enqueue a backend task (routes to Codex)
./scripts/task-queue.sh add my-project "Refactor auth module"

# Enqueue a frontend task (routes to Gemini)
./scripts/task-queue.sh add my-project "重构登录页面组件" normal --type frontend

# Run the watchdog once (for testing)
./scripts/watchdog.sh

# Watch a Codex session until it goes idle again
./scripts/watch-codex.sh autopilot:my-project 60

# Check whether upstream PRs need follow-up
./scripts/pr-monitor.sh

# Backup local workspace state to GitHub
./scripts/gitclaw-backup.sh

PR Follow-up and Heartbeat Docs

• scripts/pr-monitor.sh batches review/comment checks for upstream PRs and is designed to be called from cron, OpenClaw, or Hermes agents.
• scripts/watch-codex.sh is the lightweight completion detector used after task dispatch when you need a reliable "notify me when idle again" primitive.
• docs/HEARTBEAT.md contains a production heartbeat checklist for PR follow-up, skill updates, and other operational loops.

Python Autopilot (Alternative)

autopilot.py provides a Python-based alternative with richer state management:

python3 autopilot.py --once        # single pass
python3 autopilot.py --daemon      # continuous loop

Directory Structure

~/.autopilot/
├── SKILL.md                 # This file
├── config.yaml              # Local config (not in git)
├── config.yaml.example      # Config template
├── scripts/                 # All automation scripts
├── projects/                # Per-project task definitions
├── docs/                    # Additional documentation and heartbeat playbooks
│   └── HEARTBEAT.md         # Example production heartbeat checklist
├── code-review/             # Code review templates
├── development/             # Development workflow templates
├── doc-review/              # Doc review templates
├── doc-writing/             # Doc writing templates
├── requirement-discovery/   # Requirement discovery templates
├── testing/                 # Testing templates
├── tests/                   # Test suite
├── state/                   # Runtime state (gitignored)
├── logs/                    # Runtime logs (gitignored)
├── task-queue/              # Task queue data (gitignored)
└── archive/                 # Deprecated files