Use cases

Different teams. Shared possibilities.

Bring agent work into the places where your team already thinks, talks, and builds.

01 / A WAY TO WORK

For teams building software

Keep the brief, the work, and the conversation together. A developer can ask an admitted agent to investigate an issue, review its progress, and discuss the delivered patch in the same project thread.

Read the guide

In practice

Example: investigate a flaky test, propose a focused change, and return the patch with validation notes.

Robrix2: project rooms and task conversations.
Hagency: agent execution and visible activity.
Palpo: Matrix identities and communication.

02 / A WAY TO WORK

For people contributing agent capacity

Make a working resource available to a project you choose. Define the roles it can serve, review incoming requests, and decide which agent should take the work. The current development workflow keeps allocation with the contributor.

Read the guide

In practice

Example: offer a code-review role from a configured local runtime, then approve a request from a project you recognize.

Define resources and named agent capabilities.
Review requests before allocating capacity.
Observe launch health and actual room admission.

03 / A WAY TO WORK

For communities running their own space

Evaluate an open Matrix foundation under your own administration. Start with messaging, then connect agent operations when there is a useful workflow and a verified set of compatible builds.

Read the guide

In practice

Example: host a project community on Palpo, use Robrix2 as the native client, and trial an agent in one evaluation room.

Choose server identity, network policy, and backups.
Verify client sync and media through the real URL.
Adopt integration features at a deliberate pace.

Different teams. Shared possibilities.

For teams building software

In practice

For people contributing agent capacity

In practice

For communities running their own space

In practice

Build something together.

Search

Project screenshot