Skip to content

Language and time

Set the language of the bot’s Discord text and its time zone in roundtable.config.ts:

export default {
// ...
locale: "zh-TW",
timeZone: "Europe/Berlin",
} satisfies RoundtableConfig;
Key Values Default
locale "en" or "zh-TW" "en"
timeZone An IANA time zone name, such as Europe/Berlin or Asia/Taipei "UTC"

The host applies both settings at startup and keeps them for the life of the process. Restart the bot after changing them.

locale chooses the message catalog for the text the bot shows in Discord. Both catalogs have the same keys. This includes:

  • The approval and question cards, with their buttons and footers.
  • The stop button and the note on a long turn.
  • The /roundtable command’s description, its refusal for non-owners, and the schedule panel.
  • The self-updating status message and the notices a conversation posts, such as a failed reply or a stopped turn.
  • How a time zone is named in tool descriptions: the English catalog uses the IANA name (Europe/Berlin), and the zh-TW catalog uses the place name (Berlin).

A value other than en or zh-TW is an error:

config locale: expected a locale, en or zh-TW, got "<value>". Fix the value in roundtable.config.ts.

Some text has its own language:

  • Audit-log reasons and Discord administration tool refusals are English in both locales.
  • The text the core adds to the agents’ prompts is English.
  • Your prompts, your agents, and your plugins’ text are yours to write in any language.

timeZone is the zone the bot uses for anything with a clock time.

  • A schedule’s one-off time ("YYYY-MM-DD HH:MM") and its repeating time of day ("HH:MM") are in this zone, and the schedule tools say so in their descriptions.
  • Time stamps in schedule messages and lists, and in the output of channel_read, use it.
  • “Today”, for the upcoming events that go into each speaker’s memory block, is the date in this zone.

roundtable doctor accepts any non-empty string; the bot checks the time zone name at startup. A zone the runtime does not recognise stops roundtable start once the checks have passed:

Invalid time zone: <value>

For schedules in practice, see Schedules and background work.