BMC Next with Agentic Coding

· Blog, BMC

#ATProtocol#AI#codingharness

I’ve avoided going deep with LLM usage, including for agentic coding.

This is has been for a number of reasons. I don’t want to be sending data to US tech platforms is a big one. I don’t want to start there, and I don’t want to get used to it.

And I didn’t want to have a mental model that was “these things aren’t good at stuff”. Because mostly the question is, what are they going to get good at. Going back to 2024’s Situational Awareness of AI, and now, with the step change in December 2025 where models got really good at agentic coding, the question is how fast will they get good at things.

Now that the Z-Space Local AI project ZAI is up and running, I’ve being using our local cluster to test things out, and generally integrating with more tools that support BYOK.

And, I succumbed to FOMO1 from chatter on Bluesky, and ended up buying a founders subscription to Umans, a French startup hosting open models. Still TODO, try out @ed3d.net’s coding harness Polytoken, which is allegedly what drove a LOT of purchases of the Umans plan.

And so, this weekend, I finally did the thing I’ve wanted to do for a long time: got BMC Jekyll moved over to BMC Next. This site is now powered by Astro.

I initially used the Claude Code app for the first half, and then decided to go all the way and used OpenCode to finish things off. The design / CSS is still a little bit janky, but it works, and I’ve even imported a bunch of pages from my LogSeq notes site.

Going Atmospheric

Ms Boba is the Astro expert that I know, so she pointed me towards her astro-atproto-loader. I created the Links page which fetches all my Semble note cards. Whenever I do a new build of the site, it fetches all my Semble note cards. Other than me forgetting the structure of Semble records2 and then tweaking the design a little, this came together quickly.

Next I integrated what is my main tech blog, blog.bmannconsulting.com. It’s running on Leaflet and now the blog overview page here mixes locally authored posts with links to the Leaflet posts.

I’ll get around to Standard Site integration in the other direction, too.

What about the Digital Garden?

Most info here is in my interconnected notes aka Digital Garden. These days I use Obsidian for editing, using wikilinks to make it easy to link to other pages, and to show backlinks — see what other pages point to a page. And one of the ways you can visualize that is through a big graph.3

But notes aren’t microblog posts and they aren’t really long form writing in a publication. So I don’t want to publish them as Standard Site documents or a publication. They’re being edited and updated over time, which is closest to the activity of a wiki, except just edited by me.

I do like the look of Lichen Wiki, an atproto wiki implementation. It supports backlinks, which I think is one of the key attributes of interlinked notes.

More Agentic

This is close to my first foray into agentic coding skills, I’m switching between tools of various kinds - Zed as an editor, CLI for interaction with the agent, GUI version of agent, Television for display artifacts, local only git pushing over Tailscale etc etc.

That’s a lot for me to keep straight, never mind providing context for an agent. No one shot apps quite yet, although tips on Proxmox Setup with Claude Code for gnarly virtualization and networking stuff is useful already.

Other things to dive into:

  • figuring out skills, and using Vit as an atproto native way to trust other devs and share / sync / fork skills
  • MCP, especially ones like the Lexicon Garden one

This

Oh and yes, there are likely to be broken things here and there, and the design is kind of janky. If you’ve seen my site before, it’s the same eccentric pieces of my brain.

Footnotes

  1. Fear of Missing Out. And I almost did! I was in the Stripe checkout page in one tab when the main page started showing as sold out. $500USD for a year of Coding Max. Cancelled everything else I was experimenting with. ↩

  2. Semble uses the Cosmik Network namespace, with cards as the main item. There are link cards, and then your notes on them are of type NOTE, with the parentCard containing the full info on the URL. I wanted to include only NOTE cards, where I had written something about the URL. ↩

  3. And yes, the graph is more “neat” than useful, and currently that visualization is a bit busted. Having all the notes on that page means you can use your browser to quickly search pages at least. ↩