Add GPT-Vis 1.0 vision documentation in src/ai#281
Merged
Conversation
|
Co-authored-by: hustcc <7856674+hustcc@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update GPT-Vis for improved AntV visualization integration
Add GPT-Vis 1.0 vision documentation in src/ai
Jan 26, 2026
hustcc
approved these changes
Jan 26, 2026
Contributor
|
🎊 PR Preview 1d4f3ff has been successfully built and deployed to https://antvis-GPT-Vis-preview-pr-281.surge.sh 🕐 Build time: 18.179s 🤖 By surge-preview |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Documents GPT-Vis 1.0 repositioning as AntV's framework-agnostic entry point for AI-powered visualization, moving away from React-only implementation.
Changes
New documentation:
src/ai/readme.mdoutlining:Release timeline: Version 1.0 stable expected March 21, 2026
Contribution policy: Enforces AI-generated code only
Aligns with RFC discussion on making visualization accessible in AI-driven scenarios (data analysis, reports, presentations) while maintaining AntV's visualization capabilities.
Original prompt
This section details on the original issue you should resolve
<issue_title>RFC: GPT-Vis 1.0 stable, AntV Visualization for AI, Friendly!</issue_title>
<issue_description>### 背景
GPT-Vis 开源了有接近一年多了,当时还是在 RAG 时代,期望通过组件 + 知识库,为 AI 带来可视化能力,再结合 Markdown 输出,让大模型能多模态输出能力,验证来看确实是不错的。到现在,大量以 Markdown 为协议作为 LLM 输出的方案。
这一点 AntV 也算走在前列,可惜的是 GPT-Vis 没有在社区形成足够的影响力和规范。
当前蚂蚁的 Ant Design X 中 x-markdown 方案,聚焦在 Markdown 的大模型输出,并内置了一些 UI 组件,客观来说,确实在 Ant Design 中是更合适的,不过更好的架构是提供非 React 依赖的库,然后在以此封装 React、Vue 等技术栈方案,让前端的大模型渲染上可以保持一致。
基于这些背景,GPT-Vis 需要做一些技术定位的转型,避免重叠和重复,保持特色。
定位
GPT-Vis 当初取名,就是为了给 AI 提供 Vis 能力,只不过在 antv 组织中,更多的考虑的是数据的可视化。现在依然沿用这个名字和释义。
新定位:为大模型提供 AI 友好的可视化组件库,作为 AntV 在 AI 环境的入口,用于在 AI 数据可视化,AI 数据分析,AI 报告,PPT 等提供素材。
原因主要有:
方案
主要关注一下点:
示例
English Version
Background
GPT-Vis has been open-source for over a year. Introduced during the RAG era, the goal was to integrate components and knowledge bases to empower AI with visualization capabilities, coupled with Markdown outputs for multimodal capabilities. The results have indeed been promising. Today, many solutions leverage Markdown as the protocol for LLM outputs.
In this regard, AntV has been a pioneer. However, GPT-Vis has yet to achieve sufficient influence or establish standards in the community.
Currently, Ant Design X’s x-markdown focuses on large language model (LLM) output via Markdown, incorporating built-in UI components. Admittedly, this aligns well with Ant Design. However, the ideal architecture involves providing libraries independent of React, then wrapping them into solutions tailored for React, Vue, or other tech stacks. This ensures consistent rendering for LLM-powered frontend solutions.
Given this background, GPT-Vis requires a strategic shift to avoid redundancy, while maintaining its distinct features.
Positioning
When GPT-Vis was named, its intent was to deliver visualization capabilities for AI, though the focus within the AntV organization was primarily data visualization. The name and its purpose remain consistent today.
New product positioning: Provide an AI-friendly visual component library for large models, serving as a resource for AI data visualization, AI data analysis, AI reports, PPT presentations, and more.
Reasons:
1.. Under AI, users will gradually shift focus away from the underlying engines of data visualization, focusing instead on their specific needs and AI solutions.
2. Being AI-friendly is a long-term theme that needs to be followed. AI evolves rapidly, with transitions from Prompt -> MCP -> Skill. Without keeping pace, one risks being left behind in the AI race.
3. Keeping things straightforward enables better collaboration with Ant Design X, leading to higher ROI.
Plan
The focus areas include:
Show Case