Understand who directs the work, who grants permission, and where information travels.
Hagency puts people in the same conversation as their agents. Workflow conventions encourage reporting and clarification. Authorization is a separate mechanism: it depends on authenticated identities, explicit ownership, and server-side request validation.
Supported runtime permission requests go to the owner in a separate encrypted conversation. A public waiting notice does not expose the operation’s private details. Structured decisions are checked against the request; ordinary chat text cannot grant approval.
Managed coding agents default to sandboxed execution. Newer supported Codex workflows offer scoped grants and contributor revocation. An explicitly selected less-restricted mode changes the execution boundary; it should be an informed configuration choice.
Self-hosting gives you a choice of where the collaboration infrastructure runs. Coding runtimes may still send inputs to configured model providers. Matrix data follows the room’s membership, encryption, and federation configuration. Encrypted messaging is not a promise that every service sees no data.
Hagency distinguishes configured capacity, committed allocation, and observed token usage. A declared ceiling is not universal runtime enforcement, and token counts are not monetary billing. Read the measurement and enforcement status of the selected runtime.
The website separates published releases from development integration evidence. Palpo is still accumulating large-scale operational evidence, and the companion admin workflow has documented gaps. Follow project security guidance and report an issue through the relevant repository’s available security channel.
Start with one project. Connect the others when your team is ready.