You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
One agent in Slack, Mattermost, Telegram, a widget and the API
#2221
A published agent in Vstorm AgenticOS answers in eight places (as of v0.0.522), and every one of them runs the same frozen version through the same runner:
Where
What it needs
Who the person is
Web chat (the console)
nothing
a signed-in member
Website widget
a <script> tag
anonymous, or a user your backend vouches for
Raw WebSocket
an embed key
whatever your integration says
Hosted page
a link
anonymous
HTTP API
a session or an API key
whoever holds the credential
Slack
a bot token
a Slack account, optionally linked to a member
Telegram
a bot token
a Telegram account, optionally linked
Mattermost
a bot token and your server URL
a Mattermost account, optionally linked
The widget is the shortest path. Create the embed under the agent's Availability tab, list the sites it may run on, and paste one line:
The spending limit is checked before each model request, never after.
The run belongs to exactly one organization and is recorded with the surface that admitted it (web, embed, api, slack and so on), so you can see how an agent is actually used.
A failed run is still in history with what it spent.
What differs, on purpose:
An empty allowed-sites list allows nothing. The widget's key is public by construction, so the origin list is what stops someone else running your agent on your bill. Publishing without one is refused.
Personal tools need a linked account in chat. An MCP binding that speaks to Notion or Jira as the person who wrote the message has no account to use for an unlinked Slack or Telegram user, so the agent tells them to /link first. The link is minted only in a direct message (it's a bearer credential), lasts fifteen minutes and works once.
One bot answers as one agent. Binding a second agent to the same bot is refused. One agent can sit behind a Slack bot, a Telegram bot and two Mattermost servers at once.
A thread it joins partway is read first, up to fifty messages and four files, where the platform has threads. Telegram has none.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
A published agent in Vstorm AgenticOS answers in eight places (as of v0.0.522), and every one of them runs the same frozen version through the same runner:
<script>tagThe widget is the shortest path. Create the embed under the agent's Availability tab, list the sites it may run on, and paste one line:
What stays the same on every surface:
web,embed,api,slackand so on), so you can see how an agent is actually used.What differs, on purpose:
/linkfirst. The link is minted only in a direct message (it's a bearer credential), lasts fifteen minutes and works once.Details: Channels
Question: where do people in your company actually ask questions: a chat tool, a web page, email?
All reactions