Use Generate docs to create new pages from a repository's code rather than waiting for a correction to a page that already exists. This is useful when you want a runbook, an incident playbook, a set of architecture decision records, or a product updates backfill, and nothing suitable exists yet.

Generation uses credits, separate from the subscription that covers daily checks. Each page-set generation run offers one free sample page before you pay to generate the remaining pages. Product-update and architecture-decision history runs require credits and do not offer that sample in the generation screen. See Managing your plan, billing, and credits for how to buy credit packs and check your balance.

Choose a doc type

Open Generate docs from the dashboard and select Start a new generation. The doc types available depend on the audience you're generating for:

Doc type What it produces Available for
Docs & guides Prose corrected and extended as code changes Engineering docs, Help center
On-call runbook Repeatable procedures with prerequisites, steps, and verification Engineering docs
Incident playbook Steps to diagnose a service failure, limit its impact, and verify recovery Engineering docs
Product updates Dated entries added under a page as the repo ships changes Help center
Architecture decisions One record per decision, sourced from pull requests and commits Engineering docs

<aside> ✏ Product updates can only be generated to a Notion destination. If the page's destination is a GitHub docs folder or wiki, product updates is not offered as a doc type.

</aside>

Pick the repo the generation reads from and the destination the output is written to (a Notion page, or a GitHub docs folder or wiki, depending on what you've connected). See Mapping pages to repos for how destinations are set up.

Review the estimate

After you choose a repo, doc type, and destination, Amendary estimates the generation before it starts: how many credits it will cost based on the size of the repo and the scope of the doc type. Review this estimate before committing, since starting the run holds the estimated credits against your balance.

If your team uses its own Anthropic key, the estimate shows model usage billed to your Anthropic account instead, and no credits are held against your balance.

  1. Select Start a new generation.
  2. Choose the repo, doc type, and destination.
  3. Review the estimate shown on screen.
  4. Confirm to start the run.

The generation begins, and its progress appears both on the Generate docs screen and in generation history.

<aside> ✏ A free sample applies to one page in a page-set generation run. It does not provide a free product-updates backfill. Regenerating the outline does not reset a run's sample allowance.

</aside>

Track progress in generation history

Select History from the Generate docs screen to open generation history, which lists every run, finished or still in progress, each with the repo, doc type, and current status. Select a run to open it and pick up where it left off, for example to review a draft outline or the sections generated so far.

Regenerate or delete a run

From generation history, or from an open generation, you can: