Clarification: paid image-focused desktop clients using official Codex app-server and ChatGPT sign-in

[im942k]

Hi Codex team,

I'm developing DROPOLY, a local-first macOS app for image generation and editing. Before releasing it commercially, I'd like clarification of the applicable terms from the responsible OpenAI team, or help finding the right contact.

Integration being considered for release

• The app launches the user's locally installed official Codex CLI with codex app-server --listen stdio:// and communicates through the documented app-server protocol (account, thread and turn methods).
• Codex manages sign-in to the user's own ChatGPT account. The app does not read/copy Codex authentication tokens, implement its own OAuth client, or call private OpenAI backend endpoints directly.
• Image generation/editing is requested through Codex's built-in image-generation capability. Prompts and reference images are sent to OpenAI through Codex; projects and image files are managed locally.
• Users install Codex separately. There is no shared account, pooled subscription, resale of account access, or bypass of usage limits.

Proposed business model

A free private beta, followed by a closed-source desktop app with a one-time KRW 49,000 price for the interface, workflow and local asset-management features, including one year of app updates. The price would not include an OpenAI subscription, AI credits, unlimited generation or guaranteed future model availability. Users would need their own eligible ChatGPT/Codex access and remain subject to its limits and terms.

Questions

1. Do the current terms permit distributing and selling a third-party app with this design, including an image-focused, non-coding workflow, using each user's ChatGPT/Codex subscription through the official app-server interface?
2. Is separate written permission, a partnership agreement or client registration required? If so, which team/intake handles this specific question?
3. How should developers distinguish permission to distribute commercially from production support/stability guarantees? I have received guidance mentioning experimental/unsupported production status; I do not want to mistake that for either commercial approval or a prohibition. Does that caveat apply to the standard stdio integration described above, and what is its practical scope?
4. If free distribution and paid distribution are treated differently, or image generation/editing has additional restrictions compared with coding, could you point to the applicable public terms?

I have read the app-server documentation and followed the official discussion link. Support has clarified the technical connection but has not resolved this commercial-distribution question. I am not treating the open-source license of Codex, technical availability, or other third-party apps as authorization to use OpenAI services.

If this is outside the maintainers' scope, a referral to the responsible human team would be greatly appreciated. Thank you!