github topoteretes/cognee v1.6.10
v1.6.10  Reliability & Observability Improvements

one hour ago

v1.6.10 � Reliability & Observability Improvements

Release Date: 2026-11-18
Changes: v1.6.9 → v1.6.10

Pull Requests: #6744


Summary

This release focuses on making Cognee more reliable and easier to debug: Postgres connection pools are tightened to reduce runaway connections and long waits, LLM call capture now records nested follow-ups and caller information for better observability, and the document chunking path is hardened to avoid incorrect chunk reuse. CI/test sharding was also expanded to reduce flakiness.

Highlights

  • Safer Postgres per-dataset connection pools: lower default overflow and bounded wait times to avoid huge connection spikes and long stalls.
  • Improved LLM call capture: records follow-up (nested) LLM calls and includes caller metadata for clearer debugging and usage analysis.
  • Chunking robustness: stricter validation and centralized stamping of chunks so stored chunks are reliably identified and reused when possible.
  • CI split into more shards to lower flakiness and speed up test feedback during development.
  • Documentation updated for a retired Anthropic model name (now recommends claude-sonnet-5-5).

Breaking Changes

  • Postgres per-dataset pool behavior: Defaults for per-dataset Postgres connection pools have been tightened (smaller max overflow and explicit pool wait behavior). If your deployment relies on very large, short-lived spikes of concurrent writes to per-dataset engines, you may see more immediate 'pool exhausted' errors. Action required: review and, if needed, increase your VECTOR_POOL_ARGS or dataset-specific pool settings and/or raise pool_timeout to suit your workload.

New Features

  • LLM call capture follow-ups: The LLM call capture feature (which writes one JSONL record per LLM call Cognee makes) now also captures follow-up / nested LLM calls and records who called them (a "caller" field). What it does: you get a clearer, traceable record of both the original LLM request and any internal subsequent calls. Why it matters: easier debugging, cost analysis and observability of complex multi-step LLM flows.

Improvements

  • Per-dataset Postgres pool defaults tightened: The default ceiling for per-dataset Postgres pools (used by the pgvector backend and other per-dataset DB engines) has been reduced so each dataset uses fewer excess connections. The configuration comments now also call out a pool_timeout value (how long an operation waits for a free connection before failing). What it does: reduces the chance of opening too many DB connections and of long, unexpected stalls. Why it matters: more predictable deployments and lower database resource pressure in multi-tenant setups.
  • Stricter chunking checks: The document chunking logic (which splits documents into smaller 'chunks' for indexing and retrieval) now performs tighter validation of chunks. What it does: catches invalid or mismatched chunks earlier and avoids silently accepting chunks that could corrupt update behavior. Why it matters: fewer mysterious rebuilds or data inconsistency when updating documents.
  • Centralized chunk stamping: Chunk objects are now stamped centrally with the chunker identifier (the marker that shows which chunking rule produced the chunk). What it does: ensures stored chunks reliably carry the origin id instead of relying on distributed stamping. Why it matters: improves correctness when the system decides whether existing chunks can be reused during incremental updates.
  • Docs: Anthropic model name updated: references to the retired model name 'claude-3-5-sonnet-20241022' were replaced with 'claude-sonnet-5-5' in documentation. What it does: prevents confusion from referencing removed models. Why it matters: keeps setup instructions accurate and reduces wasted time when configuring Anthropic providers.

Performance

  • Lower connection overhead for per-dataset Postgres engines: By reducing the pool overflow ceiling and clarifying pool timeouts, typical deployments will open fewer concurrent DB connections. Practical impact: reduced DB resource usage and lower contention on hosts that serve many datasets; extreme spikes will fail faster instead of blocking for long periods.

Bug Fixes

  • Fixes to unit tests and CI stability: Several failing unit tests were fixed and the test suite was reorganized to improve reliability (see CI changes below).
  • Chunking-related bug fixes: Tightened chunker checks and centralized stamping resolve cases where chunks without proper identifiers could cause update failures or inconsistent state.
  • Postgres pool and wait behavior fixes: Addressed issues where per-dataset pools could grow too large or block callers for long periods without failing fast.

Technical Changes

  • CI/test sharding increased: Integration tests were repartitioned (Retrieval -> 5 shards, Documents & Tasks -> 6 shards, Infrastructure -> 4 shards) and unit tests split into 4 shards in cross-OS CI. What it does: reduces test flakiness and evens out execution time per shard. Why it matters: faster, more reliable CI feedback for developers.
  • New/updated observability internals: new module files added to capture and write richer LLM call records (including follow-ups) and associated tests added to cover this functionality.
  • Internal: MCP version bumped and multiple test files adjusted/added to reflect the new behavior and to lock down regressions.

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

Don't miss a new cognee release

NewReleases is sending notifications on new releases.