step-by-step workflow to move a loveable.dev project into openai codex with github sync, internet prompts, and clean pull requests.
share this post
stay in the loop
When we publish new experiments or playbooks, we’ll send you the highlights so you can apply them faster.
Your feedback helps us improve how we deliver practical playbooks.
Productized execution
Execution speed matters when your team is asked to ship often. Prism combines AI-assisted production workflows with stable web engineering and QA systems.
Keep learning
More experiments and playbooks from the Prism team.
from strategy to shipped ui: fast pages, clear messaging, and measured outcomes.
By Enzo Sison — Founder of Prism
Video walkthrough included below.
Loveable.dev gets your site (opens in a new tab) from zero to launch-ready fast. But when you need fine-grained control over code, design tweaks, or integrations, you need a developer-grade workspace that still respects what Loveable already built. That’s why we pair Loveable with OpenAI (opens in a new tab) Codex for our Prism clients—it keeps the AI (opens in a new tab)-powered speed while giving us GitHub (opens in a new tab)-native editing and review.
Here’s the exact process we use in-house so you can replicate it yourself.
Before connecting anything, make sure Loveable has shipped at least one saved version of your site. That gives Codex a stable codebase to work with.
Confirm you have:
Inside the Loveable dashboard, open your project settings and follow the GitHub transfer flow:
Loveable will provision a GitHub repository and surface the repo URL—copy it, because you’ll need it for Codex.
With your repo live, hop into OpenAI Codex (via chat.openai.com or your workspace):
dental-referral-buddy).During environment creation, toggle on Agent Internet Access. That allows Codex to pull in current context or docs without you manually pasting links.
Once everything looks right, click Create Environment.
Open the environment and begin prompting. You now have the best of both worlds: Loveable’s generated foundation plus Codex’s GitHub-aware AI editor.
In our demo we prompted:
Change the site’s main color from green to blue.
Codex identified the correct files, made the update, and pushed commits back to GitHub automatically—without undoing Loveable’s structure.
When Codex wraps a task, jump into GitHub. You’ll see a pull request waiting for review. Inspect the diff, request tweaks if needed, then merge.
Because the repo stays synced with Loveable, those merged changes flow back into the builder shortly after.
Return to your Loveable project and refresh. Your update (like that new blue primary color) should appear. If it doesn’t show immediately, give it a moment or refresh—Loveable sometimes caches versions before syncing the latest commit.
Loveable.dev excels at rapid prototyping and visual collaboration. But as projects scale, we consistently see teams hit limits:
Codex solves the gap by layering GitHub-native editing, diffing, and agent-powered refactors on top of the Loveable output. You keep shipping fast while gaining the safety net of real version control.
At Prism we run dozens of client sites through this exact workflow across dental, consulting, and hospitality brands.
That division of labor lets us move faster without sacrificing technical quality.
Over the past year we’ve seen recurring issues when teams stay purely inside Loveable:
Connecting to Codex gives you an escape hatch—you can patch, extend, and optimize without abandoning Loveable’s speed.
If you’re building on Loveable.dev, adding Codex is one of the smartest upgrades you can make. You’ll be able to:
Need a partner to set this up—or want Prism to handle the ongoing build? Reach out here (opens in a new tab) and we’ll help you connect Codex, optimize your stack, and keep your site performing like a top-tier digital asset.
Together, we build smarter.
— Enzo