Skip to content

docs(#3996): document verified generated-image behavior - #4030

Draft
aheritier wants to merge 2 commits into
generated-image-inline-tuifrom
generated-media-docs
Draft

docs(#3996): document verified generated-image behavior#4030
aheritier wants to merge 2 commits into
generated-image-inline-tuifrom
generated-media-docs

Conversation

@aheritier

@aheritier aheritier commented Aug 22, 2026

Copy link
Copy Markdown
Collaborator

What

Documents verified generated-image behavior across model configuration, sessions, TUI usage, Google provider guidance, and examples.

Why

Provides a concise, reproducible reference for configuring and using generated images safely.

Validation

Documentation/example review; task test is unchanged by this docs-only PR.

Test instructions

Run:

task test

Follow examples/gemini_image_output.yaml and the generated-image provider, session, and TUI documentation using a supported Gemini image-output model. Expected: the documented configuration is valid and the workflow produces and displays generated media as described.

…nd validation walkthrough

User-facing documentation for the generated-media feature across
docs/features/tui/index.md (Generated Media section: storage location,
naming and collision behavior, no-resend placeholders, bounded/sanitized
warning and placeholder wording), docs/features/sessions/index.md
(generated-media lifecycle), and docs/providers/google/index.md
(image-output model guidance), plus a step-by-step manual validation
walkthrough for contributors.
Document that image-output-capable models request TEXT+IMAGE on supported
Google surfaces, with explicit output_capabilities values overriding automatic
models.dev detection. Explain local rejection of unsupported tool and
structured-output combinations, provider-controlled formats and text-only
responses, generated-file naming and collision handling, workspace escape
confirmation, and inline TUI rendering with safe fallbacks.

Update the example and remove stale claims that image output is not requested
or rendered, while keeping developer-only validation details out of user docs.
@aheritier aheritier added area/docs Documentation changes kind/docs Documentation-only changes labels Aug 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docs Documentation changes kind/docs Documentation-only changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant