Tako AI v2.2: Your Okta AI Agent, Now in Slack

Your Okta AI agent is now available directly in Slack. No context switching, no extra tabs — just type a question in any channel and get answers about your Okta tenant instantly.

Huge shoutout to our newest contributor @LcTrKiD for the original Slack bot PR — we built on top of it to ship v2.2.

/tako Commands

Ask anything about your Okta tenant directly in Slack:

/tako list active users in Engineering with no MFA enrolled
/tako which apps use SAML and have more than 100 assigned users?
/tako show contractors who haven't logged in for 60 days

Browse and re-run past queries:

/tako history     → your last 5 queries with ▶ Run and ☆ Star buttons
/tako favorites   → your starred queries, always one click away
/tako help        → full command reference

Results post back to the thread. Small sets get an inline table, large ones attach as CSV. Re-running from history skips the AI pipeline entirely — instant results from the saved script.


Security First

The bot is locked down by default — nobody can use it until you explicitly grant access. Configure access in your .env:

Variable Purpose
SLACK_ALLOWED_EMAILS Comma-separated list of allowed user emails
SLACK_ALLOWED_GROUPS Comma-separated Slack user group handles (e.g. okta-admins,it-team)
SLACK_ALLOW_ALL_USERS ⚠️ true opens the bot to your entire workspace — use only in fully trusted environments
SLACK_OPERATION_MODE socket (default, no public URL needed) or http

Socket Mode means Tako opens an outbound WebSocket to Slack’s servers — no port forwarding, no reverse proxy, no public URL required. History and favorites are ephemeral and private to each user.

Get Started

This feature started with a community PR — that’s exactly the kind of contribution that keeps this project moving forward. Setup takes about 10 minutes if you already have Tako running.

The Slack integration is opt-in and disabled by default. Set ENABLE_SLACK_BOT=true in your .env to activate it and configure access control — see the setup guide below for full instructions.

Questions or ideas? Open an issue on GitHub or email us at support@fctr.io.

—Dan & the Fctr team

Leave a Reply