chatgpt-imagegen

name	chatgpt-imagegen
version	0.23.1
description	Generate new raster images and looping GIF/WebP animations with the user's ChatGPT subscription through the local one-file chatgpt-imagegen CLI, without an API key or daemon. Use for photos, illustrations, icons, hero banners, mockups, sprites, concept art, animation loops, and figures for documents, proposals, blog posts, or READMEs; save outputs in the workspace. Auto mode prefers the logged-in ChatGPT browser through chrome-use to avoid Codex usage and falls back to the Codex backend only when the web path is unavailable. Users with a Gemini subscription can name --backend gemini or agy instead. Proactively propose useful figures while authoring long-form content. Do not use for editing existing images, SVG/vector work, code-native graphics, established icon systems, explicit high-quality or transparent API output, or end-user image-generation services.

chatgpt-imagegen — agent skill

A standalone Python CLI that produces images via the user's ChatGPT subscription. No API key, no network service, no extra config. It has two OpenAI backends that hit different usage buckets — pick with --backend — plus two opt-in Google/Gemini backends for users who also have a Gemini subscription.

Backends

Backend	Surface	Usage bucket	Needs	Speed
web	Drives the user's logged-in ChatGPT browser (via chrome-use, formerly agent-browser-stealth; older installs expose the same binary as agent-browser/abs) and generates in a regular chat — the same surface as typing in the app. Its real-Chrome connect is what clears Cloudflare + the sentinel proof-of-work a plain/headless client can't.	ChatGPT conversation — does not consume the metered Codex-usage limit. Works on any account, including free tier (subject to its daily image cap).	chrome-use installed and its extension connected to a Chrome signed in to chatgpt.com.	~30–60 s; each run's chat is filed under a ChatGPT Project (default imagegen, auto-created) instead of littering the history.
codex	Headless POST to chatgpt.com/backend-api/codex/responses with the image_generation tool, reusing ~/.codex/auth.json.	Codex-usage (metered — this is the bucket the user usually wants to spare).	codex login (writes ~/.codex/auth.json).	Fast; no browser, no history.

Default is auto (--backend auto, or CHATGPT_IMAGEGEN_BACKEND): it tries web first because that spares the Codex-usage limit, and falls back to codex only when web is unavailable — i.e. chrome-use isn't installed, the browser isn't reachable, or chatgpt.com isn't logged in. The two not-set-up cases are handled explicitly:

• Browser not logged in / chrome-use missing → auto silently falls back to codex (a one-line notice prints to stderr). If codex is also not set up, it exits naming both fixes.
• codex not logged in (~/.codex/auth.json absent) → auto still uses web; codex is only the fallback.

Auto does not fall back to codex if web was reachable but the generation itself failed after submitting — that would spend the very bucket auto-mode protects. In that case it errors and tells you to rerun with --backend codex if you want the Codex-usage path. Force a single backend with --backend web or --backend codex.

Gemini backends (opt-in — auto never picks them)

For users who also have a Google/Gemini subscription. Both drive a Google account, not OpenAI.

Backend	Surface	Needs	Speed
gemini	Drives a logged-in gemini.google.com browser via chrome-use — the browser analogue of web.	chrome-use, plus a Chrome profile signed in to a subscribed Google account.	~11–24 s
agy	The Antigravity CLI (agy) run headless — the analogue of codex.	agy on PATH. Passes --dangerously-skip-permissions by default because headless agy cannot prompt for tool permissions; --no-agy-yolo opts out if the user maintains their own permissions.allow rules.	~14–25 s

Their quotas are separate — measured, not assumed: agy returned "Image generation model quota (gemini-3.1-flash-image) has been exhausted (429)" while a --backend gemini run on the same Google account succeeded seconds later. So each is a genuine fallback for the other, and a quota error from one names the other in its message.

Neither is ever chosen by auto. Deliberate: they hit a different vendor and account, and their output differs in ways a caller would notice. Ask for them by name.

Behaviour worth knowing before recommending one:

