Overview

An extension is one file that teaches the agent a new capability. Drop a .tsx into conciv/extensions/ in your project root and it is discovered automatically, no registration, no config.

import {z} from 'zod'
import {defineExtension, defineTool} from '@conciv/extension'

const deployRun = defineTool({
  name: 'deploy_run',
  description: 'Deploy the current branch',
  inputSchema: z.object({env: z.enum(['staging', 'prod'])}),
}).server(async ({env}) => ({url: `https://${env}.example.com`}))

export default defineExtension({name: 'deploy', tools: [deployRun]})

Restart your dev server and ask the agent to deploy. It now has a deploy_run tool: typed input via zod, execution in node, and a result card in the thread.

One file, both sides

The same file describes the server half and the browser half. The plugin splits it: .server(...) code runs in node next to your dev server, everything else is compiled into the widget as Solid JSX (even when your app is React). You never wire the two together; calling a tool from chat just works.

conciv/extensions/deploy.tsx
        │
        ├── server: tool execution, custom routes, long-lived processes
        └── client: result cards, composer buttons, widget panels

What an extension can carry

Built-ins

Two extensions ship with conciv and are on by default: the whiteboard and the test runner. They are built on this same contract, nothing private. Read them as worked examples in Built-ins.

Next