Tools

The codebase had grown fast. Features landed, bugs got fixed, new capabilities kept shipping. Then a structural audit revealed what that pace had cost: god files, god functions, and a growing maintenance burden.

Sentinel could generate code, build websites, write files. But every piece of content was synthetic — generated from scratch by an LLM. What if it could use real photos, real videos, real documents?

Sentinel could browse the web. It could read files and write code. But it couldn’t answer ‘what’s the weather?’ without fabricating something. Time to give it real data backends.

file_patch needs the planner to find a unique anchor string in existing code. The planner is bad at this. What if the system placed named markers instead?

LLMs don’t always respect file boundaries. Raw CSS lands in HTML files, JavaScript appears without script tags. Building a detector to catch it.

New planner, new classifier, new patching tool. Putting it all together to iteratively build and modify websites through conversation.

Full-file regeneration breaks at scale. The new tool generates only the changed fragments and splices them deterministically.