Use when Codex needs Genesis capabilities through MCP without joining Genesis's session lifecycle. Covers tool selection, explicit state changes, and session-boundary limits.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
This Codex conversation is not a Genesis session. It may call the Genesis MCP servers on demand, but Genesis must not register, heartbeat, extract, summarize, or otherwise manage this conversation. The external launcher removes inherited Genesis session identity, provenance, supervision, slot, and trace context before starting either MCP server. In a Git worktree it resolves Genesis's live runtime state through the main checkout rather than creating worktree-local state.
Codex defers MCP schemas until requested. Before calling a Genesis tool that is
not already visible, use MCP tool discovery for its exact server.tool name.
The initial Codex surface provides approved health and recall tools only. It does not expose persistent memory writes, task dispatch, browser control, outreach, Discord, recon, campaign management, or session controls. Do not work around this allowlist; expanding it needs a separate capability review.
The standalone launcher enforces --external-client on the server as well as
the client allowlist. Both the external default and explicit validator
profile currently expose the same health and recall floor. Direct calls to
other tools are rejected before their bodies run; the health bootstrap also
skips dispatch queue and campaign initialization. These tool profiles are not
authentication or isolation from an operator with full host access.
Do not pass a Codex thread or session identifier to session_charter,
session_ledger_*, or other session-bound tools. Those tools operate only on an
explicitly identified, existing Genesis session. Never create a synthetic session
or charter to make one work.
Use genesis-health for live status and genesis-memory for recall. Recall
may update Genesis retrieval-use metadata; this is expected and does not make
the conversation a Genesis session.
If a capability requires automatic context injection, transcript extraction, session continuity, or background delivery into this conversation, explain that it is unavailable to an external client. Do not add lifecycle hooks or work around the boundary.
The project also wires a local Codex CLI shell action guard for review budgets.
It denies actions requiring fresh approval and requests user handoff, without
registering a Genesis session or persisting approval receipts. See
docs/reference/codex-review-stop.md for activation, tested failures, scope and
integration limits; this is not universal client enforcement.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap
The English summary is being prepared. Showing the original description.
Canonical guide to Genesis browser automation - layers (Camoufox, Chromium, the user's Chrome over CDP, TinyFish, desktop), per-tool timeouts, safety gates, verify-after-act, what a click checks (scroll, hit test, covered targets), overlays, iframes, tabs, and failure diagnosis
The English summary is being prepared. Showing the original description.
This skill should be used when a session BUILDS one Genesis item: implementing a change in a worktree through to opening its PR, including rework from a send-back spec. Load `genesis-development` (the shared core) first. Do NOT load it for driving open PRs to merge (`closing-session`), post-merge verification (`validating-merges`), or specifying a change before it is planned (`spec-session`).
The English summary is being prepared. Showing the original description.
Update Claude Code (the CC CLI / "clog code") to a new version, or bump the pinned CC version. Use when the user asks to update Claude Code, bump the CC pin, evaluate a new CC release, or says "clog code update". Routes to the canonical, standardized process in docs/reference/cc-compatibility.md — do NOT re-derive the update mechanism by grepping every time. Do NOT use for general "what changed in CC" trivia with no intent to update.
The English summary is being prepared. Showing the original description.
This skill should be used when a session's job is to DRIVE OPEN PRs TO MERGE rather than to write new code — "close out the open PRs", "review and fix the open PRs", "what's blocking our PRs", "which PRs are mergeable". It owns the In Review column: it reads each PR's gate status, verifies and fixes review findings on PRs OTHER sessions built, replies in-thread, and merges a PR only under the owner's authorization: a per-PR yes, or the owner's request for closing work covering a PR whose every gate passes. Do NOT load it for building a feature and opening its PR — that is a build session (`build-session`).
The English summary is being prepared. Showing the original description.
Code understanding tool selection. Use when exploring architecture, finding definitions, tracing call chains, assessing blast radius of changes, or debugging code paths in the Genesis codebase.
The English summary is being prepared. Showing the original description.