PR #60883: feat: add cover image support to Discord event create

• Repository: openclaw/openclaw
• Author: bittoby
• State: closed | merged: True
• Link: https://github.com/openclaw/openclaw/pull/60883

Description (problem / solution / changelog)

Summary

Discord scheduled events support cover images, but the CLI and agent tool have no way to provide one. This adds an optional --image parameter that accepts a URL or local file path, validates the image (PNG/JPG/GIF, max 8MB), and passes it to the Discord API.

No behavior change when the parameter is omitted.

Linked Issue

Closes #60889

Usage

CLI:

openclaw message event create --guild-id 123 --event-name "Show" --start-time 2026-04-10T20:00:00Z --image /path/to/cover.png

Agent tool:

{ "action": "event-create", "guildId": "123", "eventName": "Show", "startTime": "2026-04-10T20:00:00Z", "image": "https://example.com/cover.jpg" }

What changed

Notes

• Follows the same loadWebMediaRaw + MIME validation + data URI pattern as uploadEmojiDiscord
• Threads mediaLocalRoots through the guild action path so configured local directories work
• Backward compatible, no config or migration needed
• Typecheck and formatting pass

Changed files

• CHANGELOG.md (modified, +1/-0)
• extensions/discord/src/actions/handle-action.guild-admin.ts (modified, +4/-1)
• extensions/discord/src/actions/runtime.guild.ts (modified, +10/-0)
• extensions/discord/src/actions/runtime.ts (modified, +1/-1)
• extensions/discord/src/send.guild.ts (modified, +21/-0)
• extensions/discord/src/send.ts (modified, +1/-0)
• extensions/discord/src/send.types.ts (modified, +1/-0)
• src/agents/tools/message-tool.ts (modified, +3/-0)
• src/cli/program/message/register.discord-admin.ts (modified, +1/-0)

PR #62647: feat: add cover image support to Discord event create

• Repository: openclaw/openclaw
• Author: itdeveloper1988
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/62647

Description (problem / solution / changelog)

Add --image <path/url/base64> parameter for attaching cover art to Discord scheduled events, matching the existing send/media pattern.

Supports URLs, local file paths, and data URIs with MIME validation (PNG, JPG, GIF) and 8 MB size enforcement.

Closes #60889

Summary

Describe the problem and fix in 2–5 bullets:

If this PR fixes a plugin beta-release blocker, title it fix(<plugin-id>): beta blocker - <summary> and link the matching Beta blocker: <plugin-name> - <summary> issue labeled beta-blocker. Contributors cannot label PRs, so the title is the PR-side signal for maintainers and automation.

• Problem:
• Why it matters:
• What changed:
• What did NOT change (scope boundary):

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #
• Related #
• This PR fixes a bug or regression

Root Cause (if applicable)

For bug fixes or regressions, explain why this happened, not just what changed. Otherwise write N/A. If the cause is unclear, write Unknown.

• Root cause:
• Missing detection / guardrail:
• Contributing context (if known):

Regression Test Plan (if applicable)

For bug fixes or regressions, name the smallest reliable test coverage that should catch this. Otherwise write N/A.

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
• Target test or file:
• Scenario the test should lock in:
• Why this is the smallest reliable guardrail:
• Existing test that already covers this (if any):
• If no new test is added, why not:

User-visible / Behavior Changes

List user-visible changes (including defaults/config).
If none, write None.

Diagram (if applicable)

For UI changes or non-trivial logic flows, include a small ASCII diagram reviewers can scan quickly. Otherwise write N/A.

Before:
[user action] -> [old state]

After:
[user action] -> [new state] -> [result]

Security Impact (required)

• New permissions/capabilities? (Yes/No)
• Secrets/tokens handling changed? (Yes/No)
• New/changed network calls? (Yes/No)
• Command/tool execution surface changed? (Yes/No)
• Data access scope changed? (Yes/No)
• If any Yes, explain risk + mitigation:

Repro + Verification

Environment

• OS:
• Runtime/container:
• Model/provider:
• Integration/channel (if any):
• Relevant config (redacted):

Steps

Expected

Actual

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

• Verified scenarios:
• Edge cases checked:
• What you did not verify:

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

• Backward compatible? (Yes/No)
• Config/env changes? (Yes/No)
• Migration needed? (Yes/No)
• If yes, exact upgrade steps:

Risks and Mitigations

List only real risks for this PR. Add/remove entries as needed. If none, write None.

• Risk:
  • Mitigation:

Changed files

• extensions/discord/src/actions/handle-action.guild-admin.ts (modified, +2/-2)
• extensions/discord/src/actions/runtime.guild.ts (modified, +5/-4)
• extensions/discord/src/actions/runtime.test.ts (modified, +167/-0)
• extensions/discord/src/actions/runtime.ts (modified, +1/-0)
• extensions/discord/src/channel-actions.ts (modified, +2/-0)
• extensions/discord/src/send.guild.ts (modified, +40/-11)
• src/agents/tools/message-tool.ts (modified, +1/-3)
• src/cli/program/message/register.discord-admin.ts (modified, +1/-1)