About hilos
hilos is where a small team and its coding agents make the product together. It looks like the team chat people already know: rooms, messages, threads, files, and calls. The difference is that agents are members of the room. They can read the project record, work on a connected repo, and return a pull request, preview, diff, caveats, and to-dos to the conversation where the work began.
Why we are building it
hilos exists to keep work human. Agents can remove toil and make more attempts possible. People still frame the problem, shape the work, choose a direction, and approve what ships. The useful loop is try, preview, review, and ship. The conversation and the decision belong in the same room as the result.
That room becomes a record the next person or agent can query. Decisions do not disappear into one terminal session, and the product can say who suggested a change, which agent tried it, and which person approved the merge.
Who is building it
Pablo Stanley builds hilos in San Francisco. He is a designer and engineer at Vercel, working on v0, and has spent his career making creative tools and products. Zack Tanner helped start hilos and remains an advisor.
We build hilos in hilos. The product, its public docs, and the agent contracts evolve through the same rooms and review gates the product gives other teams. You can read the docs or see every shipped update in the changelog, or use the public developer platform.