Leo, the AI agent

Overview

Leo is the AI agent built into Whisperer. It sees your meetings, tasks, calendar and files, and acts in those same places — creating a task, moving a card, adding a calendar event, finding what was said on a call three months ago. Leo is a participant in the product, not a chat window bolted onto it: the tools it calls are the same ones the interface uses, so there is no second implementation that could behave differently.

Leo is not a separate chatbot and not a model. Which model answers is a setting you control; Leo is the agent that decides what to do and which tool to call.

When to use it

  • You need to find something across past meetings: what was decided, who promised what, how a topic evolved.
  • You want work created for you: a task on the right board, an event in the calendar, a note in the knowledge base.
  • You want a briefing before a call: what is still open, what is coming due.

Step-by-step

  1. Open the assistant in the web cabinet.
  2. Ask in your own words. "What did we agree with Acme about pricing?", "Create a task to send the contract by Friday", "What is unresolved in this hub?"
  3. Check the source. For anything Leo took from a meeting it shows where it came from — which meeting, which moment. Ask "why do you think that?" and you get the source, not a paraphrase.
  4. Confirm irreversible actions. Deletions are shown with a preview of exactly what would be affected before anything happens.
  5. Choose the model for the answer role in your settings, if the default does not suit the task.

What Leo will not do

  • Act on anyone's data but yours.
  • Delete anything without your confirmation.
  • Invent a deadline or an obligation: if there is no source, Leo says so instead of guessing.
  • Pass access you granted Whisperer on to an external client (see MCP: connecting Claude, ChatGPT and Cursor).

Common mistakes

  • Expecting Leo to know what was never recorded. It answers from your meetings, files and knowledge base — not from memory of a call you did not capture.
  • Asking for a task without a board. If the meeting has no hub and no board is chosen, Leo declines rather than filing the task in an arbitrary project.
  • Treating a commitment as a task. An obligation someone stated on a call is tracked separately until you decide to turn it into a task.

Best practices

  • Ask for the source when the answer matters — it costs one sentence and turns an assertion into evidence.
  • Keep hubs tidy: the better a meeting is addressed, the more precise Leo's answers about that work become.
  • Tell Leo what to remember about you; see What Leo remembers.

Related articles