Skip to main content
connic

Change your agent in the editor.
Try it on real messages seconds later.

Every save runs in your own cloud environment, with its own channels and data. You try changes on real chats and webhooks before anything reaches your customers.

agents/front-desk.yaml
You answer members of the club.
Members may bring one guest per
class. Guests pay €12 at the desk.
[18:03:11] → Detected change: front-desk.yaml
[18:03:12] → Files changed, uploading...
[18:03:12] ✓ Uploaded 11907 bytes
Fitness Clubtest bot

Can I bring a friend on Thursday?

Yes, one guest per class. They pay €12 at the desk.

Test the whole flow in the channels your customers use.

A dev environment has its own connections, so chats, schedules, webhooks and your app reach the code you just saved. Production keeps running as it is.

In the dev environment, a schedule starts the reminders and your own test bot sends them. Adjust the wording until it reads right, before a member gets one.

9:41
Fitness Club
test bot · online
Thursday
Reminder: Yoga Flow tomorrow, Fri 07:00 in Studio 2 with Anna. Reply cancel to free your mat.19:00
cancel19:04
Done, your mat went to the first person on the waitlist. Want Saturday's 09:30 class instead? 5 mats left.19:04
yes please19:05
Booked: Yoga Flow, Sat 09:30, Studio 2. See you there!19:05
Message

The member system's test setup sends cancellations straight to the dev environment, and each one runs your latest code. The agent's win-back draft waits for a person to send it.

Members (Sandbox)
members-sandbox.example.com/members/M-20417
MembersSANDBOXSearch members
JW
Jonas Weber
M-20417
Cancels Nov 30
Plan
Flex, monthly
Member since
Mar 2024
Home club
Berlin Mitte
Visits, last 30 days
11
Activity
Cancelled the membership in the app
Reason: Moving to Hamburg · 18:21
Win-back offer drafted
front-desk assistant · 18:21
Hi Jonas, sorry to see you go. Your membership also works at our Hamburg Altona club, and we can move it there instead of ending it, with December free. Shall I switch it for you?
EditSend to Jonas

connic builds the members' schedule app on your machine and serves it from the dev environment. Save a page or a prompt, reload, and it talks to your latest agent.

Class Schedule
class-schedule-5c1e8a37.connic.app/thursday
Fitness Club ClassesHi, Lea
MonTueWedThuFriSatSun
07:00
Yoga Flow
Studio 2 · Anna
4 mats leftBook
12:15
Core Express
Studio 1 · Malik
9 spots leftBook
18:30
Spin
Cycle room · Jule
3 of 16 bikes leftBook
19:45
Boxing Basics
Studio 1 · Deniz
FullWaitlist
Ask the front desk

Are there lockers for the evening classes?

Yes, the lockers next to Studio 1 are free during your class. Bring your own lock.

Type a question

Try anything. Your customers never notice.

Each dev session runs in its own environment. Pick it in the dashboard to start its agents, open its runs and set up its connections.

Test data stays out of production
Its own variables, connections, database, document search and sessions.
Throw it away or keep it
A quick test is deleted when you quit. A named environment keeps its setup for the next session.
The same models as production
Model access belongs to the project, so connic models and your own provider keys work without extra setup.
guest-passesdev
  • productionmaindefault
  • stagingstaging
  • Dev Environments
  • guest-passes
  • test-swift-owl-3a9ctemp
  • Manage Environments
Playground
Agent
front-desk
TextJSON
{
  "member_id": "M-20417",
  "message": "Can I bring a friend on Thursday?"
}

Runs use this environment’s tools and connections.

Run

One command from your editor to a running environment.

connic dev uploads the project, then every save. connic checks the agents first, so a broken save prints the reason and the last good version keeps running.

~/fitness-club
Start
$ connic dev guest-passes
→ Validating project files...
✓ 1 agent(s): front-desk (agents/front-desk.yaml)
→ Creating dev session...
Using named environment: guest-passes
→ Starting dev runner container (this can take a minute on first build)...
✓ Container: running
→ Uploading initial files...
✓ Uploaded 11842 bytes (hash: 9b1e4c07d2a35f81...)
→ Building app class-schedule...
✓ class-schedule → https://class-schedule-5c1e8a37.connic.app
→ Watching for file changes...
Keys: [r] refresh [t] run tests [q] quit (or Ctrl+C)
Save
[18:03:11] → Detected change: front-desk.yaml
[18:03:12] → Files changed, uploading...
[18:03:12] ✓ Uploaded 11907 bytes
Test
[18:04:02] → Submitting tests to backend (target: dev session env)...
PASS front-desk::guest_pays_at_the_desk 1/1 100%
PASS front-desk::full_class_offers_waitlist 1/1 100%
PASS front-desk::no_booking_without_member_id 1/1 100%
✓ 3/3 cases passed.
Typo
[18:05:30] → Detected change: front-desk.yaml
[18:05:31] → Files changed, uploading...
[18:05:31] ! Upload failed: Agent validation failed: Agent 'front-desk': cannot resolve tool 'bookings.hold_spto': Function 'hold_spto' not found in module 'bookings'
[18:05:31] Fix the issue and save to retry...
[18:05:44] → Detected change: front-desk.yaml
[18:05:45] → Files changed, uploading...
[18:05:45] ✓ Uploaded 11913 bytes
What it watches
agents/, tools/, middleware/, hooks/, schemas/, guardrails/, tests/, connectors/ and apps/. Connector and app files apply to the dev environment like a deploy.
Keys while it runs
r uploads right away, t runs your test cases against the files you just saved, and q ends the session and cleans up.
New dependencies
requirements.txt installs when the session starts. After you change it, start the session again.

Frequently Asked Questions

Yes. It has its own variables, connectors, database, retrieval and sessions, so test traffic stays out of production. Provider keys belong to the project, so it uses the same models as your other environments.

You choose. A quick test creates a temporary environment and deletes it when the session ends. A named environment stays, with its connectors and variables, and is reused the next time you start it under the same name.

No. A named environment allows one active session at a time, and a second one with the same name is turned away until the first stops. Use different names, or quick tests, to work in parallel.

connic checks the agents before it accepts the upload. A broken save prints the reason in your terminal, and the last good version keeps running until you fix it and save again.