Release Notes

What does Release Notes do?

Turns the merged pull requests and commits between two refs into user-facing release notes, accounting for every merged pull request, and saves them as a release_notes doc.

What it declines

A task like one of these is declined with a reason, and a declined run is free:

• Tagging, publishing a release on the host, or changing the repository.
• Describing a change no pull request or commit in the range makes.
• Reviewing the changes (PR Reviewer does that).
• A changelog for a range it cannot read: every note comes from the host's own record.

What does a real run of Release Notes look like?

The input, the result (shortened where it is long), how long it took, what it cost and where it ran. Live runs used public or demo material only; a run marked as from the eval suite is not a live run.

{
  "repo": "contextstream/mcp-server",
  "base": "v1.0.32",
  "head": "v1.0.34",
  "dry_run": true
}

# contextstream/mcp-server v1.0.34 release notes

Exhaustive search now scans the indexed commit literally, so every file and line containing the text is returned with true line numbers, and a row without the text is never marked high. Search hits from files kept for exact search only, such as minified or generated bundles, now say so, and index status counts those files by reason.

## Added

- MCP 1.0.34 shows which files are exact-search only ([#221](https://github.com/contextstream/mcp-server/pull/221))

## Fixed

- Exhaustive is `git grep -F -n` on the indexed commit; a row without the text is never "high" ([#216](https://github.com/contextstream/mcp-server/pull/216))

---

Changes from `v1.0.32` to `v1.0.34`: 3 merged pull requests and 0 other commits.

What does Release Notes cost?

Release Notes costs 900 ContextStream credits a run, charged only when the run succeeds; a declined, failed, cancelled or timed-out run costs nothing. Credits come with every plan: Starter is free with 10,000 a month (11 runs of Release Notes, if spent on nothing else), and Pro is $19 a month with 25,000.

Which tools does Release Notes work with?

Claude Code, Codex, Cursor and other MCP clients: ContextStream's MCP gives them a slipstream tool that finds, runs and follows Release Notes. It also runs from a terminal or an agent's shell with ss run release-notes, and from the ContextStream web app.

• Claude Code, Codex, Cursor and other MCP clients: connect ContextStream's MCP once (setup for each editor), then ask your agent to hand the job to Release Notes.
• A terminal or an agent's shell: ss run release-notes, installed with ContextStream's command line.
• The web app: the workspace's specialist library, where each run shows its price before it starts.

What access does Release Notes need?

Release Notes gets a short-lived token for one workspace, limited to 3 scopes: Reads repos, Writes one doc and Models via ContextStream. It works in one project, and only for that run.

Model agent. A program on ContextStream's model proxy, with a short-lived token that acts for you in one workspace. It is stopped after 4 min.

How do I turn Release Notes on?

An owner or admin of your ContextStream workspace turns Release Notes on in the specialist library of the web app. Specialist agents are opening workspace by workspace; if yours is not open yet, the library says so.

1. Sign in to ContextStream: the button below opens the specialist library on Release Notes.
2. An owner or admin switches Release Notes on for the workspace.
3. Pick the project it works in, and run it from the library, from your coding agent or with ss run.

How do I call Release Notes from Claude Code or Codex?

Ask your coding agent to hand the job to Release Notes, or call it yourself: ss run release-notes in a terminal, or slipstream(action="run", agent="release-notes", input={...}) over MCP. A priced run starts only once its price is accepted.

Connect ContextStream's MCP (it also writes each editor's connection):

curl -fsSL https://contextstream.io/scripts/mcp.sh | bash

Notes for v1.3.0, saved as your own release_notes doc. Over MCP:

slipstream(action="run", agent="release-notes", input={"repo":"acme/api","base":"v1.2.0","head":"v1.3.0"}, accepted_price_credits=900)

In a terminal (curl -fsSL https://contextstream.io/cs/install.sh | sh installs ss):

ss run release-notes repo=acme/api base=v1.2.0 head=v1.3.0

Over MCP, a call without accepted_price_credits returns the quote first; ss asks on a terminal, and scripts pass --yes.

Input

Related agents

Every Slipstream agent