/tasks commands not showing in discord | Friends of the Crustacean 🦞🤝 | Page 1

quasi grotto Apr 15, 2026, 9:11 PM

#

I'm interested in leverage the /tasks commands in discord but they are not available to me.

chilly cedarBOT Apr 15, 2026, 9:12 PM

#

/tasks is built in, so if it is not showing in Discord, it is usually one of these:

Native commands are off
- commands.native: true or channels.discord.commands.native: true
The bot was invited without applications.commands
- In Discord OAuth, the bot needs both bot and applications.commands
Gateway needs a restart after config changes
- openclaw gateway restart
It is an auth issue, not a registration issue
- If the command shows up but says you are not authorized, check channels.discord.guilds... allowlists or commands.allowFrom

Also, once /tasks works, it only shows tasks linked to the current session, so “no tasks yet” is normal. “Command does not exist” is a different problem.

First thing, what does this show?

#

openclaw --version

If you want, also paste:

openclaw status
openclaw gateway status

Docs:

If you paste your Discord config block, I can sanity check it quickly.

quasi grotto Apr 15, 2026, 9:22 PM

#

commands.native is set to auto channels.discord.commands.native doesnt exist. OpenClaw 2026.4.11 (f17fd73)

chilly cedarBOT Apr 15, 2026, 9:23 PM

#

Yep, with commands.native: auto on 2026.4.11, Discord native commands should already be on. You should not need channels.discord.commands.native just to get /tasks.

So I’d focus on these, in order:

Bot invite scope
- make sure the bot was invited with both:
  - bot
  - applications.commands
Restart the gateway
```
openclaw gateway restart
```
Check whether this is “no commands registered” vs “auth blocked”
- If no OpenClaw slash commands show up at all, it is usually registration/invite scope.
- If commands like /help or /status show up, but /tasks does not, that’s weird and I’d force a refresh.

#

If /tasks shows up but says you are not authorized, check commands.allowFrom and channels.discord.guilds... allowlists.

Force a re-register once
Since commands.native: false clears registered Discord commands on startup, a good reset is:
- set commands.native: false
- restart once
- set it back to auto (or true)
- restart again

If you want, paste:

openclaw status
openclaw logs --follow

And one quick clarifier: do you see any OpenClaw slash commands in Discord right now, or is it just /tasks that is missing?

quasi grotto Apr 15, 2026, 9:28 PM

#

now all of the commands have gone

chilly cedarBOT Apr 15, 2026, 9:29 PM

#

That part is expected if you tried the reset. commands.native: false clears the Discord slash commands on startup.

Next step:

set commands.native back to true (or auto)
restart the gateway again

I’d use true for now, just to remove ambiguity.

If they still do not come back after that, the next likely cause is the bot invite missing applications.commands. In that case, re-invite the bot with both scopes:

bot
applications.commands

If you want, paste your commands + channels.discord config block and I’ll check it. Docs: https://docs.openclaw.ai/tools/slash-commands and https://docs.openclaw.ai/channels/discord

quasi grotto Apr 15, 2026, 9:30 PM

#

"commands": {
"native": true,
"nativeSkills": "auto",
"restart": true,
"ownerDisplay": "raw"
},

"discord": {
  "enabled": true,
  "allowBots": true,
  "groupPolicy": "allowlist",
  "streaming": {
    "mode": "off",
    "block": {
      "enabled": true
    }
  },

chilly cedarBOT Apr 15, 2026, 9:31 PM

#

The native-command part looks fine now. commands.native: true is correct.

One thing is missing for actual guild use though:

you have groupPolicy: "allowlist"
but I do not see a channels.discord.guilds entry

So once the commands come back, OpenClaw will likely block them in that server unless your guild is explicitly allowlisted.

Something like:

channels: {
  discord: {
    enabled: true,
    groupPolicy: "allowlist",

#

    guilds: {
      "YOUR_SERVER_ID": {
        requireMention: false,
        users: ["YOUR_USER_ID"],
      },
    },
  },
}

Important nuance:

missing guilds allowlist explains “I can’t use commands in the server”
it does not usually explain “all slash commands disappeared from Discord UI”

For the disappearing part, the most likely culprit is still the bot invite missing applications.commands. I’d check that next and re-invite the bot if needed.

#

If you want to narrow it down fast, paste these two:

openclaw status
openclaw gateway status

And if this fixed it later, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it.

quasi grotto Apr 15, 2026, 9:33 PM

#

I also have channels inside my guilds do I need to add users to them as well?

chilly cedarBOT Apr 15, 2026, 9:33 PM

#

No, not by default.

With groupPolicy: "allowlist":

you must allowlist the guild
you do not need to add users to every channel
you only need per-channel entries if you want to restrict which channels are allowed

Behavior is:

guild allowlisted, no channels block → all channels in that guild are allowed
guild allowlisted, with a channels block → only the listed channels are allowed

And same idea for users:

put users / roles at the guild level if the same people can use all channels
only add users / roles at the channel level if you want extra per-channel restrictions

#

So the simple setup is usually:

channels: {
  discord: {
    groupPolicy: "allowlist",
    guilds: {
      "YOUR_SERVER_ID": {
        users: ["YOUR_USER_ID"],
      },
    },
  },
}

Then later, if you want only some channels, add a channels block under that guild.

#

Docs: https://docs.openclaw.ai/channels/discord

quasi grotto Apr 16, 2026, 1:08 AM

#

how do i launch task flows?

chilly cedarBOT Apr 16, 2026, 1:09 AM

#

Short version: you don’t directly launch Task Flows from chat/CLI yet.

Right now, Task Flow is the orchestration layer above background tasks. The public commands are for inspection/management, not creation:

openclaw tasks flow list
openclaw tasks flow show <lookup>
openclaw tasks flow cancel <lookup>

So if you’re asking “how do I start one?”, the answer is basically:

you start the underlying work (ACP run, subagent, cron, plugin workflow, etc.)
Task Flow is what coordinates or mirrors that multi-step work

If your real goal is to run a multi-step workflow yourself, the better user-facing options are:

#

Lobster for deterministic workflows/pipelines
cron jobs for scheduled automation
ACP / subagents for detached agent work

Docs:

If you tell me the workflow you want to launch, I can point you to the right mechanism instead of the wrong abstraction.

quasi grotto Apr 16, 2026, 2:06 AM

#

my agent wants to spawn tasks with /acp can they do that ?

chilly cedarBOT Apr 16, 2026, 2:07 AM

#

Yes, ACP spawns create background tasks.

So if your agent kicks off an ACP session, /tasks can show it.

The nuance is:

You can do it from chat with /acp spawn ...
The agent should usually do it via the ACP runtime directly, meaning sessions_spawn with runtime: "acp", not by literally sending /acp to itself

So, practically:

human/operator path:
/acp spawn codex --bind here
agent/internal path:
spawn an ACP session with runtime: "acp" and an explicit harness like codex

A plain-language request like:

#

“run this in Codex”

should also route to ACP automatically, and that spawn is tracked as a background task.

Two gotchas:

ACP must be enabled/working
If you want Discord thread spawning, you also need the Discord ACP thread-bind support enabled

Docs:

If you want, I can show you the exact /acp spawn ... shape for:

same channel bind
new thread
one-shot run

#

persistent Codex session

quasi grotto Apr 16, 2026, 2:11 AM

#

yes please

chilly cedarBOT Apr 16, 2026, 2:12 AM

#

Yep, here are the clean starter shapes.

1) Same channel, keep talking here

/acp spawn codex --bind here

binds the current Discord channel/thread to Codex
does not create a child thread

2) New thread when possible

/acp spawn codex --mode persistent --thread auto

if you’re already in a thread, it binds that thread
otherwise OpenClaw can create/bind a child thread if Discord ACP thread spawning is enabled

3) One-shot run, unbound

#

/acp spawn codex --mode oneshot --thread off

fire-and-forget style
no persistent bind

4) Persistent Codex session in this chat

/acp spawn codex --mode persistent --bind here

good default if you want “this channel is now Codex-backed”

Useful extras

/acp spawn codex --bind here --cwd /absolute/path/to/repo
/acp spawn codex --bind here --label my-codex-session

#

After spawning

/acp status
/tasks
/acp steer keep going, focus on the failing tests
/acp close

Two gotchas

--bind here and --thread ... cannot be combined
for thread creation on Discord, you need ACP thread spawning enabled for Discord

If you want, I can also give you the exact Discord config flags needed for /acp spawn ... --thread auto.

#/tasks commands not showing in discord

1) Same channel, keep talking here

2) New thread when possible

3) One-shot run, unbound

4) Persistent Codex session in this chat

Useful extras

After spawning

Two gotchas