Website-building request silently triggers source upload and deployment through Sites skill

What issue are you seeing?

Description

I asked Codex to build a landing page for a research paper in my local workspace:

make a landing page website for this paper with strong anti design style

I did not request hosting, deployment, or uploading the manuscript to an external service.

Codex automatically loaded the Sites skill, created a hosted project, uploaded the website source and manuscript PDF, and initiated deployment. When I interrupted with “dont publish it to site,” the deployment had already completed.

What steps can reproduce the bug?

Ask Codex to "build a website for X"

What is the expected behavior?

A request to build a website should authorize local creation and testing. The Sites skill should not be loaded unless asked.

Why this is a problem?

1. It can override the requested design direction. I explicitly requested a strong anti-design aesthetic. Automatically loading a skill with its own visual conventions can steer the result toward conventional polish, undermining the user's creative intent.

2. It uploads and hosts local content without explicit authorization. Asking to build a website does not imply permission to publish it or transfer its source, manuscript, and assets to an external service. Private-by-default hosting still moves content off the user's machine and creates an Internet-hosted copy. Access restrictions do not substitute for consent to upload.

No response

Reproduce the issue from the described entry point by asking Codex to “build a website for X” in a local workspace. Trace when the Sites skill loads and when source or manuscript files are uploaded or deployment begins. Done means local website creation and testing remain possible without loading Sites or transferring content unless the user explicitly requests it.