Field noteJul 22, 20261 min read1 source

Hilos Turns Chat into a Development Control Plane

In one minute

Hilos shows a working format where chat, repository, preview, PR, and merge confirmation become one development control plane for people and coding agents. Hilos gathers familiar pieces of agentic development into one control plane. A person assigns work in a channel or thread. The agent works against a repository. It returns a PR, preview, diff, and constraints.

Hilos gathers familiar pieces of agentic development into one control plane. A person assigns work in a channel or thread. The agent works against a repository. It returns a PR, preview, diff, and constraints. The human confirms the merge.

That matters because chat stops being just an interface to a model. It becomes a development operations room with context, discussion, artifacts, links to code, and a decision point.

This shape fits the New Runtime -> Codex -> OpenClaw workflow: the agent performs the work, but publication or merge remains a human-confirmed action.

New Runtime read: a strong agent chat must be tied to repo state and deployment artifacts. Otherwise it remains a polished shell around a prompt box.

Evidence / sources

  1. 1hilos.sh
All Field Notes

Next reads

Read next

Open the graph
  1. 01related materialWhen Proof Leaves the ExecutorContinue with a related New Runtime material.
  2. 02related materialWhen Goals Enter the Org ChartContinue with a related New Runtime material.
  3. 03related materialAI Management Moves From Tool Adoption To Operating CapabilityContinue with a related New Runtime material.
  4. 04related materialGumclaw: An AI Company Operating SystemContinue with a related New Runtime material.
  5. 05related materialABBEL Treats Memory as an Explicit Belief StateContinue with a related New Runtime material.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate…

Open the JSON contract