Reviewable plan for the user three asks: (1) file previews for office/image/markdown/code files and web links, docked in the right rail or the system overlay; (2) keep artifact deletion as a reserved API capability with no UI entry; (3) implement sandboxed fs tools behind a default-off gate.
The proposal carries a reasonableness assessment per idea, a FilePreview capability component with a format matrix (lazy-loaded mammoth/SheetJS/JSZip), an SSRF-guarded /api/url-preview endpoint, the gated fs tool family, four delivery phases with acceptance criteria, and decision points D1-D5.
Documentation only; implementation follows after D1-D5 are settled.
Refs: task feature/file-preview-proposal.
## What
Reviewable plan for the user three asks: (1) file previews for office/image/markdown/code files and web links, docked in the right rail or the system overlay; (2) keep artifact deletion as a reserved API capability with no UI entry; (3) implement sandboxed fs tools behind a default-off gate.
The proposal carries a reasonableness assessment per idea, a FilePreview capability component with a format matrix (lazy-loaded mammoth/SheetJS/JSZip), an SSRF-guarded /api/url-preview endpoint, the gated fs tool family, four delivery phases with acceptance criteria, and decision points D1-D5.
Documentation only; implementation follows after D1-D5 are settled.
Refs: task feature/file-preview-proposal.
Why: the user asked for a reviewable plan covering (a) previews for
office/image/markdown/code files and web links, docked in the right rail
or the system overlay, (b) keeping artifact deletion as a capability with
no UI entry, and (c) implementing fs tools without enabling them.
Evidence: the proposal assesses each idea against current architecture,
defines the FilePreview capability component with a format matrix and
lazy-loaded office parsers, the SSRF-guarded url-preview endpoint, the
gated sandboxed fs tool family, four delivery phases with acceptance
criteria, and decision points D1-D5 for the user.
Impact: documentation only; implementation follows in a separate task
after D1-D5 are settled.
Refs: task feature/file-preview-proposal; extends 2026-09-30
ui-redesign-and-auth.md section 9.
weichen
merged commit ffb2aa7cc4 into main2026-09-30 16:03:25 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Reviewable plan for the user three asks: (1) file previews for office/image/markdown/code files and web links, docked in the right rail or the system overlay; (2) keep artifact deletion as a reserved API capability with no UI entry; (3) implement sandboxed fs tools behind a default-off gate.
The proposal carries a reasonableness assessment per idea, a FilePreview capability component with a format matrix (lazy-loaded mammoth/SheetJS/JSZip), an SSRF-guarded /api/url-preview endpoint, the gated fs tool family, four delivery phases with acceptance criteria, and decision points D1-D5.
Documentation only; implementation follows after D1-D5 are settled.
Refs: task feature/file-preview-proposal.