Codex capability boundary

This is source guidance, not an installed connector or a runtime proof. Resolve tools against the current host and read their actual schemas before using them. Preserve the named product and requested outcome. If a required operation is unavailable, report its exact name and leave that step incomplete. Do not invent tool names, connect accounts, install helpers, spend money, or broaden access from this document alone. Current operator authorization and native permissions govern every action.

Use the official Codex Google plugin and its owning skill when available. The tool names and schema details below describe the upstream connector; they are not promises about the Codex plugin. Map each operation only after inspecting the exposed schema. If the official plugin lacks the operation, name the gap; do not fall back to GOG or another credential route without explicit authorization. Never widen sharing or make a private image public to satisfy an image URL requirement. For visual work, apply available design guidance and inspect exported output.

Google Drive files

Ids come from search, never guesses

Every tool takes Drive file ids. Get them from search (or list_folder for a known folder, list_recent_files for "what was I just working on"), or from the id in a URL the user pasted. exact_name beats query for a known filename; add mime_type_filter to cut noise. Never invent an id or reuse one from a stale conversation - re-search first.

Folder targeting