Hi HN, I’m building AgentWing.

The idea is simple: AI agents usually execute work as one long sequence:

plan → act → wait → observe → act again → verify → finish

That makes agent workflows feel slow, especially when parts of the task do not actually depend on each other.

AgentWing adds a director layer that turns one agent task into multiple isolated worker runs. The director decides which parts can run at the same time, assigns each worker its own scoped job, runs them in parallel, then verifies and combines the result.

For an enterprise-grade setup, each worker can run inside its own isolated VM or sandbox, so every agent has its own environment, files, tools, and execution boundary.

Example:

Task: “Research a market and prepare a competitor summary.”

A normal agent may do this sequentially:

- find competitors - analyze pricing - compare positioning - look for user complaints - write summary

AgentWing can run the independent parts in parallel:

- worker A finds competitors - worker B analyzes pricing - worker C checks positioning - worker D gathers user complaints - verifier combines the final result

The goal is to make agent tasks feel much closer to instant by removing unnecessary sequential waiting.

I’m experimenting with two modes:

- split mode: different workers handle different parts of one task - race mode: duplicate workers try the same subtask and the best verified result wins

This is still early. The hard part is the director: deciding what can safely run in parallel, what must stay sequential, and how to verify the final output.

I’d love feedback on where this breaks, what workflows would benefit most, and what demo would best show the speedup.