Codex + Google Sheets
Codex runs the task; the Google Sheets connector supplies only the operations and resources allowed by the account you authorize. The Composer selects Codex, asks for Google Sheets access before sending, and keeps both choices in one task draft.
How the combination works
Codex plans and executes. Google Sheets supplies authorized app access.
Codex owns the coding-agent loop: it explores the repository, changes files, runs commands, and returns evidence from the cloud workspace.
Use Google Sheets to create and edit online spreadsheets. Get insights together with secure sharing in real-time and from any device.
Codex
Owns the task loop, model calls, cloud computer, tool choices, progress and final result.
Google Sheets connector
Supplies the currently exposed operations for the authorized Google Sheets account. It does not promise every feature in the Google Sheets product.
Permission boundary
The connected identity, granted provider scopes, organization policy, resource sharing and the task's explicit instruction all constrain what Codex can do.
Setup and first task
Connect one Google Sheets account and verify one known resource.
The Composer preselects Codex with GPT-5.6 Sol. Start read-only when possible, then expand to write operations only after the account and resource boundary are clear.
Open the Codex Composer
The Composer above carries Codex, GPT-5.6 Sol, and Google Sheets. Add a precise target and expected result; the draft stays on this page during sign-in or connector authorization.
Authorize the intended Google Sheets account
Select the intended Google account and review the requested scopes. Your account must be able to access the spreadsheet; Sheets API permissions apply to spreadsheet files, not a single tab.
Run and verify a bounded task
Ask the agent to summarize a named spreadsheet tab and range. Specify whether the first row is a header and request a read-only result. Compare totals and sample rows against the sheet. For later writes, use a disposable copy first and inspect formulas as well as displayed values.
Access, cost and limits
What to verify before scaling Codex + Google Sheets
Software engineering tasks that benefit from Codex's repository navigation, command execution, and iterative implementation loop.
Establish with the first run
- Codex and GPT-5.6 Sol remain selected after sign-in.
- Google Sheets shows the intended connected account before the task is sent.
- The returned data matches one known source resource, with write actions excluded until separately authorized.
Still depends on your setup
- A catalog listing does not guarantee every Google Sheets website feature is available as an agent operation.
- OAuth scopes do not replace organization policy, resource sharing or a precise task instruction.
- Total task cost can include model tokens, active computer time, paid tools, connectors and the provider's own plan or quota.
Verification and recovery
Check Google Sheets itself before trusting the result.
Compare totals and sample rows against the sheet. For later writes, use a disposable copy first and inspect formulas as well as displayed values.
Connection troubleshooting
Check the signed-in Google account, spreadsheet sharing, exact tab name and range. Do not mistake a permission error for an empty sheet.
Writes need explicit scope
Name the target record and exact allowed change. A request to summarize, analyze or draft does not authorize sending, publishing or deleting.
Re-check current state
For decisions or follow-up writes, open the resource in Google Sheets and check its current state. A successful earlier read may already be stale.
Common questions
Related resources
Codex
Review Codex's supported models, capabilities and browser Composer.
Google Sheets connector
Review the application-specific authorization and first-task guide.
Codex + GPT-5.6 Sol
Review the current default agent and model combination.
Pricing
Review model, active-computer, tool and connector charges.