Claritty Studio
A free desktop app for AI automations: the ones that run on a schedule, react to a webhook, hold credentials, and have to be debugged six weeks after you wrote them. You describe what you want, the coding agent you already use writes it, and it runs on your machine with your own keys.
What runs where
An automation is a plain git repo with an intelligence.yaml manifest and a little Python. Studio runs a local control plane on 127.0.0.1 that serves it everything it needs: model calls routed to your provider key, credentials from your OS keychain, run checkpoints, traces. The automation itself is a portable artifact, so the same folder runs under docker compose on a server, or on the hosted platform, unmodified.
Local first, stated plainly
- No account, and no sign-in. There is nothing to register for. Nothing on this page requires one later either.
- No telemetry, and no phoning home. Studio talks to exactly two kinds of remote host: the model provider whose key you configured, and the third-party APIs your own automation calls. Nothing else. Links a person clicks live in one constants file that is not allowed to fetch, and CI fails if it grows one.
- Your keys stay yours. Credentials go to the OS keyring and are brokered: the automation process gets a local, revocable token and never sees a key. A compromised dependency yields no credential.
- Your own OAuth apps. Where a service needs one, for Gmail, Jira or WhatsApp, you create it. There is no Claritty client id to sign into, which is the point: your automations talk to your accounts.
- MIT, and it is the whole product. Build, run, schedule, connect and debug all work locally, for free, with 13 services you can connect. It is not a trial with steps removed.
What it is not
It is not a coding-agent harness. Those are development scratchpads, good at running agents side by side and silent about 9am on Tuesday. Studio is the other half: the schedule, the webhook ingress, the credential vault, and a run timeline with the tokens and the cost on it.
It is also not a hosted service with a local mode. Closing the app stops the work rather than moving it somewhere you cannot see, which is a real limit and worth knowing before you arm a 6am schedule. That one is covered on its own page.