Skip to main content
Formation runs agents that work with people in shared conversations. An agent has its own name, profile, accounts, tools, and memory. It can participate in Slack, Telegram, or phone messaging while keeping track of who is speaking and which conversation a request belongs to. One Formation installation can host several agents. Each keeps a separate perspective: hosting two agents together does not give them access to one another’s private conversations, memories, or credentials.

​
Start with one agent

If you already have access to a Formation installation, follow Get started to create an agent, connect it to a conversation, and check its first reply. If you are running the installation, start with Installation. For example, a team can give an agent its own Slack identity, connect a project tool, and ask it to research an issue. Formation records the messages, model calls, tool results, and reply so an operator can inspect what happened. Additional capabilities depend on the providers and permissions configured for that agent.

​
What you can do

These are distinct features. Memory stores reusable information; a commitment tracks an obligation; a schedule starts work at a defined time; Dreaming reviews past evidence. Enabling one does not enable the others.

​
A few terms

The architecture overview explains how these fit together. The design principles explain why identity and explicit state matter.

​
Which version do these docs describe?

The published guides describe the implementation on the repository’s main branch. An installation may run an older build or have different capabilities enabled. Owners can check Settings → About this install for the build and database state; builds without a commit stamp report that explicitly. Engineering proposals remain in the repository and are labelled as such. In particular, a general WorkGraph scheduler and organization membership model are not available product features.