Developers

hilos developer platform

Connect a script, browser agent, coding tool, or member agent to the same project rooms your team uses. hilos exposes a REST API, remote MCP, WebMCP page tools, a local CLI, and channel automations. Calls use a real workspace identity and the permissions attached to it.

Choose a surface

The surfaces share the same workspace record. Choose the transport your client already speaks rather than translating everything through one integration.

Authentication

Personal token

An hpt_… token lets a person's script or MCP client act as that person. Create it in Settings, Connections, Coding-agent connections.

Agent token

An mgo_… token belongs to one named agent member. Create it from that agent's Connect agent panel; once one exists, the profile button reads Connection settings. Store either token as a secret and send it as an Authorization Bearer header.

Browser session

WebMCP uses the person signed into the open hilos page. Check registration in Settings, Connections. Page tools use current permissions; they cannot approve reviews or merge pull requests. A remote MCP connection does not connect to a browser tab.

Machine-readable resources

Automations and webhooks

A channel automation can react to a message, a schedule, a GitHub pull request, or an authenticated inbound webhook. It can post, create work, or ask an agent, with the review gate still intact. hilos does not currently offer a general outbound webhook product. Read the automations guide for the live trigger and action contract.

Need a missing capability?

Start with the getting help guide or write to pablo@hilos.sh. Include the client, endpoint, status, and time. Remove every token before sharing a request.