arizuko › products › Slack team agent

Slack team agent

One agent in a Slack channel, with channel-scoped persona and thread context but per-teammate memory, grants, and private web chat.

system shape

• Channel as workspace. A Slack channel maps to an arizuko group folder. The product ships its base persona and rules in ~/.claude/CLAUDE.md; the channel’s own ~/CLAUDE.md overrides and extends them — allowed tools, citation rules, refusals, voice for this channel. #eng-support behaves differently from #design from #incidents. The folder mounts at /dav/<channel>/ over WebDAV — edit in Finder, rclone, or any editor.
• Per-user memory. The agent maintains a memory file per teammate (users/<channel>-<id>.md inside the channel folder) — preferences, recurring tasks, prior conclusions. Alice has hers, Bob has his. (Per-user secrets — distinct from memory — are spec 9/11, not yet shipped; folder-scoped secrets work today.)
• Per-user grants. Per-user grant rules decide which actions each member can ask the agent to take. A teammate’s sub-folder (e.g. eng/alice/) inherits from the channel and overrides only what differs — tweak one skill, keep everything else.
• Linked identities. GitHub, Google, Discord, and Telegram logins resolve to the same user record so the same person reaches the same memory and grants across surfaces.
• Private web workspace. The same channel exposes a token-bound chat URL (/chat/<token>/) — a browser chat against the same agent. Take the conversation off Slack onto a phone or laptop without losing context.
• Operator dashboard. /dash/ for grants, routing, scheduled tasks, admission queue, and per-channel health.
• Customisable, upgradable in place. Persona, skills, and channel rules are plain Markdown edited via WebDAV or chat. Each release ships migrations the agent applies as a per-group 3-way merge, preserving local edits.

example: shared thread, user-scoped state

#eng-support · thread

  alice  @bot summarize the fix from the cold-start runbook for this thread
  bot    Bundle growth after deploy is coming from broad SDK imports.
         Recommended: switch back to per-service imports.
         source: /docs/runbooks/lambda-cold-start.md:67

  bob    @bot save that conclusion to my notes
  bot    Wrote notes/lambda-cold-start.md in your user area.

  alice  @bot remember: prefer per-service imports for any new lambda
  bot    Saved to your memory.

Same thread, same channel CLAUDE.md, different resolved user state. The answer is visible to the team; Bob’s write lands in Bob’s user area; Alice’s preference lands in her memory file. Shared deliberation, user-scoped state. None of Bob’s notes are visible to Alice; none of either user’s memory leaks into the channel’s shared context.

how teammates use it

• AI sidebar pane. Click the AI icon in Slack to open a private pane against the channel agent — suggested-prompt buttons, a per-pane title, and full channel context. Details: slack pane.
• In a channel. The bot stays quiet by default. @bot mentions fire a turn. With the recommended routing rule (see setup), channel chatter lands in #observe — agent reads for context but doesn’t reply unless called on.
• In a thread. Replying to one of the bot’s messages counts as a mention — the agent answers in the same thread, with the thread’s history as context.
• In a DM. Every message is for the bot. No mention needed; replies come back in the same DM.
• File uploads. Drop a file on the bot or in a mentioned thread. The agent reads it via the file-read skill and replies in-thread.
• Reactions. An emoji reaction on a bot message can fire a turn if the route table is set up for it — handy for “thumbs up to confirm” flows.

data & trust

• Your server. Conversation history, channel files, per-user memory, channel-scoped secrets, agent state — all live under /srv/data/arizuko_<name>/. Backup is one tar of the directory; no DB dump.
• Default outbound paths. Slack for bot traffic; Anthropic for model calls. Any extra agent egress goes through crackbox and only reaches hosts you allowlist per channel.
• Channel-scoped secrets. API keys for tools the agent calls live in the secrets table (plaintext at rest; operator trusts disk + FS perms). Folder-scoped values are merged into the container's spawn env; Slack channels get folder secrets only (per-user overlay is 1:1-chat only).
• Channel boundary. A teammate in #eng-support sees that channel’s context and their own user area; #design’s files and persona are inaccessible unless granted explicitly.

per-user features (optional)

• Per-teammate memory file. Auto-created on a teammate’s first message; keyed by Slack user ID. Not shared with the channel; not visible to other teammates. Works without any sign-in — Slack workspace membership is the fence.
• OAuth sign-in (optional). A teammate who signs in at /auth/login with GitHub or Google links that identity to their Slack user. Memory and grants then survive across surfaces: the same person reaches the same notes from the web chat, from a DM, or from a different channel.
• Per-user secrets. Spec 9/11 — the arizuko user-secret CLI exists today, but the full broker model (per-tool, audit-logged) is not yet shipped. For now, secrets are folder-scoped.

same shape on Discord

Most of this maps to Discord 1:1 — guild channels behave like Slack channels (room JID, per-channel CLAUDE.md, per-user memory), threads behave like Slack threads. Three deltas worth flagging:

• No AI sidebar. Discord has no equivalent of Slack's assistant pane. Suggested-prompt buttons land on Discord via interaction components (different mechanism, not yet ported to discd). DM + mention flow works the same.
• Mentions look different. Slack uses <@USERID> in body; Discord uses <@123…>. Both are normalized to @<assistant-name> before reaching the agent.
• Routing JIDs differ. Slack: slack:T1234/channel/C5678. Discord: discord:guild/channel. Same grant primitive, different namespace.

Run the same product over both: install both adapters, route each channel to the same folder, agent doesn't care.

setup

arizuko create acme
cd /srv/data/arizuko_acme
$EDITOR .env             # set Slack/Discord/Telegram tokens; enable the adapters you want
arizuko run acme

# in Slack:
#   create the Slack App, set bot token + signing secret in .env
#   subscribe events to https://<your-host>/slack/events
#   invite the bot to a channel; teammates sign in via OAuth at /auth/login
#   linked identities resolve to the same user record; per-user state goes live

Full step-by-step is in the operator setup guide; the Slack adapter how-to covers Slack-specific quirks. Per-channel CLAUDE.md override lives in the channel folder; edit via WebDAV or directly on the server.

go deeper

• arizuko platform overview — the primitives this product is built on
• grants — per-user and per-group action scoping
• slack pane — the AI sidebar surface, pane-open events, suggested prompts
• personas — how voice + skills + frontmatter shape one channel’s agent
• Slack adapter how-to — Slack-specific quirks and verification steps
• auth — OAuth providers, account linking, identity resolution
• webdav — mounting the channel workspace
• crackbox — per-channel egress isolation
• deployment guide — first instance, first channel, first invite