Independent VS Code extension

code-office

AI tools create more drafts, citations, Korean office files, and review artifacts. code-office keeps those document-heavy workflows inside VS Code: editable HWP/HWPX, Markdown authoring, Office previews, 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 previewing a DOCX review brief inside VS Code
DOCX briefGenerated review reports stay 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 presentation preview inside VS Code
PPTX previewCurrent text/media preview for narrative decks.
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 editing is the main product split from upstream office viewers.

The default path loads a packaged rhwp-studio build from the extension, not a remote page. The editor is wired into VS Code's editable CustomEditor lifecycle so dirty state, save, backup, revert, and format checks stay under the host editor.

HWP/HWPX file CustomEditorProvider React WebView rhwp WASM exportHwp/exportHwpx VS Code save

Full rhwp surface

Toolbar editing, text changes, table and cell selection, and export paths are exposed through the bundled studio runtime.

Local by default

The packaged runtime is copied into resource/rhwp-studio during build. Remote studio URLs are an advanced opt-in override.

Format guardrails

Save checks preserve the destination format and reject silent mismatches before bytes are written back to disk.

File coverage

One extension for the files that usually scatter a workspace.

FamilyExtensionsModeImplementation note
HWP / HWPX.hwp, .hwpxEditableBundled local rhwp-studio WASM runtime.
Markdown.md, .markdownEditableVditor-based authoring with inherited export paths.
Word.docx, .dotxPreviewdocx-preview/docxjs-derived rendering.
Excel.xls, .xlsx, .xlsm, .csv, .odsPreview / inherited edit pathsSpreadsheet viewer stack from the office lineage.
PowerPoint.pptxRead-only previewText/media preview while deeper fidelity work remains on the roadmap.
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

Use a release VSIX until Marketplace publishing is intentionally opened.

Stable VS Code

code --install-extension ./code-office-<version>.vsix

VS Code Insiders

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.*.

Release discipline

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

Local gate

npm run release:local

Type-checks, builds, verifies HWP hardening, packages the VSIX, and inspects packaged contents.

VSIX inspection

Checks that rhwp WASM, NOTICE, and LICENSE are included while vendor sources, samples, docs, 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. Obsidian-style [[wikilink]] completion, navigation, and WebView/export integration.
  2. PPTX preview stabilization beyond text/media extraction.
  3. Markdown CJK inline formatting and strikethrough polish.
  4. Excel strikethrough and style preservation.
  5. Optional LibreOffice fallback completion for legacy presentations.

Sources and attribution

Independent project, visible open-source lineage.

code-office 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, 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.