HTML 产物是我现在与代理协作的重要方式
TL;DR · AI 摘要
HTML 产物结合 AI 代理可实现动态自动化，作者通过极简技术栈（HTML+JS+Markdown）构建自优化系统，无需数据库或复杂应用。
核心要点
- 使用 HTML + JS 构建的轻量级 artifact 可与 AI 代理交互，实现自动化写作与排程。
- 所有数据基于 Markdown（如 Obsidian），便于代理读取和修改，无需数据库。
- 作者自研代理编排工具，简化技术栈，提升个性化与维护效率。
结构提纲
按章节快速跳转。
HTML artifacts 正成为作者与 AI 代理协作的核心界面。
artifacts 能触发动作或辅助用户行动，不只是存储内容。
仅用 HTML、JS 和 Markdown 实现完整自动化系统，无需数据库。
所有数据保留在本地 Obsidian 中，支持递归自我改进系统。
该模式已应用于写作、研究、设计等多个领域。
作者将举办直播讲解其代理编排工具的工作机制。
思维导图
用一张图看清主题之间的关系。
查看大纲文本（无障碍 / 无 JS 友好）
- HTML Artifacts 与 AI 代理协同
- 核心理念
- 产物即交互界面
- 动态可执行
- 技术实现
- HTML + JS
- Markdown 数据源
- 无数据库架构
- 优势特点
- 高个性化
- 低维护成本
- 递归自改进
金句 / Highlights
值得收藏与分享的关键句。
当与代理结合时，产物不仅能存储信息，还能采取行动或帮助你行动。
所有数据都在 Markdown（Obsidian 仓库）中，因此代理可以随时访问和修改。
我意识到简化工具链是一种超能力。
我不需要去开发或付费使用完整的应用程序，一个简单的 artifact 就够了。
Artifacts can be more than just static files.
When combined with agents, they can take action or help you take action.
This unlocks all kinds of interesting ways to work with agents.
This is clearly the future. https://t.co/w5mTOb2vxa" / X
HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week: academy.dair.ai/events/cmovobp
0:01 / 0:17
0:15