Who it is forA researcher who returns to the same subject over many sessions and wants earlier findings reused.
The problemEach new research session starts from zero, so earlier findings and working methods get lost.
The outcomeA Poirot setup with memory recall, auto-consolidation, and skill evolution enabled in .env.
What you need first
- Python 3.12 or newer
- A DeepSeek API key (the README says to set DEEPSEEK_API_KEY in .env)
- Git and a terminal
- Docker only if you want the container sandbox
Steps
- Set up the project with
pip install -e ".[dev]"after creating a virtual environment, as in the Quick Start. - Copy the sample config with
cp .env.example .envand set DEEPSEEK_API_KEY. - Add the memory variables POIROT_MEMORY_USE=default, POIROT_MEMORY_PHASE2_ENABLED=true, and POIROT_MEMORY_PHASE2_TURNS=10 to .env.
- Add the skill variables POIROT_SKILL_ENABLED=true, POIROT_SKILL_EVOLVE_ENABLED=true, and POIROT_SKILL_EVAL_ENABLED=true to .env.
- Start Poirot with
poirot, ask a research question on your topic, then type/skill searchto browse skills.
Prompt for your agent
In the Poirot repo at <path to poirot checkout>, add the memory and skill variables from the README's Enable Advanced Features block to .env, then run `poirot` on the topic <topic>. Expected output: a session where memory recall and skill injection are active. Verify that the variables are set in .env before launching.
Caveat. The README lists these flags as optional advanced features and sends full configuration details to USAGE.md, so confirm the behavior there before relying on it.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for HezaoHezao/poirot and "Turn on long-term memory and skill evolution for a recurring topic"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer