Independent VS Code extension

code-office

code-office keeps document-heavy workflows inside VS Code: local HWP/HWPX editing, editable DOCX, Markdown authoring, PowerPoint-like PPTX review, PDFs, archives, images, HTTP request files, and registry files.

Showcase

Built for the review work that AI-era document flows actually create.

The extension is not an AI generator. It is the VS Code surface for the document formats that show up around AI-assisted work: generated DOCX drafts, Korean HWP/HWPX references, Markdown notes, PDFs, spreadsheets, archives, and source files that need to stay inspectable together.

Format wall

HWP, DOCX, XLSX, PDF, PPTX, and HTML stay in the same review room.

AI-era document work is rarely a single file. code-office keeps the generated brief, the Korean source form, the spreadsheet gate, the PDF evidence packet, the presentation narrative, and the HTML export visible as one workspace story.

code-office PDF source review map inside VS Code Insiders
PDF source map preview captured in VS Code Insiders with the packaged VSIX installed.
code-office showing an editable Korean HWP document with toolbar controls in VS Code
HWP/HWPX editorLocal rhwp-studio runtime, toolbar editing, and VS Code save lifecycle.
code-office editing a DOCX review brief inside VS Code
Editable DOCXGenerated review reports can be edited next to source context.
code-office spreadsheet review dashboard previewed in VS Code
XLSX gateSpreadsheet review checks, owners, scores, and publish readiness.
HTML review room sample rendered for code-office HTML smoke testing
HTML exportLocal browser render used when VS Code WebView capture blocks data-heavy drafts.
code-office PowerPoint-like PPTX viewer inside VS Code
PPTX reviewPowerPoint-like read-only viewer with thumbnails, notes, grid, fullscreen, presenter view, and zoom.
code-office PDF source review map preview inside VS Code
PDF evidence mapSource packets and provenance maps stay inspectable beside the workspace.

Bundled local runtime

HWP/HWPX opens in Viewer first, then switches into editing without leaving the tab.

The default path loads a packaged rhwp-studio build from the extension, not a remote page. The same inherited cweijan.hwpEditor tab now owns internal Viewer and Editor modes, remembers the last mode selected by the user, and keeps dirty state, save, backup, revert, and format checks under VS Code's editable CustomEditor lifecycle.

HWP/HWPX file CustomEditorProvider Viewer / Editor mode React WebView rhwp WASM Save PDF / SVG / HWP bytes VS Code lifecycle

Viewer first

HWP/HWPX files open in a stable Viewer surface by default. Edit/View switches stay inside the same custom editor tab.

Save PDF

The Viewer toolbar and Command Palette use a native rhwp PDF helper when the current-platform binary is packaged, then fall back to image PDF export.

Internal find

Cmd+F / Ctrl+F opens HWP search inside the WebView, highlights rendered SVG text in Viewer, and routes Editor search through rhwp's own find control.

File coverage

One extension for the files that usually scatter a workspace.

FamilyExtensionsModeImplementation note
HWP / HWPX.hwp, .hwpxViewer + editableBundled local rhwp-studio WASM runtime, native-first Save PDF, SVG/debug export, and WebView-local find highlighting.
Markdown.md, .markdownEditableVditor Live Preview, Reading Preview, Raw Source, boundary-aware wikilinks, and inherited export paths.
Word.docx, .dotxEditableDedicated DOCX custom editor using SuperDoc (@superdoc-dev/react) and the VS Code save lifecycle.
Excel.xls, .xlsx, .xlsm, .csv, .odsPreview / inherited edit pathsSpreadsheet viewer stack from the office lineage.
PowerPoint.pptx, .pptm, .ppsxRead-only viewerPowerPoint-like viewer with visual thumbnails, resizable/collapsible sidebar, speaker notes, grid, fullscreen, presenter view, and zoom.
Legacy PowerPoint.pptOptional fallbackLibreOffice conversion is opt-in and disabled by default.
PDF, images, fonts, archivesMultiplePreviewViewer surfaces inherited and kept behind release smoke checks.
HTTP, Registry, HTML.http, .rest, .reg, .html, .htmTooling / previewLegacy runtime IDs remain for compatibility.

