code-office is a VS Code extension that lets you edit DOCX, Markdown, and Korean HWP/HWPX files, review PPTX decks with a PowerPoint-like read-only viewer, and preview other Office/workspace formats such as spreadsheets, PDF, HTML, archives, images, and fonts — all inside VS Code tabs. No external applications needed.

Yes. code-office is open source under AGPL-3.0-or-later. Upstream MIT notices from the vscode-office lineage are preserved in NOTICE.md.

No. Everything runs locally. The HWP editor uses a bundled WASM runtime that runs inside VS Code's WebView. No network requests are made to process your documents.

Editable: Markdown (.md, .markdown), DOCX (.docx, .dotx), HWP, HWPX

Read-only viewer: PPTX, PPTM, PPSX, XLSX, XLSM, XLS, CSV, ODS, PDF, HTML, HTM, ZIP, JAR, APK, VSIX, RAR, TTF, WOFF, WOFF2, OTF, SVG, JPG, PNG, GIF, APNG, BMP, ICO, WEBP, TIF, TIFF, JFIF, AVIF, PSD

Export: Markdown → PDF, DOCX, HTML

code-office is built on the foundation of vscode-office (by cweijan), which was the most popular VS Code office document viewer. After 3 years of inactivity, we forked it via rjwang1982's maintained fork and added HWP editing, modern Mermaid support, and a restructured architecture for AI-era document workflows.

DOCX rendering and editing now use SuperDoc (@superdoc-dev/react), which is AGPLv3/commercial dual licensed. Because SuperDoc is bundled in the product, the top-level project license is AGPL-3.0-or-later.

No. The product wedge is local HWP/HWPX editing and cross-format document review inside VS Code. Markdown stays useful because it sits beside DOCX, HWP/HWPX, PPTX, PDF, spreadsheet, and source files in the same workspace. code-office does not claim Obsidian's graph/mobile/plugin ecosystem or native office-suite layout fidelity.

The extension bundles a local WASM runtime called rhwp-studio (based on edwardkim/rhwp). HWP/HWPX files open through the existing cweijan.hwpEditor custom editor ID, but the tab now has internal Viewer and Editor modes. First open defaults to Viewer; after the user chooses Edit or View, the last selected mode is reused for future HWP/HWPX tabs. Edits happen in the WASM runtime. Saves validate magic numbers before writing. Same-file Cmd+S writes in place to avoid rename churn in VS Code's custom editor lifecycle; Save As, backup, and toolbar fallback writes use the temp-file atomic path.

If the document is clean, the switch renders Viewer pages immediately. If the Editor is dirty, code-office first runs the normal VS Code custom editor save lifecycle. The mode changes to Viewer only after save succeeds. If save fails, times out, or is cancelled, the tab stays in Editor and the persisted last mode is not changed.

Use the Viewer toolbar Save PDF button or the Command Palette command HWP/HWPX: Save as PDF to save the rendered Viewer pages as a PDF. The extension asks for the destination once, saves a dirty editor first through the normal VS Code lifecycle, then tries the bundled native rhwp PDF helper in resource/rhwp-native/<platform>-<arch>/. That helper is packaged for the platform that built the VSIX; if the helper is unavailable, mismatched, or fails, code-office falls back to the older webview image-PDF assembly path. Use HWP/HWPX: Export SVG Pages, HWP/HWPX: Show Debug Overlay, and HWP/HWPX: Dump Paragraph for the developer surfaces. SVG/PDF export and debug overlay are also available from the Viewer developer menu. Paragraph dump uses the vendored rhwp-vscode glue/WASM pair in resource/rhwp-vscode so it can inspect paragraph metadata from the extension host. It reads the saved file from disk; if the document is dirty in an open editor, save it before dumping.

Yes. Set code-office.hwp.studioUrl to the URL of your rhwp-studio server. The extension will use postMessage RPC with token-based authentication to communicate with the remote editor. The default is empty, which uses the bundled local runtime.

The save pipeline has multiple safety layers:

1. Magic number validation: Verifies the exported bytes match the expected format (OLE for .hwp, ZIP for .hwpx)
2. Size check: Rejects empty exports and files over 50 MB
3. Write policy: Same-file VS Code saves write in place after validation. Save As, backup, and toolbar fallback saves use temp-file atomic writes.
4. 120-second timeout: If the WASM editor doesn't respond, the save fails with an error instead of hanging.

