Author: philz42
Channel: #general
Link: https://discord.com/channels/1405685085923049482/1405686123908567141/1540126413825253526
Description
Add a native exe.dev API integration to allow VMs to control and spawn other exe.dev VMs without requiring HTTP proxy workarounds.
Context
Currently, there is no dedicated exe.dev integration for self-referential use cases. Users need to work around this limitation by either:
- Using HTTP integrations as a proxy
- Creating peer VM integrations that attach to themselves
This is inconsistent with the extensive set of other integrations available in the platform.
Use Case
A user wants to set up a software factory where a control center VM uses an exe.dev API token to spawn and manage other exe.dev VMs. This is a common pattern for orchestration and automation scenarios.
Status
Marked as "on the roadmap" by the team.
Author: philz42
Channel: #general
Link: https://discord.com/channels/1405685085923049482/1405686123908567141/1540126413825253526
Description
Add a native exe.dev API integration to allow VMs to control and spawn other exe.dev VMs without requiring HTTP proxy workarounds.
Context
Currently, there is no dedicated exe.dev integration for self-referential use cases. Users need to work around this limitation by either:
This is inconsistent with the extensive set of other integrations available in the platform.
Use Case
A user wants to set up a software factory where a control center VM uses an exe.dev API token to spawn and manage other exe.dev VMs. This is a common pattern for orchestration and automation scenarios.
Status
Marked as "on the roadmap" by the team.