voice-call confusion

[covert spruce]

Do I have to install this plugin or is it bundled? What is the most recent version?

Docs say it supports streaming with open ai gtp4o-mini-tts

[void stream]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[steady swallow]

Yep — for Voice Call, install/enable it, but on recent OpenClaw it’s also shipped inside the OpenClaw package.

Current check, 2026-04-28:

• openclaw@latest on npm: 2026.4.26
• bundled @openclaw/voice-call inside that package: 2026.4.25
• standalone npm @openclaw/voice-call@latest: 2026.3.13 — looks older/lagging

So I’d do:

openclaw --version
openclaw plugins install @openclaw/voice-call
openclaw gateway restart
openclaw voicecall setup

Docs: https://docs.openclaw.ai/plugins/voice-call and https://docs.openclaw.ai/tools/plugin

Also tiny typo: it’s gpt-4o-mini-tts, not gtp4o-mini-tts. OpenAI’s docs list it as a TTS model and describe streaming audio output support via the Speech API. (platform.openai.com)

[covert spruce]

If I run that plugin install command there is going to be a bundled version and this standalone version right? Or does this command update the bundled version?

[steady swallow]

Good catch. It does not update the bundled copy inside OpenClaw — bundled plugins are part of the installed openclaw package, so those only change when you update OpenClaw itself.

What happens depends on the exact install spec:

openclaw plugins install @openclaw/voice-call

For current installs, this normally goes through the plugin installer/ClawHub/npm flow and creates a managed installed plugin record for voice-call. That installed copy is the one your config enables/uses. The bundled copy can still exist on disk as OpenClaw’s fallback/shipped copy, but it is not “patched” in place.

So practically:

• Bundled version = shipped with your OpenClaw version; update via openclaw update.
• Installed plugin version = managed plugin install; update via:

openclaw plugins update voice-call
openclaw gateway restart

To see what you’re actually using:

openclaw plugins list
openclaw plugins inspect voice-call

If you want the newest bundled voice-call I saw, update OpenClaw first — current openclaw@latest was 2026.4.26, carrying bundled voice-call 2026.4.25. The standalone npm package looked older (2026.3.13), so I would avoid forcing npm:@openclaw/voice-call unless someone specifically tells you to.

[covert spruce]

correct. So the bundled version is fresh and the standalone is very stale which suggests you should only use the bundled version

[steady swallow]

Yep — that’s the right conclusion.

I’d avoid the standalone npm install for now, because it appears stale. Use the bundled voice-call plugin that ships with current OpenClaw instead.

Practical guidance:

openclaw --version
openclaw plugins inspect voice-call

If it resolves from OpenClaw’s bundled dist/extensions/voice-call, you’re on the fresh bundled copy.

If you already installed the standalone one, I’d inspect first; then likely remove that managed install and use bundled/config-only instead. The docs probably need a tweak here so they don’t steer people into the stale standalone package.

[covert spruce]

right so my bundled version still lags from the latest based on your message

Status: loaded
Format: openclaw
Source: /usr/local/lib/node_modules/openclaw/dist/extensions/voice-call/index.js
Origin: bundled
Version: 2026.4.21
Shape: non-capability
Capability mode: none
Legacy before_agent_start: no

[steady swallow]

Right — your installed OpenClaw has bundled voice-call 2026.4.21, while the current packaged OpenClaw I checked bundles 2026.4.25.

So the fix is update OpenClaw, not install the stale standalone package:

openclaw update

Then verify:

openclaw --version
openclaw plugins inspect voice-call

You want it still saying: