Пропустить навигацию
Introducing Plan Mode.
0:00 / 0:53

Introducing Plan Mode.

Notion

@NotionHQ532 тыс. подписчиков

Открыть в X
691 отметка «Нравится»СкачатьОригинальный пост

69 996 просмотров

Introducing Plan Mode. Because a prompt without a plan is just a wish. In plan mode, your agent shows its work in a read-only sandbox before touching anything. Just plan → approve → execute.

28 комментариев

Комментарии из оригинального поста в X (Twitter)

  • Фото профиля Luca Capone | Building with AI

    @LucaCaponeX

    Had this with Claude Code for a while. The moment an agent shows you its plan before touching your code... you never go back. Glad to see Notion shipping it too.

    3 отметки «Нравится»

  • Фото профиля CodedDEVS

    @codeddevs

    W Notion 🤍🖤!!

    2 отметки «Нравится»

  • Фото профиля RaceJohnson

    @RaceJohnson

    The real ones saw this in app days ago 🫡

    2 отметки «Нравится»

  • Фото профиля HiddenHustles

    @UneekandCustom

    Awesome

    1 отметка «Нравится»

  • Фото профиля Notion

    @NotionHQ

    🫡

    1 отметка «Нравится»

  • Фото профиля moheb

    @mohebanwari

    why i’ve deleted my notion account. yall pivoted from what made yall great to desperately wanting to be like openAi or Anthropic. we dont need these agents to be shoved down our throats. an MCP would’ve sufficed.

    1 отметка «Нравится»

  • Фото профиля Notion Playground

    @NotionPlay

    Notion Playground in full swing

    1 отметка «Нравится»

  • Фото профиля Nitish Mutha ⚡️

    @nitishmutha

    plan before execute is the right paradigm. especially in high-stakes workflows, agents need a review layer before touching anything. this is how trust gets built gradually. legal work is the ultimate test case for exactly this pattern at @GenieAI

    1 отметка «Нравится»

  • Фото профиля Skaltek

    @SKalTekk

    The trust win here is not just planning. It is making the no-edit state explicit. Teams adopt agent workflows faster when review and approval boundaries are obvious before the first change, not after a surprise diff.

    1 отметка «Нравится»

  • Фото профиля Emon Datta

    @emonuxui

    Adding a planning step can introduce friction. For simple tasks, it may slow things down more than it helps, so the real value shows up in complex, high-stakes workflows.

  • Фото профиля All Things Heroik

    @getheroik

    You guys are giving FedEx a run for its money - shipping this much everyday.

  • Фото профиля Tahi

    @TahiGichigi

    Up until now I've been saying "I've got this idea about X, ask me clarifying questions to help me flesh it out." Looking forward to using this. A lot.

  • Фото профиля Igor Gaelzer

    @igorgaelzer

    Super cool. Question: How is it different from just asking it to write a plan on a new page before touching anything?

  • Фото профиля OneManSaas

    @OneManSaas

    This is exactly what we need for automation tools. I've built AI workflows that would randomly change things without warning - terrifying when you have real business operations running. The sandbox preview solves the "did my agent just break everything?" anxiety.

  • Фото профиля Mohammad Saed

    @Moham_Saed

    A prompt without a plan is just a wish" Spot on. This "Plan -> Approve -> Execute" flow is exactly the "Human-in-the-loop" architecture we need for safe Agentic AI. I was just discussing this shift today: we are officially transitioning from "Prompt Engineers" to "Workflow Reviewers." Brilliant update to see this natively integrated into Notion's sandbox!

  • Фото профиля Saladin

    @SaladinSeahorse

    This is what I have been looking for. I want to plan my schedule throughout the weeks and the flexibility to change each task.

  • Фото профиля Agentic Adam - DeployAIWorkers.com

    @AdamAutomates

    For real though… all these updates lately are really making a strong case for Notion. Glad I finally updated my payment method… 😅😏

  • Фото профиля AI with Remy | Learn AI

    @aiwithremy

    make a cli

  • Фото профиля Creao AI

    @CreaoAI

    Sandboxed execution is the right foundation either way. Plan-then-approve for high-stakes decisions. Autonomous scheduled runs for recurring work. The pattern isn't one or the other. Best agents do both depending on the task.

  • Фото профиля Coffee fans

    @aias_0

    Read-only previews stop agents from breaking prod. Treat it like a dry run, not a UI toggle.