Skip to content

Discord bridge overview

The Discord bridge lets a private Discord bot ask the local Kanade daemon for status, recall, or a bounded lane response. It exists so the operator can reach Kanade from Discord without making the workstation public.

The posture is strict:

  • The bot is self-hosted.
  • Requests are HMAC-signed with KANADE_DISCORD_BRIDGE_SECRET.
  • The daemon can restrict remote addresses with KANADE_ALLOWED_REMOTE_ADDRS.
  • Discord user and channel IDs are allowlisted in Kanade settings.
  • Rate limits are enforced before a turn starts.
  • The daemon records the last incoming bridge state for diagnostics.

The bridge is not a public chatbot. It is a narrow relay into the same local workstation that already owns lanes, memory, and mission context.

The current command set is small:

  • /status checks daemon and bridge readiness.
  • /ask starts a signed ask against a selected lane.
  • /recall queries Kanade memory without launching a model turn.

User-side Discord proof remains a separate verification target until the operator runs the commands from their Discord client.