Flux Agents Work as a Team: Side Threads, Parallel Work, and Agents in Other Projects

A real hardware product is not one board. It is a main board, a few daughterboards, an enclosure, and a library of parts that all of them use. Until now, an AI engineer worked on this one step at a time, in one conversation. You waited for each step before the next one could start.

The Flux agent can now work as a team. Hand it a complete product, and it plans the work. It starts side threads that work at the same time, and it starts agents in other Flux projects, for example one for each daughterboard or one for each part. The Flux agent watches every one of them, steers them when they go off the brief, and brings the results back to you. It all runs in the cloud, so you can close your laptop and Flux keeps working.

Side threads for focused work

Some jobs are self-contained: review a power stage, find second sources for a BOM, or write the test plan. The Flux agent can give a job like this to a side thread. The side thread gets a clear brief and a clean start, so it focuses only on its job. Your main conversation stays on the big picture.

Each side thread shows as a card in the chat, with its name and its progress. Open a card to see the work as it happens. When the side thread is done, the Flux agent reads the result, checks it against the plan, and decides the next step.

Parallel work

A human engineer does one job at a time. A team of agents does not have to. Jobs that do not depend on each other run at the same time. While the main board is captured, the daughterboards are designed and the enclosure is modeled. Eight circuit blocks can be reviewed at once, not one after another.

This changes how long a complete device takes. You do not wait for one long chain of steps. You get the results of many jobs in about the time of the longest one.

Flux keeps working when you close your laptop

Flux runs fully in the cloud, not on your computer. The Flux agent, its side threads, and the agents in other projects all keep working when you close the browser. Start a large job, close your laptop, and go to your next meeting. When you open the project again, you see what every agent did while you were away.

Agents in other Flux projects

In Flux, every board and every part can be a project of its own, with its own schematic, layout, history, and owner. That is how a hardware team keeps one source of truth for each design. The Flux agent works the same way. It can create a project for a daughterboard or a part, and start an agent in that project with its own brief.

Each agent works only in its own project. The Flux agent in your main project tracks all of them from one place. It can check their progress, send them new instructions, and stop work that is no longer needed. You can open any of those projects to see what its agent did.

Example: a product with daughterboards

Ask for a commercial smart thermostat with a main board, a front display board, and a 24 VAC power and relay board. The Flux agent writes a brief for each board: its outline, mounting holes, connectors, and the enclosure openings that it must line up with. Each daughterboard gets its own project and its own agent, and all of the boards are designed at the same time.

When the boards are done, the Flux agent places them in the main assembly with the enclosure. It measures the clearances and the connector alignment in millimeters, and it reports what fits and what does not.

Example: organize and repair a part library

A part library is only as good as its worst part. One wrong pin number can cost a board spin. Ask the Flux agent to create or check the parts for your next design. Each part gets its own part project and its own agent. The agent reads the datasheet, checks the symbol, the footprint, and the pin functions, and fixes what is wrong.

When a part is repaired, the agent publishes a new version of it. The boards that use the part can then update to the corrected version. Many parts are checked at the same time, so a full library cleanup is a job you can start before lunch.

You stay in control

A team of agents still works for you. The Flux agent follows your requirements, and every change is in the project history. Decisions that change the product wait for your approval, for example a change that moves an interface, changes the enclosure, or makes a board larger. You can open any side thread or project, see what its agent did, and give new instructions at any time.

Try it

Open a project in Agent mode and describe the complete product. For example:

We make building automation products. We need a wall-mounted smart thermostat for commercial offices, with a main board, a touch display board, and a 24 VAC power and relay board. Design the front board and the power board as their own projects at the same time. Also design the wall enclosure, and then check that all three boards fit in it.

The Flux agent plans the job, starts the agents, and brings the results back to you. One request. A whole team of AI engineers.