v1.6.9 — New Connectors & Integrations
Release Date: 2026-11-18
Changes: v1.6.8 → v1.6.9
Pull Requests: #6639, #6644, #6739, #6742
Summary
This release focuses on expanding integrations and stabilizing ingestion and embedding behavior. We added multiple new connectors (Slack rework, Dropbox, Vercel, Telegram, Evernote, Asana improvements) and a hermes-agent integration, plus several reliability and embedding fixes so data ingestion and retrieval are more dependable.
Highlights
- Major connector additions and Slack host refactor for improved Slack integrations.
- Hermes-agent integration: a packaged agent for capture, recall, and runtime workflows.
- Embedding and storage reliability fixes, including rejecting short embedding responses and bounded pending batches.
- Simplified and consistent document chunking (the logic that splits content for indexing) to avoid inconsistent splits.
Breaking Changes
- Slack history import removed: The older Slack history import pathway was dropped and replaced by the new Slack connector and host modules. What this means: if you depended on the old Slack history import API, you must migrate to the new Slack connector (connectors/slack) and update any custom wiring to the new host/adapter interfaces.
- Connectors packaging and ports: Several connectors were added and some Slack internals were moved into new host modules. What this means: if you vendor or patch connector internals, review the connectors/* layout and update imports to the new locations.
New Features
- Slack host rework and new Slack source: The Slack connector was ported into new host modules and a new direct Slack source was added, replacing the old Slack history import. What it does: provides a modernized Slack integration path (message sync, member linking, webhooks) maintained inside the connectors package. Why it matters: Slack ingestion and interactions are more maintainable and testable; if you previously used the removed Slack history import, migrate to the new Slack connector (see connectors/slack).
- Dropbox connector: A new Dropbox connector (client, connector, selection UI and source) was added. What it does: lets you ingest files from Dropbox into Cognee for indexing and retrieval. Why it matters: expands supported sources so you can pull documents from Dropbox for memory and search.
- Vercel connector: Added a Vercel connector and wiring for ingesting project data. What it does: provides a source implementation to capture Vercel-related artifacts. Why it matters: you can now include Vercel project data in your Cognee memories and searches.
- Telegram connector: Added a Telegram connector. What it does: captures Telegram message streams and integrates them into Cognee. Why it matters: expands chat platform coverage so Telegram conversations can be searched and recalled.
- Evernote connector: Added an Evernote connector. What it does: imports notes and notebooks from Evernote. Why it matters: users with Evernote content can include those notes in Cognee memories for retrieval.
- Hermes-agent integration: A first-class hermes-agent integration was added (provider, runtime, backend, capture policy, and tools). What it does: supplies an opinionated agent for capture, buffering, recall notices and runtime orchestration. Why it matters: simplifies running automated capture-and-recall workflows and local agent-based integrations with Cognee.
Improvements
- Default chunker unified and resolved once: The logic that decides how to split documents for indexing (the "chunker") is now resolved in one place and used consistently. What it does: prevents inconsistent splitting across code paths. Why it matters: search and embedding behavior becomes more predictable and you get more consistent retrieval results.
- Observability: LLM call capture: The system now records LLM (large language model) calls for observability. What it does: logs and telemetry include LLM calls invoked during operations. Why it matters: helps you diagnose when queries trigger LLM calls and measure usage.
- Accept graph model as JSON schema: The cognify pathway now accepts graph model definitions provided as JSON schema. What it does: makes it easier to supply a schema for graph-style data extraction. Why it matters: simplifies integration with systems that produce JSON schema graph definitions.
- Docs and docstrings strengthened: Many public APIs had their documentation and docstrings clarified (retrieval behavior, remember/add doc details, error cases). What it does: clarifies when retrievers are bypassed and permission-check behavior. Why it matters: easier to understand expected behavior and reduce integration bugs.
- Testing and CI: Test suites were split and pinned, and many connector unit/integration tests were added and stabilized. What it does: improves continuous integration reliability for the repository. Why it matters: reduces false CI failures and speeds safe releases.
Performance
- More reliable ingestion restarts for Asana: listings that previously stalled when offsets expired now restart correctly, reducing missed items during ingestion.
- Bound pending batches in storage: pending batch sizes are now bounded to prevent unbounded memory growth while buffering writes.
- Reduced redundant chunker resolution: resolving the default chunker only once cuts overhead and avoids repeated decisions during ingestion.
Security
- No new security advisories in this release. Note: Slack integration code was reorganized and signature verification utilities were adjusted as part of the Slack host refactor; if you rely on custom Slack hooks, review the new connector implementation.
Bug Fixes
- Reject short embedding responses for pgvector storage: very short or malformed embedding responses are rejected instead of being stored, preventing corrupted vectors and index errors.
- Recheck skipped rows in pgvector flows: rows previously skipped during a check will be re-evaluated to avoid losing items from the embedding index.
- Count Telegram failures once: failure metrics for Telegram ingestion were deduplicated so failure counts are accurate.
- Restart Asana listings when offset expires: Asana ingestion now restarts a listing job whose stored offset expired, avoiding stuck ingestion.
- Drop hardcoded connection limit: removed a hardcoded connection cap that caused connection handling problems in some environments.
- Scope embedding request splitting: refined how embedding requests are split so the right requests are sent together, reducing incorrect or partial embedding uploads.
- Tell apart errors that share the first line: error reporting was improved so exceptions with the same first-line message are distinguished correctly.
- Fix failing CI import errors and test robustness changes: multiple test fixes to ensure new tests run correctly in CI and avoid platform-specific failures (e.g., pytest-timeout SIGALRM usage).
Technical Changes
- Large refactor and porting of Slack host modules and adapters to the connectors package (new module layout and router/sync/adapter implementations).
- Major new connector code trees added: Dropbox, Vercel, Telegram, Evernote, Asana test/connector updates and many unit/integration tests for those connectors.
- Hermes-agent: extensive new code (provider, backend, runtime_env, http_backend, capture policy, tools) to support agent-based capture and recall workflows.
- Test and CI reorganization: tests split into groups, new GitHub workflow files added/updated to improve integration and e2e test coverage.
- Code quality: import sorting, docstring strengthening, and several refactors for clearer error handling and typing improvements (e.g., Asana auth and restart typing).
Compatibility
| Component | Supported / Required |
|---|---|
| Python | >=3.10,<3.15
|
| pydantic | >=2.13
|
| litellm | >=1.102.2,<2.0.0
|
| fastapi | >=0.116.2,<1.0.0
|
| sqlalchemy | >=2.0.39,<3.0.0
|
| lancedb | >=0.39.0,<0.40.0
|
| ladybug | ==0.22.3
|
— The Cognee Team · 2026-11-18