Skip to content

Agents, for every ticket

Tickets now arrive as fast as you can think. Every one done well.

Built like your team.

Each department has AI roles, each with a job, how-tos called skills, and an AI model.

Marketing's department chart: the Content studio, Tutorials and Audience agent teams, each with its roles in steps.
Marketing's department rules: the house rules every role carries, and what is not allowed.
Skills: each with what it does, how many roles use it, its version and its owner.
Connectors: the tools the team has connected, with what each does and its permissions.
A ticket's activity: the hand-off note a role wrote before it finished, with the checks it ran.

Tickets that start themselves

Turn on Auto mode, and tickets assigned to you are matched to an agent team, which starts the work.

Desktop agents, not cloud agents

Each agent works on a teammate's computer, with the files, tools and accounts there.

All agents in Marketing: twelve tickets in progress and sixteen agents running, each with its role, what it is doing, and whose computer runs it.
Down a long dark table, a team's laptops face each other, each with its own glowing agent tiles beside it; two people type at the nearest.
NextTogetherRoute each question to the person it belongs to, and make every run better.

Start with a pilot

One team's real work, set up by the people who build it.

Book a short call

30 minutes with the founding team.

Agents, for every ticket

Agent teams assigned to every ticket, running where your work is. With the skills, connectors and resources to do the job right.

Now the VP and sentries, automatic checks that find work, file tickets as fast as you can think, and every one needs doing well. So every ticket gets its own agent team, and every agent shows live on its ticket, on any teammate's computer.

See how it runsFull details

Built like your team.

A department is one part of your company, like marketing, with its own AI roles and agent teams. An agent team runs roles in order; a ticket goes to one role or to an agent team. The models come from your own AI account.

A big ticket gets a team of roles: a Planner outlines from the research, a Writer drafts, and a Reviewer checks every claim before the work comes back to you.

Full details

Equipped to do it right

Every role reads your department's rules first, and runs its checks before it says it's done.

You choose how far an agent goes before it asks: ask first, allow edits, or plan without editing. A permission can be allowed once, or for the rest of a session.

Draft a skill with the VP

Describe the how-to you want; the VP drafts the skill with you, and you check it before it's saved.

Skills come in versions, and each role pins the version it uses.

Does it work with your tools? Constraint connects to over 400 tools today. Type a tool's name to see whether it's one of them.

The finder only searches the list: your typing stays in your browser, and nothing is connected from here.

List updated 29 October 2026.

The rulesFull details

Tickets that start themselves

You choose which stages auto mode starts work in, and work already running carries on if its ticket moves. It asks on Home when it needs you.

Full details

Desktop agents, not cloud agents

Your agents run on your team's computers, with your files, tools and accounts. Why that's stronger: an agent on your computer reaches the files, tools and accounts there as well as your online tools, and the whole team can see it working. They can use the AI subscription you already pay for, instead of paying for each use.

It can use the apps on that computer

If you turn it on, an agent can use the apps on its computer, app by app, with your permission.

Full details

Start with a pilot

Book a short call to start. Day one: we agree the first two pieces of work. Week one: we connect your ticketing service, turn your docs into roles and skills, set up each computer. Week two: the first work runs on your real tickets.

Full details