Writer / Researcher

Submergent for Writers and Researchers

Documentation rots quietly. The page that was correct six months ago now describes a flag that no longer exists, and the only way to find out is to read the code sitting next to it. Submergent opens any folder on your Mac — a docs directory, a pile of markdown, a repository — reads what is actually there, and edits in place.

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

Write documentation from the code, not from memory

Writing docs for something you did not build means interviewing whoever did, then writing it down before you forget the parts you did not understand.

Ask for it like this› Write clear documentation for the sync module: what it does, how to use it, and what it depends on.

A draft grounded in the actual implementation rather than a description of it. Ask it to show you the code behind any claim you doubt.

Find the docs that quietly went wrong

Nobody knows which pages are stale, because knowing would mean re-reading all of them against the current code.

Ask for it like this› Read everything in docs/ and flag anything that no longer matches the code. Quote the line and say what is now true.

A list of specific contradictions with the current line and the correction, which is a work queue rather than a vague worry.

Improve the writing across a whole folder

Consistency work is mechanical and endless: the same term spelled three ways, headings in four different styles, sentences that were fine but not clear.

Ask for it like this› Improve the clarity and flow of everything in docs/guides/. Keep the meaning identical and keep my voice.

Edits applied file by file. Read them in place — it is a folder on your Mac, so any tool you already use for reviewing writing still works.

Research with the page open beside you

Research means reading sources and writing at the same time, in two places, copying between them.

Ask for it like this› Open the spec at this URL, then write me a summary of the parts that affect our implementation.

The Browser tab in the side panel sits next to the conversation, so the source and the draft are in one window.

Draft the changelog nobody wants to write

Changelogs are written under deadline from a commit log by whoever is least busy, which is why they read the way they do.

Ask for it like this› Draft a changelog entry for the recent changes. Group by what it means for the reader, not by component.

A draft organized by consequence rather than by module, which is the transformation that actually takes the time.

Work in a plain folder of markdown

Most writing does not live in a repository. It lives in a folder, and tools that assume git are useless for it.

Ask for it like this› Read this folder and tell me what is in it, then help me reorganize it.

A workspace is any folder — git is not required. Everything here works the same whether the folder is a repository or not.

Where it stops

What Submergent will not do.

Submergent edits the files in the folder you opened. It does not publish, sync to a CMS, push to a docs site, or reach anything outside that folder — apart from whatever page you open in the Browser tab. It edits in place, so there is no version history unless the folder has one.

No publishing, no CMS sync, no cloud storage integration
It edits files in place — work in a git repository or on a copy if you want an undo
It cannot reach files outside the workspace, other than references you add explicitly
Skills you already wrote for Claude or Codex show up in Submergent and work in any prompt

Questions writers ask

Does it work on a folder that is not a code project?

Yes. A workspace is any folder on your Mac — a docs directory, a research folder, notes. Git is not required.

Will it rewrite things I did not ask it to touch?

Ask it not to, and check. Plan Mode gets you a written plan before any file changes, and each session has a permission setting that decides whether it can edit at all or has to ask first.

How do I get my writing back out?

It never left. The files are on your Mac in the folder you opened, in whatever format they were already in.

Can I reuse the prompts I have already written?

Skills discovered from your Claude or Codex skill folders appear in Submergent and can be referenced in any prompt with a $ token, whichever provider the session is using.

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.ProductFind out what shipped, what is half-built, and what a request would touch.

Ready when you are.

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