The public support matrix is maintained in HWP-HWPX-COMPATIBILITY.md. Private user documents are not committed as fixtures; use synthetic or redacted samples for public bug reports.

Yes. When using the toolbar Save button, if the export format differs from the file extension, the extension offers to save as a new file with the correct extension.

code-office needs a real editable DOCX surface inside VS Code, not only a static preview. SuperDoc provides the browser DOCX runtime used by the dedicated cweijan.docxEditor custom editor while the extension host keeps file I/O and save lifecycle ownership.

No. DOCX editing is useful for workspace review and common document edits, but it is not a full Microsoft Word replacement. Complex OOXML features, exact page layout, proprietary fonts, and round-trip fidelity can differ. For documents where legal or publication fidelity is mandatory, keep a backup and verify the result in Microsoft Word or another native editor before distribution.

DOCX failures should fail visibly instead of silently writing partial output. The product direction is to keep a read-only/fallback path available when the editable runtime cannot load or export safely. The extension must not write a DOCX export that failed validation.

SuperDoc is AGPLv3/commercial dual licensed. code-office bundles the open-source package and is therefore distributed as AGPL-3.0-or-later. Teams that cannot use AGPL software should evaluate the license before installing.

Use the public registries for normal installation, or GitHub Releases when a tagged artifact is needed:

• VS Marketplace: jun6161.code-office
• Open VSX: lidge-jun.code-office
• GitHub Releases: https://github.com/lidge-jun/code-office/releases

Tag-based releases include Marketplace/Open VSX VSIX artifacts and SHA256SUMS.txt. Verify local downloads with:

shasum -a 256 -c SHA256SUMS.txt

.github/workflows/release.yml runs the same local release gate, builds the Open VSX publisher-adjusted VSIX, writes checksums, creates artifact provenance attestations, uploads workflow artifacts, and creates a GitHub Release for v*.*.* tags.

Vditor — a feature-rich WYSIWYG/IR/SplitView editor. The default ir setting gives an Obsidian-like Live Preview surface.

Yes. Set vscode-office.editorMode to raw, or click the Raw Source toolbar button next to the preview controls. Raw Source stays inside the code-office WebView, keeps the normal VS Code save lifecycle, and does not replace the separate Edit In VSCode action.

When focus is inside the Markdown WebView, Cmd+E on macOS or Ctrl+E elsewhere toggles the Vditor reading preview, matching Obsidian's Live Preview ↔ Reading Preview flow. The older Ctrl+Alt+E / Ctrl+Cmd+E shortcut still opens the file in the default VS Code text editor.

Use the export function in the Vditor toolbar. The extension uses Chromium (detected automatically: Edge → Chrome → Brave) to render and export. You can set a custom Chromium path with vscode-office.chromiumPath.

Yes. [[wikilink]] syntax is supported with:

• Click navigation from rendered Live Preview labels (resolves to the closest matching file in your workspace)
• Basic path forms including [[note]], [[note.md]], relative .md paths, and absolute .md paths
• Non-Markdown file bodies such as [[image.png]] and [[document.pdf]] stay as raw text instead of becoming note links
• Support for headings ([[note#section]]), aliases ([[note|display text]]), and block IDs ([[note^blockid]]) in the parser/resolver surface
• Inactive Live Preview chunks render supported wikilinks as clickable labels; placing the caret at a wikilink boundary reveals the local [[...]] source for editing without switching the whole editor to raw mode.

The abandoned WebView dropdown/autocomplete experiment is isolated on the dev/wikilink-authoring-autocomplete branch and is not part of the current release.

1. Check if resource/rhwp-studio/index.html exists in the extension directory
2. Try setting code-office.hwp.studioUrl to empty (use bundled version)
3. Open the Output panel → "Office" channel for error messages

Ensure you have Chrome, Edge, or Brave installed. Or set the path manually:

{
  "vscode-office.chromiumPath": "/path/to/chrome"
}

By default, the editor only loads images relative to the document folder. To allow absolute paths:

{
  "vscode-office.viewAbsoluteLocal": true
}

Note: This opens the full filesystem to the WebView. Use with caution.

Legacy .ppt format requires LibreOffice for conversion. Install LibreOffice and set:

{
  "vscode-office.pptx.libreOfficePath": "/path/to/soffice"
}