Jiayang Cloud

Codex

Deploy what Codex builds, privately

Updated

Install the jiayang CLI, add it to Codex as an MCP server or plugin, start Codex in your project and ask it to deploy. The app goes live at its own address that only the people you share it with can open, and everything Codex did is in the audit log under your name.

Set it up

First install the CLI and sign in:

jiayang login

Then add the server in ~/.codex/config.toml:

[mcp_servers.jiayang-cloud]
command = "jiayang"
args = ["mcp"]

Or install the plugin, which adds the same server and skills that tell Codex how to deploy, share, import an app, schedule jobs, put up previews and more:

codex plugin marketplace add ss2d22/jiayang
codex plugin add jiayang-cloud@jiayang-cloud

Use the plugin or the server, not both. Either way the CLI has to be installed and signed in.

Start Codex in the project's directory

Codex starts a plugin's server in the plugin's own folder, and passes on the directory Codex itself was started from. The server deploys from there. So open a terminal in the project and start Codex there, and there's nothing else to set.

If you start Codex somewhere else, or with --cd, tell the server where the project is. Run this in the project's directory, then start Codex:

export JIAYANG_MCP_ROOTS="$PWD"

The server never deploys from your home directory or a directory above it, from a hidden directory such as ~/.ssh, or from outside the directories the session works in. Every path is resolved through its symlinks first, so a link in the project can't point a deploy somewhere else. See Where a deploy may read from.

Ask Codex to ship it

For example: "Deploy this directory to Jiayang Cloud as acme/hello and tell me the URL." Then "Share it with sam@example.com as a viewer." Codex uses deploy_app, then set_access. It can also put a change up as a preview, add a scheduled job, read the app's logs, or check that the app answers with call_app.

Long builds and Codex's five minutes

Codex stops a tool call after five minutes, and a container's build can take longer. So deploy_app answers within 45 seconds. If the deploy is still going, it says how far it has got, and Codex follows it with deploy_status until the app is live or says why it failed. You don't need to raise a timeout. If yours does stop a deploy, your CLI is older than 0.1.1: update it.

What Codex can't do

Codex works as you, with your permissions and no credential of its own. It can't open an app to the internet, add someone to your workspace, sign in, pay, read a secret's value or change who signs in. Those are yours. The agent guide has the full list.

Who can open it

Only the people you share it with: any email address, everyone at your company's domain, or a group. Viewers sign in with a code sent to their address, or with Google or Microsoft, and don't need an account first. Your app gets a signed token saying who is calling, which our SDKs check in one call.

Codex Sites or Jiayang Cloud?

Codex Sites hosts what you build in ChatGPT or Codex, in your ChatGPT workspace. Jiayang Cloud runs Python, Go and other servers in containers as well as JavaScript, can share an app with everyone at your company's domain, gives your code a signed token saying who is calling, and puts every app in one list IT can see. It works the same from Claude Code and Cursor. How the two compare.

Questions

Codex says it can't deploy from here

The server refuses when Codex was started in your home directory, or when it can't tell which project the session is in. Start Codex in the project's directory, or set JIAYANG_MCP_ROOTS as above.

Is it free?

Free covers three apps and three people, with no card, for JavaScript, TypeScript and static apps. A Python server, or any other app that runs as a container, needs Team or above. See pricing.

Can I see what Codex did?

Yes. Every deploy, share and change is in the workspace's audit log under your name.

Next