What agents can do

The tools an agent can be given, grouped by what they act on, and the rule that agents compose existing features rather than improvise.

Tools are the platform's own features, exposed to the model. Give an agent only what its job needs.

Always available

Every agent can remember (private and org-wide memory), read and save project docs, decline a task that is not its job, and read this guide — so "how do I…" is answered from the documentation with a link.

Knowledge and research

Web search · fetch a web page · look up how the platform provides a capability before building anything · query your own data (tasks, tickets, flows, orders…).

Work management

Create, assign and update tasks · submit a plan · assess a step or task · raise a ticket · post to a community.

Communication

Read your inbox · send email (with confirmation) · check the calendar, find free slots, book · invite a user · send a Telegram message.

Building

Create a site · create a page or set a site's chrome and home page · add a product · build a digital product with the creator · create a course and add modules · generate an image · set a brand kit · create a flow (with a complete opt-in page) or trigger one · define and use data collections · search and add directory entries · run a published function · read, write and lint site files · apply a blueprint · create and delegate to other agents.

Compose, do not construct

Before building anything dynamic — lead capture, email, products, bookings, courses, automation, support, membership — an agent looks up how the platform already does it and uses that module. It does not build a static imitation. If a capability is genuinely missing, it reports the gap instead of faking it.

Custom data

When an agent needs somewhere to keep records (testimonials, enquiries, inventory) it defines a data collection — a real table with typed fields — rather than hard-coding rows into a page. See Data collections.