slack

Slack bot transport — runs as a NestJS module with socket-mode lifecycle. No agent-visible tools.

Source: packages/oracle-runtime/src/plugins/slack/

Attribute	Value
Visibility	silent
Stability	stable
Category	core
Default state	Opt-in — not in BUNDLED_PLUGINS. Construct it and pass it in plugins.
Depends on	—

Summary

Connects a Slack bot to the oracle. The plugin contributes no agent-visible tools — it is purely a transport. The agent does not know Slack exists; it just sees inbound messages on the Slack client. Ships its own NestJS module so the bot client can use OnModuleInit / OnModuleDestroy for socket-mode lifecycle and inject the Tier-0 services it needs (messages, sessions, cache).

Environment variables

Var	Required	Description
SLACK_BOT_OAUTH_TOKEN	yes	Slack bot OAuth token. Triggers auto-detect.
SLACK_APP_TOKEN	no	App-level token (required for socket mode in production).
SLACK_USE_SOCKET_MODE	no	Defaults to 'true'.
SLACK_MAX_RECONNECT_ATTEMPTS	no	Coerced number; defaults to 10.
SLACK_RECONNECT_DELAY_MS	no	Coerced number; defaults to 1000.

What it contributes

• Tools: none.
• Sub-agents: none.
• Middleware: none.
• HTTP routes: none directly.
• Nest module: SlackModule (registered via getNestModules) — owns the Slack socket-mode client lifecycle.
• Shared state: none.

Opt out / Opt in

slack is not in BUNDLED_PLUGINS, so features never reaches it. Load it by passing an instance:

import { createOracleApp, SlackPlugin } from '@ixo/oracle-runtime';

const app = await createOracleApp({
  config,
  plugins: [new SlackPlugin()],
});

Its autoDetect still applies once wired: without SLACK_BOT_OAUTH_TOKEN it is skipped at boot and no module is registered.

When to use it

• You want the same oracle reachable from Slack as well as the web client.

Where to read next

Add HTTP endpoints

Nest-module contribution pattern.

Visibility tiers

What silent visibility means (here, the plugin has no tools at all).