A VS Code extension that brings spec-driven development to Codex CLI. Manage your specs, steering documents, and custom prompts visually while leveraging Codex CLI's powerful AI capabilities.
- Create Specs: generate requirements, design, and task documents with Codex CLI
- Visual Explorer: browse and manage specs in the sidebar
- Spec Workflow: Requirements -> Design -> Tasks with a review at each step
- CodeLens for Tasks: execute an individual task from
tasks.md
via Codex and auto-check it off
New in this release:
- Create New Spec UI: starting a spec opens a focused editor (webview) to enter your request before generation
- Steering Documents: browse and edit global/project-specific guidelines
- Generated Docs: product, tech, and structure steering documents
- Create Prompts: scaffold
.codex/prompts/<name>.md
from the Prompts view - Click to Open: clicking a prompt opens the Markdown for review
- Inline Run Button: use the ▶ action on the right to execute with Codex CLI
- Organize & Refresh: manage a workspace prompt library with quick refresh
- Markdown Simplicity: no front-matter required; write plain Markdown instructions
- Sidebar Chat (webview): start quick conversations with Codex inside VS Code
- Run once or stream: send a one-off message or stream via a dedicated Codex terminal session
- Stop anytime: terminate the active session from the Chat view
- AGENTS, HOOKS, MCP views: hidden in this build
- "New Spec with Agents" flow: disabled
The extension provides an organized sidebar for OVERVIEW, SPEC, STEERING, PROMPTS, and CHAT. Other views are hidden in this build.
- Codex CLI v0.28.0 or later installed and available on PATH
- VS Code 1.84.0 or later
Compatibility:
Platform | Support | Notes | Status |
---|---|---|---|
macOS | Yes | Fully supported | released |
Linux | Yes | Fully supported | released |
Windows (WSL) | Yes | Supported with conditional path conversion | released |
Windows (PowerShell) | Yes | Recommended on Windows | beta |
VS Code users:
- Open VS Code
- Go to Extensions (Cmd/Ctrl+Shift+X)
- Search for "Kiro for Codex"
- Click Install
Or via command line:
code --install-extension atman-33.kiro-for-codex
Download the latest .vsix
from GitHub Releases, then:
# VS Code
code --install-extension kiro-for-codex-{latest-version}.vsix
Replace {latest-version}
with the actual version number, e.g., 0.2.4
.
Recommended flow:
- Click the Kiro for Codex icon in the activity bar
- In the SPEC view, click
+ Create New Spec
- A webview editor opens; describe your feature/request
- The extension generates the requirements document with Codex CLI
- Review and approve before proceeding to design
- Generate tasks after design is complete
Tip: From tasks.md
, use the inline CodeLens action to execute a single task and auto-check it off.
- Requirements: define what you want to build
- Design: create technical design after requirements approval
- Tasks: generate implementation tasks after design approval
- Implementation: execute tasks one by one
Create project-specific guidance:
- Click the sparkle icon to create custom steering
- Generate initial docs (product, tech, structure)
- Documents are stored under
.codex/steering/
Create and run project prompts:
- Open the Prompts view in the activity bar
- Click
+ Create Prompt
to scaffold.codex/prompts/<name>.md
- Write instructions in Markdown (no front-matter required)
- Click the prompt item to open the file and review the content
- Press the inline ▶ Run button to execute the prompt with Codex CLI (split view)
Use the Chat view to quickly iterate with Codex:
- Open the Chat view under the Kiro activity container
- Type a message and choose run mode (send once or stream)
- For streaming, the conversation continues in a dedicated Codex terminal session
- Use Stop to end the active session
The Overview view provides quick access to settings, availability checks, and helpful entry points.
Core commands registered by the extension:
kiroCodex.spec.create
: Create a new spec (requirements -> design -> tasks)kiroCodex.spec.createWithAgents
: Disabled in this buildkiroCodex.spec.navigate.requirements
/kiroCodex.spec.navigate.design
/kiroCodex.spec.navigate.tasks
: Open spec documentskiroCodex.spec.implTask
: Run an individual task fromtasks.md
kiroCodex.spec.refresh
: Refresh the SPEC explorerkiroCodex.steering.create
: Create a custom steering documentkiroCodex.steering.generateInitial
: Analyze the project and generate initial steering docskiroCodex.steering.refine
: Refine an existing steering documentkiroCodex.steering.delete
: Delete a steering document and update docskiroCodex.prompts.create
/kiroCodex.prompts.run
/kiroCodex.prompts.refresh
: Manage and run promptskiroCodex.settings.open
: Open workspace settings file.codex/settings/kiroCodex-settings.json
kiroCodex.menu.open
: Toggle visibility of views (Specs / Steering; others when enabled)kiroCodex.codex.checkAvailability
: Check Codex CLI availability and versionkiroCodex.checkForUpdates
: Manually trigger the extension update checker
Project-local settings are stored in .codex/settings/kiroCodex-settings.json
and only contain paths. UI visibility and Codex runtime options live in VS Code settings under the kiroCodex.*
namespace.
Minimal settings file:
{
"paths": {
"specs": ".codex/specs",
"steering": ".codex/steering",
"settings": ".codex/settings",
"prompts": ".codex/prompts"
}
}
Notes:
- Only the
paths.*
values are honored by the extension at runtime. - Changing
paths.*
may require a window reload to take effect. - The location of
kiroCodex-settings.json
itself is fixed to.codex/settings/kiroCodex-settings.json
(editingpaths.settings
does not relocate the file).
The extension creates the following structure in your workspace:
.codex/ # Extension data directory
specs/ # Feature specifications
{spec-name}/
requirements.md # What to build
design.md # How to build
tasks.md # Implementation steps
prompts/ # Project prompts (Markdown)
<your-prompt>.md
steering/ # AI guidance documents
product.md # Product conventions
tech.md # Technical standards
structure.md # Code organization
settings/
kiroCodex-settings.json # Extension settings
- Node.js 16+
- VS Code 1.84.0+
- TypeScript 5.3.0+
# Clone the repository
git clone https://github.com/atman-33/kiro-for-codex.git
cd kiro-for-codex
# Install dependencies
npm install
# Compile TypeScript
npm run compile
# Watch mode (auto-compile on changes)
npm run watch
- Open the project in VS Code
- Press
F5
to launch Extension Development Host - The extension will be available in the new VS Code window
# Build VSIX package
npm run package
# Output: kiro-for-codex-{latest-version}.vsix
Build details:
- Extension bundling: esbuild (outputs
dist/extension.js
) - Webview UI: Vite (outputs
dist/webview/app/**
)
src/
extension.ts # Extension entry point, command registration
constants.ts # Configuration constants
features/ # Business logic (spec, steering, etc.)
providers/ # VS Code TreeDataProviders
services/ # Process/error managers and helpers
utils/ # Utilities
prompts/ # Prompt sources (generated artifacts under prompts/target)
types/ # Shared types
webview-ui/ # Webview source (React + Vite)
dist/webview/app # Built webview assets consumed by providers
- Vitest
- Run:
npm test
(watch:npm run test:watch
, coverage:npm run test:coverage
) - Target coverage for new code: >= 80%
- PowerShell is recommended on Windows (direct Codex CLI support)
- WSL is supported with conditional path conversion
This project is licensed under the MIT License. See the LICENSE file for details.
Kiro for Codex was inspired by the excellent "Kiro for CC" project for Claude Code by @notdp. This extension started as a port/adaptation from Claude Code's Kiro to a Codex CLI–focused workflow, carrying over the spec-driven development experience and UI while integrating tightly with Codex CLI.
- Original project: https://github.com/notdp/kiro-for-cc