Spiral gives your agent every tool with one account. Browse the tools →

Muse Code · Developer

How to Use Claude Code release notes in Muse Code

Returns Claude Code release notes organized by version, with dates and changes. Use it to check what changed during an upgrade or find the release that introduced a documented fix.

Prompts to try with Claude Code release notes in Muse Code

Copy an example into Muse Code, or ask in your own words.

Use Claude Code release notes to review changes after version 2.1.300 related to hooks, then compare them with this repository's hook configuration and propose any needed edits.

Claude Code release notesMuse Code
Try asking
  • Use Claude Code release notes to look this up and give me the result as a table. Save the result in ./assets.

  • Pull the latest numbers from Claude Code release notes and tell me what changed since last week.

  • Check Claude Code release notes and summarize what you find in three bullet points.

  • Pull the newest data from Claude Code release notes and give me the result as a table.

How to set up Claude Code release notes in Muse Code

Pick the way that suits you. Each takes about two minutes.

Use Spiral's MCP server

  1. Install Muse Code
    curl -fsSL https://dev.meta.ai/install.sh | bash
  2. Ask Muse to add the server

    Start muse and ask:

    Add the Spiral MCP server at https://api.spiral.ai/mcp
  3. Sign in

    In your terminal, run:

    muse mcp login spiral

Use the Spiral skill

  1. Send Muse Code this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. Sign in or paste a key

    Approve Spiral in the browser, or give the agent a key from the console.

Use the Spiral CLI

  1. Install and sign in

    Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

    npx -y spiral-cli@latest init

Call the Spiral API

  1. Create an API key

    In the console, under API keys.

  2. Run Claude Code release notes

    One request; the result comes back by polling or a webhook.

    curl https://api.spiral.ai/v1/runs \
      -H "Authorization: Bearer $SPIRAL_API_KEY" \
      -H "Content-Type: application/json" \
      -H "Idempotency-Key: $(uuidgen)" \
      -d '{
        "provider": "alexandria",
        "model": "code-claude-com/developer-documentation/changelog",
        "input": {
          "q": "<q>"
        }
      }'

Then paste one of the prompts above: Muse Code finds Claude Code release notes on Spiral, shows the price and runs it.

Claude Code release notes providers and prices

Spiral runs Claude Code release notes through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper
Claude Code Docs · Changelog
code-claude-com/developer-documentation/changelog

Settings you can ask for

Ask Muse Code for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Limit1 to 50

Releases per page. Defaults to 10.

Offset0 to 100000

Defaults to 0.

Every API field of Claude Code Docs · Changelog is on its tool page: open its card above.

What can you do with Claude Code release notes in Muse Code?

Turn Claude Code documentation into a review of your project's hooks, skills, and settings. A coding agent can compare repository files with published references and release changes, then propose edits with supporting links.

Review a Claude Code upgrade

Find release changes affecting hooks and settings, locate the relevant documentation, check configuration names, and read the explanations needed for an upgrade checklist.

Write a hook troubleshooting guide

Map the hook documentation, find event references and relevant sections, and check release notes for changes that could explain a reported failure.

Review team configuration guidance

Collect the settings and precedence pages, look up documented keys, and review release changes before revising a team's Claude Code policy guide.

Maintain a skill authoring handbook

Find the skill documentation and frontmatter reference, read the relevant sections, and review release notes before updating authoring examples.

Prepare a support investigation

Search a reported Claude Code issue, retrieve the supporting documentation, check configuration terminology, and inspect release notes for a related fix.

Draft a release briefing

Summarize Claude Code release changes and locate documentation that explains the affected features, with links for readers who need the details.

Questions about Claude Code release notes in Muse Code

Can Muse Code use Claude Code release notes?

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run Claude Code release notes like any built-in tool.

How much does Claude Code release notes cost in Muse Code?

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.

Do I need an Alexandria account to use Claude Code release notes in Muse Code?

No. Spiral runs Claude Code release notes on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up Claude Code release notes in Muse Code?

About two minutes: install Muse Code, then ask Muse to add the server, then sign in.

Does Muse Code wait while Claude Code release notes runs?

Claude Code release notes runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.

What does the Claude Code documentation cover?

The official index covers configuration, skills, subagents, hooks, MCP, and the Agent SDK. This is the Claude Code documentation corpus.

Does this data show my organization's actual configuration?

The source is published documentation at code.claude.com. Its configuration references describe documented settings and behavior; they do not inspect your organization's installation.

Does documentation search cover the whole web?

Anthropic describes its documentation MCP server as providing full-text search over Claude Code docs. Its search coverage is the documentation corpus.

How recent is the published release information?

When checked on November 20, 2026, the official changelog included version 2.1.329 dated November 19, 2026. That establishes the recency of the published release history at that check.

How far back does the release history go?

The published changelog reaches back at least to version 0.2.21, dated April 2, 2025. This is release history, rather than an archive of every earlier documentation revision.

Get started

Start using Claude Code release notes in Muse Code

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Muse Code:

Set up Muse Code

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options