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.
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.
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.
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.
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.
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-helpruns fail last night?list_runs · get_runReadMake the previous staging deployment live again.
activate_deploymentWriteConnect the refund webhook to
fan-help.create_connectorWriteApprove the waiting refund for order 4471.
approve_tool_callWriteTry the shorter prompt on part of the traffic.
create_ab_testWriteSet 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.
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.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_orderA 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()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