docs(#3996): document verified generated-image behavior - #4030
Draft
aheritier wants to merge 3 commits into
Draft
Conversation
aheritier
added
area/docs
rumpl
requested changes
Aug 24, 2026
aheritier
force-pushed
the
generated-media-docs
branch
from
August 24, 2026 15:13
a5107cd to
962223a
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
August 25, 2026 08:01
962223a to
48a5f96
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
August 25, 2026 08:18
48a5f96 to
8c8e021
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
August 25, 2026 08:33
8c8e021 to
1445548
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
August 25, 2026 20:24
1445548 to
72f4fd3
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
August 26, 2026 11:11
72f4fd3 to
a96cef3
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
September 1, 2026 16:30
a96cef3 to
21dbfda
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
September 1, 2026 19:59
21dbfda to
d04b172
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
aheritier
force-pushed
the
generated-media-docs
branch
2 times, most recently
from
September 6, 2026 16:16
7bf4821 to
6edff56
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
September 7, 2026 11:19
6edff56 to
2a33362
Compare
aheritier
force-pushed
the
generated-media-docs
branch
2 times, most recently
from
September 7, 2026 16:13
20caea4 to
e54ff19
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
September 7, 2026 16:48
e54ff19 to
05d7df3
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
September 8, 2026 06:17
05d7df3 to
d4892e0
Compare
aheritier
force-pushed
the
generated-media-docs
branch
from
September 8, 2026 07:58
d4892e0 to
468f9cd
Compare
Add the initial TUI and session lifecycle documentation, owner-qualified references, no-resend placeholders, sanitization and a manual walkthrough. This patch describes the historical data-directory session_artifacts layout, not the workspace/portable-blob implementation, and edits only docs/features/tui/index.md and docs/features/sessions/index.md. The complete generated-media documentation replaces that storage description.
Document TEXT+IMAGE on supported Google surfaces, explicit output-capability overrides over models.dev, ordinary-request guards, provider-controlled formats and text-only replies. Explain naming/collisions, workspace escape confirmation and inline rendering with fallback labels. Correct the title-model reference to retain image-output models for utility calls, update the Google example, and replace stale claims that image output is neither requested nor rendered. The completed portable-storage documentation supplies the warning and storage caveats.
Describe workspace deliverables plus complete portable session blobs, manifest-gated blob-first restoration and uncapped legacy file fallback. User-attachment limits are unchanged. Explain in-place schema compatibility and disposable compatibility testing without active-database management instructions; consistent snapshots include stored portable copies. Document ordinary follow-up placeholders separately from explicit file attachment or tool reads. State the accepted phrase-based missing-image warning limits and the exactly-one-returned-image prompt filename fallback. For external-path denial, describe redirection rather than guaranteed save success: a redirected write can still emit a per-item failure warning.
aheritier
force-pushed
the
generated-media-docs
branch
from
September 8, 2026 17:31
468f9cd to
48cef72
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 testis unchanged by this docs-only PR.Test instructions
Run:
task testFollow
examples/gemini_image_output.yamland 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.