Why Millstone lets you bring your own AI

People ask why there is no assistant built into Millstone. The honest answer is that there might be one day. For now, the reasons for leaving it out are better than the reasons for putting one in.

Credits are where it goes wrong

Most built-in AI runs on credits. They look cheap until you try to do anything interesting or useful with them, and then they burn. There is also a middleman: the product buys the model from somebody else and sells it on to you, and a lot of products charge a premium on those credits that has nothing to do with what the credits actually cost.

I did not want a studio to open Millstone and start doing sums before asking it a question. So there is no agent tier and nothing metered. Every plan includes it.

Use the AI you already trust

Instead, Millstone speaks MCP, the open standard Claude, ChatGPT and the rest use to work inside other software. You connect the assistant you already use, sign in, and it works in your studio as you.

That matters for a few reasons:

• You pick the tool. If you trust Claude, use Claude. If your team lives in ChatGPT, use that. You are not asked to trust a new AI just because it came bundled.
• You pay the people you already pay. Your assistant's plan is your assistant's plan. Millstone does not sit in the middle marking it up.
• It is yours to change. If you want to run a local model one day, the door is open, rather than being locked to whatever we chose.

It is about ownership. The studio's system should work the way the studio wants, with the tools it already has.

What it looks like at Farside

I use it all the time. There are a million examples, but a normal one goes like this.

A new lead comes in. I tell Claude about them, it adds them to Millstone, looks them up and fills in their details, then sets up the project and the pipeline around it. From there it drafts the proposal, sets up the project plan and gets the project moving. The whole thing, end to end, from a conversation.

The other half is just talking to it. I brain dump. I use voice. I ask:

It can look back too. What did we say in that meeting? Go through every meeting we have had with this client: where did we go wrong? Reflect on this project: what did we learn? The answers come from the studio's own records, not a summary of them.

When it gets something wrong

It does sometimes. When it does, we fix the tool it was using, so it does not happen again, and the tools get more specific to how studios actually work every time.

If you do not use AI at all

I get that there are trust issues around AI. Bringing your own is our answer to that, rather than asking you to trust one more.

But honestly, it is a godsend. The tedious admin that eats whole days, done by talking to a system that actually works the way a studio does, tailored to yours. It is like having a full-time admin assistant, which could cost you twenty or thirty thousand a year, and they would not know your studio the way Millstone does. For me it is a no-brainer.