Fabr Is Now FabrCore
The framework that powers OpenCaddis has a new name. Fabr is now FabrCore. The code hasn't changed — the name has. Here's the story.
Why the Rename
When it came time to build a dedicated product site for the framework, I went to register fabr.ai. It was taken. Not parked — someone actually had it. And I really wanted a .ai domain. It's an AI agent framework — having the domain match the space isn't vanity, it's clarity.
But here's the honest part: I was never really happy with "Fabr" by itself. The acronym is great — Fabricate Agent Behavior and Reasoning — but as a standalone name it always felt incomplete. Too short, too ambiguous. People would ask how to pronounce it. It just never clicked.
The domain issue was the push I needed to fix a naming problem I'd been ignoring.
Why FabrCore
FabrCore does what the old name didn't:
- "Core" signals infrastructure. This is the foundational layer — the engine that OpenCaddis and future projects build on.
- It's immediately pronounceable. Fabric-Core. No confusion.
- The domain was available. fabrcore.ai — clean and right.
Is it the perfect name? Maybe not. But it fits well, and that's a significant upgrade from where we were.
What This Means for OpenCaddis
Nothing changes for OpenCaddis users. The framework underneath is identical — same FabrAgentProxy pattern, same agent lifecycle, same tool resolution, same everything. The GitHub repo is now at github.com/vulcan365/FabrCore.
What you do get is a proper home for the framework: fabrcore.ai — with documentation of the architecture, the FabrAgentProxy pattern, and quick start guides for building your own agent systems on the same infrastructure that powers OpenCaddis.
Builder of OpenCaddis and FabrCore.