Docs
How Tonoman behaves
These pages are the product's own definition: each line is a behaviour Tonoman is built and tested to have — 529 of them, on 21 pages. When the behaviour changes, so does the page; one that is planned is not here until it is built.
Agents
Agenta named AI worker in one tenant.Agent accounta person as one agent knows them — their Slack user id, what the agent calls them, the account they turned out to be, and their own inference login on that agent.Conversationone thread with an agent — a message becoming an answer, and what the agent remembers of that thread.Inferencehow an agent thinks — which provider (Claude or Codex), which model, and whose login pays: one shared login, or each person's own.Turn userthe Linux user a piece of an agent's work runs as, inside the worker — one for each person in a tenant, and one for each agent.Slack appan agent's own app in a Slack workspace — how people reach it.
Skills and tools
Skilla packaged ability an agent is granted.Meeting recapa built-in Skill.Agenda briefa built-in Skill.Runone execution of a skill, on one item, for one person.Credentiala secret Tonoman holds for a tenant — a token, a login, a published calendar address — always handled by reference, never shown.Connectionan outside service an agent or a person has linked — a published calendar address, a Google or Outlook calendar, a Plaud recorder.
Knowledge
People and organizations
Accounta person.Personsomeone in a tenant's organization — a member of the tenant, or someone its agents work with — placed on the chart with their title and the person they report to.Membershipan account's place in one tenant, with a role.Organizationone picture of a tenant's people and agents and how they stand to each other.Tenanta company.