Skip to content

Run AssemblyAI transcription with Sapat in Daytona - #260

Open
chinook1001 wants to merge 1 commit into
daytona:mainfrom
chinook1001:codex/assemblyai-sapat-guide
Open

Run AssemblyAI transcription with Sapat in Daytona#260
chinook1001 wants to merge 1 commit into
daytona:mainfrom
chinook1001:codex/assemblyai-sapat-guide

Conversation

@chinook1001

Copy link
Copy Markdown

/claim #13

Summary

  • add a long-form Daytona guide for running Sapat with the new AssemblyAI provider in a reproducible workspace
  • add an async speech transcription definition, first-time author profile, and original SVG workflow diagram
  • link the companion Sapat implementation PR: Add AssemblyAI transcription provider nibzard/sapat#60

Why this is distinct

This submission targets AssemblyAI on Sapat's current provider-registry architecture. Current Sapat main has the merged 29-provider plugin refactor but no AssemblyAI provider; the old AssemblyAI PR targeted the pre-refactor CLI and was closed. This guide is paired with a current-architecture provider PR rather than another generic transcription article.

Validation

  • npx --yes markdownlint-cli@0.29.0 guides/20260530_run_assemblyai_transcription_with_sapat_in_daytona.md definitions/20260530_definition_async_speech_transcription.md authors/lucas_chinook.md --ignore node_modules
  • SVG XML parse check passed for guides/assets/20260530_run_assemblyai_transcription_with_sapat_in_daytona_workflow.svg
  • Guide word count check: 1,700 words
  • git diff --check
  • Companion Sapat PR validation: full mocked provider suite passed, 183 passed, plus Black and diff checks

No secrets, private media, generated transcripts, API keys, or payout details are included.

Signed-off-by: lucas <chinook1001@gmail.com>
@chinook1001
chinook1001 force-pushed the codex/assemblyai-sapat-guide branch from 1e06e40 to 93f6794 Compare May 29, 2026 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant