Skip to content

docs(slack): explain voice input and audio clips#102410

Merged
steipete-oai merged 2 commits into
mainfrom
codex/docs-slack-voice-input
Jul 9, 2026
Merged

docs(slack): explain voice input and audio clips#102410
steipete-oai merged 2 commits into
mainfrom
codex/docs-slack-voice-input

Conversation

@steipete-oai

@steipete-oai steipete-oai commented Jul 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

What Problem This Solves

Slack's new Slackbot voice-dictation feature can look like an API capability available to third-party Slack apps, while OpenClaw's supported voice-input path is actually stored Slack audio clips. The Slack docs did not explain that boundary, omitted audio clips from the media reference, and described mention-gated audio preflight more broadly than every channel currently supports.

Why This Change Was Made

This documents the supported audio-clip path, its files:read and transcription requirements, the different retention semantics, and Slack's current mention-gate limitation. It also scopes the shared audio-preflight wording to channels that implement it. No runtime behavior changes.

AI-assisted: Yes (Codex).

User Impact

Operators can now tell which Slack voice workflow works with OpenClaw, configure audio transcription correctly, and avoid expecting Slackbot's private dictation microphone to emit Events API payloads. Users in mention-gated channels also get an explicit workaround: add a typed bot mention or send the clip in a DM.

Evidence

  • node scripts/check-docs-mdx.mjs docs/channels/slack.md docs/nodes/audio.md docs/docs_map.md — passed.
  • node scripts/generate-docs-map.mjs --check — generated docs map is current.
  • node scripts/docs-link-audit.mjs — 5,761 internal links checked, 0 broken.
  • node scripts/format-docs.mjs --check — 685 docs files clean.
  • git diff --check origin/main...HEAD — passed.
  • pnpm test extensions/slack/src/monitor/media.test.ts extensions/slack/src/monitor/message-handler.test.ts — 2 files, 50 tests passed on AWS Crabbox (run_f8cb6aaa5ecd).
  • Slack API claims were checked against Slack's Slackbot, Events API, file-object, audio-clip, MCP-client, and Block Kit documentation.

The optional anchor audit was attempted separately but Mint's pnpm dlx bootstrap failed with ERR_PNPM_NO_IMPORTER_MANIFEST_FOUND; the ordinary repository link audit above passed.

@openclaw-barnacle openclaw-barnacle Bot added docs Improvements or additions to documentation channel: slack Channel integration: slack size: XS maintainer Maintainer-authored PR labels Jul 9, 2026
@clawsweeper

clawsweeper Bot commented Jul 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Codex review: found issues before merge. Reviewed July 9, 2026, 12:20 AM ET / 04:20 UTC.

Summary
The PR updates Slack and shared audio docs to distinguish Slackbot voice dictation from Slack audio clips and to narrow mention-gated audio preflight wording to channels that support it.

PR surface: Docs +16. Total +16 across 2 files.

Reproducibility: not applicable. as a runtime bug. The actionable failure is reproduced by CI: pnpm check:docs reaches generate-docs-map --check and reports docs/docs_map.md out of date.

Review metrics: 1 noteworthy metric.

  • Generated docs map: 1 out of date. The required docs check fails until the generated docs index is refreshed for the changed Slack/audio docs.

Merge readiness
Overall: 🦐 gold shrimp
Proof: 🌊 off-meta tidepool
Patch quality: 🦐 gold shrimp
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

  • Regenerate docs/docs_map.md with the repository docs-map generator and rerun the docs check.

Risk before merge

  • [P1] The required check-docs job is failing because the generated docs map is stale after the docs edits.

Maintainer options:

  1. Decide the mitigation before merge
    Keep the Slack audio clarification, regenerate docs/docs_map.md with the repository docs-map generator, and let the maintainer-owned PR proceed through normal review.
  2. Pause or close
    Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge

  • [P2] The PR has a protected maintainer label and the branch is not maintainer-modifiable, so the generated-doc fix needs author or maintainer handling rather than cleanup close.

Security
Cleared: Docs-only changes do not alter code execution, dependencies, credentials, CI, or release behavior.

Review findings

  • [P2] Regenerate the docs map — docs/channels/slack.md:1217
Review details

Best possible solution:

Keep the Slack audio clarification, regenerate docs/docs_map.md with the repository docs-map generator, and let the maintainer-owned PR proceed through normal review.

Do we have a high-confidence way to reproduce the issue?

Not applicable as a runtime bug. The actionable failure is reproduced by CI: pnpm check:docs reaches generate-docs-map --check and reports docs/docs_map.md out of date.

Is this the best way to solve the issue?

No, not yet. The documentation direction is source-backed, but the PR is not merge-ready until the generated docs map is refreshed.

Full review comments:

  • [P2] Regenerate the docs map — docs/channels/slack.md:1217
    check-docs reaches node scripts/generate-docs-map.mjs --check and fails with docs/docs_map.md is out of date after this docs edit. Please regenerate the docs map with the repo generator so the generated docs index matches the Slack/audio docs changes.
    Confidence: 0.95

