Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

I built a Chess.com connector for Cognee so my AI agent remembers my games

Description and use

A Chess.com connector for Cognee was built to feed game data into an AI coach, enabling queries about openings, losses, and ratings.

Problem

I couldn’t query my Chess.com game history for insights without manually browsing archive pages.

Outcome

The connector successfully ingests Chess.com game data into Cognee, allowing AI queries about openings, losses, and rating trends.

Workflow

  • 1. Identify public Chess.com API endpoints for archives and games.
  • 2. Handle Cloudflare 403 by adding a realistic User-Agent header.
  • 3. Implement two‑level fetch: list archives, then fetch last N months of games (default 12).
  • 4. Convert each game to a markdown document with stable ID "chesscom:<game-uuid>".
  • 5. Extract title, result, ratings, date, opening, accuracy, and PGN.
  • 6. Handle null accuracies and zero‑archive accounts gracefully.
  • 7. Run test suite (6 tests) to verify ingestion and sync.
  • 8. Deploy connector in Cognee community repo and sync user data.

Evidence

One header fixed it: User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Source

Each game becomes one markdown document with a stable ID chesscom:<game-uuid> so unchanged games are never re-ingested

Source

The test suite proves the rest: 6 tests green, including test_pipeline_sync_edit_forget — play a new game, re-sync, and it shows up.

Source

  • Record date: 2026-10-25T12:11:32.952Z