Feature Description

Add Microsoft Teams as a supported Hermes gateway / messaging platform.

This would let Hermes participate in Teams similarly to the existing messaging adapters (for example Slack, Discord, Telegram, DingTalk, Feishu, etc.), instead of requiring a custom external bridge.

Motivation

Microsoft Teams is a primary communication platform in many enterprise environments.

Teams support would make Hermes much more useful for work coordination scenarios such as:

• being mentioned in group chats or channels and replying in-thread
• direct-message interactions with Hermes
• controlled deployment of Hermes in enterprise collaboration spaces
• reusing existing gateway concepts like allowlists, activation policies, slash-command style controls, and session isolation

Right now, users who want Teams integration need to build and maintain custom bridge code around Microsoft Graph / Bot Framework / webhooks. Native support would reduce setup cost and make the behavior more consistent with Hermes’s other messaging platforms.

Proposed Solution

Add a first-class Teams gateway/platform adapter to Hermes.

Initial scope could include:

1. DM support
2. Mention-based activation in channels/group chats
3. Threaded replies where supported
4. Session mapping per conversation/thread
5. Basic allowlist / admin controls
6. Configurable activation policy (mention-only vs always-on in approved chats)
7. Safe handling of long responses (chunking / continuation)

Potential implementation directions:

• Bot Framework-based inbound adapter for message events
• Graph integration where needed for richer Teams operations
• Reuse existing gateway abstractions for session lifecycle, slash-command handling, approvals, and permissions

Alternatives Considered

1. Custom external Teams bridge

   • Works, but every user/team has to build and maintain their own adapter
   • Behavior may diverge from Hermes gateway standards

2. Graph-only read/write tooling without a native gateway

   • Useful for assistant-driven Teams operations
   • Does not provide the same native "@Hermes in Teams" experience

Additional Context

There is already precedent in Hermes for enterprise messaging platforms such as DingTalk, Feishu, WeCom, Slack, etc. Microsoft Teams feels like a natural addition to the supported gateway list.

A phased rollout would also make sense:

• Phase 1: basic DM + mention reply support
• Phase 2: richer thread/session controls and admin policies
• Phase 3: deeper Graph-backed capabilities if needed