Talking to an agent

Most of what an agent does runs on its own. The rest is a conversation, in the same window where the job was set up.

What you can ask for

A one-off job. Something that happens once and does not deserve an automation. “Take these forty files and put the totals in a table.”

A new automation. “From now on, when a delivery note arrives, match it to the order.” The agent answers with a plan and nothing is built before you approve it.

A question about your data. “Who has not paid us?” The answer comes from your systems with the source under it. See Reports and questions.

A change to a rule. “Fuel invoices go to Fleet from now on.” It is written down for good, not for this chat. See Memory.

What comes back

Plain language, and where it helps, a block you can act on: a question with buttons, a table, a chart, a card to approve. A card that has to be approved is delivered by the platform, so it cannot be faked inside a conversation.

You can also send files. A document, a spreadsheet, a template or a script.

How a run ends

Every answer ends with the same three lines: what is done, what the next step is, and what waits for you. If the agent says a job is finished, it has to show the check it ran against the system it wrote into. A claim without that check is not accepted by the platform.

When it cannot do something

It says so and waits. It does not quietly give itself a system, a permission or a library it was not granted, and it does not guess an identity to keep a run going.