Reach your agents from where you are.

A channel lets you send tasks, read replies, and answer approvals outside the browser. You can keep working from your phone and let the agent carry on at the desk.

VERSION 0.1.20 · CHANNELS

The channels available in this release are Telegram and Slack. Browser chat always works; adding or removing a channel does not affect it.

Workflow reviews

When a workflow step marked Check with me first finishes, the review arrives as a card on Telegram or Slack, with Approve, Request changes and Stop run. Answering in one place updates the others, and the card then shows the outcome. See Workflows.

Reviews can also have a Telegram bot of their own, kept apart from your chat bot. Set it up with the Settings button on the Workflows page, under Channels. Without one, reviews use your usual Telegram bot, and with no channel at all they wait in Approvals.

How a channel is set up

You configure your own channels from your profile. An administrator can also configure a channel for another person, and the onboarding wizard offers an optional Telegram setup on first run.

Each channel needs a default target agent and a sync mode:

• Approvals + final reply — you receive the prompt you sent, approval requests with their context, and the final reply.
• Mirror chat — you also receive the completed assistant replies, matching what the web chat shows.

Both modes echo your own prompt so the conversation reads in context. Channels do not stream tokens as they are generated; you receive the message when it is ready.

Telegram

1. Open Telegram’s official BotFather, run /newbot, and copy the token it issues. Kautuka cannot create a bot for you.
2. Open a private chat with the new bot and send it any message, so Telegram creates the conversation.
3. Enter that private chat’s numeric ID in Kautuka, paste the bot token, choose the default agent, and select Save & Connect.

Kautuka verifies the bot, removes any webhook, publishes its supported commands, and uses long polling for incoming messages. Save & Connect validates the bot and polling setup; Verify with Test Prompt confirms delivery to the chat ID you entered. Kautuka never asks you to send credentials to a third-party ID bot.

Slack

Slack needs a bot token and an app-level token, because Kautuka uses Socket Mode instead of a public inbound webhook.

1. Create an app in the official Slack app dashboard, using From an app manifest and the manifest Kautuka offers.
2. Install the app to the intended workspace and copy the bot token beginning xoxb-.
3. Under Basic Information → App-Level Tokens, generate a token with connections:write. It begins xapp-.
4. Paste both tokens into Kautuka and select Verify with Test Prompt.

Kautuka validates the bot identity, every scope declared by the manifest, and the Socket Mode token before reporting the channel ready. The manifest also creates Kautuka’s slash commands, so you do not register them one by one. If Kautuka reports missing scopes, reinstall from the current manifest: Slack does not apply newly requested scopes to an existing installation automatically.

Changing or replacing a channel

• Provider credentials are encrypted and stored apart from channel records. Kautuka never displays a saved token again.
• Suspend stops new inbound and outbound work immediately and releases the runtime credentials while preserving the registration. Use it before planned maintenance or while investigating a suspected compromise.
• If you suspect a channel is compromised, revoke the provider token in the provider’s console first, then suspend and recover the Kautuka registration.
• Replace credentials clears only the secret fields in the browser. Create the replacement in the provider’s console, paste it, and run Save & Connect. Revoke the old token only once the replacement is confirmed working.
• Kautuka does not reactivate a channel merely because a credential was saved. Replace the credential, then let provider validation succeed.

Never paste provider tokens into support messages or logs.