Codex from Zero to One: Setup, Everyday Features and Overseas Business Projects

Start with one product. Install Codex, sign in, organize a project, build an English product page and short-video script, then learn to revise, verify and reuse your work. Includes Chinese diagrams and copyable prompts.

If you have never coded or built a project with AI, start here. We will use one sample product to create an English page you can open on your computer and a script you can turn into a video.

Follow sections 01–07 for your first attempt. Explore the business examples and advanced features afterward. The organizer pouch is a practice example; replace it with your verified product details to reuse the workflow.

01 · What to use Codex for

Describe the outcome you want. Codex can read project files, write and edit code, run checks and save results as files. An English product page, a quote calculator or a data-cleaning script makes a useful first project.

For a short piece of copy, a regular chat may be enough. ChatGPT Work is also suited to documents, research and spreadsheets. We use Codex here because we are turning product information into a working, editable web page.

02 · Download, install and sign in

Open the official installation guide below and choose your operating system. Current documentation may call the download the “ChatGPT desktop app”; select Codex inside the app. If Codex is already installed, check for updates first.

Mac: open the Apple menu → About This Mac to check your chip and operating system, then choose a compatible installer. Open the downloaded file, follow the installation prompts and launch the app from Applications.

Windows: choose the Windows download and follow the official installation steps, then launch it from Start. Linux users should follow the official Linux guide. Use the installer for your own system.

Open the official desktop installation guide

Open the app and sign in with your ChatGPT account. Use your existing sign-in method. If you do not have an account, complete registration and any email verification on the official account page, then return to the app. If you normally use Google sign-in, keep using it to avoid creating a second account by mistake.

Sign-in may open your browser. After confirming the account, accept the prompt to return to the app if shown. Check that the desktop app has reached its main screen; successful browser sign-in alone does not confirm that the app is signed in.

Open the official ChatGPT account page

03 · Do you need to pay?

Start by signing in with your ChatGPT account. You do not need to buy API credits or find an API key first. Available features and usage depend on your plan; free accounts may also have limited usage. Check whether your account can start a task before deciding to upgrade.

A subscription is not unlimited usage. More complex tasks and longer context can consume more. Check the app’s usage page and official pricing for current limits, reset times and features. ChatGPT Work and Codex share usage rather than providing two independent allowances.

An API key is a separate access method with separate API billing. A ChatGPT subscription does not provide an equivalent API credit balance. Skip API setup for this first exercise.

Check official plans, usage and features

04 · Create a project and organize the source material

Create a folder named “Codex出海练习” on your computer, with two subfolders: “原始资料” for inputs and “输出结果” for outputs. Include only the files needed for this exercise.

Create a local project or open a folder in the app and select “Codex出海练习”. Choose Codex, then start a new task. Labels can change by version; confirm that the project is connected to this local folder.

Save the sample below as “产品资料.txt” in “原始资料”. On Mac, switch TextEdit to plain text before saving; on Windows, Notepad works. You can begin without a product image.

This is a fictional practice product, not a product for sale.
Product: zippered organizer pouch.
Known facts: zipper closure; holds small accessories such as cables and earphones.
Target market: United States.
Audience: commuters carrying small accessories.
Demo: loose accessories on a desk → place them in the pouch → close the zipper.
Unconfirmed: material, dimensions, waterproofing, certifications, price, stock and delivery times.
Copy: natural English and short sentences; invent no sales figures, reviews or results.
Contact email: not provided; do not create a functioning contact button.

05 · Your first task: an English product page

Ask it to confirm the source material before building. Send the full prompt below instead of asking for a “nice website”. For this first attempt, use a local page without a database, login or payment system so you can follow the whole process.

Read “原始资料/产品资料.txt” in this project. Summarize the known facts and missing information, then complete the following.

1. Create “输出结果/product-page.html”: an English product page that works on desktop and mobile, covering the use case, confirmed features, a three-step demonstration and FAQs.
2. Use one self-contained HTML file with embedded CSS. No external fonts, libraries or remote images; it must open by double-clicking. Without a product photo, describe the demonstration in text instead of inventing a photo.
3. Clearly mark it as a practice page. Do not invent specifications, reviews, certifications, prices, stock or delivery promises. Do not add misleading purchase or contact buttons.
4. Save a Chinese review copy as product-copy-zh.md.
5. Check that the file opens, the layout does not overflow horizontally and no unsupported facts were added. Perform the checks you can; identify any you cannot perform.
6. Preserve the inputs and write only to “输出结果”. Give me the actual file paths and opening instructions, not just code in chat.

