Skip to main content
connic

Describe the agent you need.
Your coding agent builds and ships it.

Add the connic plugin to Claude Code, Codex, Cursor or ChatGPT. Your coding agent writes the agent, runs its tests and deploys it, then keeps working on the live project with the permissions you pick.

~/northdock-agents
Build an agent that answers fan questions about seats, tickets and returns. Add tests and deploy it to staging.
+ Created agents/fan-help.yaml
+ Created tools/tickets.py
+ Created tests/fan-help.yaml
$ connic test✓ 4/4 cases passed.
$ connic deploy --env staging --yes✓ Deployment created.
connic · get_deployment #4f2a91c3
✓ active
fan-help is live in staging, and all four test cases passed.

What a small team leaves to its coding agent.

A concert venue with two developers runs its fan service this way. They describe each job in plain words and review what comes back.

The coding agent writes the agent, a tool that reads seats and orders from the ticket shop, and test cases. connic runs the tests on deploy, and a failing case stops it.

9:41
Northdock
Ticket help · replies right away
Today
Are there still seats for Saturday?16:12
Yes, 37 seats in the balcony at €39 each. Doors open at 19:00.16:12
Can my 12-year-old come with me?16:13
Yes. Children under 14 need an adult with them and a ticket of their own.16:13
Write a message

Asked to hook up the shop, the coding agent creates a webhook connector in staging and links it to the agent. Each refund request from the shop now starts a run.

~/northdock-agents
The ticket shop should send refund requests to fan-help. Set that up in staging.
connic · create_connector webhook · refund-requests → fan-help
✓ created in staging
https://connect.connic.co/webhook/7c41e2
Done. Paste this URL into the ticket shop's webhook settings, and each refund request starts a fan-help run.

A fan was told Saturday is sold out. The coding agent finds the run, reads its trace, fixes the tool and adds a test case, so the next deploy checks for it.

~/northdock-agents
A fan was told Saturday is sold out, but there are seats left. Find out why.
connic · list_runs fan-help · "sold out"
✓ 1 run
connic · get_run 8d03f7a2 · traces
tickets.find_seats date: 2026-11-14 available: 0
The tool asked the shop for last Saturday's concert, which is over. I fixed the date and added a test case for it.
~ Edited tools/tickets.py
~ Edited tests/fan-help.yaml
$ connic test✓ 5/5 cases passed.

You decide what it may touch.

When you connect, you choose one project, its environments and each permission. Your coding agent never gets more than your own role allows.

Writes only where you allow them
Reads are on by default and can be narrowed. Each write, such as activating a deployment or changing a connector, is granted on its own.
Change or revoke at any time
Adjust environments and permissions in the project settings without reconnecting, or end access right away.
Changes on record
What it changes in the project shows up in the audit log, like the same action through the API.
Secrets stay hidden
Stored secret values are never returned. Connector credentials can be set but not read back.
Connect Claude Code to connic
Project
Northdock
Environments
staging
Permissions
Allow all read permissions
Allow all write actions
  • View runs
  • Create deployments
  • Activate deployments
  • Create connectors
  • Delete connectors
  • Override deployment checks
DenyAuthorize

It keeps working after the first deploy.

On the live project, your coding agent takes on the routine work around your agents. You say what you need, and it uses the actions your permissions allow.

It can't start agent runs directly, handle payments, delete the project or change account security.

  • Why did fan-help runs fail last night?

    list_runs · get_runRead
  • Make the previous staging deployment live again.

    activate_deploymentWrite
  • Connect the refund webhook to fan-help.

    create_connectorWrite
  • Approve the waiting refund for order 4471.

    approve_tool_callWrite
  • Try the shorter prompt on part of the traffic.

    create_ab_testWrite
  • Set up a judge that scores the tone of answers.

    create_judgeWrite

One prompt to set up, then files you can review.

Paste the prompt into a new session. The plugin brings connic's guide and access to your project. What your coding agent writes is YAML and code in your project, checked by connic test like any other change.

prompt

Paste this into a new session. Your coding agent installs the plugin and walks you through signing in.

Install the connic plugin from connic-org/connic-skill and instruct the user on how to finish the MCP auth setup.
agents/fan-help.yaml

The agent: its model, instructions and the tools it may call.

version: "1.0"
name: fan-help
description: "Answers fan questions about tickets, seats and returns"
model: connic/gpt-5.6-terra
system_prompt: |
  You answer fans of the Northdock concert venue.
  Look up seats and orders with your tools; never guess.
  Returns close 48 hours before the show starts.
  Children under 14 need an adult and a ticket of their own.
tools:
  - tickets.find_seats
  - tickets.find_order
tools/tickets.py

A tool that looks up seats and orders in the ticket shop.

import os

import httpx

SHOP_URL = os.environ["TICKET_SHOP_URL"]


async def find_seats(show_date: str) -> dict:
    """Free seats and prices for the show on one date.

    Args:
        show_date: Date of the show as YYYY-MM-DD, e.g. 2026-11-21
    """
    async with httpx.AsyncClient() as client:
        resp = await client.get(f"{SHOP_URL}/shows/{show_date}/seats")
    return resp.json()


async def find_order(order_id: str) -> dict:
    """An order with its show, tickets and return deadline.

    Args:
        order_id: Order number from the ticket email, e.g. 4471
    """
    async with httpx.AsyncClient() as client:
        resp = await client.get(f"{SHOP_URL}/orders/{order_id}")
    return resp.json()
tests/fan-help.yaml

Cases that connic test checks and every deploy runs again.

version: "1.0"

tests:
  - name: answers_seat_availability
    payload: "Are there still seats for Saturday's show?"
    expected_tool_calls:
      - tickets.find_seats
    expected_result: '"balcony" in output'

  - name: explains_return_deadline
    payload: "Can I still return order 4471?"
    expected_tool_calls:
      - tickets.find_order: params.order_id == "4471"

  - name: children_need_an_adult
    payload: "Can my 10-year-old come to the show alone?"
    expected_result: '"adult" in output'

  - name: no_lookup_without_order_id
    payload: "I want my money back."
    expected_no_tool_calls:
      - tickets.find_order

Frequently Asked Questions

Only what you grant when you connect: one project, the environments you pick and the permissions you select, never more than your own role allows. With that, it can manage deployments, connectors, approvals, judges and A/B tests, and read runs with their traces. It can't start agent runs directly, and it has no access to payments, project deletion or account security.

Each connection is listed under Project Settings → API Keys & MCP Auth. Changes to environments and permissions apply without reconnecting, and revoking ends access immediately. Projects that require two-factor sign-in ask for a recent one before sensitive writes.

The connic plugin installs in Claude Code, the Claude app, Codex, Cursor and the ChatGPT app. Other clients, such as OpenCode, add the guide and the connection to your project separately.

No. connic never returns stored secret values to it, and credentials for connectors can be set but not read back.

No. Agents are YAML files and code you can write yourself, test with connic test and deploy from the terminal or with a Git push. Deployments, connectors and approvals are in the dashboard too.