So this is what I built today. This is the foundational WOVEN x16 headless chat service build. Feels like running a marathon. About 21 hours this time. These actually get to be really easy the more you do them. The x7 build took me weeks of experimenting and research to get done. x11 build took me three months. x13 took me a week. x15 took two days.
I keep remarking about how much faster I'm moving these days. But I think it's really just how well I understand the problem. The x16 build focuses a little bit differently than the last two versions of the system.
Tool discovery and composability
I couldn't ignore MCP any longer. So I read the spec from top to bottom, and integrated it. I now understand why nobody's building MCP clients. It's complicated! But, while I was there, I also integrated FastAPI as a tooling standard. So, theoretically, if you're running both or either on your system, it should work. Just discover whatever tooling you have, and slip it right in, make any connections that need to be made, juggle the thing, and you're up and running.
The preliminary ecosystem for this thing is going to have thousands of compatible tools an agent can use with zero config on the client side.
Even the core of the thing, can be pieced out and used on any compatible client. Don't like my chat service, but love my file manager (you will love my file manager)?
No problem.
Just use it on claude code or whatever. Love everything, but don't want the client? No problem, it's headless, roll your own til your little heart's content.
What you're looking at is a state of the art agentic chat system that will support long running processes across as many agents as you like, with a flexible looping process that has no pre-defined boundaries.
It does asynchronous multi-agent concurrency across multiple services, using multiple models if you want it to.
And I'll probably be finished with it sometime next week.
It'll be totally free, totally open source and on GitHub.
Think ComfyUI, but for agents.
I'll keep yall posted.