Skip to content

fix(minimax): stop advertising music duration control#84765

Merged
clawsweeper[bot] merged 4 commits into
mainfrom
clawsweeper/automerge-openclaw-openclaw-84585
May 21, 2026
Merged

fix(minimax): stop advertising music duration control#84765
clawsweeper[bot] merged 4 commits into
mainfrom
clawsweeper/automerge-openclaw-openclaw-84585

Conversation

@clawsweeper

@clawsweeper clawsweeper Bot commented May 21, 2026

Copy link
Copy Markdown
Contributor

Makes #84585 merge-ready for the ClawSweeper automerge loop.
The edit pass should inspect the live PR diff, review comments, and failing checks; rebase if needed; keep the contributor branch credited; and stop only when validation is green or an external blocker is proven.
Known failing checks:

ClawSweeper 🐠 replacement reef notes:

  • Repair fallback: GitHub rejected the repair branch push because it updates workflow files and the ClawSweeper app token does not have workflows permission

Inherited issue-closing references from the source PR:
Fixes #84508

Co-author credit kept:

fish notes: model gpt-5.5, reasoning high; reviewed against 1c616da.

@clawsweeper clawsweeper Bot added docs Improvements or additions to documentation size: XS extensions: minimax clawsweeper:automerge Maintainer opted this PR into bounded ClawSweeper-reviewed automerge triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. proof: sufficient ClawSweeper judged the real behavior proof convincing. P2 Normal backlog priority with limited blast radius. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. clawsweeper Tracked by ClawSweeper automation labels May 21, 2026
@clawsweeper clawsweeper Bot mentioned this pull request May 21, 2026
Closed
@clawsweeper

clawsweeper Bot commented May 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Codex review: passed.

Workflow note: Future ClawSweeper reviews update this same comment in place.

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.

Summary
The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.

Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the request body has no structured duration field and only appends a natural-language hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

PR rating
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster
Patch quality: 🐚 platinum hermit
Summary: Focused patch with strong real behavior proof and no correctness findings, with ordinary compatibility acceptance and CI gating still relevant.

Rank-up moves:

  • none
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.

Real behavior proof
Sufficient (live_output): The PR body carries after-fix capability output plus a redacted live MiniMax generation run showing the provider still works while durationSeconds is ignored as unsupported.

Risk before merge

  • Compatibility: MiniMax users who passed durationSeconds will now get unsupported-override handling instead of the previous natural-language duration hint; maintainers should accept that contract correction before merge.
  • Exact-head CI still had a few in-progress checks during review, so the merge path should wait for required checks to finish.

Maintainer options:

  1. Land the contract correction (recommended)
    Accept the intentional behavior change because it stops advertising a control MiniMax does not document or enforce and routes callers through existing unsupported-override warnings.
  2. Pause for a product exception
    If maintainers want to preserve best-effort prompt steering despite the vendor contract, pause this PR and explicitly design that as a non-advertised MiniMax behavior.

Next step before merge
No repair job is needed; this PR is already the focused fix and should proceed through exact-head CI/automerge plus maintainer compatibility acceptance.

Security
Cleared: The diff only narrows MiniMax request behavior and docs/tests; it does not add dependencies, widen auth, alter secret handling, or weaken HTTP/private-network controls.

Review details

Best possible solution:

Land this PR after exact-head checks pass and maintainers accept that MiniMax durationSeconds remains unsupported until MiniMax documents a structured request field.

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

Yes, by source inspection: current main advertises MiniMax duration support while the request body has no structured duration field and only appends a natural-language hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Is this the best way to solve the issue?

Yes. Removing the advertised capability and prompt hint is the narrowest maintainable fix until MiniMax documents a structured duration request field; the shared runtime already reports unsupported overrides.

Label changes:

  • add status: 🚀 automerge armed: This PR is in ClawSweeper's automerge lane. Sufficient (live_output): The PR body carries after-fix capability output plus a redacted live MiniMax generation run showing the provider still works while durationSeconds is ignored as unsupported.
  • remove status: 👀 ready for maintainer look: Current PR status label is status: 🚀 automerge armed.

Label justifications:

  • P2: This is a focused provider bug fix with limited blast radius to MiniMax music generation capability reporting.
  • merge-risk: 🚨 compatibility: Existing MiniMax callers that passed durationSeconds will see unsupported-override behavior instead of the previous prompt hint after this PR merges.
  • rating: 🐚 platinum hermit: Current PR rating is 🐚 platinum hermit because proof is 🦞 diamond lobster, patch quality is 🐚 platinum hermit, and Focused patch with strong real behavior proof and no correctness findings, with ordinary compatibility acceptance and CI gating still relevant.
  • status: 🚀 automerge armed: This PR is in ClawSweeper's automerge lane. Sufficient (live_output): The PR body carries after-fix capability output plus a redacted live MiniMax generation run showing the provider still works while durationSeconds is ignored as unsupported.
  • proof: sufficient: Contributor real behavior proof is sufficient. The PR body carries after-fix capability output plus a redacted live MiniMax generation run showing the provider still works while durationSeconds is ignored as unsupported.

What I checked:

  • current main mis-advertises MiniMax duration control: Current main declares supportsDuration: true, appends a Target duration prompt hint, sends no structured duration field in the MiniMax request body, and records requested duration metadata after generation. (extensions/minimax/music-generation-provider.ts:109, c4f14a39a520)
  • unsupported override path already exists: The shared music-generation normalization drops durationSeconds and records it in ignoredOverrides when a provider does not advertise duration support; the runtime then passes the sanitized duration to the provider. (src/music-generation/normalization.ts:81, c4f14a39a520)
  • PR diff matches the intended boundary: The patch removes buildPrompt, removes supportsDuration, sends req.prompt.trim() directly, drops requestedDurationSeconds metadata, updates MiniMax/music docs, and adds regression expectations that the request prompt has no duration hint and no duration property. (extensions/minimax/music-generation-provider.ts:129, 1c616da45cb4)
  • MiniMax API contract check: The official MiniMax Music Generation API reference lists request body fields such as model, prompt, lyrics, stream, output_format, audio_setting, lyrics_optimizer, is_instrumental, and cover-audio fields; it shows music_duration only in response extra_info, not as a documented request duration field. (platform.minimax.io)
  • real behavior proof carried from source PR: The source PR body includes after-fix capability output showing supportsDuration: false, durationSeconds in ignoredOverrides, and a live MiniMax generation run passing with redacted MINIMAX_API_KEY output. (920a85c333ca)
  • exact-head check state: Live check-run read showed Real behavior proof succeeded and the affected lint/build/bundled-extension checks succeeded; some exact-head checks were still in progress at review time, so merge should remain gated on required CI completion. (1c616da45cb4)

Likely related people:

  • steipete: The current MiniMax music provider, provider docs, music-generation docs, and shared override-normalization path all trace by blame/log to commit 167e73c authored by Peter Steinberger. (role: introduced behavior and adjacent owner; confidence: high; commits: 167e73cd5f84; files: extensions/minimax/music-generation-provider.ts, docs/providers/minimax.md, docs/tools/music-generation.md)

Codex review notes: model gpt-5.5, reasoning high; reviewed against c4f14a39a520.

@openclaw-barnacle openclaw-barnacle Bot removed the triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. label May 21, 2026
@clawsweeper clawsweeper Bot added status: 🚀 automerge armed This PR is in ClawSweeper's automerge lane. and removed status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels May 21, 2026
@clawsweeper

clawsweeper Bot commented May 21, 2026

Copy link
Copy Markdown
Contributor Author

ClawSweeper PR egg

✨ Hatched: 🥚 common Gilded Proofling

Hatch command

Comment @clawsweeper hatch when this PR is hatchable.

Hatchability rules:

  • Merged PRs are hatchable.
  • Open PRs are hatchable when they are status: 👀 ready for maintainer look, status: 🚀 automerge armed, or labeled clawsweeper:automerge.
  • Closed unmerged PRs are hatchable only when one of those hatchable labels is still present in the durable record.

Rarity: 🥚 common.
Trait: keeps receipts.
Image traits: location branch lighthouse; accessory commit compass; palette plum, gold, and soft gray; mood sparkly; pose balancing on a branch marker; shell paper lantern shell; lighting golden review-room light; background small review tokens.
Share on X: post this hatch
Copy: My PR egg hatched a 🥚 common Gilded Proofling in ClawSweeper.

What is this egg doing here?
  • Eggs appear after the PR passes real-behavior proof. It is here for vibes, not verdicts: it does not change labels, ratings, merge decisions, or automation.
  • The shell reacts to review momentum: open follow-up work warms it up, re-review makes it wobble, and a clean final review lets it hatch.
  • Hatchability usually comes from sufficient real-behavior proof, no blocking P0/P1/P2 findings, no security attention needed, and clean correctness. A merged PR is already final, so merge makes the egg hatchable independently.
  • The hatch is seeded from this repository and PR number, so the same PR keeps the same creature; the reviewed head SHA can only change safe visual details.
  • Rarity is just collectible sparkle: 🥚 common, 🌱 uncommon, 💎 rare, ✨ glimmer, and 🌈 legendary.

@clawsweeper

clawsweeper Bot commented May 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

🦞✅
ClawSweeper merged this PR after the passing review.

Source: clawsweeper[bot]
Feedback: structured ClawSweeper verdict: pass (sha=1c616da45cb4670872b59f88edbe5c067d563237)
Merge status: merged by ClawSweeper automerge
Merged at: 2026-05-21T02:26:18Z
Merge commit: 86ebceeb2e2e