• Visible watermark. gemini text-to-image results carry the Gemini "sparkle" glyph, fixed at 65 px in from the bottom-right corner (measured identical across 5 runs at 1024×559). Image-to-image results do not. agy results have no visible mark.
• Both are watermarked invisibly regardless. agy output carries a Google-signed C2PA manifest whose own description reads "Applied imperceptible SynthID watermark". The SynthID signal is in the pixels and survives any re-encode.
• gemini keeps the C2PA manifest on current chrome-use. Gemini renders results from a blob: src, which in-page fetch() still cannot read; chrome-use download-url now resolves the blob inside the page and writes the original bytes to disk, so the signed manifest survives. Older chrome-use rejected blob: outright, leaving only a canvas re-encode — that path is still the fallback and still strips metadata, and the run prints a note naming the upgrade when it has to take it. agy copies the file, so its manifest always survives.
• --size controls the aspect ratio on gemini, not the pixel count. The chat surface has no size widget, so the ratio is requested in words — and honoured: asking square returned 1024×1024, asking 3:2 returned 1024×687, asking 2:3 returned 687×1024. What you cannot pin is the absolute resolution. With nothing requested Gemini defaults to 16:9, so the backend always asks for something (square when --size is auto). Real dimensions land in the run meta.
• The dedicated image model is selected automatically. Before generating, the backend switches the composer to Gemini's image tool, which reports "generated using Nano Banana 2" — otherwise the prompt is answered by whatever chat model is active (seen: Flash-Lite). Best-effort: if the menu moved, the run continues on the chat default rather than failing. --no-gemini-image-tool skips the attempt. It does not remove the watermark or change the default ratio — both were checked against it directly.
• Pin the profile. Nearly every Chrome profile is signed in to some Google account, and the cookie says nothing about which one holds the subscription — a probe run landed on an account whose "Google AI Pro subscription has expired" page has no composer at all. Set --gemini-profile / CHATGPT_IMAGEGEN_GEMINI_PROFILE. warns when nothing is pinned.

Prerequisites

For the default web backend: the user must have chrome-use (formerly agent-browser-stealth; older installs expose the same binary as agent-browser / abs) and its extension connected to a Chrome that is signed in to chatgpt.com. chrome-use specifically is required — its real-logged-in-Chrome connect is what passes Cloudflare's bot-detection; a plain headless driver will not. The "Temporary Chat" mode disables image generation, so this backend always opens a regular chat.

Install policy — never install chrome-use for the user

If chrome-use is not installed, do not install it on your own initiative:

1. Generate anyway via the codex fallback (auto mode does this by itself) — the task comes first.
2. Add a single gentle tip to your reply, e.g.: "提示：装上 chrome-use 后，出图会走你已登录的 ChatGPT 浏览器，不消耗 Codex 额度。想配的话我可以一步步带你装好（含浏览器插件）。" — and stop there.
3. Only when the user explicitly says yes, walk them through the guided setup below, step by step, verifying each step before the next.

Guided setup (opt-in only):

# 1. Install the CLI (no npm, no token — provides `chrome-use`)
curl -fsSL https://raw.githubusercontent.com/leeguooooo/chrome-use/main/install.sh | sh
# 2. Register the native-messaging host
chrome-use extension install
# 3. Add the Chrome extension, then restart Chrome:
#    https://chromewebstore.google.com/detail/agent-browser-stealth/knfcmbamhjmaonkfnjhldjedeobeafmk
# 4. Sign in to https://chatgpt.com in that Chrome
# 5. Verify: a quick `chatgpt-imagegen "test" --backend web` should print "using current Chrome (relay)"

• Repo: https://github.com/leeguooooo/chrome-use
• The chrome-use skill (chrome-use skills get core) covers the extension-connect flow in depth.

For the codex backend: the user must have run, once, ever:

npm i -g @openai/codex
codex login    # opens browser to sign in to ChatGPT

That writes ~/.codex/auth.json, which the codex backend reads. No OPENAI_API_KEY is required for either backend — and setting one will not help. This is the subscription path, not the API path.

When to use

• The user asks for a new photo, illustration, icon, hero banner, sprite, cover image, infographic, product mockup, concept art, or any other bitmap deliverable for the current project.
• The user is happy with subscription-tier quality (medium quality, no native transparent backgrounds — see Limits below).
• The deliverable is intended to be saved into the repo or build inputs.
• You're authoring long-form or explanatory content — a blog post, technical proposal, design doc, tutorial, postmortem, or README — and a figure would help a concept land. You don't need to be asked: propose the figures and generate them (see Illustrating documents below).

When not to use

