ask-pro

ask-pro gives coding agents a focused ChatGPT Pro second opinion through a human-logged-in browser. The calling agent supplies the context and owns the result; ask-pro never applies generated code.

Install

Both options need Node.js 24+, Chrome, and a ChatGPT account with Pro access. Browser login is manual.

Codex plugin marketplace

codex plugin marketplace add JJLiebig/ask-pro
codex plugin add ask-pro@ask-pro

This route needs Git and npm. The plugin's cached runner downloads pnpm, builds outside the plugin cache, and keeps the installed snapshot unchanged. If ask-pro is not on PATH, the skill uses that runner.

Update with codex plugin marketplace upgrade ask-pro, then restart Codex to load the updated skill.

Skills CLI (Codex and other supported agents)

Install the skill and its standalone CLI separately:

npx skills add JJLiebig/ask-pro
npm install --global ask-pro

The skills CLI installs the skill in the current project by default. Add -g for a user-wide skill or -a codex to select Codex; it supports other agents too. The npm CLI runs without Codex's plugin cache.

Update both parts:

npx skills update
npm update --global ask-pro

The browser runtime is developed and tested on Windows. Other operating systems need validation.

Browser and session state

ask-pro never asks for, types, reads, or logs passwords, MFA codes, recovery codes, session cookies, or raw auth tokens. A new browser profile may need one manual ChatGPT login. On Windows, ordinary managed Chrome runs start minimized and are hidden; login and recovery restore the window for human action.

The persistent profile lives at $CODEX_HOME/state/ask-pro/browser-profile, or ~/.codex/state/ask-pro/browser-profile when CODEX_HOME is unset. Existing legacy profiles are migrated on first use; see Windows notes for copy and recovery details.

Project sessions live under .ask-pro/sessions/<id>/. Add .ask-pro/ to your project's .gitignore. At each invocation, ask-pro deletes entire session directories at least seven days old, regardless of state.

Use

Ask for a recoverable repo consult:

ask-pro --no-temporary --prompt-file question.md --files src --files tests

ask-pro selects Latest with Pro intelligence. It has no repo or conversation context unless you provide it, so keep the prompt and file bundle focused.

Request generated files only when needed; treat them as data and never execute them automatically:

ask-pro --artifacts --prompt-file implementation-plan.md --files src
ask-pro --harvest <session-id>

Use ask-pro --help for the full CLI. For multiline prompts, use --prompt-file. Prefer --no-temporary when recovery matters; --temporary requires Temporary Chat. The skill has agent guidance.

Development

pnpm install --frozen-lockfile
pnpm run build
pnpm run lint
pnpm test
pnpm run format:check
pnpm pack --dry-run

After changing plugin files, run pnpm run plugin:refresh and restart Codex. Do not edit the installed plugin cache. Live browser tests are opt-in; see manual tests.

After the build matrix passes on main, CI publishes a new npm version through the configured trusted publisher, without a stored npm token.