On this page

How Iterium Actually Works

One agent, one tool loop, three surfaces — nothing aspirational on this page

How Iterium Actually Works

One agent, one tool loop, three surfaces — nothing aspirational on this page

Iterium is a single agent with a single tool loop (the same one behind the Dashboard Terminal, the REST API, and the SDK) — reachable from three surfaces. This page documents exactly how each one works today, including what's live and what isn't yet.

  • Dashboard Terminal — full chat UI, the only surface where you can pick a role persona. Two catalogs behind a toggle: software-team roles (PO, Tech Lead, QA, Security...) and small-business roles (Customer Care, Sales, Collections...).
  • Slack — mention @Iterium or DM it, live in production today.
  • Microsoft Teams — the adapter code exists and is wired up, but isn't active yet (see below).

Slack

Live today — mention @Iterium or send it a direct message

  1. 1Mention "@Iterium" in any channel it's been invited to, or send it a direct message — no slash command needed.
  2. 2Iterium replies in the same thread. On the first message of a brand-new thread, it identifies itself as AI before anything else (EU AI Act Article 50 transparency, applied even though it's a Mexico/US-facing product).
  3. 3Ask it to check a Jira ticket, review a GitHub PR, search Confluence, or draft a user story — it picks the right tool on its own.
  4. 4Keep replying in the same thread for follow-ups — Iterium keeps the conversation context.
@Iterium analiza el ticket PROJ-1 y dime si está listo para desarrollo
@Iterium revisa el PR #234 de github.com/tu-org/tu-repo
@Iterium busca en Confluence la especificación de autenticación
@Iterium crea una historia de usuario para el login con Google

# Pick a role for the whole thread — say it once, it sticks:
@Iterium como tech lead: revisa el PR #234
@Iterium as security: check this repo for exposed secrets

Start a message with "como <role>:" or "as <role>:" (e.g. "como tech lead:", "as po:") to set that persona for the rest of the thread — Iterium confirms the switch and every later message in that thread reuses it automatically, no need to repeat it. Works with any of the 20 roles — software-team or small-business — by their short name (qa, po, collections...) or full label (Tech Lead, Customer Care...).

What does this need to work?

SLACK_BOT_TOKEN and SLACK_SIGNING_SECRET, plus an Events API Request URL pointing at /api/slack/events — already configured on this deployment.

Does it work in a DM as well as a channel?

Yes — direct messages don't need the @mention, any message you send it is treated as a request.

What happens with images?

Attach a screenshot in the same message — Iterium can analyze it and relate it to a Jira ticket or GitHub issue.

How long does a thread remember its role?

30 days, same retention as chat history. Just start a new thread (or say "como scrum master:") to reset to the default persona.

Microsoft Teams

Built into the code, not active yet — the honest status

Teams support already exists in the codebase via @chat-adapter/teams, wired to a generic webhook at /api/webhooks/teams — the exact same /api/chat engine Slack uses. It isn't live yet: TEAMS_CLIENT_ID and TEAMS_CLIENT_SECRET are unset, so there's no registered Bot Framework app for Teams to talk to.

  1. 1Register a bot in Azure Bot Service (or the Teams Developer Portal) to get an App ID and app password.
  2. 2Add TEAMS_CLIENT_ID and TEAMS_CLIENT_SECRET to the environment.
  3. 3Set the bot's messaging endpoint to https://iterium.xyz/api/webhooks/teams.
  4. 4Once connected, usage mirrors Slack exactly: @mention Iterium in a channel, or message it directly — same engine, same tools, same human-approval gate on critical actions.

This isn't a roadmap promise dressed up as a feature — the adapter code is real and already wired to the same engine as Slack. It's genuinely one Azure app registration away from working, not a rebuild.

What Each Integration Actually Does

Every tool call, traced to the real function behind it

Jira

Reads tickets, updates status and fields, drafts new Given/When/Then user stories, and can call any advanced Jira REST endpoint directly — managing sprints, boards, backlog, and worklogs.

Confluence

Searches existing documentation, and can create or update pages directly when asked.

GitHub

Reviews pull requests, lists issues, checks CI/Actions status, lists merged PRs for release notes, reads Dependabot and code-scanning alerts, and — for the Developer role only — opens draft pull requests. It never commits directly to your base branch.

Figma

Extracts colors, typography, and CSS specs from a specific file node.

Slack (as a data source, not just a chat surface)

Iterium can also read a named channel's recent history — used by the Docs role to draft runbooks from an incidents channel, and by Support to triage requests from a support channel.

Choosing a Role

14 personas today, same agent and tools underneath

The Dashboard Terminal lets you pick which role Iterium acts as — Product Owner, Tech Lead, QA, Security, Developer, and more — each with a focused system prompt over the exact same tool loop. In Slack, the same 14 roles are available via a "como <rol>:" / "as <role>:" message prefix (see the Slack section above) — the persona sticks to that thread until you change it.

  1. 1Open the Add-ons tab in the Dashboard.
  2. 2Any module marked "Available Now" has a green "Try It in Terminal" button.
  3. 3Clicking it opens the Terminal with that persona pre-selected — or switch roles anytime from the pill selector at the top of the Terminal.

Try It Yourself

No credit card, live in minutes

Launch the app and open the Terminal — it's the fastest way to see the real tool loop in action before wiring up Slack or Teams for your team.

Launch App Free