Developers · build on Quox
Your code, on every QuoxCORE.
The route from a scaffolded plugin to a signed .quoxplugin and a reviewed marketplace listing. The SDK is in private preview, so the developer path is being rebuilt and the packages are not on npm yet. This page shows the route and how to get early access.
In plain words
What it is, where it lives, when to reach for it
- What is it
- The developer hub: the SDK, the protocols and the paths to build on the Quox platform.
- Where do I use it
- Start here, then follow each track to its own docs or tooling page.
- When would I use it
- When you want to build a plugin, a skill or an integration on the platform.
- How do I use it
- Pick a track below; the plugin SDK and the Developer Kit are free to start with.
The intended loop
Scaffold to signed package.
An illustration of the intended loop, not a recording: generate a project from a template, build it into a .quoxplugin, and sign it for verified distribution. The scaffolder runs in private preview only.
real commands from the SDK · the Plugin SDK page has the full toolchain →
Why build here
The platform is the distribution.
Community plugins list in the marketplace credited to their author, free or sold on your terms, and install on any QuoxCORE.
The format
One file. Everything inside.
A .quoxplugin is a ZIP archive. QuoxCORE extracts it, validates the manifest, and registers routes and sidebar entries automatically.
- manifest.json Metadata, the permissions your plugin declares, sidebar config.
- plugin.esm.js Compiled ESM bundle. React is externalised and shared by the host.
- plugin.css Optional scoped styles.
- signature.json Optional Ed25519 signature over the manifest. Cryptographically checked when the installing organisation has pinned a publisher key.
my-plugin.quoxplugin/ ├── manifest.json ├── plugin.esm.js ├── plugin.css ├── assets/ │ └── icon.svg └── signature.json # signed · Ed25519 · over the manifest
Where your work fits
Four kinds of add-on, clearly labelled.
No one should have to guess which is which. Plugins you build with the SDK list as Community plugins, credited to you.
Core
Ships inside every QuoxCORE install. Always present, no purchase, cannot be removed. QuoxCORE itself is the platform runtime, not a plugin.
Installable
Added from the marketplace when you want it. Toggle on and off.
Quox-installable
Quox-made, but a genuine install: a daemon, service or desktop app.
Community
Built by an outside developer and credited to its author. Listing is not open yet.
Sell what you build. Community plugins can be listed free or sold through the storefront. Browse the marketplace →
Publishing
From your repo to a listing.
This is the shape publishing takes. The automated gate runs today; listing and staffed human review are not open yet, and the trust model page → says exactly where each part stands.
Build you
npm run build produces the .quoxplugin ZIP: bundle, manifest, styles and optional signature.
Upload you
In QuoxCORE, the seller dashboard takes the file and a version number.
Automated review gate 1
Runs instantly: manifest validation, ID format, bundle size limits, blocked code patterns. Results in seconds. It does not check the signature.
Human review gate 2
Designed, not staffed. The approve and reject step exists in the platform and belongs to an instance administrator; there is no Quox review team reading submissions today.
Live marketplace
Users discover, install, review and rate your work.
seller trust ladder:registered→developer→verified→trusted partner
AI pair
Your Claude already knows the SDK.
The private-preview SDK includes a Claude Code skill that understands the whole QuoxCORE plugin architecture. Copy it into your skills directory and ask in plain language.
Quox as a Claude extension
Point your Claude at Quoxpert. It becomes a Quox expert.
Quoxpert is a distributable Claude skill. Once installed, your Claude (Claude Code, Claude Desktop, claude.ai, or the Agent SDK) knows how to operate Quox: the CLI, the MCP tools, workflows, the agent fleet, plugins, and the four governance protocols.
Early access until launch. Quoxpert is not publicly installable yet: the repository is private, early-access customers get access with the installer, and public install commands will be published at launch.
Meet Quoxpert and its early access status →
Open protocols
Build against the specs, not the app.
Four open protocol drafts underpin everything a plugin or agent does on Quox. Each has its own documentation.
Quickstart
The intended path to a running plugin.
Scaffold, develop, build, sign. These commands work from a private-preview SDK checkout only. The packages are not on npm yet and will be published under the @quoxai scope.
npx create-quox-plugin my-pluginStart now
Ship something this afternoon.
Scaffold a plugin, run it locally, sign it, and put it in front of a customer. What signing proves and what the marketplace does not do yet are both written down →.
Go deeper