No reviews yetBe the first to leave a review for Datailor Preference MCP
Maker
📌
Datailor is a solution to a personal frustration.
Session memory is a dead end. Teach Claude your coding style today, start a new thread tomorrow, and you're explaining indentation preferences all over again.
AGENTS.md promises permanence, but it's a static wall of text that never learns, never adapts, and quietly becomes outdated the moment your workflow shifts.
LLM-native memory is opaque, unreliable, and hopelessly vendor-locked. Cross-device portability? Try migrating your "preferences" from Cursor to Claude to Codex and watch them evaporate.
I wanted something that actually understands the problem:
◼ Dynamic matching — knows when to surface a preference and when to stay out of the way
◼ Automatic capture — learns from what you do, not from what you claim you do
◼ Intentional expiration — lets stale preferences fade instead of accumulating digital hoard
◼ Conflict detection — surfaces contradictions instead of silently guessing wrong
So I built Datailor. One Markdown file. Any agent can read it.
Datailor is deliberately minimal, human-readable, and open source. I beleive AI tooling should be like good conversations: respectful, interactive, and actually listening.
Report
Maker
Hi all!╰(*°▽°*)╯ Thank you guys for the following and votes.
◼ New in Datailor: datailor disable / datailor enable.
Shipped an on/off switch for Datailor today, because a user said it best: you don't always want your AI to know your preferences too well.
So now you stay in control:
▎ datailor disable # AI stops getting your preferences ▎ datailor enable # turn it back on ▎ datailor status # check current state
Disabling only stops injection. Capture keeps running quietly in the background, so you lose nothing by switching off for a sensitive task or a fresh-eyes session. Flip it back anytime.
Report
I think everyone who uses multiple AI tools has had the experience of explaining the same preferences again and again. It's a small annoyance individually, but it adds up quickly.
Report
Maker
@abul_hassan6 Exactly Abul! It's one single preference md file that can be accessed globally by all agents, and readable and editable by both users and agents, that's the whole point.
Hi all!╰(*°▽°*)╯ Thank you guys for the following and votes.
◼ New in Datailor: datailor disable / datailor enable.
Shipped an on/off switch for Datailor today, because a user said it best: you don't always want your AI to know your preferences too well.
So now you stay in control:
▎ datailor disable # AI stops getting your preferences
▎ datailor enable # turn it back on
▎ datailor status # check current state
Disabling only stops injection. Capture keeps running quietly in the background, so you lose nothing by switching off for a sensitive task or a fresh-eyes session. Flip it back anytime.
I think everyone who uses multiple AI tools has had the experience of explaining the same preferences again and again. It's a small annoyance individually, but it adds up quickly.
@abul_hassan6 Exactly Abul! It's one single preference md file that can be accessed globally by all agents, and readable and editable by both users and agents, that's the whole point.