Approved menu files and website copy
Codex · illustrative everyday use case
Luis keeps his bakery website consistent from one update to the next
Luis owns a neighborhood bakery and uses Codex to maintain his simple website even though he is not a programmer.
He describes changes in ordinary language and lets Codex handle the site files. DiskDrive gives the work continuity: Codex can save approved versions, retrieve prior decisions, and carry the bakery’s rules into a later task.
The connection
How Luis connects Codex
DiskDrive uses a browser authorization flow. The person signs in directly to DiskDrive, reviews permissions, and never gives the AI a DiskDrive password or pasted access token.
- 1
Luis copies the plain-language DiskDrive setup message from the connection guide and pastes it into a Codex desktop task.
- 2
Codex checks its own settings and asks permission only if it needs to add the DiskDrive connection; Luis approves that specific change.
- 3
After one restart when required, Luis signs in through the browser, reviews the permissions, and asks Codex to confirm that DiskDrive is connected.
The everyday benefit
What goes into DiskDrive
The AI helps with the conversation. DiskDrive holds the finished files and explicit Memories that should still exist afterward.
Brand language and accessibility requirements
A record of why important site changes were made
Later, when it matters
The next time Luis changes the menu, Codex can retrieve the established wording, color choices, and accessibility checklist before touching the site. Luis keeps ownership of the source files and the business knowledge behind them.
More examples
See how people could use DiskDrive with another AI
Your archive. Your permissions.