Read the progress messages while it works. If a permission request appears, check which file it will access or which command it will run. This exercise needs only the practice inputs and output files. If it asks to connect customer email, buy a service or upload an unrelated folder, ask why first.

When finished, open “输出结果”, find product-page.html and double-click it in your browser. Review the Chinese copy against the input. If the file is missing, ask it to finish saving the actual file.

06 · Revise until the result is usable

Continue revisions in the same task so the previous context remains available. Specify the section, the problem and the desired change. Instead of saying “the page looks bad”, try this.

Revise product-page.html.
Shorten the headline and keep the subtitle to at most two sentences. Improve body-text readability and use consistent type sizes and spacing.
At a 390-pixel mobile width, prevent horizontal overflow and stack the three demonstration steps vertically.
Preserve the confirmed facts and add no new selling points. Open and check the result after editing. If browser access is unavailable, tell me what I need to check manually.

Check four things: the file exists; it reads well at desktop and mobile widths; the English adds no unsupported promises; and links and buttons do what they claim. Send the full error or screenshot back to the same task and ask for a fix plus a fresh check.

Opening a local file does not put it online. Customer access requires hosting and a public URL, and a real product page needs the missing product details. A path on your computer is not a shareable website address.

If the local page will not open, check in this order

First find the file in the project folder. If Windows hides extensions, enable file name extensions in File Explorer and check that the file is not product-page.html.txt. On Mac, inspect Name & Extension in Finder Get Info. A screenshot of code is not a web page.

If double-clicking displays source code, use Open File in a browser. If images are missing, check that their files accompany the page and that paths are correct. Include images when handing the page to someone else. The original single-file example has no external images; keep the first version simple.

If the project later needs a local server, ask Codex for the actual start command, working directory and preview URL. Do not assume every project opens by double-clicking HTML or install unrelated dependencies to fix an unknown error.

Diagnose product-page.html in this project before rewriting anything.
1. Confirm its actual path, extension and saved state.
2. Use the reported symptom to distinguish a file-opening problem, image path issue, styling defect or need for a local server.
3. Preserve the original and make a corrected version. Fix only the identified issue; add no product claims.
4. Before running commands, explain the directory, purpose and dependencies. Do not execute scripts from unknown sources.
5. Open and check the result where possible. Give me the correct entry point, changes made and remaining manual checks.
Observed symptom: [paste the full error or attach a screenshot]

07 · Reuse the product facts for a video script

Use the same product facts to create an approximately 20-second English short-video script and save it to “输出结果/video-script.md”.
For each time segment, provide the visual, English voiceover, Chinese subtitles and required footage.
Start with scattered desk accessories, demonstrate packing, then show the organized result.
Use natural spoken English. Invent no personal experience, sales figures or waterproofing claims. End with one save-for-later reminder.
Include a filming checklist and check whether the voiceover fits about 20 seconds; shorten it if needed. Create the script only, without calling paid image or video services.

Read it aloud and time it, then compare every shot with what you can actually film. Ask it to replace unavailable footage with feasible actions. A script is not a finished video. Using Xiaoyunque or another generation service requires access to that tool, the necessary inputs and confirmation of generation costs.

08 · Everyday features to learn first

Projects: keep the material and tasks for one business together. Separate products where needed to avoid mixing prices, audiences or specifications.

Tasks: use one task per clear deliverable. Continue the same task when revising a page; start another for a new quote calculator.

Files and images: identify the file or attach it, then ask Codex to confirm it was read. Supply text when small print is unreadable.

Preview and revision: request actual file paths, inspect the output and point out problems with a screenshot. Saving, previewing and deploying are separate steps.

Models and reasoning: start with the available default. Adjust for complex logic later. Clear inputs and acceptance criteria matter more than choosing elaborate settings on day one.

09 · Apply it to overseas business

Cross-border ecommerce: complete one SKU page before expanding to a catalog. Provide verified specifications, images, target market and brand voice so the page, FAQs and script stay consistent. Check units, compatibility and delivery promises before publishing.

Read the customer inquiry and quotation rules I provide. Extract the product, quantity, destination, requested timeline and missing information. Save an English reply draft with a Chinese review copy. Treat unconfirmed prices, trade terms and lead times as questions to resolve. Draft only; do not send email.

Foreign trade: use the prompt above for an inquiry draft. Remove personal information not needed for the task. Confirm prices, lead times and trade terms before replying.

Manufacturers: provide the company profile, equipment list, verified certifications and product scope to build an English presentation page. Do not fill gaps with invented capacity, client names or test results. Start with one product line.

