Meet Archyl in Slack & Teams: Ask Your Architecture, In Chat

The fastest question about your architecture is the one you never have to leave your conversation to answer. "What depends on the payments service?" "Who owns the API gateway?" "Is there an ADR about the move to event sourcing?" — these come up in the middle of a thread, and the answer usually means someone context-switching into a tool, digging, and pasting a screenshot back.

Today that changes. Archyl now lives in Slack and Microsoft Teams. Mention @Archyl, ask in plain language, and get an answer grounded in your real architecture — without leaving the channel.

Two ways it answers

The bot meets you where your team is, and it has two modes:

  • Direct — a single AI answer built from your project's architecture context (C4 model, ADRs, docs, ownership).
  • Agentic — when you give the bot an API key, it goes further: it calls live MCP tools to look things up and even make changes, and it shows its work — each 🔧 tool it runs streams into the thread before the final answer.

Ask "what depends on the payments service?" and you'll watch it call find_relevant_context and impact_of, then come back with: 3 systems depend on PaymentService: Checkout, Billing and the Mobile API — Billing is owned by the Payments team. Grounded in your graph, not guessed.

Set it up in a minute

Both connect from Organization → Bot:

  • Slack — click Add to Slack, authorize, then mention @Archyl in any channel. Answers come back in a tidy thread.
  • Microsoft Teams — download the app package, install it, and run @Archyl link <code> once to bind your workspace. Then mention away.

To turn on agentic mode, pick an API key under Bot → MCP tools. A read-scoped key lets the bot look things up; a write-scoped key lets it create ADRs and documentation too. Full steps are in the Slack & Teams Bots docs.

Built to be safe by default

  • The bot answers with the permissions of the admin who connected it, scoped to your organization.
  • In agentic mode, what it can read or change is governed by the scope of the API key you pick — choose read-only if you only want answers.
  • Tokens are encrypted, and questions count toward your usage just like the in-app chat.

Why it matters

Architecture knowledge has a half-life. The moment it's locked inside a tool nobody opens mid-conversation, it starts to drift from how the team actually thinks. Putting Archyl in Slack and Teams collapses that gap: the C4 model, the ADRs, the ownership map — all one mention away, in the place decisions actually get made.

And because the agentic bot uses the same MCP tools your AI coding agents use, the answer your teammate gets in Slack is the same ground truth your agents reason over in the IDE. One source, everywhere.

Try it

Open Organization → Bot, connect Slack or Teams, and ask your first question. Your architecture just joined the conversation.

Read the setup guide →