Turn release notes into a team podcast: a real brief

The Rust 1.99.0 release post became a short team update in the brief style. Hear it, copy the request, and see its cost and what our check found.

How this was made. Audio and video overviews, slide decks and infographics are made with Google's Gemini Notebook (formerly NotebookLM), on accounts that AutoContent operates. AutoContent has no agreement with Google. Google can limit or stop this access at any time.

The brief1 min 46 s

AI-generated with AutoContent APIDownload MP3 Full transcript (TXT)

What came out, and what we would change

We set style to brief and wrote the audience into the text: an engineering team that uses Rust, what changed, what to try first, and what needs action. The brief runs 1 min 46 s and covers the three main items of the post in its order: functions with a variable number of arguments, layout information from raw pointers, and the new advice on Box::leak.

What is right: such functions can now be written in Rust and not only called, the size and alignment functions for raw pointers are stable, and code that frees memory after Box::leak should move to Box::into_raw.

What is overstated: the brief calls the Box::leak advice a critical warning to address before upgrading. The post says the release does not change the language; it updates the documentation to recommend against the pattern. Our first try with the same request also called the new raw-pointer functions trivially safe, which the post says only of one case. We rejected that output and published this second one.

To steer a brief, say what matters in the text, for example "say which items change behavior and which are only recommendations". This brief took 4 min 14 s to generate and used 10 credits. For a weekly team podcast, send one request per release post and add podcastId, so each brief lands in the same show feed.

Transcript excerpt

Speech-to-text of the output, not edited and without speaker labels. It is part of the sample output.

This is the brief on the Rust 1.99.0 release. So, Rust 1.99.0 literally just dropped, and for our engineering team, it brings from absolutely exciting new C interoperability alongside a critical memory management warning you kinda gotta address before upgrading. First, native C-ABI variadic functions. Basically, you can now write functions natively in Rust that accept a totally flexible number of arguments, outputting a C-compatible VList. Think of it like this. We used to just attend C's party, but now we're actually hosting the whole shebang right here in Rust. But hey, getting closer to the metal naturally means we've got to talk about raw memory.

The exact request

The body that was sent to POST /content/Create, unchanged, and the same request as curl.

request.json

{
  "resources": [
    {
      "type": "website",
      "content": "https://blog.rust-lang.org/2026/10/01/Rust-1.99.0/"
    }
  ],
  "outputType": "audio",
  "style": "brief",
  "text": "A short internal update for an engineering team that uses Rust: what changed in this release, what to try first, and anything that needs action when upgrading. Do not name individual contributors.",
  "language": "English"
}

curl

curl -X POST "https://api.autocontentapi.com/content/Create" \
  -H "Authorization: Bearer $AUTOCONTENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resources":[{"type":"website","content":"https://blog.rust-lang.org/2026/10/01/Rust-1.99.0/"}],"outputType":"audio","style":"brief","text":"A short internal update for an engineering team that uses Rust: what changed in this release, what to try first, and anything that needs action when upgrading. Do not name individual contributors.","language":"English"}'
# then poll until "status" is 100:
curl -H "Authorization: Bearer $AUTOCONTENT_API_KEY" "https://api.autocontentapi.com/content/Status/<request_id>"

How we checked it

Transcript: We transcribed the output with Whisper large-v3-turbo and compared the transcript with the source.
Language: Detected en, requested en.
Loudness: -24.2 LUFS integrated, true peak -5.8 dBTP.
Notes: The three items match the post; the Box::leak advice is presented as more urgent than the post says. The first output of this request was rejected for a false statement about safety and is not published.
Checked on: 2026-11-02. Failed generations are run again and never published.

More examples

All examples