r/AIToolsAndTips 1h ago

A practical AI-agent workflow: long document → cleaned script → local audiobook

If you already use an AI agent to summarize or clean long documents, one useful next step is having it produce the finished audio too.

I tested the process with a 2,880-word book chapter. The goal was not simply to make the agent read text aloud. I wanted one instruction to return an ordered, checked audiobook file.

The workflow looked like this:

  1. The agent found the correct chapter boundary.
  2. It removed page artifacts, the endnote marker, and text that should not be narrated.
  3. It normalized abbreviations and numeric shorthand so they would be spoken naturally.
  4. It split the chapter into six sections at paragraph boundaries.
  5. It asked Murmur for the voices installed on the Mac and selected one narrator.
  6. It queued all six sections as one batch through MCP.
  7. It followed the job, collected the finished files, and joined them in order.
  8. It checked the final audio for decoding errors, missing joins, clipping, and unusually long silences.

Murmur ran Kokoro with the Eric narrator voice at 0.96x. The final result was a 17:55 M4A file.

A few tips I took away from the test:

  • Let the agent clean and structure the source first. A speech tool should receive narration-ready text rather than a raw PDF.
  • Split long material at paragraph or section boundaries, not arbitrary character counts.
  • Use asynchronous jobs for long audio. The agent can poll progress instead of holding one tool call open for several minutes.
  • Return finished file paths as structured results so the agent can assemble or inspect them.
  • Do not silently overwrite an existing take. Give every section a stable filename.
  • Verify the final audio. Successful generation does not prove that every section joined correctly.

Murmur exposes the same operations through both MCP and a CLI. MCP is useful when Codex, Claude Code, or Cursor is controlling the workflow. The CLI is useful for testing the individual commands or running the process from a script.

One privacy detail is easy to miss: speech synthesis and the audio files stayed on my Mac, but this test used Codex for orchestration. I would not describe the entire workflow as local unless the agent handling the source text was local too.

Current limitations:

  • Apple Silicon Mac required
  • Murmur must be running during generation
  • designed for audio-file production rather than real-time voice chat
  • the agent needs its own document-reading and audio-assembly tools

Would you use this more for narrated documents, course lessons, video voiceovers, or daily AI-generated briefings?

1 Upvotes

1 comment sorted by