AWC: Agent Workbench for Codex CLI (Unofficial)
Agent Workbench (AWC) is an independent, unofficial VS Code client built exclusively for the OpenAI Codex CLI. It provides an editor-first interface for managing chats, tool runs, approvals, and diffs.
AWC is not affiliated with, sponsored by, or endorsed by OpenAI. OpenAI and Codex are trademarks of their respective owner.
What's new in 1.8
AWC 1.8 adds Remote access from your phone, dedicated browser tabs inside VS Code, an image workspace, and richer chat and goal controls.
- Remote: pair a mobile device to access chats, attachments, modes, goals, and supported approvals.
- Browser: browse pages, share page context, annotate elements, and attach screenshots.
- Rich chat: edit images, render math and Mermaid diagrams, and answer structured questions.
- Workflow: queue goals and restore messages, skill mentions, and session history more reliably.
View the full changelog.
Highlights
- Editor-first Codex workflow — manage chats, approvals, tool runs, inline diffs, and undo checkpoints without leaving VS Code.
- Precise context sharing — attach files, selected code, images, and annotated chat or diff excerpts directly to a request.
- Isolated worktree agents — run tasks independently in Git worktrees, compare their results, and apply the result you choose.
- Multi-agent orchestration — coordinate substantial tasks across specialized agents while keeping progress and results visible in one place.
- Continuous conversations — switch and restore sessions, then queue or steer follow-up messages while work is running.
Installation
AWC automatically downloads the Codex CLI version approved for the installed
AWC release and verifies the download. Running chats are not restarted by an
update; the approved version is selected on the next connection. Initial setup
requires access to GitHub releases. Sign in to Codex to start using it.
You can also use an existing Codex installation:
- Install the official Codex extension for VS Code and sign in to Codex.
- Install and authenticate the standalone Codex CLI. Set
awc.cliExecutable to use that executable instead of the managed CLI.
Disable awc.managedCodexRuntime to use the official extension or PATH
without automatic runtime downloads. If managed installation fails, AWC falls
back to a previously installed managed version or an existing Codex installation.
Then install AWC: Agent Workbench for Codex CLI (Unofficial) from the Visual Studio Marketplace, or run:
code --install-extension yonnq.awc
Marketplace extension ID: yonnq.awc
Requirements
- VS Code 1.90 or later
- A trusted local workspace
- Either the official Codex extension for VS Code or an authenticated standalone Codex CLI
- At least 2 GB of free disk space recommended for installation and the optional browser runtime
The extension can run commands and read or modify files, so it does not run in Restricted Mode.
Getting started
- Run
AWC: Open from the Command Palette.
- Select the model, reasoning effort, and execution mode for your project.
- Send a message to start a new chat.
Use the Agent Workbench button in the editor title bar to open another panel. You can attach selected code with Add to Codex Thread or attach the active file with Add File to Codex Thread.
AWC includes AWC Guide ($awc-guide) for feature help and troubleshooting.
On startup it manages one skills/awc-guide folder under CODEX_HOME (or
~/.codex), skips unchanged files, and preserves an existing unmanaged or
user-modified guide. No versioned skill copies are created.
Features
- Account and session integration through the Codex
app-server
- Per-session model, reasoning effort, and IDE Context settings
- Plan, Ask, and Full execution modes
- Command and file-change approvals
- Inline diffs and editable native VS Code diffs
- Chat creation, switching, branching, renaming, archiving, and deletion
- Follow-up queue and steer behavior while a run is active
- Skills, plugins, and MCP status
- Context usage and account rate-limit displays
- Undo checkpoints for code changes
Remote
Open /remote in AWC, sign in, and use Connect device to create a pairing QR code. Open the AWC Remote download page on your phone to download the Android APK for Android 7.0 or later on ARM64 devices. The desktop download page also provides a QR code for opening it on your phone.
Sign in on the mobile device, scan the pairing code, and approve its access on the PC. Device permissions can be changed or revoked in the Remote popup. Automatic approval for new devices is disabled by default; enabling it grants all Remote permissions to newly approved connections and leaves existing device permissions unchanged.
For Galaxy installation warnings, follow the download page's Security Policy update guidance. Keep device security protections enabled.
Browser
Run AWC: Open Browser from the Command Palette to open a browser tab inside VS Code. Share a page with the agent, select and annotate elements, or attach a page or area screenshot to a conversation. Navigation history and closed-tab restoration are available from the browser controls.
The browser downloads its Electron rendering runtime when you select Install Browser and reuses it across extension updates. The runtime is not included in the VSIX; an internet connection is required for the initial download. Manage it in Agent settings → Runtime: Remove runtime asks for confirmation, closes browser tabs, and deletes Electron while keeping browsing history. AWC: Open Browser remains available and opens a setup page when installation is needed.
Agents
Worktrees
Use /worktree to run a task in isolated Git worktrees. Agents work independently from the selected base branch, and you can review their results before applying changes to your current checkout.

Orchestration
Use /orchestration to explicitly coordinate a message. The coordinator determines how to divide the task, delegates suitable work to agents, and may complete simple requests without workers.
AWC can also start orchestration automatically when a task has at least two substantial, independent worker assignments. Automatic orchestration is enabled by default and can be turned off in Agent settings > Automatic orchestration. Manual /orchestration remains available when automatic orchestration is disabled.

Permissions and data
Agent Workbench may perform the following operations to provide its features:
- Read files and selected text in the current workspace
- Create, modify, or delete files after user approval
- Run the Codex CLI and approved commands
- Read Codex account, session, usage, and plugin information
- Store session metadata and undo checkpoints in VS Code extension storage
- Connect paired mobile devices and relay Remote traffic through the configured service
- Store browser history and site data in the browser profile when Browser is enabled
The extension does not collect its own analytics, advertising data, or tracking telemetry. Prompts, attached context, commands, and tool requests may be processed according to the policies of the Codex CLI and any connected services. See the public Privacy Policy for details.
Settings
awc.cliExecutable: path to the Codex executable
awc.openOnStartup: open Agent Workbench when VS Code starts
awc.browserEnabled: enable browser tabs and Browser commands (enabled by default)
awc.remote.autoApproveNewDevices: automatically grant all Remote permissions to new devices (disabled by default)
awc.ideContextEnabled: include the active file or selection
awc.followUpQueueMode: use Queue or Steer for follow-up messages
awc.reviewDelivery: show reviews Inline or Detached
awc.automaticOrchestrationEnabled: allow Codex to start orchestration automatically for suitable tasks
awc.runCodexInWindowsSubsystemForLinux: run Codex through WSL on Windows
openOnStartup is disabled by default for public distribution.
License
See the included LICENSE for the project license and the public Third-Party Notices for bundled third-party components.
Report security issues using the process in the public Security Policy, not through a public issue.