About Semantix Studio
Why Semantix Studio exists — and the conflict of interest it was built to avoid.
Semantix Studio is a desktop IDE that indexes your code and lets AI agents do real work in it, including while you're away.
That's the what. This page is the why.
Why it exists#
Almost every AI coding tool makes its money on the tokens you spend. Sometimes it's a subscription with a quota, sometimes it's resale at a markup — either way, the meter belongs to them.
That isn't villainy. It's structure. But structure has consequences, and this one is worth saying out loud: a tool that profits from your token spend can never be trusted to help you reduce it. An entire category of features is closed to them. Anything that shows you exactly what you're paying for. Anything that shrinks what you send. Anything that lets you check whether the model you paid for is still the model you're getting.
Those aren't features they forgot. They're features that cost them money.
Semantix doesn't hold the meter. You bring your own provider key, your bill goes to your provider, and we don't take a cut of your tokens. We have nothing to lose by helping you use fewer.
Everything below follows from that one fact.
Because of that: you can see everything#
We're not selling you tokens, so we have no reason to hide them.
Every turn shows you what it actually did — the model, the tokens in and out, the tool calls it made, the context it was carrying. Per turn and per conversation, in the app, while it happens.
Note
Coming: the same numbers across a date range, and one model held against another. So questions like "is this model worse than it was last month?" or "why did this week cost double?" stop being arguments on the internet and become something you can look up.
This isn't about accusing anyone of anything. It's simpler than that: you shouldn't have to take anyone's word for how a model is performing, or what it cost you. Including ours.
Transparency also means being straight about what leaves your machine:
Stays on your machine: the index, your projects, your files, your settings and your themes. The editor, search and the code graph run entirely on-device — they work with no network at all, and they never upload your code.
Leaves it, only when you run an agent: your prompt, the file context for that request, the results of the tools the agent runs, and your provider key. That goes to our service, which passes it to the model provider you chose.
Important
The editor half and the agent half have different privacy properties, and it would be easy to imply otherwise. Understanding a codebase happens on your machine. Asking a model about it involves a model, and models live somewhere else.
Because of that: we want you to spend less#
Our revenue doesn't move when your bill does. So we can build the things a reseller won't.
Images are downscaled before they're sent. Paste a 4K screenshot and Semantix caps it at 1568px on the long edge and about 1.15 megapixels — roughly 1,500 vision tokens instead of several thousand — before it ever reaches a provider. You don't configure it. It just costs less.
Coming: context compression and smarter context assembly. Sending the model what it needs instead of everything nearby is the single biggest lever on cost, and we're on the right side of it.
Because of that: the work doesn't stop when you do#
A chat window only works while you're sitting in front of it. That's a real ceiling on what AI can do for you, and it has nothing to do with how good the model is.
Semantix has a scheduler. A task can run at 4am, or every hour, or on an event, and be finished when you get back. It can be a shell command, a real headless Claude session in your workspace, or a saved flow of several agents wired together on a canvas.
Important
Every write, delete and shell command goes through a permission gate first. You approve or deny, and denying stops the turn. The agent never edits your project behind your back.
The part that isn't about incentives#
One thing here has nothing to do with business models — it's just the foundation.
Semantix indexes your project first: every symbol, every reference, every call site, and the import graph between files. Tree-sitter parsers, stored in SQLite and Tantivy, on your machine.
That index is what the agents work from. They aren't guessing at your architecture from the file you have open — they can look it up. Who calls this? What breaks if I change it? Which function is this line inside? Those are lookups here, not inferences.
It's also cheaper, for the same reason: an agent that can query structure doesn't need half your repository pasted into its context to find its way around.
Where it is now#
Note
Semantix Studio is early — alpha, honestly, moving toward beta. Interfaces change. It is built and tested on Linux. Where something on this page is marked coming, it means exactly that.
It has been in development for four years, most of that as one person's project. The first public release is close.