@@ -69,7 +69,7 @@ Mění se i ladění. Místo kopírování stack trace do chatu řeknete "koukni
 Agent, který zná Nette
 ======================
 
-**[Plugin pro Claude Code |agent-plugins]** dodá to, co ve vašem kódu nikde nenajde: jak se věci v Nette dělají. Celá rodina skills pokrývá architekturu, formuláře, databázi, komponenty, bezpečnost, Latte, NEON a další. Každý se zapne sám, jakmile na jeho téma přijde řeč. Zeptáte se na validaci formuláře a naskočí skill pro formuláře. Zeptáte se na BlueScreen a naskočí ten pro Tracy.
+**[Pluginy pro Claude Code a Codex |agent-plugins]** dodají to, co ve vašem kódu nikde nenajde: jak se věci v Nette dělají. Celá rodina skills pokrývá architekturu, formuláře, databázi, komponenty, bezpečnost, Latte, NEON a další. Každý se zapne sám, jakmile na jeho téma přijde řeč. Zeptáte se na validaci formuláře a naskočí skill pro formuláře. Zeptáte se na BlueScreen a naskočí ten pro Tracy.
 
 Výsledek vypadá, jako by ho psal někdo, kdo Nette dělá roky, ne jako obecné PHP poslepované z útržků.
 
@@ -80,7 +80,7 @@ Jak začít
 Celé nastavení zabere zhruba deset minut:
 
 1. [Nainstalujte si AI nástroj |getting-started], doporučujeme Claude Code
-2. [Přidejte plugin pro Nette |agent-plugins], aby agent znal framework
+2. [Přidejte pluginy pro Nette |agent-plugins], aby agent znal framework
 3. [Nastavte MCP Inspector |mcp-inspector], aby znal *vaši* aplikaci
 
 Pak už jen popište, co chcete, zavřete agenta do smyčky a nechte ho pracovat. Až budete chtít z agenta vytěžit víc, přečtěte si [Vibe coding v praxi |vibe-coding].
 
@@ -1,5 +1,5 @@
 - [Úvod |@home]
 - [Začínáme |getting-started]
-- [Plugin pro Claude Code |agent-plugins]
+- [Pluginy pro agenty |agent-plugins]
 - [MCP Inspector |mcp-inspector]
 - [Vibe coding v praxi |vibe-coding]
@@ -222,7 +222,7 @@ AI je opravdu dobrá, ale pořád je to asistent. Za výsledný kód zodpovídá
 Ignorovat hlášení linteru
 -------------------------
 
