How is Vantage different from ChatGPT or Claude?

ChatGPT and Claude write you a document. Vantage keeps the document, prototype, tickets and roadmap connected to the feedback and decisions behind them, and tells you when one of them changes. You can also bring your Vantage context into Claude or ChatGPT, so you don’t have to choose.

Do I have to move off Notion or Linear?

No. Keep the tools you use and connect them to Vantage. Tickets push to Linear with two-way sync, and you approve every change that comes back.

What can I do in the first ten minutes?

Paste customer feedback or describe a problem, and get a PRD with every requirement linked to its source. You can try the demo on this page without signing up. Connect your tools whenever you’re ready.

I own several projects. What does Vantage do across them?

It briefs you every morning on what needs your call, catches specs that contradict each other, and flags anything that went stale after a decision changed. It works for a single project and earns its keep at two or more.

What if the AI gets something wrong?

Nothing updates silently. Every requirement cites the quote, call or metric behind it, and every change arrives as a diff you accept or reject before it touches your docs, tickets or Linear.

Can I use Vantage from Claude or ChatGPT?

Yes. Connect Vantage’s MCP server to Claude, add the GPT Action in ChatGPT, or use an API key. Then ask about your projects, search your specs, or create tickets from wherever you work.

Start on your own for free. When teammates join, they work from the same context, with admin, editor and viewer roles and private drafts that stay invite-only until you publish.

What does fair use mean on the unlimited features?

Unlimited features are meant for real day-to-day work by one person: up to 50 questions a day on Pro and Business, and on Business up to 10 PRDs, journeys or ticket batches a day. Very few people get close. If your team regularly needs more, talk to us.

Your data is encrypted in transit, and we never train on it. The AI providers we use are contractually barred from training on it too. You can disconnect any integration or delete your account at any time. We’re pursuing SOC 2 Type II.

How much does it cost?

Vantage is free to start with 300 credits and no credit card. Projects are unlimited on every plan, and AI work like generating a PRD or a ticket batch uses credits. Pro is $19 per seat a month billed annually ($25 monthly) with 1,500 credits a month, unlimited questions and prototypes. Business adds a shared team workspace and 4,000 credits per seat a month.

Can generated release notes remove the need for editorial review?

No. They summarize repository changes. Review omitted work, migration instructions and user-facing implications before publishing.

Can excluded labels hide user-visible changes?

An excluded label can hide a change that users need to know about. Inspect the actual range rather than assuming the label taxonomy is perfect.

How should I handle a pull request with several category labels?

Review the category order and inspect its placement in draft notes. Use a clear labeling convention so the intended reader-facing category does not depend on accidental overlap.

How-To2026-10-302 min read

Configure GitHub Release Notes Categories

Configure generated release-note categories and exclusions in the repository release configuration. Generated notes summarize merged pull requests; editorial review still determines whether the release explanation is useful and complete.

Step-by-step guide

Check access and scope

You need write access and maintained pull-request labels. Review the current configuration format in GitHub documentation before committing changes.

Audit pull-request labels

Review labels on representative merged pull requests.

Configure release YAML

Create .github/release.yml with the following minimal configuration. Replace bug, enhancement and ignore-for-release with your actual pull-request labels; an excluded label removes the pull request from generated notes.

changelog:
  exclude:
    labels:
      - ignore-for-release
  categories:
    - title: Fixes
      labels:
        - bug
    - title: Improvements
      labels:
        - enhancement
    - title: Other changes
      labels:
        - "*"

Worked example: Group fixes and improvements separately, and exclude internal maintenance only when that omission will not hide a user-visible change. Explain migration requirements outside the generated pull-request list.

Include uncategorized changes

Keep the quoted "*" catch-all last so pull requests that match no earlier category appear under Other changes. Review that category for missing labels and user-visible changes.

Generate draft notes

Open Releases > Draft a new release, choose the intended tag and explicitly select the Previous tag. Click Generate release notes and save the draft while reviewing categories and omissions.

Review omissions and context

Review omitted work and add reader-facing context manually.

Verify the result

The draft notes include all intended changes and no unsupported promise of automatic completeness.

Common mistakes

Check the handoff edge case

A missing catch-all category can leave unexpected changes unexamined. Inspect uncategorized work during release preparation.

Sources and verification

Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.