Skip to main content
An agent is a brief you write once and run whenever you need it, on a schedule or by hand. Each run does the same work a research turn does: it reads your sources, drafts the result with its sources attached, and leaves it for a person to review. An agent never writes to a connected system on its own. Open Agents in the sidebar. The page lists Your agents (only you can see and run them), Organisation agents (shared, managed by organisation admins) and a New agent button. With no agents yet, Start with a routine offers starting points such as Monday client brief, Competitor scan, Tender and RFP watch, Desk research starter, Project method capture and Source freshness check.

Describe an agent in plain English

The page opens with a box headed What should this agent do? Describe the work the way you would brief a colleague: “Every Monday at 8, brief the delivery team on budget burn and deal movement for our active clients.” Hebno writes the brief, sets the schedule and fills in the settings from your sentence. Anything it could not match, such as a project name that does not exist, appears under Worth checking. Nothing is saved until you select Save agent, so read the result and correct it first. Select Create manually to skip the box and go straight to the form.

The agent form

Schedules

Choose On a routine, then set How often. The agent runs automatically at the chosen time in your time zone. The form shows the result in words, for example “Every Monday at 08:00”. Each scheduled run is labelled Scheduled in run history. Runs you start yourself are labelled Started by hand.

Connected sources and allowed actions

Connected sources are files and folders. Allowed actions apply to the other integrations your organisation has enabled. For each one, choose what the agent may do: Reads use the connection that applies to the run. Personal connections use the owner’s own permissions, so an agent never reads anything its owner could not open directly. A proposed write does nothing until a person confirms it in agent approvals. Finance and ERP integrations allow draft creation only, and an admin’s Read only access setting on an integration overrides Propose writes here.
Run history and notifications can include excerpts from mail, meetings and finance systems. Share a run’s chat only with people who may read them.

Example agents

Schedule: weekly, Monday at 08:00. Project: none, or one per client. Connected sources: SAP S/4HANA, HubSpot, Outlook. Allowed actions: Read only for all three.Instructions: “For each active client, report SAP project budget burn against plan, any project over 80 percent of budget, HubSpot deal stage changes since last Monday, and client emails from the past week that need a reply. Lead with the three items that need a decision. Cite every figure.”
Schedule: weekly, Friday at 15:00. Connected sources: Deltek WorkBook, Xero. Allowed actions: WorkBook Read only, Xero Propose writes.Instructions: “List jobs with unbilled time above one week of fees. For each, propose a draft invoice in Xero.” The drafts appear in Agents → Approvals for finance to confirm.
Schedule: daily at 07:30. Connected sources: Outlook and the library. Allowed actions: Read only.Instructions: “Check the bids inbox for new tender notices. Summarise scope, deadline and fit with our credentials, and cite the matching case studies.”
Schedule: When you run it. Project: the engagement that just closed.Instructions: “Read the project files and Teams meetings and write up the method we used, the templates we built and what we would change.”

Run an agent

Open an agent and select Run now. Each run creates its own chat and research run, so you can open it and ask follow-up questions. Under Runs, every run shows a status: Queued, Working, Ready for review or Failed. Select Open run to read the result and its sources. An agent with no runs shows Not run yet.

Personal and organisation agents

Pause, edit and delete

Open an agent to manage it. Edit changes any field. Pause stops scheduled and manual runs without deleting anything, and you can resume at any time. Delete agent? requires confirmation, then removes the agent and its run history. The chats its runs produced remain in your chat history. When an agent’s spend cap is reached it pauses and its owner is notified. Raise the cap or wait for the period to reset, then resume it.

Notifications

Under Settings → Notifications, the Agents category includes An agent run finishes, An agent run fails and An agent reaches its spend cap. Run failures and spend caps also send email by default. Proposed writes notify the owner as well.

Next steps

Agent approvals

Confirm or dismiss the writes an agent proposes.

Skills

Reuse instructions across agents and chats.

Spend and limits

How caps and organisation limits interact.

Notifications

Choose how you hear about runs.