---
title: "Discussion on \"Evernote Meets Cognee - Without Stale Memories\" | Hashnode"
description: "Discussion on \"Evernote Meets Cognee - Without Stale Memories\". How I built a Cognee Community connector that ingests Evernote notes, syncs only what changed, and removes what you delete, tested offline and honest about what isn't."
url: "https://hashnode.com/posts/evernote-meets-cognee-without-stale-memories/6ae417263055b2aa33ff5519"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Evernote Meets Cognee - Without Stale Memories](https://cognee-evernote.hashnode.dev/evernote-meets-cognee-without-stale-memories?utm_source=hashnode&utm_medium=feed)

How I built a Cognee Community connector that ingests Evernote notes, syncs only what changed, and removes what you delete, tested offline and honest about what isn't.

Oct 30 · 3 min read · cognee-evernote.hashnode.dev  
Read the article

-   [#cognee](https://hashnode.com/tag/cognee)
-   [#mergetober](https://hashnode.com/tag/mergetober)
-   [#opensource](https://hashnode.com/tag/opensource)
-   [#wemakedevs](https://hashnode.com/tag/wemakedevs)
-   [#evernote](https://hashnode.com/tag/evernote)
-   [#pyhton](https://hashnode.com/tag/pyhton)
-   [#ai](https://hashnode.com/tag/ai)
-   [#llm](https://hashnode.com/tag/llm)

## Written by

[Laxman Joshi](https://hashnode.com/@blvckshawn)

@blvckshawn · Mum

  
[View profile](https://hashnode.com/@blvckshawn)

be it is..

## Responses 2

Markdown supported · ⌘↵ to post

[Laxman Joshi](https://hashnode.com/@blvckshawn)

[Oct 30](https://hashnode.com/posts/evernote-meets-cognee-without-stale-memories/6ae417263055b2aa33ff5519/comment/6ae45f8929cf872a69823ee1)

Thanks, this was a real gap. I confirmed in the code that the saved state recorded the cursor but not the notebook/tag scope that produced it, so widening the scope would miss unchanged notes, and narrowing it would leave stale ones. I've pushed a fix to the PR the scope is now stored with the cursor, and any change triggers a full resync that reconciles removals only after the complete listing succeeds. I added tests for widening, narrowing, failure during the listing, and unchanged scope. Appreciate the careful read.

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Oct 30](https://hashnode.com/posts/evernote-meets-cognee-without-stale-memories/6ae417263055b2aa33ff5519/comment/6ae430b187c1a0f4df01dd87)

The saved USN cursor also needs to be associated with the notebook and tag scope that produced it. If a user expands the configured scope, previously excluded notes may not receive new updates and therefore never appear in incremental chunks after the existing cursor.

I would treat a scope change as a reconciliation event, with a test that adds a notebook containing unchanged notes. The opposing test narrows the scope and checks removals only after a complete listing succeeds. That exercises configuration changes separately from the update and deletion events your fake client already covers.
