#Persistent ACP Channel

1 messages · Page 1 of 1 (latest)

slate notch
#

What will happen after /acp close on a persistent ACP discord channel?

nimble sageBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

raw talonBOT
stone ledgeBOT
#

Let me verify the docs path and the command behavior in the repo.

#

There’s a subtle difference here between a temporary thread/current-chat binding and a top-level persistent bindings[] config, so I’m checking the code path too.

#

Short version:

  • /acp close closes the ACP session and removes the live binding.
  • It does not delete the Discord channel/thread itself.

The important nuance is where the persistence came from:

  1. Runtime-created persistent bind
    Example: /acp spawn ... --bind here or --thread auto
    → After /acp close, that bind is gone, and follow-up messages stop routing to that ACP session.

  2. Config-based persistent ACP channel via top-level bindings[]
    → /acp close closes the current runtime session, but the config binding still exists.
    → On the next message in that channel, OpenClaw will recreate/ensure the configured ACP session again and route messages back into it.

So if you mean a truly persistent ACP Discord channel from bindings[], /acp close is basically “close it for now”, not “turn this channel off permanently”.