Install the Ask The W Coding Plugin

Install Ask The W in Codex

These are the same setup steps shown on /plugin. The website cannot install the plugin for you; Codex asks you to confirm the install from its plugin UI or REPL.

1. Add the marketplace

Run this command once so Codex can discover Ask The W:

codex plugin marketplace add AskTheWAI/codex-plugin --ref main

2. Install in Codex

Install Ask The W from the askthew marketplace in the Codex Plugins UI, or open /plugins in the Codex REPL after adding the marketplace.

This step is manual: select Ask The W in Codex, confirm the install, then open a new Codex session in the repo you want connected.

The marketplace package exposes the installable plugin from its plugins/askthew entry. You should not need to edit Codex config files or plugin cache directories.

3. Connect your workspace

When Codex first uses Ask The W, it may ask you to complete setup. Follow the prompts in order:

1. Provide your email address.
2. Enter the six-digit verification code.
3. Open the browser confirmation URL.
4. Confirm the displayed code.
5. Wait until Codex reports that the workspace connection completed.

After connection, Ask The W keeps session signals, decisions, recaps, and coaching attached to the active workspace.

Recovery

If Ask The W does not appear after adding the marketplace, run codex plugin marketplace upgrade askthew, reopen /plugins, then install Ask The W from the askthew marketplace. If Codex still shows an old Ask The W card, uninstall Ask The W and install it again from that marketplace.

The setup steps above are the canonical entry points from /plugin. The rest of this guide covers what the install stores locally, how captures behave, and how to operate or troubleshoot the workspace connection.

The Codex marketplace plugin loads the Ask The W MCP runtime, stores local identity and diagnostics under ~/.askthew, and keeps workspace scope with each captured signal.

The tool surface includes capture_session_signal, signal reads, decision writes, recap, coach, signup, workspace connection, and identity or export commands depending on the current setup state.

Captures include workspace scope, session, sequence, and an idempotency key so retries can be ordered and deduplicated.

Workspace-connected installs use the workspace plan and keep abuse-protection limits in place.

Use askthew-mcp doctor, identity status, refresh, token rotate, token revoke, export, delete-me --confirm, and uninstall for ongoing operations.