Sellable Installer

Installs Sellable MCP for Claude Code and Codex.

npx -y @sellable/install@latest --host all

Paste that command in your terminal, not inside the Codex chat. Mac/Linux users can use Terminal. Windows users can use PowerShell or Windows Terminal; if PowerShell blocks npx, run:

npx.cmd -y @sellable/install@latest --host all

After install, restart Codex Desktop so the Sellable skill appears.

After install, sellable create is a terminal helper that prints the correct agent command for launching a campaign:

sellable create

Campaign creation itself runs inside Claude Code or Codex, where the Sellable MCP tools and approval flow are available.

Install is auth-free by default. If you do not pass a token, the agent handles Sellable sign-in on the first campaign run with a magic-link handoff.

The installer uses package stdio MCP by default:

npx -y @sellable/mcp@latest

That keeps new Claude Code/Codex MCP starts on the latest stable package. The MCP server also checks npm at startup and during get_auth_status, caching the result at ~/.sellable/update-check.json so users are prompted to rerun the latest installer only when an update is actually available.

For CI/scripted installs, get a Sellable API token from:

https://app.sellable.dev/settings

Then pass it with --token / SELLABLE_TOKEN plus --workspace-id / SELLABLE_WORKSPACE_ID.

Auth is stored once at:

~/.sellable/config.json

Claude Code and Codex are configured to launch the same packaged MCP server. The installer also writes Sellable agent definitions from the packaged agents/ registry, but normal create-campaign runs use only the Message Drafting background agent (post-find-leads-message-scout). Source discovery and filter/rubric setup stay in the parent thread with product-native MCP tools. get_post_find_leads_scout_registry returns the Message Drafting worker for the normal path; get_source_scout_registry intentionally returns no custom source-scout agents.

Names

Use the same public entrypoints in both hosts:

• Claude Code: /sellable:create-campaign
• Claude Code: /sellable:interview
• Claude Code: /sellable:load-voice
• Codex: $sellable:create-campaign
• Codex: $sellable:interview
• Codex: $sellable:load-voice
• Codex Desktop plugin: sellable@sellable
• Codex visible skill: Sellable Create Campaign
• Codex visible skill: Sellable Identity Interview
• Codex visible skill: Sellable Load Voice
• Internal MCP workflow prompt: create-campaign-v2

Do not ask users to run /sellable:create-campaign-v2, $sellable:create-campaign-v2, or $sellable:sellable:create-campaign. create-campaign-v2 is loaded internally by the skill.

Structured Questions

Claude Code uses AskUserQuestion. Codex uses request_user_input when that tool is exposed in an interactive session. The installer enables Codex Default mode support by writing default_mode_request_user_input = true under [features] in ~/.codex/config.toml. codex exec is non-interactive, so it cannot show the structured questionnaire UI.

For Codex Desktop, the installer also writes a local Sellable plugin bundle into ~/.sellable/codex-marketplace, includes the Sellable skill entrypoints, and enables it in ~/.codex/config.toml.

Create-Campaign Soul

The create-campaign workflow includes a SOUL.md identity for the Sellable campaign GTM engineer. It keeps the UX focused on launching a campaign: quick setup questions, campaign brief, lead sourcing, message review, and approval. It uses the phrase quick question panel for structured intake and approvals. It also tells the agent not to expose prompt-loading, MCP, plugin-cache, or tool names in normal customer-facing progress updates.

The installer writes compatibility cache aliases for recent Codex plugin versions so stale Desktop skill links resolve to the current wrapper instead of showing file/version debugging to the user.

If only one host is installed, --host all installs the available host and tells you how to add the other one later.