Document editor

Every document in Forginate can be edited by conversation. The vibe editor is a chat panel attached to the document you're viewing: tell it what you want changed, and it proposes an edit you can accept or discard. This page covers how it works and how to get the best results from it.

Opening the vibe editor

Open any document from the document tree and open its chat panel — labeled "Vibe with <document title>". The panel keeps a per-document chat history, so you can pick up an editing conversation where you left off.

How an edit happens

1. You describe the change in plain language: "tighten the executive summary to one paragraph", "add a section on rate limiting after the API section", "replace every mention of SQLite with Postgres and explain why".
2. The editor responds, streaming its reply live. When it decides an edit is warranted, it proposes one as a patch against the current document.
3. The patch is pending — the document itself hasn't changed yet. You see exactly what would be modified.
4. You accept or discard. Accepting applies the patch and creates a new document version; discarding throws it away with no trace in the document.

Nothing changes without you

The vibe editor can only propose. Until you accept a pending patch, the document is untouched, and the version history only ever contains edits you accepted. Approval state is separate too — an accepted edit creates a new version, which still needs approval like any other.

What it's good at

• Focused revisions — rewording, restructuring, expanding, or trimming a section.
• Applying review feedback — paste a reviewer's notes and ask it to address them.
• Consistency passes — "make the terminology match the architecture doc: we call it 'workspace', not 'project folder'".
• Explaining the document — you can just ask questions about the content without requesting an edit; it won't propose a patch unless a change is actually called for.

What to keep in mind

• One document at a time. The panel edits the document it's attached to. For plan-wide changes, work through the affected documents individually or use Request changes / Regenerate at the pipeline level.
• Be concrete. "Make it better" gives the editor nothing to aim at. Point at sections, name the problem, state the desired outcome.
• Review the patch, not just the chat. The proposal you accept is the diff, so read it — especially for sweeping instructions like "rewrite this whole document".

Direct editing and regeneration

The vibe editor sits alongside two other ways to change a document:

• Direct editing — open the document and edit it yourself. Best when you know exactly what to type.
• Regenerate — re-run the pipeline step that produced the document for a from-scratch new version. Best when the document misses the point entirely.

All three produce versions in the same history, so you can mix them freely.

Suggested phrasings

Some prompts that work well in practice:

• "Address this feedback: <paste reviewer notes>. Keep everything else unchanged."
• "The scope changed — we're dropping the mobile app for v1. Update this document accordingly and note the deferral."
• "Add a 'Non-goals' section after the overview listing what this product deliberately won't do."
• "Read this document and tell me what's underspecified" — a question, not an edit; useful before approving.

Which model powers it

The vibe editor runs on an Anthropic model. If your organization brings its own keys, it uses your org's default Anthropic provider — so make sure one is configured and marked default under Settings → Providers. Otherwise it uses the platform's configured chat model.

Costs

Vibe-editor conversations are model calls and are metered like other usage — platform-billed or passed through to your own key, depending on your provider setup. See Billing.

Who can use it

Chatting with the vibe editor and accepting edits requires editor (power user) access or better on the project. Viewers can read documents and history but can't change anything. See Teams and roles.