Claude Code

Build and deploy RootCX apps and AI agents directly from your terminal. The RootCX plugin for Claude Code turns your CLI into a full development environment -- no IDE required.

Claude Code guided by the RootCX plugin produces code that is 100% compatible with RootCX Studio. The same 6 official skills power both tools, ensuring consistency whether you build from Studio or from the terminal.

Getting Started

Prerequisites

• Claude Code installed
• The rootcx CLI on your PATH (download)
• A running RootCX Core (local via Docker or on rootcx.com)

Workflow

# 1. Connect to your Core
/rootcx-connect http://localhost:9100

# 2. Scaffold a new project
/rootcx-new agent support_bot

# 3. Describe what you want -- Claude Code builds it using the 6 RootCX skills
"Build a support agent that can query customer orders, create tickets,
 and send Slack notifications. Add a chat UI with a sidebar."

# 4. Deploy to the Core
/rootcx-deploy

# 5. Test the agent
rootcx invoke support_bot "What are my open tickets?"

That's it. Claude Code handles the manifest, the frontend, the backend, and the agent configuration -- guided by the same knowledge base as Studio's AI Forge.

Commands

The plugin adds three slash commands to Claude Code:

/rootcx-connect

Connect the current workspace to a RootCX Core.

/rootcx-connect <url> [--token <token>]

The CLI auto-detects the Core's auth mode:

• No auth -- connects directly.
• First-time setup -- prompts to create an admin account.
• Password login -- prompts for credentials.
• OIDC -- opens the browser for SSO.
• Token -- uses the provided bearer token (useful for CI).

Credentials are saved to .rootcx/config.json.

/rootcx-new

Scaffold a minimal RootCX project.

/rootcx-new app my_crm
/rootcx-new agent support_bot

Generates a Vite + React + Tailwind skeleton with manifest.json, a frontend, and (for agents) the backend/agent.json and system prompt. Claude Code then fills in the real code using the RootCX skills.

/rootcx-deploy

Deploy the current project to the connected Core.

/rootcx-deploy

The deploy pipeline:

1. Installs the manifest (POST /api/v1/apps).
2. Uploads and deploys the backend (if backend/ exists).
3. Uploads the frontend (if dist/ exists -- builds first if needed).
4. Starts the worker.

The 6 RootCX Skills

Skills are curated knowledge modules that guide Claude Code when writing RootCX applications. They are loaded automatically by the plugin and activated contextually -- Claude Code uses the right skill at the right time.

rootcx-manifest -- Data Contract & RBAC

Teaches Claude Code to write manifest.json:

• Entity definitions with field types (text, number, boolean, date, timestamp, json, file, entity_link, [text], [number])
• System columns id, created_at, updated_at (auto-generated, never declared)
• Relationships via entity_link with references (local entities or core:users)
• RBAC permission keys (entity.action convention, auto-prefixed with app:<appId>:)
• Schema sync behavior -- Core auto-diffs and migrates on every deploy

rootcx-sdk-hooks -- React Data Hooks

Teaches Claude Code to use @rootcx/sdk:

• useAppCollection<T>(appId, entity, query?) -- list, filter, create, update, delete
• useAppRecord<T>(appId, entity, id) -- single record CRUD
• useIntegration(integrationId) -- connect, call actions, manage OAuth
• useCoreCollection<T>(entity) -- read-only access to platform data (users)
• useRuntimeClient() -- imperative API for event handlers
• Full where-clause DSL: $eq, $ne, $gt, $lt, $like, $ilike, $in, $contains, $isNull, $and, $or

rootcx-ui -- UI Components & Styling

Teaches Claude Code to build frontends with @rootcx/ui:

• AppShell + Sidebar layout pattern
• AuthGate entry point (login/register/OIDC)
• DataTable with server-side pagination and sorting
• Forms, dialogs, toasts, and feedback components
• Dark mode via ThemeProvider + semantic CSS tokens
• Tailwind CSS v4 styling conventions (bg-background, text-foreground, border-border)

rootcx-backend-worker -- Bun Worker & IPC

Teaches Claude Code to write backend logic:

• JSON-lines IPC protocol between Core and Bun worker
• RPC handlers with caller authentication (userId, email, authToken)
• Background job processing via onJob hook
• Direct PostgreSQL access via database_url
• Lifecycle hooks: onStart, onJob, onError, onShutdown
• 30-second RPC timeout -- use jobs for long-running work

rootcx-rest-api -- Core HTTP API

Teaches Claude Code to call the Core API directly:

• Collections CRUD: GET, POST, PATCH, DELETE on /api/v1/apps/{appId}/collections/{entity}
• Bulk operations: POST /bulk and POST /query
• Integration actions: POST /api/v1/integrations/{id}/actions/{actionId}
• Job queue: POST /api/v1/apps/{appId}/jobs
• Bearer token authentication for all requests

rootcx-agent -- LangGraph AI Agents

Teaches Claude Code to build AI agents:

• backend/agent.json configuration (name, system prompt, memory, limits, supervision)
• LangGraph createReactAgent with provider-specific LLM SDK
• IPC bridge for tool calls (query_data, mutate_data, invoke_agent)
• Supervision modes (autonomous, supervised, strict) with policies
• SSE invocation endpoint and session management
• System prompt best practices

How It Works

The plugin consists of three layers:

1. Commands (/rootcx-connect, /rootcx-new, /rootcx-deploy) -- map directly to rootcx CLI commands. Handle authentication, scaffolding, and deployment.

2. Skills (6 knowledge modules) -- loaded into Claude Code's context when relevant. They are the single source of truth shared with Studio's AI Forge, ensuring code compatibility.

3. CLI (rootcx binary) -- the execution layer. Connects to Core, scaffolds projects, packs and uploads archives, starts workers.

Skills Path Resolution

The plugin finds skills in this order:

1. ROOTCX_SKILLS_DIR environment variable (if set)
2. Relative to the rootcx binary (../.agents/skills/)
3. ~/.rootcx/skills/ (fallback)

What You Can Build

From Claude Code, you can build anything the platform supports:

• Full-stack applications -- CRM, project tracker, billing dashboard. Manifest + React frontend + backend RPC handlers.
• AI agents -- customer support bots, data analysts, workflow automators. LangGraph backend with tools and supervision.
• Integrations -- Slack, Stripe, email connectors. Actions, webhooks, and credential management.
• Cross-app systems -- agents that query data from multiple apps and delegate to other agents.

All deployed artifacts are identical to what Studio produces. You can start in Claude Code and switch to Studio (or vice versa) at any point.