What is not available

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

Every product has a shape people expect it to have, and this is where this one differs from that shape. Nothing here is coming in a particular release; it is simply not offered today.

The page exists so you can plan around it rather than spending an afternoon looking for a switch.

#Not available

  • The legacy image library macro ('Image (Capable)' / 'Images macro (Capable)') has NO configuration panel. It is also absent from the capability client's macro list, so it has no Capable config editor, no style options and no migrator. It only ever acts as a picker placeholder that replaces itself. The conclusion. No configuration panel. Still stands.).

  • The legacy image library macro is hidden from the Capable macro browser and the Command palette (its metadata sets it invisible). Its stored subtitle. 'Display a image from a provided URL or make one yourself'. Contains a typo and does not describe what the macro does; do not quote it.

  • The generated form schemas on both configurable macros are fallback metadata, not the released configuration UI. 'Image ID', 'Space ID', 'Folder ID', 'Display', 'Column Mode', 'Scope'. As labels a user sees.

  • The image verbs (describe, search, get, fetch, create, update, insert, upload-begin) are NOT published to other people's agents. The standalone Images app deliberately declares no MCP module at all, and the Suite's MCP module publishes only its two approval tools.

  • Command palette image search does not exist in the standalone Images app. Suite only.

  • There is no migrator for the legacy standalone image library macro, even though the shared migration code knows its key suffix.

  • A 'thumb' variant option on the editor attachment fetch is declared in the shared type but never read by the server and never sent by any client. Document editor image loading as always full-resolution, auto-downsized only above 3 MB. Not as having a thumbnail mode. The accompanying version field is explicitly documented as ignored (cache key only).

  • The legacy full-screen Unsplash browser modal is in the route tree but nothing in the product navigates to it. The live insert surface is the insert dialog the byline points at. Anything that exists only in that legacy modal. Including its 'Set as banner' card action and its Unsplash colour/orientation filter shape. Must not be documented as a user flow until reachability is proven. Note that the

  • A 'navigation' capability entry for Images is present but commented out.

#A few things worth knowing

  • If one of these is the reason you are evaluating the product, say so before you buy rather than after.

  • The list changes with each release, so check the release notes before assuming it still applies.

  • Where the app's own wording differs from this page, believe the app.

Better to know now than hunt for a switch.