Running agents

Once you've created an agent, there are several ways to make it run. Every invocation — whoever or whatever starts it — converges on the same agent run, so the message history, cost, and audit trail are identical no matter how the run began.

Run it interactively

The fastest path is a conversation. Open the agent detail page and go to the Invoke tab (/a/<account>/p/<project>/agents/<id>/invoke), type your input, and send. This opens a thread — a durable conversation surface you can return to. Threads for a project live at /a/<account>/p/<project>/threads, and each renders the full model and tool-call history as it streams in.

Run it from a trigger

For unattended runs, configure a trigger on the agent's Invocations tab (/a/<account>/p/<project>/agents/<id>/invocations). Five surfaces are available:

1. Manual — the interactive path above.
2. Cron — a schedule (for example 0 9 * * MON) runs the agent unattended. connect0 provisions the schedule for you.
3. Webhook — an inbound POST to webhooks.connect0.ai/agent/<id>, verified with a per-agent HMAC secret you're shown once at setup.
4. REST — POST /v1/agents/<id>/runs with a bearer token, for your own automation.
5. MCP — expose the agent as a tool so any MCP client (Claude Code, Cursor, your own) can invoke it.

Channels like Telegram, Slack, and email are configured here too. Each trigger you enable becomes an authorized entry point; nothing runs on a surface you haven't turned on.

Whatever the entry point, every invocation converges on the same run and ends in one recorded outcome:

Watch and read runs

• Live: while a run executes, the thread view streams each model turn and tool call as it lands.
• History: the agent's Runs tab (/a/<account>/p/<project>/agents/<id>/runs) lists every run with its status, token totals, and cost. Open a run for the full step-by-step trace.
• Fleet view: the Agents Command Center shows in-flight runs across all your agents in near real time.

A run ends in one of: succeeded, failed, timeout, budget_blocked (it hit a spend cap), cancelled, or awaiting_input (it's paused for your response). You can stop a running agent from the run detail page.

Where to go next

• Agents Command Center to monitor the whole fleet.
• Why did my run fail? to diagnose a run that ended in failed, timeout, or budget_blocked.