Claude Code & Codex

Install the Fruxon plugin and build, test, and debug agents by asking Claude Code or Codex in plain language.

The fastest way to build on Fruxon is to let your coding agent do it. The Fruxon plugin teaches Claude Code and Codex how to work with Fruxon: when you ask for an agent, a fix, or an explanation of a run, they load the right playbook and drive the fruxon CLI for you. You describe the outcome; they discover the commands, write the definitions, test the draft, and read the traces.

Install

Install the CLI and sign in. The plugin drives the fruxon command, so it needs to be on your PATH.

pip install fruxon      # or: uv tool install fruxon / pipx install fruxon
fruxon login

Add the plugin to your coding agent.

Claude Code, inside a session:

/plugin marketplace add fruxon-ai/fruxon-agent-plugins
/plugin install fruxon@fruxon

Or from a terminal: claude plugin marketplace add fruxon-ai/fruxon-agent-plugins, then claude plugin install fruxon@fruxon.

Codex, from a terminal:

codex plugin marketplace add fruxon-ai/fruxon-agent-plugins
codex plugin add fruxon@fruxon

Or run /plugins inside Codex and pick Fruxon.

Start a new session. Plugins load when a session starts.

Try it

Ask for what you want; you don't need to name a skill or a command.

"Build a Fruxon agent that triages inbound support email and drafts a reply."
"Why did the last run of support-triage fail?"
"Connect our Jira integration to the release-notes agent."
"Add an integration for our internal billing API from its OpenAPI spec."

The agent works on the draft revision and tests with fruxon agents draft run, which runs as Origin=TEST and never touches production metrics or budgets. Deletes, approvals, and other costly or irreversible commands refuse to run for an agent unless it passes --yes explicitly, so they never happen as a side effect. Deploying is an ordinary command; ask the agent to check with you first if you want to approve each deploy.

What's inside

The plugin carries the same playbooks the CLI serves with fruxon guides show, packaged as skills your agent loads on demand:

Skill	Loaded when you want to
`fruxon-meet`	Get oriented: agents, revisions, integrations, and the main commands
`fruxon-build-agent`	Author, test, and deploy an agent
`fruxon-debug-trace`	Explain a run that failed, hung, or did the wrong thing
`fruxon-use-integrations`	Wire integration tools into an agent
`fruxon-create-integration`	Create a new integration and its tools
`fruxon-agent-mode`	Drive the CLI reliably: JSON output, NDJSON streams, typed exit codes

At the start of each session the plugin checks that fruxon is installed and not older than the playbooks, and tells the agent what to suggest if it is.

Secrets stay with you. The agent never sets credentials. When an integration needs an API key or OAuth, it hands off to you to enter it in the dashboard.

Keep it current

Each fruxon release updates the playbooks, and the plugin follows within a day. Upgrade the CLI alongside it so the commands the playbooks describe exist:

pip install --upgrade fruxon

To pull the newest plugin right away, run claude plugin update fruxon@fruxon, or codex plugin marketplace upgrade in Codex.

Other coding agents

Cursor, Aider, and other agents can drive the CLI too; they just don't load the playbooks on their own. Paste the bootstrap prompt from Drive it with your coding agent at the start of a session, and set FRUXON_AGENT_MODE=1 so the CLI answers in JSON.

CLI: every command the plugin drives, for when you want to run them yourself.
Python SDK: calling deployed agents from your application.
The plugin on GitHub: its source and how it stays in sync.