DeployLog manual

07AI summaries

Paste rough notes, get a draft. Nothing is saved until you save the entry yourself.

What Generate with AI produces

An entry is one dated item in a project's changelog. A summary is the title, entry type and body the model writes from your raw material, for end users rather than developers. Open the panel in the entry editor with Generate with AI. Chapter 02 covers the entry editor.

Two input modes:

Mode What it sends
Raw release notes your text as one block
Commit messages (one per line) one item per line

Both modes go to the same model. Choosing commit messages only splits your text into one item per line.

The version, the release number you are shipping, is optional in the panel and is only a hint for the title. The model is asked to consider working it into the title. It does not fill the entry's own version field.

Press Generate with an empty box and the panel answers Paste your raw release notes or commit messages. Nothing is sent.

One press of Generate is one generation: a single request to the model that returns one summary. When the result arrives, all three fields are replaced at once and the panel closes. There is no confirmation step inside the panel. The hint under the button says it: "Overwrites title, type, and body."

Opening the panel copies the entry's current body into the box when the box is empty. That is a convenience. Replace it freely.

Generating does not save the entry. What is stored is a usage record: which model ran, how many tokens it used, and the first 200 characters of the generated title.

Entry type

The model picks exactly one label:

  • feature: primarily introduces new capabilities
  • improvement: primarily improves or refines existing behavior
  • fix: primarily bug fixes
  • breaking: contains behavior changes users must act on
  • announcement: a release note with no product changes

The allowance

An allowance is the number of completed summaries an organization may receive in one calendar month. On Free it is 5. Pro has no cap. Chapter 12 covers plans and billing.

  • The allowance belongs to your organization, not to a project or a person. Every project shares the same five.
  • A summary requested with an API key counts against the same number as one requested from the dashboard.
  • The month is the calendar month in UTC. It resets on the first of the month, not thirty days after first use.
  • A generation that fails does not count. Only a summary you actually received counts.

At five used, Generate returns a refusal instead of a summary: "Free tier is limited to 5 AI summaries per month. Upgrade to Pro for unlimited summaries." The counter refreshes and the editor fields are left alone.

Pro removes the cap. It does not change what the feature does, and each generation is still recorded.

The counter

Next to the button you get a line like 2/5 AI summaries used this month · 3 left. On Pro it reads "Unlimited AI summaries (Pro)". It refreshes after each generation and after a refusal. It is informational: if it cannot load, no counter shows and generation still works.

What it sees

Only four things:

  • the text you paste
  • the optional version
  • your project's name
  • the title, type and version of your five most recent published entries

Draft entries are never used as context. The feature does not read your repository, your git history, or GitHub.

Instructions, not limits

The model is told to keep the body under 200 words, to group related changes under the headings New, Improved and Fixed, and to leave out commit hashes, file paths, branch names and ticket IDs. Those are instructions to the model; the product enforces none of them, so nothing happens when one is crossed. Nothing counts the words: a body over 200 words is placed into the editor unchanged, with no warning and no retry. Read the draft before you save it.

Nothing to configure

One model handles every summary: Claude Haiku, from Anthropic. No key to bring, no prompt to edit, no per-project setting.

What it is not for

The model writes for the product's end users, not for developers. It is not a code reviewer, not a release manager, and not a substitute for reading what it wrote. It rewrites material you already have into one entry.