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/…