[Automated] Draft docs (kagent): feat: attach text files and images to chat messages

[github-actions]

kagent-dev/kagent#2936 — feat: attach text files and images to chat messages

Docs versions: 1.x (first shipped in v1.0.0-alpha9)

What changes for users: Chat messages can include text file and image attachments. The UI can stage attachments with the attach button, paste, or drag and drop, and external A2A callers can send raw file parts with filename and mediaType.

What the docs now say: The A2A guide now says file parts can carry raw bytes, explains how text files and images reach the model, and names the 16 MiB gRPC message cap. The UI guide already documented staging methods, file types, attachment limits, and ui.nginx.clientMaxBodySize.

Not verified: No cluster; the UI and A2A attachment flows are unrun.

How kagent-2936 was drafted, and what was not verified

• Code PR: feat: attach text files and images to chat messages kagent#2936
• Code issue: none linked
• Product: kagent (upstream) → kagent-dev/website
• Docs version: 1.x, first shipped in v1.0.0-alpha9.
• Category: scoped-edit / pr

Plan, and what changed it

• Planned: Document chat attachments and the upload-size settings on the page that owns the chat workflow.
• Learned: observability/launch-ui.md already documents the UI attachment workflow and limits, while examples/a2a-agents.md still described only text message parts.
• Did: Added the A2A file-part behavior to examples/a2a-agents.md.

Why a documentation change is necessary

The release note says chat now takes text file and image attachments, and the diff shows the UI sending raw file parts and the A2A converter preserving filename and mediaType. The UI guide already tells browser users how to attach files and which limits apply. The A2A guide still said a message needs text parts only, so API callers could not discover that raw file parts now work.

What changed on disk

• docs-site/content/kagent/1.x/examples/a2a-agents.md — Adds a short note that A2A message parts can carry raw file bytes, and explains text extraction, image handling, and the 16 MiB gRPC cap.

How to verify this change

1. Open the kagent UI with an agent that uses the kagent runtime, attach a small text file, and send a message that asks about the file.
2. The answer refers to the file contents, and the sent message remains visible as a downloadable file chip after you reload the page.
3. Send the same file through an A2A client as a raw file part with filename and mediaType; the agent sees the non-image file as extracted text, and a message larger than 16 MiB is rejected by the gRPC path.

What was not verified

The configuration was not applied to a cluster, so every command and UI action in this diff is unrun.

How the pages were chosen (triage report)

Feature clusters

Kept apart on purpose. Merging wrongly produces a guide that documents two things and explains neither, so these are reported for a person to merge rather than grouped automatically:

• feat: attach text files and images to chat messages kagent#2936 and fix(ui): keep a new chat's title in the chat list after leaving it kagent#3001 both have docs-site/content/kagent/1.x/observability/launch-ui.md as a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land there
• feat: attach text files and images to chat messages kagent#2936 and fix(ui): call the per-chat unit a session on the agent concepts card kagent#3034 both have docs-site/content/kagent/1.x/observability/launch-ui.md as a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land there
• feat: attach text files and images to chat messages kagent#2936 and fix(ui): show agent template create errors beside the Create button kagent#3075 both have docs-site/content/kagent/1.x/observability/launch-ui.md as a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land there
• feat: attach text files and images to chat messages kagent#2936 and fix(ui): hide other users' conversations from new-chat rail kagent#3091 both have docs-site/content/kagent/1.x/observability/launch-ui.md as a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land there
• feat: attach text files and images to chat messages kagent#2936 and fix(ui): count Agent resources in the dashboard Agents tile kagent#3105 both have docs-site/content/kagent/1.x/observability/launch-ui.md as a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land there
• feat: attach text files and images to chat messages kagent#2936 and fix(ui): note shared workers on the Substrate page kagent#3108 both have docs-site/content/kagent/1.x/observability/launch-ui.md as a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land there
• feat: attach text files and images to chat messages kagent#2936 and fix(ui): fix three flaky browser tests kagent#3118 both have docs-site/content/kagent/1.x/observability/launch-ui.md as a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land there
• feat: attach text files and images to chat messages kagent#2936 and fix(ui): fix the remaining flaky browser tests, and cut redundant ones kagent#3132 both have docs-site/content/kagent/1.x/observability/launch-ui.md as a candidate, but for one of them it is one page among more than 3, so they are kept apart; merge them if both drafts do land there
• (1 more weaker link(s) not shown; the work-list JSON is complete)

Draft a documentation change

kagent-dev/kagent#2936 — feat: attach text files and images to chat messages

• Product: kagent (upstream) → kagent-dev/website
• Docs version: 1.x
• Release note: Chat now takes text file and image attachments: stage several, remove any before sending, and ask the agent about their contents.
• Not tested: no cluster was available, so every command in this diff is unrun
• No rule covers 7 touched file(s). The candidate pages below come from the files that DID match a rule, so they may scope this narrower than the change is. Read these before deciding the change is only about the pages listed:
  • go/adk/pkg/agent/agent.go
  • go/adk/pkg/controllerclient/client.go
  • go/adk/pkg/fileextract/fileextract.go
  • go/adk/pkg/fileextract/llm.go
  • go/api/client/grpc.go
  • go/core/internal/grpcserver/server.go
  • ...and 1 more

Draft branch: pr-tracker-draft-kagent-2936

---

Important

The test suite has not run on this pull request. It was opened by github-actions[bot], and GitHub does not start workflows for pull requests opened with the repository's own token. This repository's checks are held as action_required until somebody presses Approve and run on the Checks tab. Checks that come from GitHub Apps rather than Actions, such as DCO, run on their own.

Please approve the checks before reviewing the content: an absence of failures here means the tests have not run, not that they passed.

[github-actions]

Docs preview

Link	Points at
Branch preview	The newest push to this branch. Updates in place.
Commit preview	7f57c91 only. Frozen.

Both are uploaded Worker versions and serve no production traffic.