/ask
Ask Fork a question or give it a task, optionally with an image.
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, bot DM, private channel.
Syntax
Section titled “Syntax”/ask <prompt:String> [image:Attachment]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”| Name | Type | Required | Allowed values / bounds | Default when omitted | Description |
|---|---|---|---|---|---|
prompt |
String | Yes | No registration choices declared; handler validation applies. | Required input | Your question, instruction, or coding task for Fork |
image |
Attachment | No | No registration choices declared; handler validation applies. | No attached image. | Optional image attachment for multimodal analysis or drawing reference |
Permissions
Section titled “Permissions”No native default-member permission is declared for this path, and no additional native member permission was identified in its reviewed direct handler.
Fork role access is evaluated using the underlying ask 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”/ask prompt:Explain role hierarchy in DiscordPrefix equivalent and aliases
f!ask Explain role hierarchy in DiscordDefault prefix: f!; installations can configure another. Handler aliases: q, ai, fork. Aliases are prefix names, not additional slash commands. Handler-declared usage: f!ask <prompt> [image attachment].
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”Fork replies in the conversation. Authorized tools may run only within the caller’s and server’s current permissions.
Failure cases
Section titled “Failure cases”Provider unavailability, exhausted usage budget, an inaccessible image, tool refusal or the per-user request limit can prevent completion. 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”8 requests per user per 60 seconds on the ask path, plus deployment/provider accounting limits.
Related commands
Section titled “Related commands”Related guides
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.