01The approval habit becomes the release habit
Working with Codex CLI, you already live in a rhythm: it proposes, you review, it applies, it commits. Publishing through the pillar pipeline adds one meaning to that rhythm. The commit you just approved is also the thing that goes live. There is no separate deployment ceremony: the review gates the work, the push fires the deploy, and neither command is new.
This is why the CLI needs nothing from the host. It wants no token pasted into a dashboard and nothing installed on your machine. Codex pushes to a repository you own with the credentials you already gave it, and the deploy happens on the far side of that push.
02Who does what, and where
| Step | Where it runs | Keep in mind |
|---|---|---|
| Write and review | Your machine, Codex CLI | The approval prompt is your chance to read the diff before it becomes history. |
| Commit and push | Your machine to GitHub | Access is scoped to the repository. LoomWeb never sees your GitHub password. |
| Build and validate | LoomWeb | The static build must come out clean before anything can go live. |
| Serve the release | LoomWeb, Australian infrastructure | HTTPS on the loomweb.co address, or on your domain once attached. |
| Roll back | LoomWeb portal | One click to any kept release, with no reverting commits required. |
The split is deliberate: your agent owns the repository side, the host owns everything after the push.
03What the push cannot carry
A push deploys files, and that is all it deploys. Codex cannot push a database migration, a cron job or a running process, because static hosting executes none of those. If the project needs a backend, this is the wrong host for that part, and no prompt will argue the serving layer into running one. It also cannot press the rollback button for you, since the portal is account-side by design. None of that is hidden fine print; it is the shape of the product, and for a site made of pages the shape fits.
04When several agents share the repo
A Codex-driven project can hand off to the Claude Code loop or to Cursor mid-week without ceremony, because the handover medium is git. Each tool reads the same history, makes the same kind of commits, and pushes to the same remote. The hosting side cannot tell which editor made a change and does not need to. For the hosting details specific to Codex projects, including the sandbox export flow, the Codex hosting guide goes deeper.
05Codex CLI publishing questions
Does Codex need a LoomWeb account?
Nothing on our side. Your account, your repository, its existing GitHub access. The push does the triggering; the tool's name never comes up.
What if it pushes half-finished work?
The push deploys like any other. Rollback is one click, or leave a change that is still taking shape on its own branch until it is ready to merge.
Can I preview before the push?
Wherever you preview today, keep doing that. The host only ever sees committed, pushed work, so nothing half-written goes live by accident.
Where does billing sit?
With BSimple (MrSoftware Pty Ltd), after a fourteen-day trial that never charges you at signup. $39 a month after, cancelled from the portal.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.