Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Google Drive 0.1.22 raw-fetch examples omit include_base64:false required for streaming

Open Beginner friendly
  • Is something wrong?
#56,815 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
json
Domain
tooling

Research direction

Read skills/google-drive/SKILL.md, especially the raw-download examples at lines 22 and 44, and compare them with the google_drive_fetch parameter documentation described in the issue. Update every affected example to include include_base64: false, adding raw_export_mime_type where a native export format is requested. Done means the examples select the documented streaming route and retain the existing metadata and readback rules.

Written by the indexing model from the issue text.

Description

CLI documentation skills

Environment

  • Codex CLI 0.164.0 via an embedding host.
  • Session-advertised curated Google Drive plugin 0.1.22.
  • Reproduced by comparing installed skill text with the tool schema exposed in the same session; no private files were downloaded.

Problem

In skills/google-drive/SKILL.md, the raw-download examples at lines 22 and 44 omit include_base64: false, while the surrounding instructions require a file reference without inline bytes.

The exposed google_drive_fetch schema says download_raw_file: true alone preserves the legacy complete raw response. Streaming to a user-scoped file_uri requires include_base64: false as well. For native files, this also selects the documented streaming download route instead of retaining the legacy export limitation.

Minimal reproduction

  1. Read the raw-fetch examples in Google Drive 0.1.22.
  2. Compare them with the current google_drive_fetch parameter documentation.
  3. Observe that the examples omit the flag required for the behavior the skill mandates.

Proposed correction

Use:

{"url":"<verified Drive URL>","download_raw_file":true,"include_base64":false}

Add raw_export_mime_type when a native export format is requested. Update every affected example and preserve the existing metadata/readback rules.

This is a source/schema mismatch, not a claim of a measured transfer failure. The public plugin repository declares issues disabled, so this report uses Codex's integration reporting route. Related #36261 concerns downstream file-reference materialization; this report concerns selecting streaming in the producer call.

Dominant language
Rust
Stars
130k
Forks
20.5k
Avg merge
1m
Merged PRs (30d)
996

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.