This example shows the expected Codex setup for an initialized Repowise repository.
cd /path/to/your-repo
codex login status
repowise init --codex --index-only --yes # fast smoke: index only, no LLM wiki generation
repowise init --codex --provider codex_cli --yesrepowise init --codex --index-only is the quick setup smoke path. Drop --index-only when you want the full LLM-generated wiki. repowise init --codex writes project-local Codex files:
.codex/config.toml
.codex/hooks.json
AGENTS.md
It does not write to global ~/.codex/config.toml.
codex mcp list
codex exec --ephemeral --sandbox read-only --json "Return exactly OK"Inside Codex, start a new session in the repository and ask:
Use Repowise to summarize the architecture and identify risky files before editing.
Codex should have Repowise MCP available, load the managed AGENTS.md, and receive hook guidance from .codex/hooks.json.
From the Repowise repository root:
codex plugin marketplace add .
codex
/pluginsInstall the Repowise plugin from the local marketplace. The plugin bundles Repowise MCP, hooks, and Codex-neutral skills; it does not add slash commands. Plugin-bundled hooks require [features] plugin_hooks = true in current Codex releases.