---
title: "AI agents | Briks"
url: https://briks.dev/docs/ai-agents
description: "Hire AI agents that look after a live site: 13 kinds led by a Team lead, or your own, each with a schedule and a budget, asking you before they act."
last_updated: 2026-10-08
---

# AI agents

AI agents look after a site once it is live. Each takes one job, runs on a schedule or when something happens, keeps to a monthly budget and asks you before it does anything a visitor would see. Agents come with every paid plan.

10 minute read Checked against the studio on 8 October 2026

Which plans include agents

Agents per project: 3 on Starter, 5 on Pro, 10 on Studio and 15 on Agency. Free does not include agents. Hiring agents and deciding what they ask is for Owners and Admins; everyone in the workspace can see them at work.

## What agents are for

A site needs looking after once it is live: questions from visitors, form entries to reply to, opening hours that change, search titles to tidy, an expiring certificate to notice. Agents are helpers that each take one of those jobs, run on a schedule or when something happens, and come to you before doing anything a visitor would see.

## The 13 kinds of agent

| Agent | Its job | When it runs | Asks you first about |
| --- | --- | --- | --- |
| Team lead | Plans the crew's week from your goals, gives each task to the agent who can do it, and sends you one stand-up. See [Team lead](https://briks.dev/docs/team-lead). | Mondays at 08:00 | The week's plan |
| Support | Answers the questions the site's chat passes on, by email from the site. | When the site's chat passes a question on | Emails |
| Leads | Replies to what visitors send through the forms, and sends you a digest. | Weekdays at 17:00, and on each form entry | Emails |
| Site keeper | Keeps the site's facts and words current: hours, prices, seasonal text, broken links. | Mondays at 08:00 | Site changes |
| Site watch | Watches that the site answers, its certificate, scheduled jobs and webhooks, tells you, and proposes repairs. | When the site goes down or comes back, a certificate is within 14 days of expiry, or a job or webhook fails | Repairs |
| SEO | Works on titles, descriptions, headings, picture text, links between pages and speed. | Wednesdays at 09:00 | Changes |
| AI search | Gets the business named when people ask AI assistants: checks that 14 AI crawlers can read the site, asks two leading AI assistants what buyers ask once the site is in production, and proposes at most two changes at a time. | Tuesdays at 09:00 | Changes |
| Articles | Writes a blog post for the site, in your voice and from your facts. When one of its older posts has lost visitors or no longer matches the site, it may ask to update that post instead. | Daily at 09:00 | Publishing, updating an article, and adding a blog |
| Designer and coder | Looks at the site on every screen size and finds what a visitor would notice. | Thursdays at 10:00 | Changes |
| Social | Writes next week's posts for the accounts connected in the project's [Marketing tab](https://briks.dev/docs/marketing), from the site's articles, pages, offers and events. | Thursdays at 10:00, and when an article is published | Posts |
| Marketing | Plans next month, turns offers and events added to the site into campaigns, and reports what brought visits and enquiries. | The 25th and Mondays at 09:00, and when an offer or event is added | Plans, posts and site changes |
| Reporter | A one page summary of the week: results, what each agent did, what needs you. | Mondays at 08:00 | Nothing: it takes no outward actions |
| Security | Checks the site's code, its keys and the live site, explains each finding in plain words, and asks the Builder to fix what you approve. See [Security agent](https://briks.dev/docs/security-agent). | Mondays at 07:00, and after every publish | Every fix, always |

Times are in the workspace's time zone, UTC unless set otherwise, and may shift by up to 10 minutes. Every agent also wakes when you write to it, or when a teammate hands it work. Social and Marketing are offered where the Marketing tab is open.

## Hire an agent

1. Open Agents

   Where: Agents

   Click **Agents** in the sidebar. Choose a project under **Project**, or leave it on **All projects**.

2. Start a new agent

   Where: Agents

   Click **New agent**. Describe the job in your own words and click **Draft the agent**, or pick one of the kinds under **Or start from a kind of agent**. **See it in action** under a kind shows how to get the most from it.

3. Check it

   Where: New agent

   Change anything before hiring: **Name**, its job, **Your instructions**, the project it **Works on**, **What it may use**, **When it works**, **What it may do on its own**, and its **Budget a month** and **Budget a day**.

4. Hire it

   Where: New agent

   Click **Hire and switch on**, or **Hire, switched off** to switch it on later from its own page.

With a project chosen, the **Crew** tab shows **Autopilot** for that project. Switching it on hires the recommended crew (Team lead, Site keeper, Support, Leads, Site watch and SEO) and switches them on together, so it needs room for that many agents on your plan; switching it off pauses them.

- **Agents per project.** Each project has its own allowance. An agent that works on **Every project in this workspace** counts as one more project. On a plan with one project, every agent counts together.
- **When the plan is full,** the Crew tab says how many agents the project has of its allowance and offers **Get more**. Agents start on Starter.

## Find your way around Agents

| Tab | What it holds |
| --- | --- |
| **Team** | The team at work, live: the lead above its crew, what each agent is doing now, its last seven days, a timeline of runs, work between agents, what they asked you and their messages. See [Team lead](https://briks.dev/docs/team-lead). |
| **Crew** | Every agent with its state, next run and spend this month, the last 30 days of credits, runs and your decisions, and **Autopilot** for the chosen project. |
| **Waiting for you** | What agents ask before they act, with the number waiting on the tab. See [Approvals and budgets](https://briks.dev/docs/agent-approvals). |
| **Chat** | Every agent in a list, the lead first. Choose one to read its thread and write to it. |
| **Memory** | What your agents remember about you, about each business and their own lessons. You can change or remove anything. |
| **Activity log** | Every run, every action an agent asked for and how it was decided, every report and what your chats did. Filter it, and press **Export CSV** to download it. |

Each agent also has its own page, with its switch, **Run now**, and the tabs **Thread**, **Settings**, **Memory** and **Runs**; the Security agent adds **Security report**. Write to it in the thread and it reads your message within a minute. **Remove this agent** at the foot of its settings stops it at once; the activity log keeps what it did.

## Approvals and budgets in short

Sending an email, changing the site, publishing or updating an article, scheduling social posts and the Team lead's plan for the week all ask you first. Requests wait under **Waiting for you**, and reach you by email, or on Telegram once you have [connected it](https://briks.dev/docs/telegram). After 5 approvals in a row with no changes, an agent offers to do that kind on its own; you decide. The Security agent's fixes always wait for you.

Each agent has a monthly budget in credits, 20 unless its job needs more, and a day budget of a fifth of that. Runs are paid from the workspace's credits, a run with nothing new to do is skipped without a charge, and three failed runs in a row pause the agent. [Approvals and budgets](https://briks.dev/docs/agent-approvals) covers all of it.

## What an agent can be allowed to use

Each agent gets only the tools its job needs. An agent hired from one of these kinds starts with the tools of its kind, a custom agent with the ones its draft chose, and you can turn each tool on or off under **What it may use** in its settings. Reporting to you and remembering what it learned are always allowed.

| Tool | What it lets the agent do |
| --- | --- |
| Read analytics | Visits, pages, sources, conversions and speed. |
| Read form entries | What visitors sent through the site's forms. |
| Read site chats | Every conversation on the site's chat, and the questions it passed on. |
| Read the site | Its pages as text and its brief. |
| Read site health | Whether it answers, its certificate, the last site check, failed scheduled jobs and webhooks. |
| Email customers | Write to a visitor from the site's own address. Asks you first. |
| Change the site | Ask for a change, built and published like any change, with undo. Asks you first. |
| Write articles | Read the site's blog, research what people search for, write posts for it and keep its older posts current. Publishing and updating ask you first. |
| See the site | Look at its pages on phone, tablet and desktop, and read its own code, to find what to improve. |
| Post on social media | Read the connected accounts and the calendar, write posts for each platform with the site's own photos and branded cards, and schedule them. Publishing asks you first. |
| Answer comments | Read the comments and mentions on the connected accounts and draft replies. Replying asks you first. |
| Check AI search | See how AI assistants read the site, ask them what buyers ask and record whether they name the business, and see the visits they send. |
| Check security | Check the site's code, its keys (names only, never values) and the live site as a visitor would, and keep the security report. Never changes the site. |
| Lead the team | Plan the week from your goals, give the crew its tasks and send you one stand-up. The plan asks you first. |

Posting, answering comments, checking security and leading the team belong to the agents made for them; a custom agent can be given any of the others.

## Custom agents

Beyond these kinds, you can describe an agent in a sentence under **What should it do?**. Briks drafts it for you: its name, its job, the tools it may use, the events that wake it and its schedule. You check and change all of it before hiring, and set its budget, 20 credits a month unless you change it. Drafting holds 3 credits and is charged what it takes.

A custom agent A yoga studio in Galway

> Every Friday afternoon, look at this week's class booking form entries and send me a list of anyone who booked twice but has not come back.

The draft gives the agent a name, its job, the tools it would use, the events that wake it and a Friday schedule, with a budget of 20 credits a month until the owner changes it.

## What agents remember

Agents remember what lasts, in three layers: **About you** and your people, read by every agent in the workspace; **About the business**, shared by every agent on that project, with its facts, voice, goals and rules; and **Each agent's own** lessons and working notes. On the **Memory** tab, **Read the site** has Briks read a project's site and brief so its agents start out knowing the business; it holds a few credits.

What an agent learns from your own words, and its working notes, are kept straight away; working notes go after 30 days. Anything else it learns is proposed, and you keep it or not. See and change all of it under **Memory**.

## Privacy: each agent stays in its workspace

Each agent sees only the workspace it belongs to. It cannot read another workspace's projects, records or messages, even one owned by the same person. A visitor's words that an agent reads, such as a form entry, are treated as information and never as instructions to it.

## Without agents, on every plan

Some of these jobs also have a feature of their own, on every plan, that works without agents:

- The [chatbot](https://briks.dev/docs/chatbot) answers visitors from your published pages and emails you the questions it passes on. It is off until you switch it on.
- [Forms](https://briks.dev/docs/forms) keep every entry in the studio and email them to you once the site is in production.
- [Analytics](https://briks.dev/docs/analytics) shows visitors, pages, sources and a live globe, counted without cookies.
- In a project's settings, **Check the published site after every change** looks at the site at four screen sizes and repairs what renders broken.
- [Making changes](https://briks.dev/docs/making-changes) in plain words covers what the Site keeper and SEO agents suggest: you ask, Briks builds and publishes it as a new version you can undo.

### Which plans include agents?

Every paid plan: 3 on Starter, 5 on Pro, 10 on Studio and 15 on Agency agents per project. Free does not include agents. Plans and credits are described on the [Billing](https://briks.dev/docs/billing) page.

### What do agents cost?

Each run is paid from your workspace's credits for the work it took, within the agent's monthly budget. A run that fails is not charged, and a run with nothing new to do is skipped.

### Will agents change my site without asking?

No. Site changes, emails, articles and posts ask first, until you choose to let an agent do one kind on its own, and even then only up to its daily number. Security fixes always ask.

## Read next

- [AI agents **Team lead** The Team lead plans your agents' week from your goals, waits for your approval, hands each task to the agent who can do it, and sends you one stand-up.](https://briks.dev/docs/team-lead)
- [AI agents **Approvals and budgets** See what agents ask before they act, approve it in the studio, by email or on Telegram, choose what they may do alone, and set the budgets that cap their spend.](https://briks.dev/docs/agent-approvals)
- [AI agents **Security agent** Hire the Security agent to check your site's code, keys and live pages, hear in plain words what it finds, and have the Builder fix what you approve.](https://briks.dev/docs/security-agent)
- [Your site's features **Marketing and social posts** Connect your X and LinkedIn profiles, write a post once with a version for each, schedule it on the calendar and see the visits and enquiries it brought.](https://briks.dev/docs/marketing)

Still stuck?

Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.