Channel runtimes

Volt

Bring your project's agents into Slack and Microsoft Teams so authorized teammates can run the same execution engine without opening the web app.

What is Volt?

Volt is ViksaAI's channel runtime layer. For each project you can install a dedicated bot in Slack (available today) or Microsoft Teams (on the roadmap). Users message the bot in DMs, channels, or @mentions; Volt enforces platform access, loads your project's agent catalog, and runs the same Think→Act→Observe loop used in chat—streaming replies back into the channel.

Architecture

In the recommended Volt Engine mode, a lightweight Slack pod handles Socket Mode and Slack APIs only. Reasoning, agent selection, and execution run in volt-engine-service, which calls auth-service for membership, builder-service for the agent catalog, and pulse-service to run Python agents.

Request path
Slack user → Runtime pod (Socket Mode)
       → volt-engine-service
            ├─ auth-service (project membership)
            ├─ builder-service (agent catalog)
            └─ pulse-service (execute agents)

Who can use the bot?

There is no separate Volt user allowlist. A Slack or Teams user must be a member of the ViksaAI project linked to the runtime. The bot resolves their workspace email and calls auth-service; access is denied if they are not a project member (fail-closed).

Which agents they can invoke follows your project's builder catalog and platform RBAC—the same rules as the web app.

Runtime architecture

The Slack runtime pod is transport-only: it connects to Slack, forwards turns to volt-engine-service, and streams replies. Brain, memory, Mongo, and agent dispatch all run on the engine — not inside the pod.

Guides

Dashboard

Open Volt in the project sidebar (requires chat module access). From there you can generate a Slack app manifest, validate credentials, install or uninstall the runtime, and monitor deployment status.

  • Navigate to your project → Volt in the left nav.
  • Choose Slack and follow the install wizard.
  • See Slack setup for token and scope requirements.