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 February 13 - February 19, 2026

What I Worked On

Two features this week are about making DevNitro safe to hand to a team instead of one developer.

The first is AI organizational memory. Persistent memory scoped to the organization, the team, the project, and the user, with policies, bundles, and an audit trail. An individual using AI keeps everything in their own head and their own chat history. A team needs shared, governed context that outlives any one session and any one person. That is what this is: a memory the whole org shares, with rules about who can see and change what. I remembered watching the movie Memento. So I looked it up and it was available to stream. I spent an evening rewatching the film while designing persistent memory system, and I half-want to name the system Sammy Jankis.

The second is a real authorization layer. I overhauled DevNitro's claims and roles, renamed claims to AccessRights, and moved every auth check out of the controllers and into the server-side services, so server-side rendering gets the same protection the API does. There is an admin UI now for managing roles, claims, and searching users, and a production seed so a new company starts with sane defaults. The goal: anyone in a company can view and manage issues as long as the company has an active seat.

Underneath both, I kept grinding on the agentic loop, which is where most of the hours actually went.

What the AI Did Well

The roles-and-claims overhaul is exactly the kind of careful, wide security refactor the agent is good at when the pattern is clear. Moving auth into services across dozens of endpoints, seeding production roles, and isolating auth cookies per app all landed cleanly. I also added multimodal support, so I can paste an image into the chat, and Codex response chaining over a WebSocket connection for the OpenAI path.

What Needed Correction

The honest grind this week was hallucinations. Opus 4.6 kept claiming it ran tools and inventing the results, and I spent days fighting it. I built a message pump and a parallel tool dispatcher, improved detection, and added recovery so a fabricated result gets caught. One decision I like: when DevNitro strips a hallucinated tool call out of a message, it stores the original untouched, so I can always see what the model actually said versus what I let through.

It is not fully solved. I tested by having it build a hat shop over and over, and while the finished hat shop looked good, getting there reliably across parallel subagents and a brand-new model took the whole week and is still ongoing.

I also hit a small but annoying auth bug where multiple sites on localhost shared one cookie. Fixed now by isolating cookies per app.

What Shipped

DevNitro has an organizational memory system with policies, bundles, and audit, scoped across org, team, project, and user. Authorization is a real roles-and-claims layer enforced in the services, with an admin UI and production seed. The agentic loop has a message pump, parallel tool dispatch, and stronger hallucination detection and recovery. TUI Chat supports pasted images, the OpenAI path uses Codex WebSocket response chaining, and create_site is now the enforced entry point for all new project scaffolding.

The Numbers

Category	Hours
Product / Features	37h 16m
Content	6h 13m
Testing	5h 43m
Community	2h 12m
Total	51h 24m

Fifty-one hours, with the agentic loop and roles taking the biggest bites, plus real testing time and multi-provider work on Ollama and OpenAI.

A developer with AI needs a good model. A team with AI needs shared memory, real roles, and an agent that does not lie about what it did. This week was three steps toward the second thing, which is the harder and more valuable one.

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

February 20, 2026 Build Log: Memory and Roles for a Team