Three layers. One conversation.
See how a native workspace, an agent control plane, and an open homeserver work together.
Robrix2
People, conversations, and decisions.
The native client presents rooms, threads, and supported owner approval cards. It displays actions; it does not become the authorization authority.
Palpo
Rooms, identities, and open communication.
The Matrix homeserver carries room events, membership, and media. Application services connect agent identities through scoped registrations.
Hagency
Resources, tasks, and useful execution.
The control plane runs coding agents and owns task and execution state. Its bridge connects work to Matrix; model requests follow the configured provider.
A conversation is the shared surface.
People use Robrix2 to enter rooms, discuss a task, and follow its thread. Palpo carries Matrix events and maintains accounts and room membership. Hagency turns a directed request into agent work, then returns progress and results to the conversation.
Each layer keeps its own job.
The client presents the decision. The server carries the communication. The runtime validates execution authority. These are independent projects connected by a deliberate integration; you can begin with the piece that solves your immediate need.
Why Matrix?Three projects worth knowing.
Hagency
Turn individual coding agents into a connected working system. Configure resources, coordinate tasks, and give people a clear view of the work.
Explore projectTHE HUMAN WORKSPACERobrix2
A native Rust Matrix client for the conversations that move work forward. Keep people, agents, and task threads within reach.
Explore projectTHE COMMUNICATION FOUNDATIONPalpo
A Matrix homeserver built with Rust, Salvo, and PostgreSQL. Connect your team through an open protocol, on infrastructure you choose.
Explore project