Install

Install from a public registry, or build the verified local VSIX fallback.

VS Marketplace

jun6161.code-office
Open Marketplace listing

Open VSX

lidge-jun.code-office
Open VSX listing

Local VSIX fallback

npm install
npm run release:local
code-insiders --install-extension ./code-office-<version>.vsix --force

HWP/HWPX files are still registered through the inherited cweijan.hwpEditor custom editor ID for compatibility. Public branding and repository metadata point to this independent project. Older vscode-obsdian.hwp.* settings are read as a fallback; new HWP settings use code-office.hwp.*. Tag-based GitHub Releases attach Marketplace/Open VSX VSIX artifacts with SHA256SUMS.txt checksums; registries and the local VSIX gate remain verified install paths.

Release artifacts: GitHub Releases. HWP support contract: HWP/HWPX compatibility matrix. Product positioning: competitive context.

Release discipline

Packaging is treated as a smoke test, not a final afterthought.

Registry targets

Release source is main. VS Marketplace publishes jun6161.code-office; Open VSX publishes lidge-jun.code-office from a dedicated publisher-adjusted VSIX. The dev/wikilink-authoring-autocomplete branch is not a release source.

Local gate

npm run release:local

Type-checks, builds, verifies HWP hardening, builds the current-platform native PDF helper, packages the VSIX, and inspects packaged contents.

GitHub Release

.github/workflows/release.yml builds Marketplace and Open VSX VSIX files, writes SHA256SUMS.txt, creates provenance attestations, uploads workflow artifacts, and publishes tagged releases.

VSIX inspection

Checks that rhwp WASM, rhwp-vscode media, the current-platform native PDF helper, NOTICE, and LICENSE are included while vendor sources, samples, docs, native Rust source, and scripts are excluded.

Manual smoke

Install the VSIX, open and save HWP/HWPX, then spot-check Markdown, HTML, XLSX, DOCX, PDF, PPTX, image, and archive surfaces.

Roadmap

Next work is deliberately scoped instead of hidden behind fork branding.

  1. Expanded Obsidian-style Markdown authoring polish after the Live Preview, Reading Preview, Raw Source, and wikilink baseline.
  2. PPTX visual-fidelity and large-deck performance stabilization beyond the current PowerPoint-like view-only UX.
  3. Markdown CJK inline formatting and strikethrough regression coverage.
  4. Excel strikethrough and style preservation.
  5. Optional LibreOffice fallback completion for legacy presentations.

Support and safety

Document viewers touch private files, so support starts with redacted repros.

code-office is designed for local document review. Keep private office files out of public issues, use synthetic or redacted samples, and treat remote HWP studio URLs as trusted-code inputs.

Issues

Report reproducible bugs and feature requests with file type, VS Code version, and redacted sample details.

Architecture

Read the architecture notes before changing HWP, Markdown, Office, PDF, or WebView surfaces.

Contribution

Use the contribution guide for setup, local verification, and release gates before proposing changes.

Sources and attribution

Independent project, visible open-source lineage.

code-office is distributed under AGPL-3.0-or-later after bundling SuperDoc. It still contains code derived from MIT-licensed vscode-office work and packages a local rhwp runtime. It is not affiliated with or endorsed by Obsidian, Hancom, Microsoft, cweijan/vscode-office, rjwang1982/vscode-office, SuperDoc, or rhwp.

Logo OpenAI image-generation concept, manually simplified into images/logo-new.svg.

Screenshots Local smoke captures from temporary HWP, DOCX, XLSX, PDF, PPTX, and HTML samples. Office and PDF captures use VS Code Insiders with the packaged VSIX installed; the HTML export capture uses the rendered local sample for a clean visual check.