Overall correctness: patch is incorrect
Overall confidence: 0.92

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 6e4670f9c147.

Label changes

Label changes:

  • add P3: This is a focused docs-only Slack clarification with low user and merge blast radius.
  • add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
  • add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: Real behavior proof is not required because this PR only changes files under docs/.

Label justifications:

  • P3: This is a focused docs-only Slack clarification with low user and merge blast radius.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: Real behavior proof is not required because this PR only changes files under docs/.
Evidence reviewed

PR surface:

Docs +16. Total +16 across 2 files.

View PR surface stats
Area Files Added Removed Net
Source 0 0 0 0
Tests 0 0 0 0
Docs 2 29 13 +16
Config 0 0 0 0
Generated 0 0 0 0
Other 0 0 0 0
Total 2 29 13 +16

Acceptance criteria:

  • [P1] pnpm check:docs.
  • [P1] node scripts/generate-docs-map.mjs --check.

What I checked:

Likely related people:

  • steipete: Recent commits touched docs/channels/slack.md and Slack media behavior, the runtime PR for Slack audio MIME was merged by this handle, and the live PR is assigned to the same maintainer account. (role: recent docs and Slack area contributor; confidence: high; commits: a6e19fe014de, f7d7148cf047, 706443c79b1c; files: docs/channels/slack.md, extensions/slack/src/monitor/media.ts)
  • vincentkoc: Recent history shows this handle maintaining Slack media/download code and shared docs/audio surfaces relevant to the documented behavior. (role: recent Slack media/docs contributor; confidence: medium; commits: 3d206140f3f0, 44b0644e883b, 21728777dfa0; files: extensions/slack/src/monitor/media.ts, docs/nodes/audio.md)
  • mcaxtr: Authored the merged Slack voice-message MIME override that makes Slack audio clips route as audio in the current runtime. (role: introduced adjacent runtime behavior; confidence: medium; commits: c45e9827cbe8, fb7f5cc0bcdb; files: extensions/slack/src/monitor/media.ts)
  • obviyus: Recent history shows work in prepareSlackMessage, the path that applies mention gating before Slack media resolution. (role: recent Slack prepare-path contributor; confidence: medium; commits: 04b55c35d2f6; files: extensions/slack/src/monitor/message-handler/prepare.ts)
What the crustacean ranks mean
  • 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
  • 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
  • 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
  • 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
  • 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
  • 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
  • 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works
  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@clawsweeper clawsweeper Bot added rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. P3 Low-priority cleanup, docs, polish, ergonomics, or speculative work. labels Jul 9, 2026
@steipete-oai
steipete-oai force-pushed the codex/docs-slack-voice-input branch from d852df9 to 2907b13 Compare July 9, 2026 04:24
@steipete-oai

steipete-oai commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

Land-ready verification for exact head 2907b136f2f75f575cd21e7de15f1b454c26ae5c:

  • Reviewed the complete changed Slack voice/media and shared audio-preflight sections against the existing Slack file-download, slack_audio MIME-normalization, message-subtype, manifest-scope, and cross-channel preflight paths. No blocking findings; best-fix verdict: focused docs correction.
  • node scripts/check-docs-mdx.mjs docs/channels/slack.md docs/nodes/audio.md docs/docs_map.md — passed.
  • node scripts/generate-docs-map.mjs --check — passed.
  • node scripts/docs-link-audit.mjs — 5,761 internal links checked, 0 broken.
  • node scripts/format-docs.mjs --check — 685 docs files clean.
  • git diff --check origin/main...HEAD — passed.
  • pnpm test extensions/slack/src/monitor/media.test.ts extensions/slack/src/monitor/message-handler.test.ts — 2 files, 50 tests passed on AWS Crabbox run run_f8cb6aaa5ecd.
  • Exact-head hosted CI passed: https://github.com/openclaw/openclaw/actions/runs/28993943367
  • OPENCLAW_TESTBOX=1 scripts/pr prepare-run 102410 — hosted exact-head gates passed; prep head equals PR head.

Known proof gap: the optional anchor audit was attempted, but Mint's pnpm dlx bootstrap failed with ERR_PNPM_NO_IMPORTER_MANIFEST_FOUND; the repository's ordinary link audit and hosted docs CI passed. Changelog not required for this docs-only clarification.

@steipete-oai
steipete-oai merged commit e2a4973 into main Jul 9, 2026
48 checks passed
@steipete-oai
steipete-oai deleted the codex/docs-slack-voice-input branch July 9, 2026 04:28
@steipete-oai

steipete-oai commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

Merged via squash.

This was referenced Jul 9, 2026
Closed
Merged
github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request Jul 9, 2026
@steipete-oai @steipete
docs(slack): explain voice input and audio clips (openclaw#102410)
0d4ce21 
* docs(slack): document voice input support

* docs: refresh generated map

---------

Co-authored-by: Peter Steinberger <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@steipete steipete

Labels

channel: slack Channel integration: slack docs Improvements or additions to documentation maintainer Maintainer-authored PR P3 Low-priority cleanup, docs, polish, ergonomics, or speculative work. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. size: XS status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@steipete-oai @steipete