From the Backlog to the Build Log
The Grok Provider Week: August 14 - August 20, 2026
What I Worked On
xAI released Grok 4.6 on Saturday. That night I downloaded Grok Build, opened DevNitro, and started on a Grok provider. By Monday I had it deployed. DevNitro can now drive Grok two ways, straight through the xAI API or through the Grok Build CLI. Same drill as March, when GitHub Copilot joined the lineup. A new model joins fast because Intelligent Engineering keeps the tools, context, and guardrails a level above any one model.
Two more threads ran alongside it. I built an ACP adapter (Agent Client Protocol) so other agent clients can drive DevNitro. Block, the company behind Square, ships a client called Buzz that speaks ACP, and I want DevNitro on the other end of that wire. That work pulled in multi-root workspace support with path validation and interactive permission prompts for file access.
The third thread was measurement, continuing the site work from last week's build log. I shipped provider-agnostic analytics with attribution and an SEO pass (canonical tags, Open Graph, robots, sitemaps, noindexed auth pages) across DevNitro, GlobalCove, and HowdyChad, plus URL shorteners with one standard UTM grammar so attribution holds across all three properties.
GTM took a big slice too. I spent over fifteen hours on messaging and offer pages for GlobalCove.
What the AI Did Well
The first pass at the Grok providers took one Saturday evening. DevNitro's agent scaffolded both providers, wired up provider and model switching with error handling, and mapped Grok tool calls into DevNitro's own tool pipeline. A couple of hours in, I was watching Grok answer through DevNitro's tools.
The ACP adapter went the same way. One evening to a working adapter, then a day of follow-up for multi-root workspaces and the permission prompts. I have not pointed Buzz at it yet, so that still need to be proved out.
The analytics layer came out clean. One provider-agnostic surface over the trackers, consent-gated loading in the blueprint, and the same attribution fields on every site.
What Needed Correction
Two Grok problems needed my hands. First, history. Grok Build manages its own conversation history, and my first integration resent the entire transcript on every turn even though Grok Build already held it. I cut it back to sending only the new turn.
Second, native tools. Grok prefers its own native tool calls over the harness's. My first fix was a denylist, which breaks the day xAI ships a tool I have not listed. I replaced it with verified isolation: DevNitro maps the native calls it knows, surfaces any unmapped call instead of dropping it, and flags a response that states intent while calling nothing. I also aligned Grok's prompt layers with the Codex and Claude Code providers and documented where the harness boundary sits.
During the production test, Claude hallucinated a joke into a weather app. I recorded it and published a short video about it.
What Shipped
DevNitro went to production Monday with Grok in the provider list. Tuesday night I upgraded the BlankSite blueprint, deployed it with the stable private GlobalCove packages, and verified the whole path in production by building a weather app from a fresh blueprint. The SEO and analytics work is live on all three sites.
The Numbers
| Category | Hours |
|---|---|
| Business | 15h 33m |
| Product / Features | 15h 28m |
| Content | 5h 31m |
| Testing | 4h 10m |
| Community | 1h 58m |
| Deploy / Infra | 0h 41m |
| Total | 43h 20m |
Business edged out product for the top slot, my heaviest GTM week so far. The product hours split across five threads (Grok, ACP, analytics, tools, shorteners). Integration week. On the shorteners front, I snagged gcove.to and devnit.ro. I already owned chd.to.
Where This Fits in Intelligent Engineering
The model is a component. The platform owns the tools, the context, and the guardrails, so a model released on Saturday can be a deployed provider by Monday without touching a single app built on top. That is the provider-independence side of Intelligent Engineering: your workflow should survive a model swap without a rewrite, because the parts you trust, support, and scale live a level above the model.
That closes the week. If you are tracking how DevNitro absorbs new models, the Grok provider took three days from release to production (I don't work Sundays). Back at it next week.
Curious how this site was built?
Watch the 5-minute walkthrough on YouTube →
0 Comments
No comments yet. Be the first to share your thoughts!
Leave a comment