# AGENTS.md — Kooker Agent Orchestration > **Previous version** (V5 spec-kit/uv workflow) archived at: > `git show origin/archive/agents-v5-spec-kit:joe-template/memory/AGENTS.md` --- ## Agent Stack | Agent | Runtime | Role | |---|---|---| | **Joe** | OpenClaw / Antigravity | Orchestrator, memory keeper, Telegram interface, PR reviewer | | **GitHub Copilot CLI** | `gh copilot` inside Joe's terminal | Coding agent — implements issues, writes tests, raises PRs | | **lex** | Telegram bot (kooker-infra) | API contract specialist | | **jbird** | CronJob (kooker-infra) | Log watcher / alerter | --- ## Joe → Copilot CLI Handover Protocol When Irwin assigns a coding task to Joe, Joe delegates implementation to **GitHub Copilot CLI** running in non-interactive mode inside his terminal. ### The key flag: `-p / --prompt` ``` gh copilot -- -p "" --allow-all-tools --add-dir ``` Copilot CLI runs headlessly, edits files, runs shell commands, then exits. **No TTY, no interactive session, no rate limit from keeping a session alive.** > **What about `/delegate`?** > `/delegate [prompt]` is the *interactive* slash command — it sends the live session to GitHub and creates a PR directly. Joe doesn't use it because he runs headlessly. Joe uses `-p` + `gh pr create` for the same result without needing a terminal session. ### One command — `joe_delegate.sh` Joe calls this for every coding task: ```bash joe_delegate.sh "" # Examples: joe_delegate.sh kooker-pacman 42 "Fix ghost wall collision on corners" joe_delegate.sh kooker-service-auth 17 "Add refresh token endpoint" ``` **What it does automatically:** 1. Fetches issue context from GitHub (title + body injected into prompt) 2. Creates branch `copilot/issue--` 3. Runs `gh copilot -- -p "..." --allow-all-tools` in the workspace 4. Commits changes + pushes branch 5. Opens a **draft PR** referencing the issue 6. Saves the Copilot session transcript to `memory/snapshots/YYYY-MM-DD/` Joe then reviews the diff and tells Irwin it's ready to approve. ### Interactive `/delegate` — when Irwin is watching For exploratory work where Irwin wants to watch live, Joe can open the interactive session: ```bash cd /home/joe/workspaces/ gh copilot # starts interactive session # type the task description, then: /delegate create a PR with these changes ``` This is the manual "pair programming" mode — use it for complex tasks that need back-and-forth. --- ## Workspace Layout All coding work happens inside the **workspaces mount** — already cloned repos, no re-cloning needed: ``` /home/joe/workspaces/ ← mounted from Mac Mini ~/workspaces ├── kooker-pacman/ ├── kooker-service-auth/ ├── kooker-service-user/ ├── kooker-gateway/ ├── kooker-web/ ├── kooker-api-specs/ ├── kooker-infra/ ├── joekookerbot/ └── ... ``` No temporary clones. Work directly in the mounted repo, branch, implement, PR. --- ## Golden Rules - **Issue-First** — every task traces to a GitHub issue (`gh issue create` if missing) - **Branch always** — never commit directly to `main`; org rule requires PR + review - **Joe reviews, Copilot implements** — separation of concerns - **PR proxy** — Joe can approve PRs on Irwin's behalf as the "second reviewer" per org policy - **No secrets in code** — all tokens via env vars; `~/.zshrc` on Mac Mini is the source --- ## Installing Copilot CLI in Joe Copilot CLI is installed via the `gh` extension system — already in Joe's Dockerfile: ```bash gh extension install github/gh-copilot ``` Authenticate with the same `GH_TOKEN` already injected at startup. --- ## Trigger Phrases → Actions | Irwin says | Joe does | |---|---| | "implement issue #N on ``" | Hands off to `gh copilot` in workspaces mount | | "what's open" / "show me the board" | `cat /home/joe/.openclaw/memory/GITHUB_STATUS.md` | | "refresh GitHub status" | `python3 /usr/local/bin/gh_snapshot.py` | | "recall / remember / did we…" | `python3 /usr/local/bin/recall.py ""` | | "sync memory to graph" | `python3 /usr/local/bin/ingest_memory.py` | | "raise a PR" | `gh pr create --fill` in the relevant workspace repo |