K

Ask in plain words (plugin)

One sentence in Claude Code — "deploy this" — covers building, deploying, and diagnosing apps

Install the axhub plugin and you can drive AxHub from Claude Code by saying things like "build an app and deploy it." There are no commands to memorize — just say what you want to do, and the plugin routes it to the right feature.

Install

Type these two lines, one after the other, into the Claude Code prompt.

/plugin marketplace add jocoding-ax-partners/axhub
/plugin install axhub@axhub

First time after installing? Just say "set up axhub" — it walks you through CLI install, login, environment checks, and the MCP connection in one pass.

To follow the whole path from install to first deploy, see the Quickstart; to install via the Claude Desktop app's UI, see the From the Claude app tab in Build and deploy your app.

What you can ask for

Say this, and this happens.

Say thisThis happens
"set up axhub", "I'm new here"First-time setup — CLI install, login, environment checks, and MCP connection, in order
"I want to create an app on axhub"Create a new app from a template in an empty folder — app, repository, and first deploy in one pass
"put this folder on axhub"Connect an existing local app to AxHub and get it ready through the first deploy
"add todo search", "build a dashboard from my data"Add or change features on an app you built — live-data screens, CRUD, UI/API improvements
"deploy this", "push it up again"Redeploy the current branch and check deploy status
"why did the deploy fail?"Diagnose the failed deploy read-only — it only diagnoses and changes nothing
"show me logs with axhub clarity", "delete this axhub app"Run precise operational commands — logs, environment variables, rollback, tables, connectors, GitHub reconnection, app deletion
"is axhub up to date?", "update it"Check and update CLI and plugin versions

When you want to be explicit, you can also call a feature directly by its slash command, like /axhub:deploy. The exact names of the 8 features (skills) and the auto-routing rules are in the reference below.

Safety rails

Even in plain conversation, risky actions never just run on their own.

  • Hard-to-undo actions (deploys, deletions, and the like) show you a preview of what will happen first and ask for confirmation once more. You can let it proceed or stop it.
  • Success is confirmed with evidence — a deploy isn't "the command finished"; it's verified against the deployment record (axhub deploy verify).
  • Secrets are collected in ways that keep them out of the screen and the command history.
  • Deploys, recovery, and rollback run only after confirming which app and which company (tenant) they target.
  • Failure diagnosis is read-only, so diagnosing never changes the app's state.