Guided setup

Say what a project should achieve, the way you would to a colleague. Tares writes a plan for it: what to watch, when to wake, who does the work and what they may use. You see the whole plan in plain words, change any part of it, and nothing runs until you click Looks right, set it up. What you end up with is an ordinary project: every part is on its own page and stays editable.

Where it is

Projects → Create new. The first step also links to Start from a template (the template gallery) and to build it by hand from existing objects, for when you would rather pick the parts yourself.

The steps

The setup has four steps, shown at the top of the page: Goal, Plan, Connect and Try it.

Goal

Answer What should this project achieve? in a sentence, or click one of the examples under Or start from one of these. Then pick Who does the work?:

• Tares agents: agents that run inside Tares on your model provider. Nothing to host.
• Your own agent: Claude Code or a service of yours joins with a project key and is woken with what happened.

Click Plan it.

Plan

Tares writes the plan in the background and shows what it is doing as it goes: reading what is already on your Tares, looking at what a source sends, writing the plan, checking it and fixing what the check found, with the seconds the current step has taken. It usually takes under a minute.

The project exists from this moment as a draft. You can leave the page while it plans or while you edit the plan: the draft waits on the Projects list with Finish setting up, which opens it where you left it. Delete draft, on that row or at the foot of the setup page, removes it. Nothing of a draft is set up yet, so nothing else goes with it.

The plan then shows as four cards, each item with Change and Remove:

1. Watches: the sources the project reads. A source already on your Tares is reused as it is. Adding or changing a source starts with the kind of source; Tares then lists your sources of that kind to pick from, or Connect a new one of that kind.
2. Wakes when: when the agents are woken, in a sentence with the numbers you can change in place, and how long to wait before waking again.
3. Agents: who looks first and who digs in after a handoff. Add an agent can Use one already on Tares (pick it from the list, then Use it) or start from a template of agent instructions. An agent that posts to Slack gets a channel picker with the channels the Tares bot is in. With Your own agent, this card is your agent instead.
4. Know-how: optional skills, the notes the agents follow. Add a skill, Upload SKILL.md, or Use one already on Tares.

Under the cards, Tools the agents can use lists the MCP servers in the plan. A tool already on your Tares is on, since someone set it up already; a new one stays off until you turn it on. Attach one already on Tares or Add a new one adds more.

Parts are shared between projects, so the plan reuses what you already have: an existing source, agent, tool or skill is used as it is and stays in the projects that already use it.

To change the plan in words, type in Say what to change (for example “only for payments-api”) and click Update the plan; Tares plans again from your edited plan, shown as it happens. Show what Tares sets up for you lists every part the plan creates or uses. When it reads right, click Looks right, set it up: Tares creates the project and everything it needs in one go.

Connect

The one step only you can do. Tares lists what it cannot connect by itself, for example the endpoint your system sends events to (with an example event and Send a test event for me), a credential a new source needs, a new tool’s address, or your own agent’s key (shown once). Each item shows whether it is connected yet. Continue moves on; I will connect it later leaves it for the project page. When there is nothing to connect, the page says so.

Try it

Run it once now runs the agent that looks first, once, on the latest event its wake-up would count, so you see a result before a real one arrives. While it works, the step shows a spinner and the seconds so far; the result appears as a card with the steps that led to it. It uses your model provider like a real run, is marked Practice, and is left out of today’s totals. With your own agent, the same button sends your agent a practice wake-up and waits for its finding.

Open the project goes to the project’s Overview.

What it needs

A model provider on the instance, the same one Ask uses. Without one, the goal step says so and links to Add a model provider.

On the API