A note about this build log entry: I published this after the week it covers. DevNitro reconstructed a draft from work-related entries in my journal, Git commit history, and time tracking. I reviewed, edited, and approved the final post. The story reflects what I knew and built at the time.

From the Backlog to the Build Log

Week of January 23 - January 29, 2026

What I Worked On

The best thing I built this week: I gave the agent a language server. Until now, when the AI needed to rename a symbol or find where something was used, it fell back on text search and hope. This week I wired in LSP code intelligence, the same Language Server Protocol your IDE uses, so the agent gets real C# understanding: go-to-definition, find-references, rename that respects scope, and live compiler diagnostics.

That is a different class of tool. A grep-based rename catches the wrong strings and misses the right ones. An LSP rename knows the difference between the symbol and a comment that happens to share its name. I auto-detect the best available C# language server, prefer csharp-ls, fall back gracefully, and got it working inside the DevNitro codebase itself.

The other large block was IssueSwarm growing a real hierarchy. It now has cross-project epics, strict parent-child type validation, priority inherited from the parent, a quick-create child button, and a Ready Issues page that surfaces the leaf-most, highest-priority work an agent can actually claim. Stale sessions auto-abandon.

I also moved BlankSite's services onto an IOperationResult pattern and a dual-mode service pattern, so every service returns a structured result instead of throwing, and runs the same way from the UI and an API. Continuing to refactor the code costs time, but I fully expect that to pay off in the long run. It is critical for AI to have good patterns to follow. When you can generate so much code quickly, you have to make sure the patterns the AI follows are solid.

What the AI Did Well

The LSP work was a lot of protocol plumbing: readiness detection, diagnostics capabilities, file-change notifications after a rename. The AI worked through it steadily, and once it was in, I used it. Precise renames across the codebase that a text search would have mangled. I also had it design a persistent memory system, scoped to company, team, project, and user, so context can outlive a single session.

What Needed Correction

LSP did not work inside the DevNitro project itself at first, which is the one project where I most needed it. It took a second day to sort out server detection and workspace reload logic before rename and diagnostics behaved on my own code.

The create-site demo defeated me again. I tried to record DevNitro generating a new site and hit port conflicts, a login-logout loop, missing email confirmation, and a bad connection string I had set myself. Not a clean enough run to show, so I scrapped the demo and recorded a "You Already Know This" reminder video instead. The generation works. Filming it going right, start to finish, is a skill I have not mastered yet.

What Shipped

The agent has LSP-backed code intelligence: navigation, find-references, scope-aware rename, and diagnostics, with automatic C# server detection. IssueSwarm has cross-project epics, a validated hierarchy, inherited priorities, and a ready-to-claim queue with concurrency-enforcing session cleanup. BlankSite services use IOperationResult and a dual-mode pattern. Company-level Stripe billing and a pricing page are in. And the persistent memory system has a design.

The Numbers

Category	Hours
Product / Features	44h 12m
Content	5h 56m
Business	3h 38m
Testing	2h 38m
Community	1h 5m
Total	57h 29m

Tools, BlankSite, and IssueSwarm split most of the week evenly, with a few hours on pricing and testing. The pricing time went into a model built around concurrent AI workstreams rather than raw seats.

Grep is how you search a codebase. An LSP is how you understand one. Handing that same understanding to the agent moves it from editing text to editing code.

Curious how this site was built?
Watch the 5-minute walkthrough at devnitro.com →

January 30, 2026 Build Log: Giving the Agent a Language Server