cuttlely/cuttlely

English | 繁體中文 | 简体中文 | 日本語 | 한국어
**Your applications deserve agents.**
The open-source agent platform for applications. Cuttlely gives your applications their own intelligent capabilities and coordinated agent teams. Start chatting with a team in minutes, then call it from your app through the API. It runs on infrastructure you control.
Contents
- What you can build
- Agent teams that power your apps
- Test every change before it goes live
- Use your team
- Use a team from your app
- Small context, big answers
- Tools your teams use
- Your first 10 minutes
- Guides
- Bring your existing flows
- Contributing
- About and credits
- Contact
Watch the narrated run (78 seconds, sound on)
A customer writes in about a late order. A customer specialist reads the account, an operations specialist finds that the parcel never left the warehouse, and a policy specialist checks the written policy once operations is done, each with its own data and tools. Harness Prime writes the decision, the reply and the actions, with the evidence. Try the demo opens this team on your own model key.
What you can build
Agent teams that power your apps
Give your app a team instead of a single prompt. An agent team is a lead agent with specialists. In Cuttlely, an agent team is called a harness. The lead, Harness Prime, reads the question, splits it into parts, sends each part to the right specialist, and writes one answer. Each specialist can have its own model, tools, playbooks and data. A chatflow calls the whole team by name, so your app, a share link or a website embed can reach it. Your app sends the team a question through the API and gets back one researched answer, a chart or an action. Harnesses guide
- **The Analyst** is a specialist with its own database. It creates tables, adds rows and answers questions about them with the real numbers, and it never reads Cuttlely's own tables. Long results come back in pages. Turn it on with CUTTLELY_ANALYST=auto. Analyst guide
Test every change before it goes live
Test with up to 100 question-and-answer pairs, with more on the roadmap.
Watch the testing run (56 seconds, sound on)
- **Drafts never touch Live.** On chatflows, agentflows, harnesses, and pipelines the canvas saves to a draft. The API, embeds, shared links, schedules, webhooks, a harness's external runs route, and a pipeline's scheduled runs keep serving Live until you publish. The canvas test chat runs your draft, including a harness canvas chat and Try it. **Preview** on a pipeline runs the draft and does not write to the store.
- **Compare before you publish.** Recent questions run on Live and on the draft, and each answer is marked Same, Changed, or Error.
- **Real answers become tests.** Add one answer with Add to test set, or thumbs-up or thumbs-down answers from a time window, up to 500 new rows at a time.
- **Score the draft.** Text, JSON, numeric and model evaluators give Pass, Fail or Error and a pass rate for Live and the draft. Evaluations
- **Publish waits for a pass.** The Passing test set gate is off until you turn it on, for a chatflow or an agentflow that starts from chat. Once on, Publish stays disabled until the current draft passes. cuttlely check --gate runs the same check in CI.
- **Every version is kept.** Open an old version as your draft or roll Live back in one step, and promote from Dev to Prod, which goes Live only when its owner selects **Promote to Live**.
- Chatflows, agentflows, harnesses and pipelines keep each saved version, with what changed and who changed it.
- Dev and Prod connect to the same GitHub repository. Prod lists what Dev published, shows what would change and which credentials it needs, and can run the same side-by-side check. Each server keeps its own credentials; only their names travel.
The gate covers Publish of the current draft only. Roll back Live, Promote from Dev, and PUT /api/v1/chatflows/:id still change Live: see which.
On a chatflow, an agentflow, or a harness, the Publish dialog can replay recent questions (4, 10, 25, 50, or 100; 4 is selected first), once on Live and once on your draft, and show both answers side by side with the tokens and time each one took. **Choose questions** hand-picks stored questions instead, still up to that admin cap. **Save as dataset** keeps the ticked questions, with blank expected answers to fill in on Datasets. An agentflow that starts from a form, a webhook, or a schedule replays that many recorded inputs instead. A pipeline lists what changed and does not run that check. The check never changes Live or your draft and leaves nothing in chat history. A flow with steps that post or write for real is skipped unless you choose to run it anyway. On a chatflow or a chat-started agentflow, under **Questions from**, choose **A dataset**, pick the evaluators, and turn on the passing test set. A harness can score a dataset for that run only, and a form, webhook, or schedule start cannot. **Admin** > **Server settings** > **Testing and Limits** turns the Publish check on or off. That switch applies on the next check and does not change Publish.