AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.

Original source
openai
License
Apache-2.0
Pinned revision
49f948faa9258a0c61caceaf225e179651397431

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read openai--imagegen at revision 49f948faa9258a0c61caceaf225e179651397431, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 7

references/codex-network.md

Codex network approvals / sandbox notes

This file is for the fallback CLI mode only. Read it only after the user explicitly asks to use scripts/image_gen.py.

This guidance is intentionally isolated from SKILL.md because it can vary by environment and may become stale. Prefer the defaults in your environment when in doubt.

Why am I asked to approve image generation calls?

The fallback CLI uses the OpenAI Image API, so it needs outbound network access. In many Codex setups, network access is disabled by default and/or the approval policy requires confirmation before networked commands run.

Important note about approvals vs network

  • --ask-for-approval never suppresses approval prompts.
  • It does not by itself enable network access.
  • In workspace-write, network access still depends on your Codex configuration (for example [sandbox_workspace_write] network_access = true).

How do I reduce repeated approval prompts?

If you trust the repo and want fewer prompts, use a configuration or profile that both:

  • enables network for the sandbox mode you plan to use
  • sets an approval policy that matches your risk tolerance

Example ~/.codex/config.toml pattern:

approval_policy = "on-request"
sandbox_mode = "workspace-write"

[sandbox_workspace_write]
network_access = true

If you want quieter automation after network is enabled, you can choose a stricter approval policy, but do that intentionally and with care.

Safety note

Enabling network and reducing approvals lowers friction, but increases risk if you run untrusted code or work in an untrusted repository.