Frontend

wot-ui CLI 1.1.0 Ships Offline Icon Migration Data and Two New AI Client Integrations

By 不如摸鱼去 · Aug 19, 2026

Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Teams upgrading a wot-ui codebase from v1 to v2 no longer need to guess icon mappings or hunt through docs — the migration skill provides a reviewed lookup table and flags the 101 icons that still need manual decisions. The two new client integrations also mean developers using OpenCode or Antigravity can onboard without writing MCP configs by hand.

Summary

Version 1.1.0 of the wot-ui CLI adds MCP-based agent setup for OpenCode and Antigravity, alongside existing support for Claude Code, Cursor, VS Code, and Codex. The same two-command init-and-doctor workflow applies, with a `--dry-run` flag to preview file changes before committing them. Configuration files are detected at both project and user levels, and the CLI preserves existing settings and JSONC comments.

A separate `migrate-v1-to-v2` skill now includes a complete, manually audited mapping of 295 v1 icons to their v2 equivalents. Of those, 194 have a recommended replacement, while 101 lack a direct counterpart and require human judgment. The mapping covers not just `<wd-icon>` name attributes but also icon-related props, object configs, and dynamic bindings.

Offline component data has been bumped to wot-ui 2.3.2, with versioned JSON snapshots for 90 components each. The CLI and its MCP server can query component APIs, demos, tokens, and changelogs without touching a live documentation API or an API key.

Takeaways

— OpenCode and Antigravity join Claude Code, Cursor, VS Code, and Codex as supported AI coding clients, all configurable via `wot agent init` and verifiable with `wot agent doctor`.

— A `--dry-run` flag lets you preview which files the init command will modify before applying changes.

— The `migrate-v1-to-v2` skill now contains a manually reviewed `icons.json` covering all 295 v1 icons; 194 have recommended v2 mappings and 101 have no direct equivalent.

— Icon migration must check `<wd-icon>` name, icon-related props like `prefixIcon` and `suffixIcon`, object configurations, and dynamic bindings — it is not a simple global find-and-replace.

— Offline component data is synced to wot-ui 2.3.2, with versioned JSON snapshots for 90 components, enabling API, demo, token, and changelog queries without a live docs API.

— Beta releases now use the npm `beta` dist-tag and no longer occupy `latest`.

— The 42,781-line diff from v1.0.6 is mostly offline data snapshots, not functional code growth.

Conclusions

Bundling a manually reviewed icon migration table as a skill asset, rather than a script, shifts the work from automated guesswork to a structured decision process — the tool surfaces the 101 no-match cases explicitly instead of silently mapping them to a wrong icon.

Offline component data snapshots remove a runtime dependency on a live documentation API, which matters when an AI coding agent is running in a CI or air-gapped environment where external calls are blocked or slow.

Supporting six AI clients through a single CLI with the same init-and-doctor pattern suggests the MCP-based agent integration surface is stabilizing enough that adding a new client is mostly a config-file concern.

Concepts & terms

MCP (Model Context Protocol)

An open protocol that standardizes how AI coding clients connect to external tools and data sources. The wot-ui CLI registers an MCP server so that supported clients can query component APIs, demos, and changelogs directly.

wot-ui

A Vue-based UI component library for building web interfaces. The CLI and its associated skills help developers use and migrate wot-ui components inside AI-assisted coding workflows.

Source: juejin.cn ↗ Google Translate ↗ Backup ↗