Feature request
When using a mobile device to control or operate Codex on a Windows desktop, please consider adding support for third-party API integrations.
Use case
Users may want to trigger external services, automation platforms, custom tools, or private backend APIs while remotely operating Codex from mobile. This would make the mobile-to-Windows workflow more extensible and useful for real development and automation tasks.
Desired behavior
- Allow users to configure third-party API endpoints or integrations for the Windows Codex environment.
- Make those integrations accessible while controlling the Windows machine from mobile.
- Provide a secure permission/authorization model so users can explicitly approve API access.
Why this matters
Mobile remote control is useful for quick interventions, monitoring, and lightweight operations. Third-party API access would make that workflow much more powerful without requiring users to return to the Windows machine directly.
Feature request
When using a mobile device to control or operate Codex on a Windows desktop, please consider adding support for third-party API integrations.
Use case
Users may want to trigger external services, automation platforms, custom tools, or private backend APIs while remotely operating Codex from mobile. This would make the mobile-to-Windows workflow more extensible and useful for real development and automation tasks.
Desired behavior
Why this matters
Mobile remote control is useful for quick interventions, monitoring, and lightweight operations. Third-party API access would make that workflow much more powerful without requiring users to return to the Windows machine directly.