Feature request: expose Google Drive to Codex subagents

Codex subagents currently cannot access the Google Drive app or connector, while the main Codex chat can use Google Drive directly. Notion has a dedicated subagent executor with MCP access, but there is no equivalent Drive executor.

Please provide a supported way to expose Google Drive to internal Codex subagents, such as a dedicated drive_executor role, per-subagent app configuration, or controlled connector inheritance. The capability should support least-privilege read/write access, write confirmations, folder or file constraints, and independent verification.

Use case: a parent agent delegates document inventory, review, upload, and update tasks to a cost-appropriate subagent without having to execute every Drive operation itself. This would improve delegation, token efficiency, and auditability.

Thanks for explaining the delegation gap. We'll share the request for supported Google Drive access in subagents with clear permission and verification controls. We don't have a timeline to share.