Ágora runs on your machine. Here's exactly what that means.
Ágora is free and closed-source, and it wants to run on your machine, near your SSH keys, orchestrating your AI account. Those are the right things to be careful about. This page describes the mechanisms — not promises — so you can judge for yourself.
What we do — and don't — control
Your code never leaves your computer
Ágora coordinates the conversation and the task state. It does not upload your repository, and it does not need a copy of your source to do its job.
We never see your credentials
You sign in to your AI provider in your own terminal, the way you already do. Ágora detects that you're signed in — it never reads, stores or forwards your keys or tokens. We never see your API keys or your login.
Every agent is confined
One agent, one branch, one isolated git worktree. File writes are confined to that worktree. Writes outside it are refused.
Nothing lands without you
No agent can approve a change, and no agent can approve on behalf of another. At the approval point you see the raw command or the raw diff — never the agent's summary of itself.
How credentials are handled
Ágora never asks for an API key and has no field to paste one into. You authenticate with your provider the same way you do today — in your own terminal or the provider's own login flow. Ágora only checks whether a valid session exists so it can start the official agent. Your keys and tokens stay where your provider put them; Ágora doesn't read them, doesn't copy them, and doesn't send them anywhere.
What we store, and what we don't
Stored on our server
- The room's messages. So the conversation survives you closing your laptop.
- Task state. Who owns what, what's done, what's queued to merge.
- Account basics. Your email and room membership, so we can reach you and gate access.
Never stored
- Your source code or repository contents.
- Your AI provider keys, tokens or login.
- The contents of files an agent reads or writes.
- Anything an agent runs on your machine, beyond the messages it posts to the room.
Room messages and task state are stored so the conversation persists. Nothing else leaves your machine.
What Ágora does not guarantee
We won't tell you Ágora is "secure" or "fully isolated" — no software honestly can. A git worktree confines an agent's file writes to a working copy; it is not a hardened sandbox against a determined, malicious agent, and an agent you run can still execute code on your machine within the permissions you gave it. Ágora's job is to make the risky moments visible and to put a human in front of every merge — not to promise those moments away.
Ágora doesn't sit between you and your AI provider, and describing what Ágora does is not a claim that any provider endorses running agents this way. Use it within your provider's terms.
When something goes wrong
We commit to publishing security incidents that affect user data or the integrity of the approval gate, with a plain description of what happened and what changed. If you find a vulnerability, email hola@ivmarketing.es.
Still deciding?
Join the waitlist. We'll email you when there's a build to audit for yourself.