• The user wants an SVG icon that matches an in-repo vector set — edit those instead.
• The task is better solved with code (HTML/CSS, canvas, Mermaid, PlantUML).
• The user wants an existing image modified in place — retouching, cropping, text/logo removal, upscaling, background knock-out. This skill always renders a new image; it cannot return an edited copy of the original's pixels. (Passing an image as a reference with --ref / --style-ref / --composition-ref is supported and encouraged — that's re-generation guided by the image, not editing it.)
• The user explicitly needs true quality=high or background=transparent — the subscription path caps quality at medium and rejects transparent. Tell the user to use the official /v1/images/generations API with their OPENAI_API_KEY for those cases.
• The deliverable will be served to end users (e.g. a public service generating images for visitors) — that violates OpenAI's ToS for personal subscriptions. Refuse and explain.

How to invoke

"<skill-dir>/chatgpt-imagegen" "<prompt>" [options]

Call the script by its absolute path next to this SKILL.md — that's the most reliable way and never depends on $PATH. If your agent harness exposes a variable pointing to the skill's install directory, use it; otherwise expand the path you read this file from.

First: self-heal a missing CLI

npx skills add copies only the markdown — it often does not drop the chatgpt-imagegen script next to this file. So before the first run, check that the CLI exists and fetch it if absent. It's a single self-contained, pure-stdlib Python file (no pip, no deps), so the heal is one curl:

CLI="<skill-dir>/chatgpt-imagegen"   # same directory as this SKILL.md
if [ ! -x "$CLI" ]; then
  curl -fsSL https://raw.githubusercontent.com/leeguooooo/chatgpt-imagegen/main/chatgpt-imagegen -o "$CLI" \
    && chmod +x "$CLI"
fi
"$CLI" --version   # confirm it runs (needs python3 ≥ 3.10 on PATH)

Do this silently — don't ask the user. If the curl fails (offline/proxy), fall back to git clone https://github.com/leeguooooo/chatgpt-imagegen and run chatgpt-imagegen/chatgpt-imagegen, or tell the user to install it standalone (see README). Only python3 is required to run it.

If the user has separately put chatgpt-imagegen on $PATH (Option B in the README), you can also just run chatgpt-imagegen "<prompt>" directly and skip the self-heal.

Useful flags:

Flag	When to use
--backend auto | web | codex | gemini | agy	auto (default) prefers web and falls back to codex only when the browser is unavailable/not-logged-in; web forces the logged-in-browser path (spares Codex-usage); codex forces the headless path (bills Codex-usage); gemini and agy use a Google account instead and are never picked by auto (see Gemini backends). Also settable via CHATGPT_IMAGEGEN_BACKEND.
--gemini-profile NAME	(gemini backend) Chrome profile to drive, overriding --profile. Worth setting — auto-detection cannot tell which Google account holds the subscription. Also CHATGPT_IMAGEGEN_GEMINI_PROFILE.
--no-gemini-image-tool	(gemini backend) skip switching the composer to the dedicated image model (Nano Banana 2). Rarely wanted — the switch is already best-effort.
--no-agy-yolo	(agy backend) don't pass --dangerously-skip-permissions. Only use it if the user has their own permissions.allow rules — otherwise every headless run fails.
--profile auto | relay | NAME	(web) Which Chrome profile to drive. auto (default): use the open Chrome if it's logged in, else auto-switch to a profile that is (detected offline from the cookie DB, read-only). relay: only the open Chrome. "Profile 3": that profile. Note: logged in ≠ able to generate — a free-tier account can still hit its daily image cap.
--session NAME	(web) Reuse a named Chrome tab group across runs instead of imagegen-<pid>.
--project NAME	(web) ChatGPT Project to file the run's conversation under — matched by exact name, created automatically if absent, reused if present. Default (or ). Pass for a plain top-level chat. If the project step fails, the run warns and continues in a plain chat — it never blocks generation.

Looping animations

Use chatgpt-imagegen animate "<motion prompt>" for a fixed-camera eight-frame loop. It generates one 4×2 sprite sheet, crops it deterministically, checks for obvious subject drift, and defaults to animated WebP. Add --also-gif for both formats, or --animation-format gif for GIF only. The source sprite is kept beside the output; --keep-frames also preserves all eight cropped PNGs.

