Repository navigation
Umbrella: integrations-plugins — connectors, channels, providers, search, media #9928
Description
Activity
- addedumbrellaEpic/umbrella tracking issue grouping member issuesEpic/umbrella tracking issue grouping member issues
on Jun 11, 2026 Umbrella complete — all 10 members merged/closed (left OPEN for human close)
Member PR Outcome #9019 OAuth→secrets gate #10087 OAuth flow + auto-refresh resolver + CSRF/XSS hardening #9003 Google Drive #10265 Create-API + UI wire-up with OAuth Connect button #9004 OneDrive/SharePoint #10271 Same pattern, Microsoft OAuth #9011 GitLab/Gitea/Forgejo #10283 UI wire-up, API-token auth #9006 Telegram #10272 Verified wired; fixed double-registration bug + added tests #9007 WhatsApp #10266 Fixed orphan — class existed, was never routed; wired inbound webhook end-to-end #9010 AWS Bedrock — Verify-and-close (already merged + registered) #9022 SearXNG #10292 New agent_loop/search/provider registry + fallback, wired into tool_handler#9023 Brave Search #10292 (batched with #9022) #9016 Video generation #10308 Runway baseline + async API + generate_videotool + inlineVideoCellMethod: parallel agents in isolated worktrees, each required to prove end-to-end wiring (not "a class exists") — this caught two real defects (WhatsApp orphan, Telegram dup-registration). Connector members reused the OAuth gate; search backends share one abstraction (one PR); Bedrock was already done.
Discovery issues filed: #10267 (WhatsApp inbound media→chat), #10273 (pre-existing AlertManager flaky tests), #10294 (plugin-loader hyphenated-path bug — affects image-gen + video-gen).
Deferred (tracked, not lost): LLC company-scoped connector secrets (AC#6 of #9019) → covered by the secrets-unification umbrella #10088. Sora/Kling video providers are registered but credential-gated pending stable APIs.
Umbrella complete — closing. Every member verified CLOSED against its actual GitHub state, not the checklist.
Working the backlog FIFO (oldest-first); this was the joint-oldest open issue in the repo (2026-06-11) alongside #9924, which closed earlier today.
All 19 members are closed. The last one, #10538 (Slack / Confluence / Jira KB ingestion connectors), closed today — and the finding there is worth recording:
#10538 was already fully built. An audit before any implementation found
knowledge/connectors/{slack,confluence,jira}.pyalready present and complete, all implementing the sharedAbstractConnectorcontract fromconnectors/base.py(auth_schema(),output_schema(), the{"status_code","body"}result shape,_load_ts()/_store_ts()checkpointing atbase.py:272-308from #12659), routing outbound HTTP throughget_http_client().tracked_request()rather than raw sessions. Delivered across five already-merged PRs — #12189 (scaffold), #12199 (offline mock/replay), #12219 (setup guide), #12225 (auth-schema key alignment) — plus the cross-cutting #12659 and #12979/#12999. Reachability was proven end-to-end:connectors/__init__.py:85-88gates the import behindAUTOBOT_FEATURE_KB_ENTERPRISE_CONNECTORS, andapi/knowledge_connectors.py::_SUPPORTED_TYPES(lines 84-86) lists all three, withGET /knowledge_base/connector_typesandPOST /knowledge_base/connectorsoperating dynamically onConnectorRegistry. 69 offline tests were already green.Had that audit not run first, three connectors would have been rebuilt from scratch.
Two genuine gaps were found and fixed instead (PR #13042, merged as
3044d6374): the setup guide had gone stale — #12225 renamed the config-read keys (bot_token→token,email/api_token→username/password) but the guide still documented the old field names and still asserted the mismatch was unresolved with "#10538 stays open" — and no connector had a multi-page pagination test, now added for all three (Slacknext_cursor, Confluencestartoffset, JirastartAt/total), each asserting real multi-call ingestion rather than absence of an exception.Checklist hygiene: #10539 was already closed but left unticked; corrected. This is the second oldest umbrella today whose checklist understated its true completion — #9924 had five such members. Reading the checklist alone would have sent work at issues finished weeks ago.
- added sub-issues
on Sep 1, 2026
Mission
Grow the integration surface via the plugin system: data-source connectors (Google Drive, OneDrive/SharePoint, GitLab/Gitea/Forgejo), messaging channels (Telegram, WhatsApp), LLM providers (AWS Bedrock), web-search backends (SearXNG, Brave), and media generation. All connector OAuth/secret handling must route through the existing secrets-management system (#9019 is the architecture gate for the connector group — land it first).
Dependency edges
knowledge/connectors/content_extraction.py,990d56fe2) — new connectors should import them.Members (sized)
M(architecture gate — do first)LLLMLMMSLTriage delta — 2026-06-19 (unfiled-issue sweep)
Triage delta — 2026-06-23 (umbrella #9928 verification)
Triage delta — 2026-06-26
Triage delta — 2026-06-27 (knowledge-work-plugins research comparison)
Source: comparison against anthropics/knowledge-work-plugins — enterprise-search/connector parity gaps.
L(biggest enterprise-search coverage gap) — closed 2026-07-30, code delivered across feat(kb): scaffold Slack/Confluence/Jira knowledge connectors behind feature flag (#10538) #12189/feat(kb): offline mock/replay knowledge connector + fixtures for sync() testing (#10538) #12199/docs(kb): operator setup guide for Slack/Confluence/Jira connectors (#10538) #12219/fix(kb): align connector credential reads with declared auth_schema (#12221) #12225/tech-debt(backend): extract knowledge-connector base — _load_ts/detect_changes duplicated across connectors #12659/perf(http): 134 raw aiohttp.ClientSession constructions remain (127 per-request) despite the shared pool at 151 sites #12979/feat(knowledge): correct auth-field docs + pagination tests for enterprise connectors (#10538) #13042~~categoryresolution)M(sibling of feat(knowledge): Slack / Confluence / Jira KB ingestion connectors #10538)MS