Development Delegation (Kilo & Codex)

How coding tasks are delegated to autonomous subagents.

Codex CLI (primary)

• Version: v0.136.0 (confirmed codex --version)
• Host: Gestalt CT112 (pve/forge01, .96)
• Repo: /root/acore_bot, branch feat/hermes-gestalt-platform
• Workflow: sister council → Codex runs implementation → Tai commits + verifies

Invocation

ssh -t gestalt "cd /root/acore_bot && codex exec --full-auto 'prompt'"

Used for Gestalt development and feature work.

Kilo CLI (secondary)

• Version: v7.3.1 (@kilocode/cli, confirmed kilo --version)
• Install: npm global
• Usage: Fenced coding worker lane — /tmp sandboxes only
• Status: Skill exists at /root/.hermes/skills/ai-agents/kilo-worker/ but not active in all profiles

Gestalt-Specific Rules

• Never git checkout on a dirty tree (657-line pipeline was lost)
• Use git stash before checkout
• If stash pop conflicts: git checkout HEAD -- . then re-apply patches
• File edits only on Gestalt codebase — no git destructuring
• Trust re-implementation and sister council for audit/planning

Related

• Gestalt
• Sister Council Workflow
• Bunsms Wasm Dev