Adapt the Chinese spoken script I provide for a US audience. Preserve the core point and replace locally specific expressions with clear equivalents rather than translating word for word. Save an English script, Chinese review copy, shot suggestions and facts to verify in one Markdown file. Add no experiences or achievements I did not provide.

Creator brands: use the prompt for localization, then read it yourself and preserve your speaking style. Subtitles, covers and editing can follow as separate tasks once the script and visuals fit together.

10 · When to use browser control, plugins and skills

Add tools when the task needs webpage interaction or authorized access to an external service. Supported versions and regions can enable computer operation through the Computer Use plugin: find it in Plugins, install and enable it, then grant the required system permissions. Mac may need Screen Recording and Accessibility access; Windows target apps need to be visible on the active desktop.

Begin with a read-only task, such as reviewing a specified public page and listing its product sections with links. Complete account sign-in yourself when needed. Connecting a tool does not grant access to every account.

Read official computer-use and permission guidance

Skills preserve a repeatable working method. After completing the product-facts → page → script → checks workflow, ask Codex to turn it into a skill for future products. Plugins commonly add tool connections and related capabilities; skills package reusable instructions.

Scheduled tasks can later handle recurring checks such as checking your own website links. First complete one run, then define the frequency, scope and notification conditions. A completed check does not mean an email was sent, a page published or a sale made.

11 · Choose skills by the output you need

A skill is a reusable working method. For English product material, it might follow the same sequence every time: read the source, verify facts, write English, inspect the layout and save the file. You do not need to repeat every instruction.

It does not change the model or automatically grant account access. Use the skills below as needed. Names can vary by version or plugin; select the actual name shown in your own skills list.

Documents: useful for English company profiles, product manuals and proposals. Provide the Chinese source, verified product details and brand requirements, then use a document skill to create an editable Word file. Check heading levels, table pagination and image placement.

Look for Documents in the skills or plugin directory. Chat text alone is not the deliverable; open and inspect the actual .docx file.

Use an available document-creation skill to turn “原始资料/公司介绍.docx” into an English buyer introduction.
Structure: company overview, product range, cooperation process and information to confirm.
Preserve verified data; invent no certifications, clients or capacity. Use concise, natural language.
Save an editable Word file and a Chinese review copy in “输出结果”. Check pagination, tables and images. If the required skill is missing, identify what needs installing first.

Spreadsheets: use for margin calculations, inquiry tracking and advertising-data preparation. Define currencies, taxes, shipping and reporting periods before asking for formulas. Separate editable inputs from calculated outputs.

Look for Spreadsheets. Verify formulas and definitions, not just colors. Manually calculate at least one row to check the result.

Use an available spreadsheet skill to create a single-product margin workbook.
Inputs: selling price, purchasing cost, packaging, shipping, platform commission rate and advertising cost, all monetary amounts in USD.
Commission = price × commission rate. Margin = price − purchasing − packaging − shipping − commission − advertising. Margin rate = margin ÷ price.
Avoid division-by-zero errors when price is zero. Clearly state that taxes and returns are excluded.
Validate the formulas with a row labeled “Practice”, and leave a blank input row. Save as “输出结果/单品毛利测算.xlsx”.

PDF: read supplier catalogs, extract specifications or prepare customer-facing documents. A PDF skill helps check both content and rendered pages. Mark unreadable scans or small print as unresolved instead of guessing.

Look for PDF or pdf. Try the following with a supplier catalog.

Use a PDF skill to read the uploaded catalog and extract model numbers, dimensions, materials and source page numbers into a table.
Keep different variants separate. Mark unreadable or missing fields as “To confirm”.
Save the table and a list of supplier questions in the output folder. Do not treat visual guesses as specifications.

Presentations: create English partner introductions, channel proposals or customer presentations. Look for Presentations. Define the audience and objective, set a slide count and keep each slide focused. Request editable slides rather than a single flattened image.

Use an available presentation skill to turn my approved English company profile into a six-slide buyer deck: what we do, product range, use cases, cooperation process, FAQs and next steps.
One topic per slide. Invent no client cases or results. If an image is missing, leave a clearly labeled image slot.
Save an editable .pptx and check every slide for clipped text and distorted images.

Images: use for article illustrations, advertising concepts and product scenes. Look for ImageGen or imagegen. Provide the reference product, specify details that must remain unchanged, then define the aspect ratio, scene and copy. Check shape, ports, quantities and text against the original.

An image skill is not video generation and does not guarantee model access. Ask which tool is available and whether additional charges apply; confirm separately billed work before generation.

