Product

Submergent for Product

You need to know what shipped this week, what is half-built, and whether the thing you are about to promise already exists. All three answers are in the codebase, and the people who can read it are the people you are trying not to interrupt. Submergent reads it for you and answers in plain language, with no diffs and no branches in sight.

Coming soonSubmergent 1.0.0 · macOS 14+ · Apple Silicon · get notified when it ships
01

Find out what actually changed this week

Commit logs are written for the person who wrote them. Standup gives you headlines. Neither tells you what a customer would notice.

Ask for it like this› Summarize what changed in this project over the last week, in plain language, and flag anything a customer would notice.

A readable summary grouped by what it means rather than by which file moved, with the changes that carry user-visible consequences called out.

02

Draft the release notes from what really shipped

Release notes written from a ticket list describe what you planned. Release notes written from the code describe what happened, and the two differ more often than anyone admits.

Ask for it like this› Draft friendly release notes for the changes since the last release. Keep it short and skip anything internal.

A draft you edit rather than a blank page, built from the actual changes and not from the roadmap.

03

Understand the architecture without reading code

Every decision you make about scope depends on how the system is put together, and the only explanations that exist are either a whiteboard photo from last year or an engineer’s afternoon.

Ask for it like this› Explain this codebase — its architecture, the main pieces, and how they fit together. Assume I do not read code.

A structured explanation in plain language. Ask follow-up questions in the same conversation; it keeps the context.

04

Check whether the thing already exists

Half of all feature requests are already built, partly built, or built and hidden behind a flag. Finding out costs someone an hour.

Ask for it like this› Does this project already support exporting a session to a file? Show me where it lives, or tell me it does not exist.

A direct answer with the location, or a clear no. Both are useful; the second one is often the more valuable.

05

Size a request before you commit to it

You are asked whether something is small. Saying yes without knowing what it touches is how a two-day change becomes a quarter.

Ask for it like this› Here is a feature request. What parts of the codebase would it touch, and what is the riskiest part of doing it?

An informed read of what the change reaches and where the risk sits. This is not an estimate and should never be quoted as one — it is a starting point for the conversation with whoever will build it.

06

Keep the spec next to the code that broke it

The spec was right when it was written. Then the implementation changed, nobody updated the document, and now the document is actively misleading.

Ask for it like this› Read docs/spec.md against the current code and update it to match what actually happens now. List what you changed and why.

An updated document plus a changelog of the corrections, which is often the most interesting output — every correction is a place the product drifted from the plan.

Where it stops

What Submergent will not do.

Submergent reads the folder you point it at. It does not read your issue tracker, your analytics, your calendar, or your inbox — there are no connectors in 1.0. It can also create and change files in that folder, so open the workspace you actually want it working in.

Questions product people ask

Do I need to install anything technical?

Submergent itself is a normal Mac app. You do need one provider account connected, and for most providers that means their command-line tool is installed and logged in — see the providers page for what each one needs. Ollama runs entirely on your Mac with nothing to connect.

Can I break something?

It changes files in the folder you opened, so treat that folder the way you would treat any working copy. Plan Mode gets you a written plan to accept or decline first, and each session has a permission setting that can block commands entirely. If the folder is a git repository, your team can see and undo anything that changed.

Can it read our Jira or Linear?

No. There are no third-party connectors in 1.0. If a spec or an exported ticket lives in the workspace as a file, it can read that.

Does it need a git repository?

No. A workspace is any folder on your Mac. Git only matters if you choose the Worktree environment, which is a developer feature you are unlikely to need.

Other ways in
EngineerRefactors, flaky tests, and the coverage you inherited — with the diff to check.DesignerClose the gap between the design and what is actually on screen.Writer / ResearcherDocumentation that matches the code, in a folder that does not need git.

Ready when you are.

Coming soonSubmergent 1.0.0 · macOS 14+ · Apple Silicon · get notified when it ships