-Pokud používáte [pluginy pro Claude Code |agent-plugins], kontrolují vám automaticky soubory PHP, Latte, NEON, JSON i JavaScript. Když některý ohlásí chybu, AI o ní ví. Místo ručního opravování prostě řekněte:
+Pokud používáte [pluginy pro Claude Code nebo Codex |agent-plugins], kontrolují vám automaticky soubory PHP, Latte, NEON, JSON i JavaScript. Když některý ohlásí chybu, AI o ní ví. Místo ručního opravování prostě řekněte:
 
 ```
 Oprav chybu, kterou jsi právě udělal.
 
@@ -69,7 +69,7 @@ Debugging changes shape too. Instead of copying a stack trace into a chat window
 Nette Knowledge, Built In
 =========================
 
-The **[Claude Code plugin |agent-plugins]** supplies the part that is nowhere in your codebase: how things are actually done in Nette. A whole family of skills covering architecture, forms, database, components, security, Latte, NEON and more, each one switching itself on when the conversation turns to its topic. Ask about form validation and the forms skill wakes up. Ask about a BlueScreen and the Tracy one does.
+The **[plugins for Claude Code and Codex |agent-plugins]** supply the part that is nowhere in your codebase: how things are actually done in Nette. A whole family of skills covering architecture, forms, database, components, security, Latte, NEON and more, each one switching itself on when the conversation turns to its topic. Ask about form validation and the forms skill wakes up. Ask about a BlueScreen and the Tracy one does.
 
 What comes out reads like an experienced Nette developer wrote it, not like generic PHP stitched together from snippets.
 
@@ -80,7 +80,7 @@ Get Started
 The whole setup takes about ten minutes:
 
 1. [Install your AI tool |getting-started] - we recommend Claude Code
-2. [Add the Nette plugin |agent-plugins] so the agent knows the framework
+2. [Add the Nette plugins |agent-plugins] so the agent knows the framework
 3. [Set up MCP Inspector |mcp-inspector] so it knows *your* application
 
 Then describe what you want, close the agent into the loop, and let it work. When you want to get more out of your agent, read [Vibe Coding in Practice |vibe-coding].
 
@@ -1,5 +1,5 @@
 - [Overview |@home]
 - [Getting Started |getting-started]
-- [Claude Code Plugin |agent-plugins]
+- [Agent Plugins |agent-plugins]
 - [MCP Inspector |mcp-inspector]
 - [Vibe Coding in Practice |vibe-coding]
@@ -1,11 +1,11 @@
-Claude Code Plugin
-******************
+Nette Plugins for Claude Code and Codex
+***************************************
 
 <div class=perex>
 
-The "Nette plugin for Claude Code":https://github.com/nette/agent-plugins gives deep knowledge of the framework. Instead of generic PHP advice, you get recommendations that follow Nette conventions - from presenters and forms to Latte templates and database queries.
+The "Nette plugins":https://github.com/nette/agent-plugins give Claude Code and Codex deep knowledge of the framework. Instead of generic PHP advice, you get recommendations that follow Nette conventions - from presenters and forms to Latte templates and database queries.
 
-Together with its companion plugins, you get:
+The same plugins work in both tools and give you:
 - A **broad set of skills** covering all major areas of Nette development
 - **Automatic validation** of PHP, Latte, NEON, JSON and JavaScript files (the `nette-lint` plugin)
 - **MCP Inspector integration** for real-time application introspection
@@ -16,7 +16,20 @@ Together with its companion plugins, you get:
 Installation
 ============
 
-If you haven't installed Claude Code yet, see the [complete setup guide |getting-started]. Once Claude Code is running, install the Nette plugin:
+The plugins come as a family, so you install only what you need:
+
+| Plugin | Purpose |
+|--------|---------|
+| `nette` | Skills with deep framework knowledge |
+| `nette-lint` | Automatic validation of PHP, Latte, NEON, JSON and JavaScript |
+| `php-fixer` | Automatic PHP code style fixing (optional) |
+| `nette-dev` | Coding standards for framework contributors |
+
+
+Claude Code
+-----------
+
+If you haven't installed Claude Code yet, see the [complete setup guide |getting-started]. Once Claude Code is running, add the Nette marketplace and install the main plugin:
 
 ```shell
 /plugin marketplace add nette/agent-plugins
