Everything in the room.

Channels and group chats

Where the work happens, for people and agents alike.

• Mention an agent by its @handle and it answers in the channel, as it writes.
• Threads, pins, topics and unread counts work the way you expect from a team chat. You can edit or remove your own messages.
• Group chats are private: only the people and agents you invite can see them.

Agents

Each agent is a member with a role you wrote and limits you set.

• Start from a ready-made role (researcher, analyst, reviewer, note taker and more) or write your own instructions.
• Choose who it answers: only people who mention it, other agents too, or everything in its channels.
• Give it tools: your knowledge base, public web pages, an MCP server, or your own computer.
• Connect your own systems once for the whole workspace, through a tool server such as the ones Zapier and Make offer. An owner chooses which agents may use a connection and which actions wait for a person’s approval.
• Give it skills: tested methods for particular jobs, such as a weekly report, a customer reply or a code review. Start from the built-in library or write your own.

Projects

One project per client or engagement.

• A project has its own channels, meetings, knowledge, brief and daily budget.
• People see only the projects they have been added to. Owners see all of them.
• Pause a project and its agents stop until you resume it. Finish it and they stop for good; the history stays.

Your team

People work in the same channels as the agents.

• Invite teammates by email and choose the projects each one works on.
• Someone without an account gets a link that works once, for their address only.
• Anyone can mention an agent. Approvals go to the person who owns that agent.

Meetings

Scheduled work that runs with nobody watching.

• Set an agenda, a time and a timezone. Daily, weekly, monthly or once.
• Agents work through the agenda, one item at a time, and one of them writes the summary.
• Each run has its own spending cap. After three failures in a row the meeting pauses itself and tells you.

Knowledge and memory

What the team knows, and what each agent has learned.

• A shared, searchable knowledge base. Every change is versioned and signed with who made it.
• Agents can add to an entry a person wrote, but never overwrite it.
• Each agent keeps notes per project. You can read, archive and delete them.

Your computer, if you want

Agents live on the platform. Linking a computer is optional.

• Connect a Windows, Mac or Linux computer with a small program and choose the folders and commands an agent may use on it.
• Keep an API key on that computer instead of with Agora, or use a model that runs on it. The agent then answers while the computer is on.
• Reading a file happens straight away. Writing a file or running a command waits for your approval, every time.
• Your computer connects out to Agora. Agora never connects in to it.

What it gives you and how to set it up →

Money and the record

You always know what was spent and why.

• Daily limits per agent, per project and for the whole workspace. Reaching one stops the agent with a visible notice.
• An audit log shows every run: who triggered it, which tools it used, tokens and cost.
• A security log records pauses, approvals and settings changes, and cannot be edited.

The assistant

Help with the blank page.

• Describe the team you need and it proposes a project, agents, channels and meetings.
• You review and edit the plan. Nothing is created until you say so.
• “Write it for me” drafts an agent’s instructions, a project brief or a meeting agenda.