AgntUX
Build guide

Build your own AgntUX plugin.

AgntUX already covers many popular data sources — but if the tool you live in isn't there yet, you can add it yourself. agntux-build walks you through it. No coding required.

Pluginagntux-build
Command/agntux-build:build
Timeabout an hour

What it does

You describe. It builds.

You describe the system you want AgntUX to support. agntux-build figures out the rest — connects to the system, designs the screen, builds the plugin, and tests it against your real data.

When it's working the way you want, you submit it back so every other AgntUX user benefits too.

Before you start

Four things to have ready.

App

Claude Desktop

The Claude Desktop app installed. Get it from claude.com (opens in a new tab).

AgntUX

AgntUX installed and set up

The AgntUX app installed, signed in, and through first-run setup — it must be running to deliver your finished plugin. Download AgntUX.

Connector

The tool you want to add

The connector for your target system (Linear, Notion, Jira, etc.) available in Claude. Most popular tools are already in the connector marketplace.

Time

About an hour

Plus patience for 3–5 rounds of testing. That's normal — not a sign anything went wrong.

How to start

Type one command in Claude Code.

claude code
$/agntux-build:build

The first time you run it, AgntUX asks for your name and email and walks you through the Developer Certificate of Origin — a short, standard open-source agreement confirming the work is yours to contribute. It only asks once. After that, just describe the system you'd like covered.

What happens next

Seven steps, all conversational.

You'll be asked to confirm each step. Nothing changes on your computer without your OK.

01

Marketplace check

If a plugin for your system already exists, AgntUX installs that one instead. No duplicates.

02

Connect

AgntUX authorises the connector for your system.

03

Plan in plain language

“Here's what your plugin will be able to read, and here's the button people will press to take action.”

04

Design the screen

You'll see a live preview. Edit until it feels right.

05

Build and test

Happens on your machine. Nothing extra to start, nothing extra to install.

06

Iterate against real data

AgntUX runs your plugin against your real data right in the conversation and shows you what it would surface. You react, it adjusts — usually 3–5 rounds. No installing, no copy-pasting.

07

Submit

When everything feels right, AgntUX finalizes your plugin and the AgntUX desktop app syncs it to the team automatically. Nothing to download, attach, or send.

Track it

Watch it move through review.

The moment you submit, your plugin shows up in the AgntUX desktop app under the Built by you tab — so you can see exactly where it stands, live, with nothing to refresh.

Built by you
  1. Queued for review

    In line. Review usually kicks off within the hour.

  2. In review

    AgntUX is building and testing your plugin.

  3. Merged

    Passed review and live in the marketplace.

Or, if review finds something
Changes requested

Review found something to fix before it can be merged.

Not accepted

Reviewed and won't be merged.

Fix mode

Fixing an existing plugin.

If you've used a plugin and hit something specific, run the same command — /agntux-build:build — and describe what went wrong. AgntUX switches into fix mode and walks the same flow with a smaller scope.

Questions, ideas, or stuck?

We're here. Click the blue chat icon in the bottom-right corner of this page and tell us what's going on.

Look for this icon, bottom-right.