@@ -29,14 +42,20 @@ For automatic validation of your PHP, Latte, NEON, JSON and JavaScript files aft
 /plugin install nette-lint@nette
 ```
 
-The full family of plugins:
 
-| Plugin | Purpose |
-|--------|---------|
-| `nette` | Skills with deep framework knowledge |
-| `nette-lint` | Automatic validation of PHP, Latte, NEON, JSON and JavaScript |
-| `php-fixer` | Automatic PHP code style fixing (optional) |
-| `nette-dev` | Coding standards for framework contributors |
+Codex
+-----
+
+In Codex, add the same marketplace from the command line and install the main plugin:
+
+```shell
+codex plugin marketplace add nette/agent-plugins
+codex plugin add nette@nette
+```
+
+The other plugins are installed the same way, for example `codex plugin add nette-lint@nette`. Then start a new session so Codex picks them up.
+
+There is one extra step for the plugins that check or fix your files. Codex doesn't run a plugin's hooks just because you installed it; you have to approve them first. Open `/hooks` in Codex, review the hook definitions of the installed plugins and trust them. When a plugin update changes its hooks, you have to review them again.
 
 
 How Skills Work
@@ -49,7 +68,7 @@ You don't need to activate skills manually. They turn on automatically based on
 - Ask about "Latte filters" → the `latte-templates` skill activates
 - Ask about a "BlueScreen error" → the `tracy-debugging` skill activates
 
-This means you get relevant, context-aware help without having to think about which skill you need.
+This means you get relevant, context-aware help without having to think about which skill you need. The skills are identical in both clients, so whenever the examples below say Claude, the same applies to Codex.
 
 
 Available Skills
@@ -318,9 +337,11 @@ One of the most useful features is automatic validation, provided by the separat
 | **JSON / JSONC** | Validates syntax after every `.json` or `.jsonc` edit and reports the exact line; comments and trailing commas are tolerated in JSONC files like `tsconfig.json` or `.vscode/*.json` |
 | **JavaScript / TypeScript** | Runs `eslint --fix` after every `.js`, `.ts`, `.mjs` or `.mts` edit (only if the project has an ESLint config) |
 
-If there's a syntax error in any of these files, Claude knows about it immediately and can suggest a fix. No more discovering errors in the browser.
+If there's a syntax error in any of these files, the agent knows about it immediately and can suggest a fix. No more discovering errors in the browser.
+
+The checks run after the agent edits a file with its own editing tools. When it changes files through shell commands instead, no hook runs, so it's worth asking it to run your project's checks afterwards.
 
-The plugin looks for the project's tools and configs (`latte-lint`, `vendor/bin/neon-lint`, the ESLint config) upwards from the edited file, not just in the folder where Claude Code is running. So even if you keep several applications in one repository and run Claude Code from its root, each file is still checked with the right tool for its application. The search stops one level above the nearest `.git` folder, so tools from unrelated projects elsewhere on the disk are never picked up.
+The plugin looks for the project's tools and configs (`latte-lint`, `vendor/bin/neon-lint`, the ESLint config) upwards from the edited file, not just in the folder where the agent is running. So even if you keep several applications in one repository and start the agent from its root, each file is still checked with the right tool for its application. The search stops one level above the nearest `.git` folder, so tools from unrelated projects elsewhere on the disk are never picked up.
 
 Sometimes you don't want a file checked - for example `fixtures` with intentionally broken templates or code used in tests. You can skip specific paths by creating a `.nette-claude.json` file in your project, where each key is a hook name with a list of paths to ignore:
 
@@ -344,7 +365,8 @@ Plugin for Framework Contributors
 If you're contributing to Nette itself, there's an additional plugin with coding standards:
 
 ```shell
-/plugin install nette-dev@nette
+/plugin install nette-dev@nette           # Claude Code
+codex plugin add nette-dev@nette          # Codex
 ```
 
 | Skill | What It Covers |
@@ -358,14 +380,14 @@ If you're contributing to Nette itself, there's an additional plugin with coding
 Automatic PHP Style Fixing
 ==========================
 
-For automatic code style fixing after every PHP file edit, install the optional php-fixer plugin:
+For automatic code style fixing after every PHP file edit, install the optional php-fixer plugin. In Claude Code:
 
 ```shell
 /plugin install php-fixer@nette
 /install-php-fixer
 ```
 
-The second command installs `nette/coding-standard` globally. After that, every PHP file you edit will be automatically formatted according to Nette coding standards.
+The second command installs `nette/coding-standard` globally. In Codex, install the plugin with `codex plugin add php-fixer@nette` and then pick the `install-php-fixer` skill, which does the same. After that, every PHP file you edit will be automatically formatted according to Nette coding standards.
 
 Because the fixer **rewrites your files**, it's important to keep it away from code you don't want reformatted - typically `fixtures` with intentionally crafted formatting. Exclude such paths with a `fix-php-style` entry in `.nette-claude.json`:
 
@@ -397,7 +419,7 @@ The plugin also comes with the `php-auto-fixer` skill, which teaches Claude abou
 MCP Inspector Integration
 =========================
 
-The plugin works even better with [MCP Inspector |mcp-inspector] - a tool that lets Claude see your actual application state. With MCP Inspector, Claude can:
+The plugins work even better with [MCP Inspector |mcp-inspector] - a tool that lets the agent see your actual application state. With MCP Inspector, Claude can:
 
 - Query your real database schema instead of guessing
 - List your registered DI services and their configuration
@@ -411,6 +433,6 @@ composer require --dev nette/mcp-inspector:@dev
 vendor/bin/mcp-inspector init
 ```
 
-Then restart Claude Code. See the [MCP Inspector documentation |mcp-inspector] for all the available tools.
+Then restart Claude Code. Codex isn't registered by `init`, so add the server to its configuration yourself as described in [Other AI Tools |mcp-inspector#other-ai-tools]. See the [MCP Inspector documentation |mcp-inspector] for all the available tools.
 
 {{repo: nette/agent-plugins}}
@@ -42,10 +42,10 @@ curl -fsSL https://claude.ai/install.sh | bash
 On macOS, you can alternatively use Homebrew:
 
 ```shell
-brew install --cask agent-plugins
+brew install --cask claude-code
 ```
 
-After installation, skip to [Starting Claude Code |#starting-agent-plugins].
+After installation, skip to [Starting Claude Code |#starting-claude-code].
 
 
 Installation on Windows via WSL
@@ -233,7 +233,7 @@ Cursor is a popular AI-first code editor. To use MCP Inspector with Cursor:
 
 3. Restart Cursor
 
-Note: Cursor doesn't have the Nette-specific skills that the Claude Code plugin provides, but MCP Inspector will still give it access to your application's services, database, routes, and logs.
+Note: Cursor doesn't have the Nette-specific skills that the [Nette plugins |agent-plugins] provide, but MCP Inspector will still give it access to your application's services, database, routes, and logs.
 
 
 VS Code
@@ -254,7 +254,7 @@ What's Next
 You're now ready for AI-assisted Nette development! Here's where to go from here:
 
 - [MCP Inspector |mcp-inspector] - Learn about every introspection tool
-- [Claude Code Plugin |agent-plugins] - Explore all the skills (Claude Code users)
+- [Agent Plugins |agent-plugins] - Explore all the skills (Claude Code and Codex users)
 - [Vibe Coding in Practice |vibe-coding] - Get the most out of your AI assistant
 
 {{description: Set up vibe coding with Nette in about ten minutes: install Claude Code, add the Nette plugin, and connect MCP Inspector to your application.}}
@@ -222,7 +222,7 @@ AI is very good, but it's still an assistant. You're the developer responsible f
 Ignoring Validation Feedback
 ----------------------------
 
-If you're using the [Claude Code plugins |agent-plugins], they validate your PHP, Latte, NEON, JSON and JavaScript files automatically. When one reports an error, the AI knows about it. Instead of manually fixing the error, just say:
+If you're using the [Nette plugins for Claude Code or Codex |agent-plugins], they validate your PHP, Latte, NEON, JSON and JavaScript files automatically. When one reports an error, the AI knows about it. Instead of manually fixing the error, just say:
 
 ```
 Fix the error you just created.
 
@@ -21,7 +21,7 @@ Kvalita kódu
 
 Umělá inteligence
 -----------------
-- [Claude Code plugin |https://ai.nette.org/en/agent-plugins] naučí Claude Code konvence Nette: skills, automatická validace Latte/NEON/JS a integrace MCP.
+- [Pluginy pro Claude Code a Codex |https://ai.nette.org/en/agent-plugins] naučí AI agenty konvence Nette: skills, automatická validace Latte/NEON/JS a integrace MCP.
 - [MCP Inspector |https://ai.nette.org/en/mcp-inspector] zpřístupní AI reálný stav aplikace: DI služby, schéma databáze, routy i Tracy logy.
 
 
 
@@ -21,7 +21,7 @@ Code Quality
 
 Artificial Intelligence
 -----------------------
-- [Claude Code plugin |https://ai.nette.org/en/agent-plugins] teaches Claude Code the Nette conventions: skills, automatic validation of Latte/NEON/JS, and MCP integration.
+- [Plugins for Claude Code and Codex |https://ai.nette.org/en/agent-plugins] teach AI agents the Nette conventions: skills, automatic validation of Latte/NEON/JS, and MCP integration.
 - [MCP Inspector |https://ai.nette.org/en/mcp-inspector] gives AI the real state of your application: DI services, database schema, routes and Tracy logs.