Tool Call Consent

Three Decisions​

The modal buttons currently render in Traditional Chinese (no i18n yet):

Auto-skip Rules​

The SDK does not show the modal and handles the call directly in two cases:

1. alreadyAllowed: true — the backend marked it as already authorized (e.g. an earlier turn chose Allow for This Chat); auto ALLOW_ONCE.
2. Allow for This Chat within this batch — once a tool has been granted Allow for This Chat in the same batch, later calls to the same toolset / toolName are auto ALLOW_ALWAYS.

Usage​

No configuration is needed — as long as the Bot Provider's Toolset has consent enabled, the SDK handles it automatically:

<Chatbot
  config={{
    apiKey: 'your-api-key',
    botProviderEndpoint: 'https://api.asgard-ai.com/ns/{namespace}/bot-provider/{botProviderId}',
  }}
  customChannelId="your-channel-id"
/>

Two-step Deny​

To avoid accidental clicks, Deny is a two-step submit:

1. First 拒絕 (Deny) click — expands the reason input, and the button changes to 送出拒絕 (Send Deny).
2. Second 送出拒絕 (Send Deny) click — actually submits the rejection (reason may be left empty).

Other Turns Are Refused While a Consent Is Pending​

While the consent modal is up, the channel is paused on the server and accepts only a consent reply; every other turn is rejected outright ("use RespondToolCallConsent"). So sendMessage() and nudge() refuse locally, up front, throwing ChannelAwaitingConsentError:

import { isChannelAwaitingConsentError } from "@asgard-js/core";
 
try {
  await channel.sendMessage({ text: "never mind, different question" });
} catch (error) {
  if (isChannelAwaitingConsentError(error)) {
    // Answer the consent first — that is the only way forward
  }
}

The only way out is replyToolCallConsents(); the guard releases itself once the consent is answered. The error's processId is the paused batch's process id, but it is an empty string after a rejoin (a prompt rebuilt from the backend's durable pause state deliberately leaves it blank), so treat it as a diagnostic hint, never as a key.

With the built-in <Chatbot> you do not wire any of this: the composer and the Nudge entry point are both locked while a consent is pending, so the user cannot reach them. The guard is there for headless / custom shells.

If the consent reply itself fails, the pending state is restored and the modal stays put for a retry rather than leaving you with neither.

Theming​

The modal follows the Chatbot's --asg-color-* design tokens by default, so no extra setup is needed.

In addition, since 0.2.61, the modal's accent color (tool-name highlight, primary button, focus ring) automatically follows the brand color you set via theme — the resolution order is chatbot.primaryComponent.mainColor → chatbot.mainColor → userMessage.backgroundColor, and the text painted on the accent comes from the corresponding secondaryColor. So once you set a brand color through theme, the consent modal usually needs no manual CSS-variable overrides.

If you still need to override individual colors, set the CSS variables on any parent element:

.my-chatbot-wrapper {
  --asgard-consent-modal-bg: #0f172a;
  --asgard-consent-modal-accent: #6366f1;
  --asgard-consent-modal-danger: #ef4444;
}