Hey, thanks for the feature request. Cool idea, especially the part about factory federation.
We don’t currently have a fully autonomous, config-defined “factory” with built-in cross-factory federation. But some building blocks are already available if you want to put something together in that direction:
Projects: a cloud coordinator that orchestrates and spins up worker agents Projects | Cursor Docs
Automations: run agents without a human in the loop via triggers and schedules Automations | Cursor Docs
Federation between separate factories, meaning cross-owner agent communication, isn’t supported yet. That’s the newest part of your request.
Related topic: there’s a thread about a cloud orchestrator that coordinates existing agents. You might want to take a look and add a vote Cloud Mediator/Orchestrator agent
I’ll leave your request open so it can collect community votes. If you can describe the federation use case in more detail, like how factories should communicate and what trust boundaries you need, that’ll help us evaluate the idea.
I think you should target level 5 dark factory autonomy.
This will be the future.
I believe this can be easily done by a company of your scale.
I explored the above 2 suggestions but they are inadequate and brittle. They cannot achieve 24/7 hands off operation as there is not but in mechanism to handle operational issues and factory tuning without running into issues. I actually did not do an implementation. This was more of the thought experiment and conceptualisation as actual implementation will burn tokens and credit. Conceptually there are may ways it will not be affective as a dedicated level 5 dark factory framework as the glue code and set up i brittle and can break.
Thanks for expanding on the idea. The level 5 dark factory vision is clear, and honestly the 24/7 hands-off setup with self-healing and automatic tuning is a strong ask.
I’ll be direct. We don’t have a dedicated framework for this right now. Projects and Automations are building blocks, and you’re right that they’re not enough for fully autonomous operation with no human in the loop. There isn’t a mechanism yet that can handle operational issues on its own and retune the factory on the fly. Federation between separate factories cross-owner communication and trust boundaries is also a separate and very new part of the request.
This isn’t something I can share plans or timelines for. I don’t want to promise what isn’t there yet. I’ll keep the thread open so it can collect community votes.
To make the request stronger for evaluation, it’d help if you can spell out specifics.
How exactly factories should share info, and what trust boundaries you need within one org vs cross-owner
What exact operational issue handling you expect from level 5 what the system should detect, how it should recover, and what it should tune without a human
The more concrete the scenario, the clearer it is which gaps in the current building blocks we should close first.
I think the starting point would to be able to use Cursor cloud agents to build agent teams, sub teams, sub sub team, like docker cloud agents. I think this would be a good point to start.
Once we can define and deploy and agent team, we need to be able to assign them roles.
The communication and work flow orchestration between the defined agents.
Defining workflows and procedures like the methodologies that need to be followed.
Inter factory communication would be from how I see it down stream library consumers sending feedback and feature requests upstream. Also lunching experimental projects with the view of improving the main library, if the experiment proves to be sound.