Skip to content
Fork Docs
Guide v1

/chat clear

Clear the current channel’s AI conversation history.

Availability

Section titled “Availability”

Public source-edition command; execution remains conditional on installation, server policy and the running service. This reference is built from the repository, not a live Discord registration probe. Explicit registration contexts: server.

Syntax

Section titled “Syntax”
/chat clear

Angle brackets indicate required input; square brackets indicate optional input. In Discord, choose the command and fill its named options, rather than typing the brackets.

Parameters

Section titled “Parameters”

No registered options.

Permissions

Section titled “Permissions”

Required native member permission(s): ManageMessages (Administrator normally satisfies native permission checks).

Fork role access is evaluated using the underlying clearchat policy key, even when the slash name is grouped. Native Discord permission checks remain separate from Fork role grants. Sensitive commands fail closed before valid setup; native Administrator bypasses Fork’s role matrix, not Discord’s bot permissions or target hierarchy. See Permission model.

Examples

Section titled “Examples”
Slash options
/chat clear
Prefix equivalent and aliases
Default prefix
f!clearchat

Default prefix: f!; installations can configure another. Handler aliases: clearcontext, resetmemory. Aliases are prefix names, not additional slash commands.

Grouped prefix routes also delegate to the original handlers, but aliases retain that handler’s argument parsing. Conflicting aliases are rejected as ambiguous. Prefix replies are generally visible in the channel; prefer slash privacy controls for sensitive personal data.

Expected result

Section titled “Expected result”

Clears channel-chat context; it does not erase Discord messages or all users’ personal memory.

Failure cases

Section titled “Failure cases”

Requires Manage Messages and a server context. Storage failure may leave clearing unconfirmed. Check the returned error, current bot status and the relevant server permissions. A timeout or uncertain receipt is not proof that nothing happened; inspect state before repeating a mutation.

Usage limits

Section titled “Usage limits”

No fixed command-specific cooldown is declared in this reviewed entry. Discord rate limits, provider budgets, service admission and server policy can still apply; this is not an unlimited-usage promise.

Section titled “Related commands”
Section titled “Related guides”

Source edition v1 · Registration, direct handler and shared authorization review are hash-bound in the local documentation validation. This is not a production feature-availability certification.