console AI chat: an uploaded image/PDF goes to the model and the agent puts that same file into the record's file field, as the user — ruled A

Filing category: ② a decision only the maintainer can make.

维护者速读

现象：员工最自然的做法是"把发票照片发给 AI，让它填报销单"。用外部 AI（Claude 等）走 MCP 时，照片在 AI 厂商那边，平台拿不到原文件，只能再发上传链接让人重选一次（storage + mcp: one upload link on a multiple: true file field accepts several files (same user, record, field, one use, same expiry) — ruled A #32747）。而平台自带的「问 AI」聊天，照片本来就是传到平台自己的页面里的，现在却直接回一句"当前仅支持读取表格类附件……这些文件的内容我没有读取"。
要你裁：自带 AI 是否读取图片/PDF 附件，并把同一份上传直接写进它建的记录的文件字段（不再让人选第二次）。
推荐：A：读取 + 直接附加，附加仍以当前用户身份、走记录的编辑门，图片与 PDF、限大小。

One-sentence problem

The one place where the photo's bytes are already inside the platform (the console's own chat) is the one place that refuses to look at it.

Evidence (reach)

ui/packages/app-shell/src/console/ai/AiChatPage.tsx doSend: files not matching \.(xlsx|xlsm|csv|tsv|txt)$ are not sent; the user's message gets (用户上传了 N 个附件:… — 当前仅支持读取表格类附件(Excel/CSV),这些文件的内容我没有读取。) (read at framework d7c3d44e).
External-client path measured on a hosted tenant (pnpm dev:stack --with-ui, cloud ff373e02): create_record → create_upload_link → user re-picks the file → read_file reads it back → run_action submits. Works, at the cost of re-picking every invoice.

Governing text

objectstack#30892 (closed): "An AI client sees an image the user attaches in its own chat, but it has no bytes to send." True for external clients; not true for the console chat, whose composer holds the File.
docs/NORTH-STAR.md: "Every step of the road must hold for both kinds of user."

Options

