Move public sketches into a GitHub archive

A creative coder used Codex to gather 200+ public OpenProcessing sketches and publish them in a GitHub repo with docs and pages.

Done with Codex· Intermediate

What they did
Gonçalo Perdigão linked his GitHub account to Codex with OAuth, then asked it to handle the transfer. Codex wrote a script that opened each public OpenProcessing sketch, pulled out the HTML and JavaScript, and sorted the results into separate versioned folders. It also drafted commit messages and README files, then pushed the collection to GitHub and set up GitHub Pages.
How it went
The migration finished in under 10 minutes, and all 200+ sketches were archived in the repository. A clickable GitHub Pages site was available within seconds. The write-up does not describe any failures or manual cleanup.
Tips
For a job like this, ask the agent to show the folder plan and a sample commit before it pushes anything. If you want a safety check, require approval before any publish step or repo overwrite.

Try it yourself with Codex

Connect my GitHub account and prepare a migration plan for my public projects from [source profile URL] into [destination repo]. For each project, collect the available code and assets, place them in a clearly named folder, write a short README that identifies the project and links back to the source, and prepare one descriptive commit per project. Before you push anything, stop and show me the proposed folder structure and one example commit message for approval. After I approve, publish the repo and tell me what was copied, what was skipped, and whether any step failed.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.