It works in a folder you choose
Register a workspace — any folder on your Mac. The agent reads and writes inside it, and you can reference files from other workspaces read-only.
Submergent is a desktop app where you and an AI agent work on the real files on your Mac — your folders, your provider account, your machine. Turn on Developer Mode when you want the machinery.
Bring your own account · seven supported providers →
Claude Code, Codex, Copilot, Cursor, OpenCode, Pi, Ollama — seven separate tools, each with its own way in. Submergent gives them one home: connect the accounts you already have, then point the conversation at a folder on your Mac and work there.
Register a workspace — any folder on your Mac. The agent reads and writes inside it, and you can reference files from other workspaces read-only.
Sessions run concurrently across workspaces. Start a second one while the first is still thinking — you stay the bottleneck, not the agent.
1 · Add the schema2 · Wire the endpoint3 · Backfill testsTurn on Plan Mode and the agent proposes a plan instead of making changes. Accept it, accept it with a different model, or decline.
Long sessions compact automatically — Submergent keeps the decisions and drops the noise, so a long task doesn't hit a context-window cliff.
Pick the model per task from the provider accounts you already have. Change provider or model in the middle of a session and the conversation goes with you — you never re-explain the task to start over.
Three steps: schema, endpoint, form hook. Start with the schema — it's the only migration.
Scaffolded /api/signup with validation. 12 tests passing.
Changelog drafted and saved to docs/changelog.md.
Submergent asks which one you are the first time you open it, then hides the machinery you do not need. You can turn it back on whenever you want.
Submergent asks what you do when you first open it, and shows the developer surfaces only if you need them. The switch lives in Settings and it gates chrome — it never changes how a session behaves.
Pick one before a session starts. Two of them are optional, and the differences between them are worth knowing before you point an agent at something you care about.
The agent works directly in the folder you registered. Nothing is copied and nothing is branched — changes land in your working tree, where you can see them with the tools you already use.
Chosen before a session’s first message. Submergent creates a managed git worktree and branch from a base branch you pick, so the work stays off your current checkout. Deleting the session keeps the worktree and branch — Submergent tells you where they are.
Chosen before a session’s first message. The agent and its commands run inside a container that mounts your workspace read and write. It is an execution choice, not a security boundary: the container can change the files in your workspace.
Sessions, files, and history live on your Mac, in application data you can inspect and delete. Submergent runs against your filesystem — your work is not uploaded to us, and an Submergent account is for licensing the app, not for storing what you do in it.
What you send goes straight from your Mac to the provider you picked, under that provider's terms. Submergent does not proxy it and does not keep a copy.
Crash and error reporting is disabled by default. Turn it on and it sends operational fields only — never prompts, file contents, paths, or terminal output.
Submergent runs on your Mac, in folders you choose, against a provider account you already have.
Submergent for Mac is not out yet. Leave your email and we will tell you when it ships.
Release news only. Every email has an unsubscribe link.