What merged:

  • The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
  • Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:

  • PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
  • PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
  • PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

The automerge loop is complete.

Automerge progress:

  • 2026-05-21 02:19:37 UTC review passed 1c616da45cb4 (structured ClawSweeper verdict: pass (sha=1c616da45cb4670872b59f88edbe5c067d563...)
  • 2026-05-21 02:24:01 UTC review queued 1c616da45cb4 (queued)
  • 2026-05-21 02:24:43 UTC merge check queued 1c616da45cb4 (checks and exact-head review are ready)
  • 2026-05-21 02:26:20 UTC merged 1c616da45cb4 (merged by ClawSweeper automerge)

@clawsweeper clawsweeper Bot merged commit 86ebcee into main May 21, 2026
180 of 199 checks passed
@clawsweeper clawsweeper Bot deleted the clawsweeper/automerge-openclaw-openclaw-84585 branch May 21, 2026 02:26
@github-actions github-actions Bot mentioned this pull request May 21, 2026
Open
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 24, 2026
@clawsweeper @neeravmakwana
@Takhoffman @SebTardif
fix(minimax): stop advertising music duration control (openclaw#84765)
bdbf78e 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 24, 2026
@clawsweeper @neeravmakwana
@Takhoffman @SebTardif
fix(minimax): stop advertising music duration control (openclaw#84765)
1d61663 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 24, 2026
@clawsweeper @neeravmakwana
@Takhoffman @SebTardif
fix(minimax): stop advertising music duration control (openclaw#84765)
1f7902f 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
github-actions Bot pushed a commit to Desicool/openclaw that referenced this pull request May 24, 2026
@clawsweeper @neeravmakwana @Takhoffman
fix(minimax): stop advertising music duration control (openclaw#84765)
37fa123 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
galiniliev pushed a commit to galiniliev/openclaw that referenced this pull request May 25, 2026
@clawsweeper @neeravmakwana @Takhoffman
fix(minimax): stop advertising music duration control (openclaw#84765)
5f906eb 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 26, 2026
@clawsweeper @neeravmakwana
@Takhoffman @SebTardif
fix(minimax): stop advertising music duration control (openclaw#84765)
7fa9672 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 26, 2026
@clawsweeper @neeravmakwana
@Takhoffman @SebTardif
fix(minimax): stop advertising music duration control (openclaw#84765)
68e9c1f 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SebTardif pushed a commit to SebTardif/openclaw that referenced this pull request May 26, 2026
@clawsweeper @neeravmakwana
@Takhoffman @SebTardif
fix(minimax): stop advertising music duration control (openclaw#84765)
ea89ee9 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
jameslcowan pushed a commit to jameslcowan/openclaw that referenced this pull request Jun 2, 2026
@clawsweeper @neeravmakwana @Takhoffman
fix(minimax): stop advertising music duration control (openclaw#84765)
7533258 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
SYU8384 pushed a commit to SYU8384/openclaw that referenced this pull request Jun 3, 2026
@clawsweeper @neeravmakwana @Takhoffman
fix(minimax): stop advertising music duration control (openclaw#84765)
e72d437 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
sablehead pushed a commit to sablehead/openclaw that referenced this pull request Jun 10, 2026
@clawsweeper @neeravmakwana @Takhoffman
fix(minimax): stop advertising music duration control (openclaw#84765)
1e83068 
Summary:
- The PR removes MiniMax music duration support from provider capabilities and docs, stops prompt-injecting duration hints, updates the MiniMax provider test, and adds a changelog entry.
- Reproducibility: yes. by source inspection: current main advertises MiniMax duration support while the reque ... uage hint. I did not rerun a live pre-fix MiniMax request, but the code path and vendor contract are clear.

Automerge notes:
- PR branch already contained follow-up commit before automerge: docs(minimax): align music controls
- PR branch already contained follow-up commit before automerge: docs(music): remove minimax duration steering claim
- PR branch already contained follow-up commit before automerge: fix(minimax): stop advertising music duration control

Validation:
- ClawSweeper review passed for head 1c616da.
- Required merge gates passed before the squash merge.

Prepared head SHA: 1c616da
Review: openclaw#84765 (comment)

Co-authored-by: Neerav Makwana <261249544+neeravmakwana@users.noreply.github.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

clawsweeper:automerge Maintainer opted this PR into bounded ClawSweeper-reviewed automerge clawsweeper Tracked by ClawSweeper automation docs Improvements or additions to documentation extensions: minimax merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. P2 Normal backlog priority with limited blast radius. proof: sufficient ClawSweeper judged the real behavior proof convincing. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. size: XS status: 🚀 automerge armed This PR is in ClawSweeper's automerge lane.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[bug] MiniMax music_generation provider: durationSeconds is not passed to API, silently produces default-length tracks

1 participant

@neeravmakwana