Skip to content

vowelbot

vowelbot - Auto-implement AI voice

vowelbot is a GitHub-integrated service that adds voice agent capabilities to web projects (React, vanilla JavaScript, or Web Components) via GitHub comments. Click the image above to watch the demo video.

Use vowelbot to add vowel to a GitHub repository with an automatic onboarding flow at add.vowel.to. Just click a button — the integration runs entirely in an isolated branch, leaving your existing work pristine.

Supported Projects

  • Supported: React, vanilla JavaScript, Web Components (web projects only)
  • Not yet supported: iOS Swift, Android, Flutter, and other non-web frameworks

Quick Start

1. API Keys (Optional)

vowelbot uses OpenCode directly inside the GitHub action — no setup required! The integration automatically uses high-quality free models (Minimax M2.5, Big Pickle, or Kimi K2.5).

Want premium models? Add one of these as a GitHub secret:

Secret nameWhere to get it
ANTHROPIC_API_KEYconsole.anthropic.com — Claude models
OPENAI_API_KEYplatform.openai.com — GPT models
GROQ_API_KEYconsole.groq.com — Fast Llama models
OPENCODE_API_KEYopencode.ai/zen — Use paid models with OpenCode credits

Where to add secrets:

  • Organization: Org → Settings → Secrets and variables → Actions → New organization secret
  • Single repo: Repo → Settings → Secrets and variables → Actions → New repository secret

Note: If you add any API key, vowelbot will use that provider instead of the free OpenCode models.

2. Integrate — One Click

Go to add.vowel.to and click Add vowel to your project. Choose the repo you want to integrate vowel into.

That's it. The workflow is added to your repo, the first integration runs automatically, and OpenCode opens a PR with voice agent changes tailored to your stack (React, vanilla JS, or <vowel-voice-widget>). Everything runs in one go — no manual re-run needed.

Your existing code stays untouched. The integration uses agent skills from the vowel repositoryvowel-react, vowel-vanilla, vowel-webcomponent, or voweldocs — selected automatically based on your project type.

During setup, vowelbot creates an isolated add-vowel branch in your repository. All workflow setup, integration logic, and voice agent changes are committed to this branch only. When complete, it opens a pull request from the add-vowel branch to your default branch for you to review and merge. Your existing branches and work remain completely untouched until you choose to merge.

3. Use It (Later Runs)

  • In an issue or PR: Comment /vowelbot integrate (or /vowelbot + your request)
  • Manual run: Actions → vowelbot integration → Run workflow

Your keys stay in your repo — vowelbot never sees them.

GitHub Codespaces

No additional setup required — when the OpenCode agent integrates vowel into your repository, a GitHub Codespaces environment is automatically configured for testing.

You can also explore the skills directly in GitHub Codespaces: Open in GitHub Codespaces

Troubleshooting

IssueSolution
Workflow fails with "no API key"This should not happen — vowelbot uses free OpenCode models by default. If you see this error, it may be a temporary issue with the free model provider. Try running the workflow again, or add an API key from Anthropic, OpenAI, or Groq as a fallback.
Clicked integrate and workflow failedGo to Actions → vowelbot integration → Run workflow to retry. Free models may occasionally be unavailable during high demand — adding an API key ensures reliable access.
"Project not compatible"Vowel supports React, vanilla JavaScript, and Web Components only. iOS Swift, Android, Flutter, and other non-web frameworks are not yet supported.

Onboarding Flow

Architecture

Key Architectural Principles

  1. Branch-based onboarding (pristine): All changes happen in an isolated add-vowel branch. Your existing branches, default branch, and working code remain completely untouched. The integration runs entirely within this branch, then opens a PR for your review. Nothing changes in your repository until you explicitly merge.

  2. Zero key custody: User API keys stay in their repo secrets. We only use GitHub App credentials.

  3. GitHub-native triggers: After initial setup, /vowelbot comments trigger Actions directly — no persistent infrastructure in the hot path.

Reference