Option	What it does	What the customer sees	Effort
A	Console chat uploads image/PDF attachments to storage as the user (pending `sys_file`), sends them to the model as image/text parts, and lets the agent put that file id into a file field of a record it creates or edits (edit door as the user; only files this user uploaded in this conversation)	"Here's my taxi receipt" → claim drafted with amount filled and the photo attached, nothing to pick twice	ui + cloud AI seats · 2–3 PRs · precedent: spreadsheet attachments (cloud#797)
B	Read only: the agent sees the photo and fills fields; attaching still goes through an upload link	Fields filled, photo picked again	ui + cloud AI seats · 1–2 PRs
C	Keep declining non-spreadsheet attachments	User types the numbers or uses the form	none

Business reading: A makes the built-in assistant the shortest path for expenses, claims, contracts; B halves it; C keeps it a spreadsheet-only helper.

Recommendation

A. The bytes are already the user's own upload inside the platform, so attaching them raises none of #32747's provenance question (the user picked the file; the agent only routes it). Confidence gap: model vision cost per image and the size cap; recommend images ≤ 10 MiB, PDFs through the existing read_file text extraction.
Self-check: ①②③④ all pick A or B; only ④ alone would accept B first.

After the ruling

A: composer uploads non-spreadsheet attachments as pending files; the agent gets them as parts plus their file ids; a write that names such an id in a file field commits it; e2e: one photo in chat → a draft claim with the amount and the photo on invoices.

os-decision-facets
① 项目长远合理性: A 让文件只上传一次、由用户本人上传，复用现有文件字段和编辑门。
② 实际业务拉动: 报销（发票照片）是最常见的"拍照即录入"场景，本次实测用户第一反应就是把照片发给 AI。
③ 防 AI 犯错: A 只允许附加本人在本对话里上传的文件，agent 不能凭空造文件；读出的金额仍可用 read_file 复核。
④ 创业阶段不扩散: B 更小，A 多一步附加；都复用现有通道，不新增对外接口。
Prior rulings read: #30892 (external-client upload link); #32747 (open, one link for several files); thread: none

Reader who acts: the domain:ui seat (AiChatPage composer) and the cloud AI seat (agent message parts and the attach step), after the ruling.
Dedupe: repo:objectstack-ai/objectstack is:issue AI chat image attachment → 31 hits (#30892 closed, external clients; others PM seats); repo:objectstack-ai/cloud is:issue chat image attachment invoice photo → 0; Non-spreadsheet attachments chat → 0.

triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

Path: none

分诊首触 + 决策分析(fable 档独立评估)· 2026-11-12T16:56Z

维护者速读

员工把发票照片发给平台自带的「问 AI」,得到「只支持表格类附件」。拍照即录入是 AI 原生报销的标准形态,方向上应该做。
卡里说的「先例」不成立:表格附件是在浏览器里解析的,字节从不离开页面;读照片则要把图片送到存储和模型厂商。这涉及视觉模型成本、套餐边界和数据出境。
归属:应用内 AI 归 cloud 仓(ADR-0033 头注);objectstack 只有 AiChatPage.tsx 那一半。
请裁:A 读取并把同一份上传挂到记录(排在 [Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686 之后,决策部分转 cloud)/ B 只读取 / C 不做。推荐 A。

是否已有裁决: 未找到(cloud 的 ADR 里没有图像或多模态相关条目)。

前提核实:

ui/packages/app-shell/src/console/ai/AiChatPage.tsx:2196-2212:表格在客户端解析。
cloud 的 service-ai 里没有图像消息部件,所以这是新模态。

选项	客户看到	工作量
A 读取 + 挂载	发照片即得草稿报销单,照片已挂上	ui + cloud · 3–5 个 PR;无先例;挂载一步依赖 #32686
B 只读取	字段已填,照片要再选一次	2–3 个 PR
C 不做	手工录入	0

四轴:

① 长远:Expensify SmartScan、SAP Concur ExpenseIt、钉钉和飞书的智能报销都是拍照即录入,照片由用户本人上传。
② 拉动:用户的第一反应就是发照片(实测一次)。
③ 防 AI:只能挂本人在本对话里上传的文件,识别出的金额落为草稿,由人确认。
④ 不扩散:新模态带来视觉成本和额度口径。

推荐 A,排在 #32686 之后。置信缺口:每张图的成本、在哪些套餐开放、出境合规口径都未定。自检: 只看①选 A;④单看会选 B 或暂缓,不翻转。人工底线项:模型成本与套餐、图片出境。

os-decision-facets

① 长远:拍照即录入是 AI 原生报销的主流形态;文件只上传一次,由本人上传
② 拉动:实测一次,是用户的第一反应;第一方应用无此类对象
③ 防 AI:只可挂本人本对话上传的文件;读数落草稿,由人确认
④ 不扩散:新模态带视觉成本与额度口径,非沿用 cloud#797;排在 [Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686 之后

Prior rulings read: objectstack ADR-0033 header (in-app AI is cloud's); cloud ADR-0005/0023 (model tiers); thread: none

Generated by Claude Code

triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

Brief-claimed-by: session_01Q4EjjMnyLqJdzuktEmRPXH · batch #2 · 2026-11-13T04:45Z

Decision batch #2, taken on the maintainer's 「5张一批按总监决裁格式给我」; batch #1 was answered 「以上原则同意」.

triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

Ruling recorded · #32749 · A · 2026-11-13T05:19Z

Maintainer, verbatim (triage#1 session): 「32677 暂停，先由元数据项目自己处理。其他同意」, answering decision batch #2 (proposed 32627 1B·2B·3A / 32749 A / 32979 A / 32677 B / 32688 C). The batch was analysed independently at the fable tier, with prior rulings checked first.

A: the console's own AI chat stores images and PDFs as files pending claim, uploaded once by the user. The model reads the image, and when the AI creates or edits a record it puts that file id in the file field. This is a second entry to [Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686 A (upload first, the record references the id). Bytes never pass through model output (storage + mcp: one upload link on a multiple: true file field accepts several files (same user, record, field, one use, same expiry) — ruled A #32747).
Attached condition (from the analysis): when the tenant's model cannot read images, the chat must say so plainly and must never invent a value from a file name.
Order: the attach step waits for [Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686. The "unbound pending file" case (the target table is not yet known at chat upload) is settled in [Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686's contract review, so there is one mechanism, not two.
Still open, for the cloud seat to propose to the maintainer: image billing, which plans get it, and data-egress policy. The maintainer did not rule these here.
Execution: the cloud lane files the execution card at this card's grade (p2) per the app-repo rule. domain:ui changes the chat composer. needs-user-decision → pm:queue.

Generated by Claude Code

Re-grade on the maintainer's instruction: priority:p2 → priority:p0. State unchanged (pm:queue, domain:cloud, unassigned). Written by a test session, not a seat.

Whose instruction: the maintainer, in an MCP capability-test session (Claude Code), 2026-11-13.
Verbatim: 「把 [Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686 也提到 P0 .这些也都开始处理.这样我们审批相关的MCP就非常好用了.」, said about the MCP upload and approval cards listed together: [Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686, storage + mcp: one upload link on a multiple: true file field accepts several files (same user, record, field, one use, same expiry) — ruled A #32747, console AI chat: an uploaded image/PDF goes to the model and the agent puts that same file into the record's file field, as the user — ruled A #32749, Upload links: refuse at issue a field whose readonlyWhen holds now (carries the issue-time readonlyWhen half of #32734) #32768.
Order kept: as ruled, the attach step waits for [Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686. The parts that do not depend on it, such as the image read and the plain notice when the model cannot read images, are the lane's call to start now.
Identity: this session has no fleet App credentials, so this write goes through the user account. Nothing is claimed here; the cloud lane claims under its own identity.

Generated by Claude Code

triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

Path: none

Triage: p0 → p1 · not an 18.4.0 blocker · 2026-11-13T07:57Z

⛔ Not a claim; the claim and state are unchanged, and the work continues.

Maintainer, verbatim (triage#1 session): 「6张MCP卡（[Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686、Upload links: refuse at issue a field whose readonlyWhen holds now (carries the issue-time readonlyWhen half of #32734) #32768、console AI chat: an uploaded image/PDF goes to the model and the agent puts that same file into the record's file field, as the user — ruled A #32749、storage + mcp: one upload link on a multiple: true file field accepts several files (same user, record, field, one use, same expiry) — ruled A #32747、[Decision] Should an approver be able to see and decide their pending approvals over MCP? #32442、MCP: a submitter's agent cannot recall or resubmit its own approval request — approval_recall / approval_resubmit are not ai.exposed, while the approver's four decide actions now are (ruling A on #32442) #32993）被 os-bob 测试会话一次性升为 p0，这些不阻塞发版」.
In this fleet p0 marks main or merge-queue red and the release window's blockers (「阻塞卡升 p0」). These six cards are MCP approval and upload capability work, not 18.4.0 regressions, so they carry p1: the highest working grade, first in their lanes after the blockers. That keeps the intent of the 07:27Z regrade (「…这些也都开始处理.这样我们审批相关的MCP就非常好用了.」) without holding the cut.
Order inside the family is unchanged: [Decision] How should an MCP agent create a record whose required file field must be filled (e.g. an expense line with a required e-invoice)? #32686 (upload before the record exists) → storage + mcp: one upload link on a multiple: true file field accepts several files (same user, record, field, one use, same expiry) — ruled A #32747 (several files per link) → console AI chat: an uploaded image/PDF goes to the model and the agent puts that same file into the record's file field, as the user — ruled A #32749 (the console chat attach step), with [Decision] Should an approver be able to see and decide their pending approvals over MCP? #32442 and MCP: a submitter's agent cannot recall or resubmit its own approval request — approval_recall / approval_resubmit are not ai.exposed, while the approver's four decide actions now are (ruling A on #32442) #32993 on the approval side and Upload links: refuse at issue a field whose readonlyWhen holds now (carries the issue-time readonlyWhen half of #32734) #32768 on upload-link refusals.

Generated by Claude Code

Navigation Menu

Repository navigation

console AI chat: an uploaded image/PDF goes to the model and the agent puts that same file into the record's file field, as the user — ruled A #32749

维护者速读

One-sentence problem

Evidence (reach)

Governing text

Options

Recommendation

After the ruling

分诊首触 + 决策分析(fable 档独立评估)· 2026-11-12T16:56Z

Triage: p0 → p1 · not an 18.4.0 blocker · 2026-11-13T07:57Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

console AI chat: an uploaded image/PDF goes to the model and the agent puts that same file into the record's file field, as the user — ruled A #32749

Description

维护者速读

One-sentence problem

Evidence (reach)

Governing text

Options

Recommendation

After the ruling

Activity

objectstack-fleet commented on Nov 12, 2026

分诊首触 + 决策分析(fable 档独立评估)· 2026-11-12T16:56Z

objectstack-fleet commented on Nov 13, 2026

objectstack-fleet commented on Nov 13, 2026

os-bob commented on Nov 13, 2026

objectstack-fleet commented on Nov 13, 2026

Triage: p0 → p1 · not an 18.4.0 blocker · 2026-11-13T07:57Z

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions