Motions are the atomic unit
A motion is a natural-language proposal for action. Every non-trivial thing your team decides — a feature to ship, a contract to sign, a plan to commit to — can be captured as a motion. When you give Monnet a motion, it works through three phases with your team:Gather input
Search the web, read past motions, pull context from files, and ask the right people the right questions.
Align
Draft and refine the proposal, post comments, ping approvers, iterate — until the team is on the same page.
The team: humans and agents
A workspace holds the humans and agents collaborating on motions. Humans have roles at the workspace level (Owner / Admin / Member) and can also have motion-level roles (Editor / Commenter / External). See the Glossary for the permission matrix. Agents are AI teammates. They can pick up a motion, do the work, and report back. Monnet supports three agent connectors:- Claude Managed Agent — hosted by Anthropic. Easiest setup.
- Daemon Agent — runs on your own machine, picks up work when assigned.
- GitHub Actions — dispatches a workflow in your repository.
Tools: what Monnet can do
Tools are what make Monnet capable of coordination. Without tools, an LLM can only answer with text. With tools, Monnet can read, write, message, and delegate. Monnet’s built-in tools fall into four categories:| Category | What Monnet can do |
|---|---|
| Knowledge | Search and browse the web, search and read motions, read files. |
| Motion | Edit the summary, edit the body, edit the plan, set the priority. |
| Communication | Post comments, send messages, ask for approval. |
| Delegation | Prompt an agent. |
Interfaces: where you interact with Monnet
Three surfaces:- Inbox — the motions that need your input, across all your workspaces. Your home page.
- Motion page — the proposal itself: body, plan, discussion, versions, files. Where you comment, approve, and chat with Monnet.
- Workspace — team, agents, policy (MONNET.md), skills, settings. The admin surface for your organization.
MONNET.md: persistent context
Every workspace has aMONNET.md file. It’s the brief Monnet reads at the start of every motion — how your team works, what your priorities are, who approves what. You write it in plain English.
MONNET.md grows with your team’s shared understanding. Add a line when Monnet makes the same mistake twice, when you find yourself re-typing the same clarification, or when a new teammate would need the same context to be productive.