📝 docs: background chat image generation + bundled Python packages
cd991e0
📝 docs: best-effort telemetry caveats — absent reports/events are inconclusive (round-7 R7-2)
a592f9d
📝 docs: least-privilege WAF guidance and source-correlation for HTML 401/403 saves
dec2bb7
📝 docs: document tool-call save recovery and HTML 401/403 gateway troubleshooting
d18657d
📝 docs: document the in-chat Image tool and Code Interpreter behavior
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0c29e69
📝 docs: clarify full-screen dismissal (close in place vs Back returns to previous screen)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
bd7cfb0
📝 docs: note Mermaid diagrams open full-screen and are dismissible
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
5939052
📝 docs(wiki): distinguish full HTML/SVG (inline) from bare fragments (source)
Reconcile the code-block section with the implemented policy: full HTML pages,
SVG and Mermaid render inline with the Preview/Code toggle; a bare HTML fragment
stays source with the on-demand eye-icon preview.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
121d65e
📝 docs(wiki): remove background-generation note (feature reverted)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
821b589
📝 docs(wiki): SVG code-block preview scope + background generation note
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
43db016
📝 docs(wiki): note code-block diagrams render inline + mobile dismissal
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
7fd726d
📝 docs(wiki): gradients are stripped from inline SVG diagrams
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0094e4d
📝 docs(wiki): align Inline SVG Diagrams page with hardened sanitizer and styled export
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
4df851f
📝 docs(wiki): add Inline SVG Diagrams page
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
456d0c1
📝 docs(knowledge): clarify mobile category vs base navigation and upload owner
Round-2 review follow-up: the mobile section now states that categories
always return to All Files (even from a base-detail route), that opening a
named base drops current filters, and that the header carries the single
upload action. Aligns the wiki with the workspace-first shell fix.
Co-authored-by: Cursor <cursoragent@cursor.com>
077ac4b
📝 docs(knowledge): update mobile workspace navigation
Document the workspace-first mobile Knowledge UI: opening Knowledge goes
directly to All Files, the header menu switches categories and named bases
in a left drawer, bottom navigation stays visible, and search/upload/file
rows are touch-friendly with a full-width chunk drawer.
acddd48
📝 docs(mobile): document More navigation
034172c
📝 docs(knowledge): clarify file membership
Co-authored-by: Cursor <cursoragent@cursor.com>
40dd576
📝 docs(markitdown): clarify universal chunk drawer routing
State that filename and card clicks open the chunk drawer for every file,
while unsupported formats still receive the explanatory empty state.
eead03f
📝 docs(knowledge): document universal chunk drawer
2936864
📝 docs(markitdown): restore chunk provenance sentence
Restore the sentence subject after the bounded-table explanation so the chunk
viewer documentation reads correctly.
a3d8fbc
📝 docs(knowledge): document bounded chunk drawer tables
Explain bounded Markdown table pages, capability-aware Office empty states,
and the provenance-only chunk metadata contract.
ebc2ce1
📝 docs(knowledge): document chunk drawer pagination
Document Markdown-rendered per-chunk navigation, Office zero-chunk parsing, and the re-parse requirement for existing malformed tables.
5c902ac
📝 docs(knowledge): document chunk-paginated File Preview popup
Describe the new Reference Chunks -> File Preview workflow: the Chunk tab
paginates a message's retrieved chunks and the File tab paginates every
chunk of the source file (one chunk per page), replacing the old
single-scrollable whole-document view. PDF and image files keep their
native renderers.
16d6cfd
📝 docs(markitdown): per-file MarkItDown icon + content-only chunk viewer
Document the new MarkItDown file-row action (re-parse via MarkItDown + open
converted content) and that the chunk drawer is now a content-only viewer —
Office documents no longer preview via Office Online, and clicking an Office
file's name opens the converted-content viewer once chunked.
848ef20
📝 docs(markitdown): document in-UI re-parse action and chunk provenance badge
The Verify section now describes the portal affordances instead of implying
provenance is only visible via raw metadata: the Chunks tag opens the drawer,
each chunk shows a MarkItDown/LangChain provenance badge, clicking a chunk
opens a detail modal with converted_by/type, and historical files can be
re-chunked via the file row's "Re-parse chunks" action (which routes through
the sidecar once MARKITDOWN_SERVICE_URL is set).
d13b50d
📝 docs(markitdown): fix LLM base URL wording, drop output-equivalence claim, distinguish image description from OCR
Three wording corrections after d6391d8:
- LLM_BASE_URL: "custom or non-OpenAI endpoint that exposes an
OpenAI-compatible API" (3 spots: env example, feature table, build-time
env block). The old "non-OpenAI-compatible endpoint" was self-contradictory
— the openai SDK only talks to OpenAI-compatible APIs. Confirmed against
server.py docstring which already calls it an "OpenAI-compatible endpoint".
- Alternative images: drop "handles every native-text format identically —
verified by importing every converter". Converter imports prove
availability, not output equivalence. Replaced with "supports the same
native-text input formats" plus a fixture-validation note.
- What-it-adds image row: "EXIF metadata, plus an LLM-generated description
when configured; OCR is available separately through supported Azure paths"
— separates the built-in ImageConverter's description from OCR.
a258b07
📝 docs(markitdown): clarify LLM base URL conditionality and split captioning from OCR plugin
Three wording corrections after the structural redesign:
- markitdown.env comment: MARKITDOWN_LLM_BASE_URL is set only for a
non-OpenAI-compatible endpoint; API_KEY + MODEL are the required pair.
- Conditional feature groups: split the bundled "LLM vision" row into
standalone image captioning (built-in ImageConverter, no plugin) and the
OCR plugin (needs ENABLE_PLUGINS + INSTALL_OCR_PLUGIN). Standalone
captioning never required ENABLE_PLUGINS.
- markitdown-ocr plugin scope: it registers converters for PDF/DOCX/PPTX/XLSX
only, not standalone PNG/JPEG. Confirmed against upstream pyproject.toml
(v0.1.7): description lists PDF, DOCX, PPTX, XLSX; no standalone image
format in keywords. Standalone images go through the built-in
ImageConverter, which uses the same llm_client without plugins.
d6391d8
📝 docs(markitdown): redesign page structure — unified Quick start, env_file compose
Consolidates the two parallel "Run" flows (prebuilt + build) that had grown
to duplicate topology, verify, and ChatHub-wiring sections into one Quick
start with a shared markitdown.env and two options (A pull, B build). Moves
the build-path docker-compose.yml to env_file: so it matches the prebuilt
one and ChatHub's component-scoped env convention — no inline environment:
block remains. Gathers all ChatHub-side wiring into a single Connect ChatHub
section. No factual changes; same HTTP contract, same OCR coverage, same
Dockerfile/requirements/server.py.
621c1eb
📝 docs(markitdown): apply review corrections — plugin enablement, recipe scope, Azure boundary, output, reproducibility
Five review findings, all verified against the markitdown v0.1.7 source and
the running production image before applying.
1. Plugin enablement needs MARKITDOWN_ENABLE_PLUGINS=true, not just the
build arg. MarkItDown loads entry points only when enable_plugins=True,
and the sidecar defaults MARKITDOWN_ENABLE_PLUGINS to false. Building
with INSTALL_OCR_PLUGIN=true without the runtime flag leaves the
markitdown-ocr entry point unregistered. The full LLM-OCR path needs all
three: INSTALL_OCR_PLUGIN=true + MARKITDOWN_ENABLE_PLUGINS=true +
MARKITDOWN_LLM_*. Corrected in Build-time only and OCR for scanned
documents and pictures.
2. INSTALL_OCR_PLUGIN is Debian-recipe only. The current prebuilt Wolfi
image does not define or consume it, so "off by default on every recipe"
was too broad. The component table now has separate Debian and Wolfi
columns, and the intro notes the Wolfi recipe must be extended before
the arg can be used. Verified from the image's docker history.
3. Azure Document Intelligence is not equivalent to markitdown-ocr for
embedded Office images. In markitdown v0.1.7 the
DocumentIntelligenceFileType enum marks DOCX/PPTX/XLSX/HTML as
"# No OCR" and PDF/JPEG/PNG/BMP/TIFF as "# OCR", so Azure runs Office
formats without OCRing their embedded images. Reworded the Azure path
to state the boundary; noted Content Understanding is a separate path,
not identical to Document Intelligence. Verified from
converters/_doc_intel_converter.py.
4. Scanned PDFs return empty Markdown, not EXIF. EXIF metadata is an
image-input concept (exiftool converter); PDFs go through text
extractors which return empty for image-only pages. Distinguished the
two cases with the verified {"chars":0,"markdown":"","title":null}
output for an image-only PDF.
5. Reproducibility and compatibility claims softened. Removed "unpinning
produces a working image", "converts files identically", and "pin for
byte-for-byte output" — upgrades may change behaviour and top-level pins
do not guarantee reproducibility. Replacement states upgrades are
supported but require HTTP-contract tests, conversion fixtures, and a
fresh CVE scan; true reproducibility needs a full lock, pinned
base-image digest, pinned upstream revision, and controlled build
environment.
Confirmed-correct conclusions left in place: native-text completeness, no
LLM/Azure needed for basic conversion, text-PDFs-with-images supported,
image contents ignorable, markitdown-ocr optional not missing, PyMuPDF is a
renderer not the OCR engine.
22d686b