genesis-external-clientlisted
Install: claude install-skill WingedGuardian/GENesis-AGI
# Genesis from Codex
An owner-operated Codex session gets the same Genesis MCP servers and tools a
Claude Code session gets: health, memory, outreach and recon, with no client
allowlist (owner ruling, 2026-11-08). `scripts/codex_owner_mcp.py` starts the
ordinary server and labels it `codex`, so every tool call is recorded in
`client_tool_calls` and credential lookups are stamped `client=codex`, once the
database has that table and column (migration `20261108071709`; until it runs,
calls are served and a warning is logged instead). The label
is a record of which client acted, never a permission. In a Git worktree the
launcher resolves Genesis's live runtime state through the main checkout.
Approvals: read tools are pre-approved; anything that writes, sends, spends or
spawns asks before it runs, and so does any tool not yet classified in
`.codex/config.toml`. That holds only under an approval policy that can ask:
started with `--dangerously-bypass-approvals-and-sandbox`, Codex runs every
tool without asking (measured, codex-cli 0.166.0), as Claude Code does under its
skip-permissions mode. Genesis's own gates (the payment tap, outreach rules,
board and contributor approvals) still apply on top. `browser_fill_card` asks
first like any spending tool; the payment vault's peer check may also refuse a
Codex-started server, and the owner's per-payment Telegram tap is the control
that always applies.
A Codex run that Genesis starts unattended (the executor's verifier, the
contribut