How Meridian works
Agents do work in runs; jobs make it recur; approvals guard anything that leaves or changes.
Everything in Meridian comes down to five ideas. Once you know them, every screen reads the same way.
Steps
- Agents are teammates. An agent has a name, instructions, skills, and the accounts it may use. Meridian is the default agent that answers when you do not pick one. The others you find in Agents have a job to do, such as preparing your meetings or sorting your inbox. You turn an agent on for yourself, write it notes, chat with it, or duplicate it.
- Work happens in a run. Every request, whether you typed it or a schedule fired it, becomes a run inside a chat. A run reads what you can see, does the work, and leaves a record you can open later. There is no hidden work.
- Jobs make work recur. A routine that names an agent is one of that agent's jobs. A job fires on a schedule, on an event such as an email arriving or a meeting ending, or when a record changes. It runs for each person who turned the agent on, with their accounts.
- Spaces hold shared work. A Space is people and agents working toward goals. It keeps the chats, Tasks, files, routines, and instructions for one effort, and everyone in it sees the same things.
- Approval and access sit at the boundary. Reading, searching, drafting, and summarising happen on their own. Anything that changes a record, sends a message, shares with more people, or cannot be undone waits for a person to approve it on a card in the chat. And you see only what you may see: connected accounts stay private to the person who connected them unless they share, a shared agent never carries someone else's mailbox with it, and admins can configure the workspace without that opening private accounts.
What waits for your approval
Outbound email and messages, writes to connected systems, changes to shared databases, sharing and deleting. An approval card shows what will happen before it happens. On your own runs you can choose Always allow for you on a card so the same action does not ask next time.
Limits
- Meridian keeps records as they came from each account. Two people who both received an email each have their own copy; Meridian does not merge them into one.
- The Workspace database of synced records is read-only. Your own tables live in separate Databases.
- Agents learn from notes you write and from work in a Space. They do not learn from accounts you have not connected.