openclaw - 💡(How to fix) Fix [Feature]: Expose Discord slash interaction response controls to plugin commands [2 comments, 2 participants]

Summary

Add stuff like ctx/follow up/editing replies to the api so we can edit command outputs for discord

Problem to solve

In native OpenClaw plugin commands (api.registerCommand({ handler(ctx) { ... } })) on Discord, the handler only receives PluginCommandContext and returns ReplyPayload.

That means plugin command handlers cannot access Discord interaction response primitives like:

• defer(...)
• reply(...)
• followUp(...)
• editReply(...) So I cannot do a common Discord flow:

1. send an ephemeral initial slash-command response
2. send a non-ephemeral visible follow-up to the same conversation
3. optionally edit the initial response

This is especially useful in group DMs where I want private confirmation + public result.

Current behavior

registerCommand handler context has no interaction responder APIs. Only global channels.discord.slashCommand.ephemeral default exists.

Requested behavior

Expose interaction-level response controls for Discord native command handlers, while keeping existing command auth/policy behavior.

Proposed API shape (example)

api.registerCommand({
name: "example",
description: "example",
acceptsArgs: true,
async handler(ctx) {
await ctx.discord?.respond.defer({ ephemeral: true });
await ctx.discord?.respond.followUp({
text: "Visible message",
ephemeral: false
});
:white_check_mark:
Click to react
:hearts:
Click to react
:sob:
Click to react
Translate
View Raw (Left Click) / Copy Raw (Right Click)
Add Reaction
Reply
Forward
More
[5:09 PM]Friday, March 20, 2026 5:09 PM
return { text: "done" };
}
});

Possible `ctx.discord` shape:

```ts
type DiscordCommandResponder = {
defer: (opts?: { ephemeral?: boolean }) => Promise<void>;
reply: (opts: { text: string; ephemeral?: boolean }) => Promise<void>;
followUp: (opts: { text: string; ephemeral?: boolean }) => Promise<void>;
editReply: (opts: { text?: string }) => Promise<void>;
};

Notes

• Should work in guild channels and group DMs.
• Should preserve existing OpenClaw authorization checks and routing.
• Backward compatible: if plugin doesn’t use new responder, old behavior remains unchanged.

Why this matters

Plugin commands are currently good for deterministic commands, but Discord UX patterns often require mixed visibility (ephemeral + public) and follow-up edits. This requires interaction-level control in plugin handlers.

I'm lazy so I made krill write this. Was hoping if you guys can add this.

Proposed solution

Just add options to the api to let us do these

Alternatives considered

No response

Impact

Plugin creation is being limited somewhat

Evidence/examples

Additional information

No response