For developers · Plugin SDK on GitHub
Build on Quox, then ship it.
An SDK, signed plugins and a set of tools for working with governed agents.
Start here.
Four doors into building on the platform. Most people begin with the first.
SDK overview
Protocols, SDKs, plugin and marketplace in one place.
Plugin SDK
Build plugins with their own governed backends.
QuoxProof
Signed, offline-verifiable receipts for every agent tool call.
Developer Kit
Everything you need to build on the platform.
More ways to build
The SDK, in three lines.
What you get when you install it.
- Public on GitHubSource
- 8Templates
- Ed25519Signing
Signed plugins show a Signed badge in the QuoxCORE plugin manager. Read what a signature does and does not prove in the marketplace trust model.
Ship it, and share it.
Where a built plugin goes, and the protocols underneath it.
The Dev Suite, and the loops.
Tools for the day job: governed dev servers, and the workflows that run on them.
Dev Suite
Quox Dev Suite
The bundle: every member here, on one governed dev server.
QuoxBuild
The build queue as a product: serialised and witnessed.
QuoxSlots
A durable address for every agent session.
Shared skills and rules
One governed skill pack, every machine, both backends.
Qlarity
Governed browser inspection: seven named inspectors, every look logged.
Dev workflow
RepoBrain
Code intelligence with file and line citations, not a file dump.
Gripe
A one-line complaint becomes a tracked issue, with context.
Triage
The agent that works the inbox and asks before it applies a fix.
FixLoop
Bug to passing test, minimal fix, and a stop after three tries.
ProofLoop
From a claim to shipped evidence, with the gaps filed.
DoneEngine
Is this done, and on what evidence? Two finish lines.
What exists, what does not.
Real today
- The Plugin SDK is public on GitHub (quoxai/quox-plugin-sdk), with eight scaffolder templates. It is not published to npm.
- Plugins are signed with Ed25519. The marketplace trust model is published, and says what a signature proves and what it does not.
- Four open protocol drafts (AEE, AOCL, VOLT, WARD) are public.
What you need alongside it
- A QuoxCORE instance to install and test your plugin on. The SDK builds plugins, it does not host them.
- Your own signing key. A signature shows who published a bundle, not that the code is safe.
- Quoxpert drives Quox through the quox CLI, so it needs the CLI and an instance as well.
Not yet
- The community marketplace catalogue is not open yet. Today you build, sign and install on your own instance.
- Dev Suite members are at different stages. Each page says what it does today and what it does not.
Pick a door. Build the first plugin.