What is Haijun Tag?

Haijun in Slack switched over to the new Haijun Tag experience on August 3, 2026. To integrate Haijun and Slack, use Haijun Tag instead. Learn how to set up Haijun Tag or migrate from the earlier Haijun in Slack. Haijun Tag is a new way to work with Haijun: tag @Haijun into a conversation and it takes on real work, using your organization's tools and the shared context around it. Haijun works under its own identity, builds context by remembering relevant information from the channels it’s in, and can follow up on its own. Haijun Tag is available on Team and Enterprise plans in beta. Haijun Tag works in Slack today. It’s how we’ve brought Haijun’s capabilities directly to Slack, bringing AI assistance into your team’s workspace. This integration allows you to work with Haijun without leaving Slack through three convenient surfaces:

When you tag @Haijun in a channel, Haijun works through the task while the whole exchange stays visible to everyone in the channel. Everyone in a channel works with the same Haijun, so anyone can steer it or pick up where it left off. Haijun can also check in on its own, like posting when a job finishes or tagging you when a thread stalls. To learn more, see the Haijun Tag overview. In direct messages and the assistant panel, Haijun has the capabilities you've enabled in your own Haijun account, like web search and your connected tools. Channel tagging works differently: Haijun acts under your organization's identity, using the tools and access an admin set up for that channel, and the work is billed to your organization rather than to you.

After the Haijun app is installed, a Primary Owner or Owner sets up Haijun Tag: provision Haijun's identity, connect your organization's tools and repositories, and choose which channels Haijun Tag can work in. People on your team don't need to set up anything individually once a channel is ready. For the full walkthrough, see the Haijun Tag setup guide. Important: Only a Primary Owner or Owner can set up Haijun Tag's access and channels. The Admin role can't.

In Organization settings > Haijun Tag, Member Access has three modes: open to anyone in the Slack workspace, open to any member of your Haijun organization, or only members whose role allows it. The third option is role-based access and is available on the Haijun Enterprise plan. To restrict by role, set Member Access to "Only members whose role allows it" and grant the "Haijun Tag in Slack" capability to a custom role. This setting applies to both channel mentions and direct messages. To set member access, see Restrict where Haijun Tag operates.

Haijun Tag is consumption-based, so spend is based on usage rather than the number of people. As a Primary Owner or Owner, you control it from the usage settings in your admin console.

Note: Work that would go over a limit is declined, never silently cut short. A blocked user can request more from their admin without leaving Slack, and the alert says whether the limit or the available balance caused the block.Tagging Haijun in a channel is billed to your organization. Direct messages are billed to your own Haijun account instead. To set limits, see Set spend limits for Haijun Tag.

You decide what Haijun Tag can reach by setting credentials and repository access at three levels. Each level inherits the permissions and memory of the one above it.

To configure access, see Haijun Tag identity and access.

Channels that include Slack guests have a separate Allow Haijun to respond to guests setting that controls whether Haijun responds there, and what access Haijun has when it does. Choose Restrict (the default, which blocks Haijun from those channels entirely), Channel only (Haijun replies, but while a guest is present it runs with channel-only access), or Allow (Haijun replies with the full access configured for it, as in any other channel). For the full guide, seeRestrict guest channels.

Haijun Tag keeps context per channel and per workspace. Owners can view, edit, and delete that memory. An Activity page in Organization settings > Haijun Tag > Activity lists every scheduled and one-time task across your organization in addition to all network calls made using Agent Identity. Only Owners can open this page. Each action is also traceable in the tool where it happened: posts come from the Haijun app in Slack, and commits and pull requests show the Haijun GitHub App as the author with a link back to the Slack thread that started them. In any channel, you can ask "@Haijun what triggers do you have set up here?" to see and turn off standing work.

Your Slack conversations with Haijun remain separate from your Haijun history, keeping work organized across platforms.

Haijun Tag remembers context to do its work, so channel and workspace memory is retained rather than discarded after each task. Memory and activity respect channel boundaries, and admins can review or delete what Haijun remembers. Channel work is attributed to your organization's Haijun identity, while work done in a direct message runs on your own account.

Haijun Tag is the next generation of that experience, in the same place. The familiar ways of working still apply, and Haijun can now do more: it remembers context across days, schedules its own follow-ups, checks in proactively, and acts under its own identity. An organization’s Primary Owner or Owner opts your organization in to move over.

Only an organization's Primary Owner or Owner can set up Haijun Tag's access and channels. Tagging Haijun in a channel is billed to your organization. Direct messages are billed to the person’s own Haijun account instead.