# October 24: Support for content versioning, duplicate policies, AskGraphlit MCP server

### New Features

* 💡 Graphlit now supports **content version control** when restarting content in-place. When documents are re-ingested from connected feeds, version history is automatically tracked, enabling developers to audit document revisions over time.
* 💡 We have added configurable **duplicate handling policies**. You can now specify whether duplicates are allowed across feeds or across the entire project. An event is fired when duplicates are detected, enabling custom handling workflows.
* We have launched **AskGraphlit**, a free public MCP server that incorporates our latest documentation. Developers can use this with AI assistants like Claude to get help coding with Graphlit SDKs.
* Content metadata is now more flexible: you can update `creationDate` and `modifiedDate` on content items, and filter contents by `modifiedDate` ranges.
* Child content (extracted images, meeting recordings, package contents) is now automatically added to the parent's collection when using collection workflows, simplifying organization for complex document hierarchies.

### Bugs Fixed

* GPLA-4657: Fixed search clause limit errors when filtering by large numbers of feeds or content IDs
* GPLA-4672: Optimized default model selection for entity extraction to reduce costs