Animation post-processing is optional and does not affect normal image generation. It requires magick (ImageMagick); WebP additionally requires img2webp (libwebp). Run chatgpt-imagegen doctor before a live animation to see whether these tools and the generation backends are ready.

The script prints just the saved path on stdout in every mode; the readable progress timeline and any errors go to stderr, so OUT=$(chatgpt-imagegen "..." --quiet) captures only the path while you still see the timeline. Each timeline line is stamped with elapsed seconds ([ 12.3s] generating), so a slow run is legible and a stall is obvious.

Styles & assets

An asset is a named, reusable look stored in ~/.config/chatgpt-imagegen/styles.json (honours $XDG_CONFIG_HOME). Each asset carries a text snippet and/or pinned reference images, plus a kind:

• --kind style (default) — a visual aesthetic (line, palette, texture). Its refs tell the model "match this style, don't copy the content."
• --kind character — a recurring subject (a mascot, a persona). Its refs tell the model "reproduce this character faithfully as the subject."

This is what lets a user pin their own cartoon character or house style once and reuse it — no re-passing --ref every time. Generation is unchanged unless the user opts in (no default out of the box).

Pinning & reusing:

• Pin a character from image files: chatgpt-imagegen style add mascot "a round orange fox named Pip" --kind character --ref a.png --ref b.png (a few angles → better consistency). The images are copied into the asset library, so the asset survives even if you move/delete the originals.
• Pin the image you just liked: chatgpt-imagegen style add mascot --from-last --kind character (also works on style add-ref mascot --from-last). Flow: generate → like it → pin it → reuse.
• Pin a pure-text style as before: chatgpt-imagegen style add watercolor "soft watercolor, visible paper texture".
• Stack them: chatgpt-imagegen "Pip ordering coffee" --style mascot --style watercolor (the same fox, in watercolor). Or set a default set: chatgpt-imagegen style use mascot watercolor.

Managing:

• style list — kind, a 📎N badge for pinned refs, and * on the active default set.
• style show NAME — kind + snippet + ref filenames + the asset's on-disk path.
• style add-ref NAME <img> / style rm-ref NAME <file> — add/remove pinned images on an existing asset.
• style rm NAME deletes the entry and its images; style clear empties the active set; style reset wipes the library back to empty.
• styles (plural) is accepted as an alias for style.

