The agent that stays home.

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.

macOS 14+ · Apple Silicon · release news only, unsubscribe anytime
submergent
submergent / docs● working
Summarize what changed this week in plain language, then draft release notes.
Reply to submergent…
Claude Sonnet 4.5Plan first

Bring your own account · seven supported providers →

ClaudeCodexCopilotCursoropencodeOllamaPiClaudeCodexCopilotCursoropencodeOllamaPi
What you keep

Keep the tools you love. All in one place.

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.

Draft the release notes docsAudit spacing in Settings webFix the sync retry loop api

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.

Refactor auth ● agentToken audit ● chatFix flaky test ● full

Run several tasks at once

Sessions run concurrently across workspaces. Start a second one while the first is still thinking — you stay the bottleneck, not the agent.

Proposed plan Plan Mode1 · Add the schema2 · Wire the endpoint3 · Backfill tests
AcceptAccept with modelDecline

Get a plan before it acts

Turn on Plan Mode and the agent proposes a plan instead of making changes. Accept it, accept it with a different model, or decline.

Context window 62% · healthyCompacted 3 older turns · kept task, diffs, decisions

Stays sharp deep into a task

Long sessions compact automatically — Submergent keeps the decisions and drops the noise, so a long task doesn't hit a context-window cliff.

Continuous context

Change the model. Keep the thread.

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.

Live · same task, multiple providers
Plan the signup feature — what's the smallest safe change?
Claude Plan

Three steps: schema, endpoint, form hook. Start with the schema — it's the only migration.

⇄ switched to Codex · context carried over
Good plan. Build it.
Codex Build

Scaffolded /api/signup with validation. 12 tests passing.

⇄ switched to Ollama · context carried over
Tests look good — wrap it up.
Ollama Ship

Changelog drafted and saved to docs/changelog.md.

Plan → Build → Ship across models — one thread, context intact
Use cases

Same app. Different job.

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.

EngineerRefactors, flaky tests, and the coverage you inherited — with the diff to check.Read more →DesignerClose the gap between the design and what is actually on screen.Read more →ProductFind out what shipped, what is half-built, and what a request would touch.Read more →Writer / ResearcherDocumentation that matches the code, in a folder that does not need git.Read more →
Developer Mode

One switch for the machinery.

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.

Verbose tool eventsGit branch pickerEnvironment pickerReview tabFiles tabTerminalDeveloper settings
submergent
submergent / docs● working
Does the setup guide still match how onboarding actually works?
Reply to submergent…
Claude Sonnet 4.5
Where it runs

Three places the agent can do its work.

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.

01default

Local

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.

Nothing to set up
02optional · git

Worktree

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.

A git repository
03optional · docker or podman

Container

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.

Safe with real work

Private enough to point at your real work.

01

Local by default

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.

02

Your account, direct to the provider

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.

03

Diagnostics off unless you turn them on

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.

Ready when you are.

Submergent runs on your Mac, in folders you choose, against a provider account you already have.

Get notified

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.