docs: how to run multiple named agent bots in Teams - #898
Merged
Conversation
Operators had no single place that says how to get several omadia agents into Microsoft Teams as separate named bots. The knowledge was spread across three repos, two manifests, five migrations and a handful of PR descriptions, so every attempt rediscovered the same traps: consent that silently does not apply, ARM fields whose absence is a partial success rather than a failure, and a teams_bots block nothing syncs for you. The new guide walks the whole path and states the platform limits up front, because they decide the architecture: Teams cannot change a bot name per message, bots never see each other, and rate limits are per bot (which is an argument FOR separate identities, not against them). Every API path, field name, state and setup key is verified against main rather than carried over from the draft, which predated three waves -- the operator UI (#896), the memory ACL (#881) and the .template ingest fix (#880) all landed after it. The one claim that could not be grounded in code is marked as a VERIFY comment instead of asserted. Part of #860
26 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Neue Operator-Doku
docs/teams-multi-agent-identities.md(DE) plus Verlinkung imdocs/README.md-Index und ein CHANGELOG-Eintrag. Reine Doku, kein Code.Was drinsteht. Der Weg von null zu mehreren omadia-Agenten, die in Microsoft Teams
als jeweils eigener benannter Bot auftreten: Plattform-Grenzen (1 Agent = 1 Teams-App/Bot,
kein Namenswechsel pro Nachricht, Bots sehen einander nicht, Rate-Limits pro Bot) →
Voraussetzungen (Plugin-Mindestversionen, Core-Migrationen
0049/0050, KG-Migration0031, Graph-Scopes samt der drei Consent-Fallstricke, optionale ARM-Felder =Registration-only) → Setup von M365-Connector und
channel-teams→ Identität anlegen(Operator-UI zuerst, REST als Alternative) → in ein Team bekommen (UI-Zuordnung,
Auto-Install, Fallback-Card) → Rechte pro Agent → Persona im nativen Agent Builder →
Kontext-Memory-ACL inklusive des standardmäßig ausgeschalteten Rollout-Flags →
Troubleshooting (17 Zeilen) → Grenzen und Ausblick.
Für wen. Technisch versierte Admins, byte5-intern und auf Kundenseite. Deutsch,
Platzhalter statt echter Hosts, keine Secrets.
Abgedeckte Waves. W0a / W0b / W1a / W2a / W5 — also inklusive der drei Änderungen,
die nach dem Entwurf gelandet sind: Operator-UI (#896), Kontext-Memory mit ACL (#881)
und der
.template-Ingest-Fix (#880, behoben ab v0.136.2).Verifikation. Jeder Pfad, Feldname, State und Setup-Schlüssel ist gegen
maingeprüft, nicht aus dem Entwurf übernommen. Korrigiert gegenüber dem Entwurf unter
anderem: es gibt keine Migration „0010" (richtig ist KG
0031), die Deinstallationantwortet
501statt zu funktionieren, das Feature ist nicht mehr API-only, und dasKemia-Kapitel entfällt ersatzlos zugunsten des eingebauten Agent Builders. Die eine
Aussage, die sich im Code nicht belegen ließ (Plugin-Config-Verhalten des
Fallback-Agenten), steht als
VERIFY-Kommentar statt als Behauptung.Part of #860
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.