Use an available image-generation skill to make a 4:5 commuting-scene illustration for this organizer pouch.
Match the uploaded product photo: preserve shape, zipper placement and color. Use a clean desk with cables and earphones. Add no logos, sales figures or text.
First confirm that you can read the reference and explain the generation tool and any charges. Wait for confirmation of additional fees. Compare the generated product details with the reference and save a new file without replacing the original.

12 · Install and invoke a skill

First, check what is available. Open Skills in the app sidebar, or ask Codex: “Which document, spreadsheet, PDF and image skills can you actually invoke in this task? List their exact names.”

Then add only what is missing. For plugin-provided skills, find the corresponding plugin in Plugins, review its description, dependencies and permissions, then install and enable it. For standalone local skills, use $skill-installer to inspect the curated catalog. The prompt below lists options before installing anything.

 $skill-installer
List the skills in the current curated catalog for documents, spreadsheets, PDFs and image creation. Include exact names, purposes and installation status. List options only; do not install them in bulk.

After obtaining the exact name, ask to install that specific skill, such as pdf. Avoid duplicating an equivalent plugin. Newly installed skills are normally discovered automatically; restart the app if the list does not refresh. Review third-party sources, instructions and dependencies before running installation commands.

Select a skill actually available in your current composer. Codex CLI and the IDE extension support /skills or $ mentions; the built-in creator can be invoked with $skill-creator. Desktop controls depend on the current version, while ChatGPT uses @ for skills. If unsure, ask to use the currently available PDF skill and identify which skill was loaded.

Open the delivered file to verify the result. Seeing a skill name in chat does not prove successful installation, execution or access to an external service.

Read the official skill installation, invocation and creation guide

13 · Turn your overseas workflow into a skill

Start with a task that already works well. Once you are happy with the product-facts → English page → video-script workflow from this tutorial, preserve its format and checks for the next product.

Use the built-in $skill-creator. The name overseas-product-kit below is a new skill we are creating, not an existing skill to search for and install.

$skill-creator
Turn our completed and approved workflow into a skill named overseas-product-kit for creating an English page and short-video script from verified product facts.
Inputs: product fact file, target market, audience and optional product photos.
Steps: validate inputs and list gaps; write English copy with a Chinese review version; create a self-contained local HTML page; write an approximately 20-second script and filming checklist; verify facts, files and mobile readability.
Outputs: product-page.html, product-copy-zh.md and video-script.md in “输出结果”.
Rules: invent no specifications, certifications, reviews or achievements; preserve source files; do not publish, send emails or call paid generation services automatically.
Start with an instruction-focused skill without unnecessary scripts. Explain its saved location, scope and invocation, then test it with a product labeled as practice. Identify any steps that cannot be completed.

After creation, review SKILL.md and confirm the inputs, steps, outputs and boundaries. Test it with another practice input. Do not stop at “created successfully”; verify the saved outputs and check for missing sections.

For future work, select $overseas-product-kit and supply the new source location, market and audience. A skill name without product information is not a complete task.

$overseas-product-kit
Use “原始资料/产品资料.txt” for the US market and a commuter audience. Check the inputs first, then follow the skill to create the English page, Chinese review copy and video script. Save this run in “输出结果/本次练习” without overwriting the previous outputs.

14 · Troubleshooting your first attempt

Sign-in keeps spinning: return to the browser and confirm sign-in completed, then look for a blocked “open app” prompt. Check that the browser and app use the same account and try signing in again once. If it still fails, record the full error and check official service status.

Codex or a feature is missing: check for app updates and confirm the account, plan, region and administrator restrictions. Follow current official instructions when button locations change.

Usage exhausted: check the usage page for the reset time. Reduce the task to one product, page or file. Consider an upgrade only if you need more usage, rather than repeatedly resubmitting the same task.

Files cannot be read: confirm this is a local project and that the file is inside a connected folder. Provide its exact filename instead of “the thing on my desktop”.

It says done but there is no file: request the saved path and check the folder. Ask for an actual file rather than accepting chat text as delivery.

The page is blank or errors: keep the full error and screenshot and continue the same task. Explain whether you double-clicked the HTML or used a local preview URL. Fix it before deployment.

The English sounds unnatural: identify the audience, setting and awkward sentence. Request two alternatives with Chinese review copies. Verify the product facts yourself.

Check official OpenAI service status

15 · Should you learn the CLI or API later?

Not yet. The desktop project is enough for this exercise. If you edit code regularly, explore the Codex IDE extension; if you prefer terminals, learn the CLI. Study APIs and billing when you need to call models from your own software.

Today’s goal is simple: open your page, locate the saved script and get an identified problem fixed. Then repeat the process with one real product and complete source information.

Explore the official quickstart and other interfaces