Notion agents can rewrite your page. Make them suggest edits instead.

Aug 28 shipped line-level proposals you approve one by one. The phrase is “suggest edits.” Direct rewrite is still the default if you don’t ask.

I asked an agent to clean up a page. It cleaned up the page. The draft I had open was gone. The new version was fine. It just wasn’t mine anymore.

That’s the part that makes people nervous about agents on docs they already care about. Not that the writing is bad. That you don’t get a beat between “here’s what I’d change” and “it’s already changed.”

On 28 August 2026 Notion shipped a way out of that. Agents can propose changes instead of making them directly. You ask for suggestions. You walk the list. You approve each one.

What actually shipped on 28 August

Notion’s release title is blunt: “Ask your agent to suggest edits.”

Their words, not mine: your agents can now propose changes instead of making them directly. Ask your agent to suggest edits, then move top to bottom to approve each one. They call out line-level work, like a grammar pass.

The starter phrase is short. Ask the agent to “suggest edits.”

I’m not going to invent a settings toggle Notion didn’t document. The control is the ask. If you don’t say it, you’re back in the rewrite habit.

This is not the old human Suggest edits mode

Notion has had a separate Suggest edits path for people with comment access for a while. That one lives under the page ••• menu. You flip into Suggesting, type or delete, and the owner accepts or rejects from the side panel. Help still describes it that way.

The 28 August release is about agents. Same idea (propose, don’t overwrite), different door. You talk to the agent. You don’t have to put yourself in Suggesting mode first just to get an AI pass that doesn’t eat the draft.

If you’ve been avoiding agents on finished pages because they write in place, this is the release that was meant for you.

How I actually use it

I open the page I already trust. I tell the agent what kind of pass I want, and I include the words “suggest edits.”

Examples that fit the release:

• Suggest edits for grammar and clarity. Don’t change meaning.
• Suggest edits to shorten this. Keep the product names.
• Suggest edits on the intro only. Leave the steps alone.

Then I go top to bottom. Approve what I meant. Reject what I didn’t. That’s the whole workflow Notion described.

I still use a direct rewrite when the page is a scratch pad, a first draft, or something I’d throw away if the agent got it wrong. Suggest edits is for the pages you’d be mad to lose.

When suggest edits is the better ask

Use it when the page already has a voice. Meeting notes you’re turning into a sendable recap. A help doc with exact product names. A brief a client already saw once.

Skip it when you’re brainstorming into an empty page, when you want a full rewrite, or when you’re fine with the agent owning the next version. Direct edit is faster there. Suggest edits is slower on purpose.

Notion’s own example is a grammar pass. That’s the signal. Line-level. Reviewable. Not “rebuild this doc from the prompt.”

One quiet thing I built

I built a tool called Monoboard. Three steps: connect Notion, describe the dashboard, paste the share link as an Embed. It sits on the Notion databases you already have and embeds a live dashboard back into Notion.

[embed]Living Dashboards for Notion A shared visibility and reporting layer for Notion. It transforms existing Notion databases into simple, persistent…monoboard.app

Which page on your team still gets a full agent rewrite because nobody typed “suggest edits?