CreatixChu
7bc30c4cba
* test(api): measure historical image read costs * fix(test): resolve image benchmark paths from its config * fix(attachments): read stored images without scanning sessions * test(attachments): complete by-id fixtures and access assertions * fix(docs): implement image-id read on catalog fixture * docs(attachments): refresh generated read contracts * test(web): verify stored images across history and forks * docs(api): clarify image read metadata and permission scope * test(api): type benchmark instrumentation without unsafe returns * test(api): retire unknown-cast allowances with removed history fixtures * test(attachments): isolate browser cases and document store-wide access * test(web): intercept the by-id thumbnail read path * docs(perf): run generated diagnostic from its owning package * refactor(attachments): reuse reference reads for conversation images * docs(api): refresh complete image reference client contract * test(ui-chat): assert complete image reference forwarding * test(perf): measure image reads against current Session observations
description, kind
| description | kind |
|---|---|
| Package map for the durable image attachment capability family: what you can do with image attachments, and where your images are stored. | package-group |
attachment/ — durable attachment capability family
English | 中文
Summary
The attachment/ group provides durable image attachments: attach images to prompts and commands, and the harness saves them on your machine, shows them again in conversation history, and sends them to the model in later turns. The shipped dsh composition enables this with no setup. The capability and its storage are split across two packages, described below. Stored images survive restarts and are never deleted automatically, and only raster image formats are supported.
Table of Contents
Packages
These two packages provide durable image attachments; each README describes what you can do with its part.
| Package | Role | ctx key |
|---|---|---|
attachment/ |
Image attachments for prompts and commands that persist and come back in history | ctx.attachments |
attachment-local/ |
Stores your attached images on this machine below DSH_HOME |
registers on ctx.attachments |
Related documentation
Start with the subsystem reference for the service contract, then the capability-seam table and the configuration surface of the local backend.
- Attachment subsystem reference — service contract, payload types, and the
ctx.attachmentsCordis surface. - Capability seams — the Service Definition / Service Provider / Consumer split this family follows.
- Generated configuration catalog — every accepted field of the local backend.
Dev Note
Working context for maintainers — click to expand
None.