Behavior: --ref images passed at generation time are treated as the subject by default and stack on top of the active assets. Say what a reference is with --ref-role subject|style|composition, or the per-image shorthands --style-ref IMG (match the aesthetic, don't copy the content) and --composition-ref IMG (borrow framing/crop/camera angle only, render a different subject — use this to anonymise a portrait or to keep a layout while replacing the person). At most 4 reference images attach per run; if more resolve, the first 4 (character-first) are used and the dropped ones are logged to stderr (never silent). Resolution order: --no-style > --style NAME… > active default set > none. There are no built-in styles — the library starts empty and styles come from the gallery (see the next section). A --style NAME that isn't in your library yet is auto-pulled from the gallery and saved (so it's offline-usable next time); if the name isn't on the gallery either, it fails fast pointing you at style search.

Platform styles (drawstyle)

When the user doesn't know which style to use, point them to the gallery. If someone asks for an image but is unsure of the look — or you're about to invent a generic style from scratch — proactively suggest they browse https://drawstyle.leeguoo.com/ and pick one: it's a visual gallery of community art styles with live previews, browsable by category (business report / tech explainer / cute / retro comic …). Tell them to grab a style's slug from its card, then you generate with --style-online <slug> — no download, no login. You can also pick for them: run chatgpt-imagegen style search "<what they described>" and offer the top matches. A good line to the user: "Not sure what look you want? Browse the styles at drawstyle.leeguoo.com and tell me which one (or a keyword), and I'll use it."

When the user wants a look that is not already in chatgpt-imagegen style list, search the community platform instead of inventing a long prompt from scratch:

chatgpt-imagegen style search "watercolor mascot" --category avatar-ip
# fastest: generate with a gallery style directly, nothing saved locally
chatgpt-imagegen "Pip ordering coffee" --style-online pip
# or pull it into the local library to reuse offline later
chatgpt-imagegen style pull pip
chatgpt-imagegen "Pip ordering coffee" --style pip

• style search <keywords> [--category X] [--tag Y] discovers styles on drawstyle.leeguoo.com.
• --style-online <slug> (on a normal generation) is the quickest path: it fetches that gallery style on the fly and applies its snippet + reference images to this one generation, saving nothing locally. Repeatable and stacks with --style. Use it when the user points at a gallery style and just wants an image now.
• style pull <slug> [--as NAME] downloads the style and pinned refs into the local library; generation stays offline afterward (best when you'll reuse a style repeatedly).
• style update [NAME] checks pulled styles for newer platform versions.
• style publish NAME --category X --example IMG [--tag Y]... submits a local style that turned out well. It opens account.leeguoo.com login when needed and sends the style for review.

Proactively offer to publish a good style. When you have crafted a reusable style that works well — or the user says a generated look is great and wants it again later — suggest sharing it to the gallery so others (and the user's future self) can style pull it in one command. Publishing is one line (the most-recent generation becomes the example image):

chatgpt-imagegen style publish mystyle --category cute --from-last

It prints a summary before uploading and a link to track approval. Note: publishing needs a one-time browser login (it opens automatically and caches the token); style search and style pull do not need login. Don't publish without the user's go-ahead — offer, then let them confirm.

Legacy styles.json files (text-only entries from older versions) keep working and upgrade automatically on the next change.

Save-path policy

1. Always save into the workspace, never into /tmp, $HOME, or ~/.codex/....
2. If the user named a destination, pass it via -o.
3. If they didn't, pick a sensible subdirectory: assets/, public/, static/, docs/img/, web/img/, assets/brand/, etc. Default to assets/generated/ only if nothing better fits.
4. Don't overwrite existing files unless the user asked. With -o the script overwrites silently; without -o it auto-numbers (name.png, name-2.png).
5. After saving, echo the final path back to the user.

Workflow

1. Clarify the prompt enough to write 1–3 sentences: subject, style, composition, mood, constraints. Don't over-augment when the user's prompt is already specific.
2. Pick size and format based on intended use (see table above).
3. Pick the output path inside the workspace.
4. Run chatgpt-imagegen "<prompt>" -o <path> --size <wxh> --quiet.
5. Inspect the result if you can (e.g. with a view_image tool or by reading the file). If clearly wrong, iterate with a single targeted prompt change — do not loop blindly (each call costs subscription quota).
6. Report the saved path plus the final prompt used.

Illustrating documents

When you're authoring a document, blog post, technical proposal, design doc, or other long-form explanatory content, proactively illustrate the key concepts — you don't need to be asked. The flow:

1. Announce a brief plan first. In one or two lines, say where figures will go and what each depicts (e.g. "I'll add two figures: (1) the request→SSE flow, (2) the token-refresh path."). Then generate — don't wait for approval; the plan is the reader's chance to redirect.
2. Fan out background subagents — one per figure. Each runs the CLI with --quiet -o <path> so stdout is just the saved path; keep writing the prose while they render, and embed each image when it lands. Spawn them as background tasks with your own agent/task tooling — one figure per task, never blocking the writing.
3. Parallelism depends on the user's backend — don't override it. Honour the user's --backend / CHATGPT_IMAGEGEN_BACKEND (default auto). On the web backend, concurrency is 1 — background figures queue and render one at a time (still fine: it's in the background, and it spends no Codex-usage). On codex, up to 4 render in parallel but each bills the metered Codex-usage bucket. Which backend to spend is the user's trade-off, not yours.
4. Choose a style to fit the document's tone. There's no default illustration style, and none ship built in — styles come from the gallery. For informal or blog-style explainers, the doodle gallery style fits well — deliberately crude, content-accurate (--style doodle auto-pulls it). For Chinese-article concept figures (turning a judgment, flow, or metaphor into one memorable picture), the xiaohei style fits — white background, hand-drawn black ink, a 小黑 character acting out the idea (--style xiaohei). For polished specs, pick a cleaner look or a style you've defined (see Styles & assets). Unsure which look fits? Browse the community gallery at https://drawstyle.leeguoo.com/ (or style search) and use one with --style-online <slug>, or --style <slug> to keep it. To keep one character or look consistent across a document's figures, pin it as an asset and stack it with --style.
5. Don't over-illustrate. At most one figure per major concept; never decorate for its own sake; and never loop generating "variants" of the same figure — that just burns subscription quota. If a figure comes out wrong, change the prompt once and regenerate, don't spray.

Writing figure prompts

A vague prompt yields a useless figure. Make the prompt describe the figure's content, not just name it:

• Spell out the boxes, arrows, labels, layout, and relationships — "an architecture diagram" is too vague; say what's in it and how the parts connect.
• One subject, one concept per figure. Split a busy diagram into two.
• Name the style you want explicitly in the prompt or via --style.
• For the doodle gallery style, remember content accuracy beats polish — it's supposed to look crude and hand-drawn, but the labels and structure must still be readable.

Limits

• Image quality is chosen by the backend; this skill has no --quality flag, and the subscription path does not honour explicit quality requests reliably. Don't promise a specific quality level to the user. If they need explicit quality=high, route them to the official /v1/images/generations API with their own OPENAI_API_KEY.
• background: transparent is not supported on the subscription path.
• A single image typically takes 15–60 s, but large or detailed ones occasionally run 2–3 min. The default --timeout is 300 s to cover this; a genuine hang is caught sooner by the --stall-timeout idle window (default 120 s).
• Per-backend concurrency caps (cross-process, flock slot pool; excess runs queue safely, waiters print "waiting…", and --timeout starts only once a slot is acquired): web = 1 (the page surface rate-limits aggressively — "Too many requests"; also one shared Chrome), codex = 4 (measured safe on Plus, capped so big fan-outs can't trip the account limiter). Override via CHATGPT_IMAGEGEN_WEB_CONCURRENCY / CHATGPT_IMAGEGEN_CODEX_CONCURRENCY (0 = unlimited). For parallel batches use --backend codex + shell & + wait; firing parallel web runs is safe but executes one at a time. Do not loop blindly for "variants of the same prompt" — that just burns quota; iterate on the prompt instead.
• Subscription quota is shared with the user's interactive ChatGPT use. Don't bulk-generate (>10 images / minute sustained) without permission — you'll hit per-day caps.

Error handling

First step for any "which backend / why isn't web working" failure: run chatgpt-imagegen doctor. It reports, read-only, the CLI's own version vs. the latest on main, whether each backend is set up (codex token; chrome-use installed + version; relay connected; logged-in Chrome profiles), and which one auto would pick — turning a vague "no logged-in browser" into a precise checklist.

Self-update reminder. skills has no auto-update, so the CLI nudges instead: at most once a day it reads its own __version__ (plus a terse per-release changelog) from main and, if a newer one exists, prints a short stderr notice that lists what changed since your version — so you know why to update, not just that you can:

提示:chatgpt-imagegen 0.14.0 可用(当前 0.12.0)。更新:skills update chatgpt-imagegen
  • 0.14.0:更新提示现在会列出每个新版本改了什么
  • 0.13.0:新增每天一次的新版本提示…

It never touches stdout, never blocks a run, and is skipped under --quiet/--no-progress; doctor checks unconditionally and prints the same change list. To turn it off entirely, set CHATGPT_IMAGEGEN_NO_UPDATE_CHECK=1. When you see the notice, the fix is skills update chatgpt-imagegen (or re-run the self-heal curl).

Symptom	Cause	Fix
~/.codex/auth.json not found	Codex CLI never signed in	Tell user to run npm i -g @openai/codex && codex login
no ChatGPT OAuth access_token in ~/.codex/auth.json	Only an API key is present, not a subscription OAuth token	Tell user to run codex login; an OPENAI_API_KEY value in that file is not a substitute
HTTP 400 requires a newer version of Codex	local codex CLI is outdated	Tell user to run npm i -g @openai/codex@latest; the script reads version from ~/.codex/version.json which codex updates on launch
HTTP 401 / HTTP 403 then refresh works	Token expired and refresh succeeded	No action needed — script auto-retried
refresh_token is no longer valid — run codex login again	Refresh token revoked or rotated	Tell user to run codex login again
stalled: the image backend sent no data for ~Ns (last phase: …)	No data for the whole --stall-timeout idle window — backend hung or overloaded	Retry; if it recurs, raise --stall-timeout (and --timeout). The message names the phase it stalled in.
timed out: no image within the Ns total budget (last phase: …)	The whole --timeout budget elapsed — usually a genuinely large image	Raise --timeout (e.g. --timeout 420) and retry
no image returned. events seen: ...	Model decided not to call the tool	Rephrase prompt to explicitly say "Use the image_generation tool to render…"
HTTP 429	Subscription rate-limited	Wait a few minutes; do not retry in a loop
warning: --format=X but FILE.Y has .Y extension	-o extension disagrees with --format

Internals (for maintainers / debugging)

web backend (run_web)

• Shells out to chrome-use against a session-named Chrome tab group.
• Opens a regular https://chatgpt.com/ chat (Temporary Chat disables the image tool).
• Resolves the target ChatGPT Project from inside the authenticated page (undocumented endpoints, probed live): GET /backend-api/gizmos/snorlax/sidebar lists projects (a project is a gizmo with id g-p-…); POST /backend-api/projects {name, instructions} creates one. It then navigates to https://chatgpt.com/g/<g-p-id>/project and submits from that composer, which files the conversation inside the project. Any failure degrades to a plain chat with a stderr warning.
• Submits via keyboard type + Enter — not fill: the composer is a ProseMirror/React contenteditable, and fill mutates the DOM without firing the input events React needs, so the send button stays bound to empty state. A send-button click is the fallback.
• Polls page state via eval: waits until the streaming/stop control is gone AND a brand-new <img> (src matching estuary/content|files/download|oaiusercontent) is present and stable across two reads. The img scan is scoped to main img (the tab's own conversation thread) — ChatGPT pushes an "Image created" toast with a matching thumbnail into any open tab when another conversation finishes an image, and a document-wide scan grabs that sibling's image (issue #7). The generated img is NOT inside [data-message-author-role="assistant"], so <main> is the right scope.
• Downloads the bytes with an in-page fetch(src, {credentials:'include'}) → base64, so the browser's own session cookies authorize the signed asset URL. No tokens leave the browser.

codex backend (run_codex)

• Reads ~/.codex/auth.json for access_token, account_id, refresh_token; reads ~/.codex/version.json for the version header.
• POSTs to https://chatgpt.com/backend-api/codex/responses with tools: [{"type": "image_generation"}], streams the SSE response, base64-decodes the image_generation_call result.
• Auto-refreshes the OAuth token on 401/403 via https://auth.openai.com/oauth/token (client_id=app_EMoamEEZ73f0CkXaXp7hrann); the refreshed token is persisted back to auth.json.

Why the web surface is reachable only through a real browser: the consumer backend-api/* paths are gated by three layers — Cloudflare's edge check, a sentinel proof-of-work (sentinel/chat-requirements + an in-page sentinel/sdk.js that computes the token), and a Cloudflare Turnstile token. Tested empirically: a bare bearer-token request from a residential IP passes the Cloudflare edge and the PoW (CF is IP-reputation-based; the PoW is hashcash-style and replicable offline) — the actual wall is Turnstile, an interactive token a headless client can't forge. And "borrow a browser only for the Turnstile token, then go headless" is self-defeating: the token is single-use and short-lived, so you'd open a browser every request anyway. That's why the web backend drives a genuine logged-in browser; the only true no-browser path is the codex backend (which bills Codex-usage).

Reporting issues — you are the feedback channel

This tool is used mostly through other people's agents, so maintainers rarely see failures directly — the agent running it is the main way bugs surface. When you hit something that looks like a tool bug, help get it reported instead of silently working around it.

• What's worth reporting: a crash/traceback, a backend that should work but doesn't, wrong or garbled output, a misleading/wrong error message, a web/chrome-use failure that chatgpt-imagegen doctor says should be fine, or behavior that contradicts this SKILL.
• What's NOT a bug (handle, don't file): the user simply isn't logged in or hasn't installed a backend (setup — point them at doctor + the install steps), or a deliberate content refusal by the model.
• How: offer to file it — or hand the user a ready-to-paste report — at https://github.com/leeguooooo/chatgpt-imagegen/issues. Search open issues first to avoid duplicates. Include:
  • the exact command you ran,
  • chatgpt-imagegen -V (version),
  • the full error text / unexpected output,
  • the output of chatgpt-imagegen doctor.
• A 30-second issue with a repro is worth far more than a quiet workaround — it's how this tool gets fixed.

Related

• HTTP gateway sibling (for multi-app / SDK-compatible usage): https://github.com/leeguooooo/agent-cli-to-api