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 16 - January 22, 2026

What I Worked On

The milestone this week is a little recursive: I used DevNitro to build DevNitro. I set up a local deployment loop so the tool can work on its own codebase without locking the files it needs to compile, then had it build three of its own tools, the task-output tool, the grep-search tool, and the glob-files tool. AI-assisted .NET development is a lot more convincing when the AI is assisting on the thing you sell.

The biggest single block of time was team subscriptions. I got companies, teams, and personal projects working end to end. When I subscribed with my own email, the system created the company from the email domain automatically, and I could edit the company and team in the web UI. Dual authentication is in place too, so the API accepts both an API key and a logged-in user.

I also matured IssueSwarm, the issue-tracking side of DevNitro. Claiming and releasing an issue now requires a status, so work cannot silently vanish. Issues have dependencies, a review workflow, default priorities, and a rolled-up-versus-all toggle on the dashboard. And I can finally create and edit issues from the web UI, not only the CLI.

What the AI Did Well

Two things stood out. First, the self-hosting: pointing DevNitro at its own repo to build its own tools worked, which is the strongest test I have. Second, I implemented a context algorithm, with a specific approach straight from a scientific paper. I wrote the spec with Opus 4.5 and let the autonomous C# agent build it, moving the context-summary levels into the data seeder so they are configuration, not code. Turning a research paper into a working feature in a day surprised me.

What Needed Correction

The unglamorous stuff piled up. The bin/obj clear bit me again, so this time I wrote the fix into AGENTS.md so the agent and I both stop losing an hour to it. Session persistence half-works: sessions save, but the conversation messages inside them do not yet. Timeout tests were failing and needed real digging. And I hit 92 percent of my weekly model allotment by Wednesday, which is its own reminder that heavy agent work has a real, metered cost.

CLI paste also refuses to cooperate. Ctrl+V still does not behave, and I have burned more time on it than I want to admit.

What Shipped

DevNitro builds its own tools through a local deployment loop. Team subscriptions work, including auto-creating a company from an email domain and editing company and team in the web UI, behind dual authentication. IssueSwarm has status-gated claim and release, dependencies, a review workflow, priorities, and web-based editing. Context management is in. And DevNitro.Core is refactored into feature folders.

The Numbers

Category	Hours
Product / Features	52h 49m
Content	4h 23m
Community	2h 15m
Total	59h 27m

Fifty-three hours of product this week, split across subscriptions, IssueSwarm, and the recursive context work, with a light content week around it.

The test I trust most is whether DevNitro can build DevNitro. This week it built its own tools, tracked its own work, and managed its own context. It also ran out of tokens on Wednesday. Both of those are true, and both of them matter.

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

January 23, 2026 Build Log: DevNitro Builds DevNitro