assistant-ui ships its first VS Code extension, placing generative UI behind a webview-to-host bridge
assistant-ui released @assistant-ui/vscode 0.0.1 on November 12. The extension runs assistant-ui inside a VS Code webview, routes fetch through the extension host, opens external links through the host, and stores thread state in Memento. A companion CLI scaffolds extensions.
Why it matters
Generative UI is moving from standalone chat pages into everyday work surfaces such as editors. This implementation concentrates networking, navigation, storage, and theme adaptation in the bridge between a webview and a locally privileged extension host, creating a reviewable boundary around model output.
A closer look
The implementation uses a nonce-based content security policy, disallows unsafe-eval, blocks remote media, and checks webview message origin. External navigation accepts only http, https, and mailto while rejecting command, vscode, file, javascript, and other schemes. The project reports 138 tests and 8/8 VS Code probes passing, with coverage for theme tokens, thread storage, and host routing.
Who this is for
Extension, frontend, agent-platform, and security teams embedding generative UI in VS Code or other webview hosts.
Original sources
- assistant-ui official release and implementation pull request ↗github.com
- Official implementation and security review notes ↗github.com
Revisions & corrections (1)
— Evidence-complete catch-up from the official release and implementation review; distinct native-surface event.