Hoplite's agents can now ask your team

We stumbled on Hoplite this week and liked it straight away. It runs coding agents in the cloud as a software factory: you give an agent a thread, it works in its own persistent workspace, and it comes back with a preview and a pull request. The API is clean, the events are signed, and when an agent is unsure it does the sensible thing. It stops and asks a structured question, with a short list of options, instead of guessing. We thought it was a very cool piece of work, so we made it our weekend integration project.

Why we built it

Hoplite already does the hard part, which is getting the agent to ask. We wanted to add what Deliverd is for, which is making sure the right person answers. A question about which database to use, or whether to keep an old endpoint, is a decision someone on your team should own. Now it goes to the people you choose, in the Slack, Teams or email they already use, and the answer and who gave it are kept on the record. Hoplite keeps building, and your team keeps the say.

That is the whole idea behind Deliverd, and it is why we keep adding platforms. Agents are being built everywhere: in coding tools, in automation platforms, in frameworks and in clouds like Hoplite's. We want Deliverd to fit into as many of them as we can, so that whichever one you use, the decisions that matter still reach a person, and the evidence your compliance team needs is there afterwards. Agents do the work, and people stay at the heart of it.

How it works

An administrator connects Hoplite once, on Admin → Integrations (how). They paste a key for a Hoplite service account and name who answers: a few people, or a team. Deliverd checks the key and the permissions it has, then subscribes to Hoplite's signed events itself, so there is nothing to configure on the Hoplite side.

From then on:

1. A Hoplite agent asks. Hoplite tells Deliverd, and Deliverd checks the signature before reading anything.
2. Your people are asked. Each question becomes a short form with the same options, and goes to the people you named in Slack, Teams or email, wherever they already get Deliverd requests. A question that allows several answers lets them pick several.
3. The first answer goes back. Deliverd posts it to Hoplite, and the agent's run carries on. If Hoplite cannot be reached for a moment, Deliverd tries again rather than losing the answer.
4. Answered in Hoplite instead? Then Deliverd withdraws its copy, so nobody answers a question that is already settled.

Every question, who answered it and what they chose stays on the record in Deliverd, beside your approvals, reviews and the rest of your agents' work.

What it does not do

It asks people Hoplite's questions. It does not approve tool calls: Hoplite's cloud runs make those calls under their own policy. If you want a person to approve a merge before your factory code merges one of Hoplite's pull requests, that is one call to Deliverd's SDK before you call Hoplite's merge.

The key and the webhook's signing secret are encrypted at rest, and only an owner or an administrator can connect or disconnect Hoplite. Disconnecting stops the events and withdraws anything still being asked.

Hoplite sits under AI assistants on the Integrations page, beside everything else Deliverd works with.