How it works

Type in anything you want to understand — a homework problem, a concept, a "why does…" question. You get two doors:

• Build it. The tutor finds the last thing you actually know, then walks you forward one step at a time. You predict before you see, explain steps back in your own words, and get checked on the concept at the end. Slower, but it sticks — and it's the only path that marks a concept learned.
• Just the answer. You get the full worked answer immediately, no ceremony. The tracker records the concept as answer-only — you have the result, but you haven't proved you could rebuild it. You can always come back and build it properly later.

During a build lesson the tutor mixes intuition steps (why something is true) with routine steps (mechanical moves), asks you to predict outcomes before revealing them, and opens short discussions when you push back. If a check shows a gap, it detours to reteach before moving on.

Every concept you touch lands on your board ("What you know so far" on the home page, and the Concepts section of my lessons). Each chip carries an honest status:

• learned — you proved understanding by building or teaching it back.
• shaky — you attempted it and the check showed weakness.
• answer-only — you took the answer without proving it. Taking an answer never downgrades a concept you've already learned.

Chips link back to the lesson that produced them — tap one to reread the transcript. Signed in, your ledger syncs across devices.

Knowledge decays. Concepts you haven't touched in a while fade on the board — faded chips with a dashed ring mean it's slipping. When enough are due, you'll see a "concepts fading" banner.

Tap a fading chip to rep it: you get a fresh scenario that uses the same idea in a new disguise, so you can't pattern-match your old answer. Pass and the concept is marked learned again with a full-strength clock. Miss twice and the answer is revealed — the concept drops to shaky, and it'll come back around.

Want something kept warm on purpose? Pin a topic to the "Keeping sharp" board and its concepts stay in the rep rotation.

Signed in, every lesson is recorded. My lessons lists them all; open one and you get two views:

• Lesson view — the hand-drawn cards replayed in order: plan, predictions, checks, teach-backs. Cards start collapsed so you can skim the outline first.
• Chat view — the same lesson as a plain conversation.

Drills recorded from outside (see agent access below) show up here too, with adrill badge.

Every answer box understands LaTeX between dollar signs — type $x_t = \sqrt{\bar{a}_t} x_0$-style math and a live preview renders it as you go. The √x math keys row offers tap-to-insert symbols mined from the current question, so the symbols you need are usually one tap away. Plain dollar amounts like "$5 and $10" stay plain — it only treats it as math when it looks like math.

Your learning data is yours — any AI agent that speaks MCP can read it, and trusted tutors can write graded drills back. Sign in and grab your endpoint + API key from the Agent access card in settings.

The server lives at https://learn.carlneil.io/api/mcp (Streamable HTTP) and authenticates with your key as a Bearer token. Connect from Claude Code:

claude mcp add --transport http intuition https://learn.carlneil.io/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

…or from any MCP client with an HTTP config:

{
  "mcpServers": {
    "build-your-intuition": {
      "type": "http",
      "url": "https://learn.carlneil.io/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Six tools are available:

record_drill_assessment is how an external tutor (say, a Telegram bot drilling you on the bus) files its results: the question, your answer, the verdict, and any misconception it caught become a real drill session in your history and update your ledger — learned and shaky verdicts are authoritative fresh evidence; a seen verdict never downgrades a learned concept.

Keep your API key private — anyone holding it can read your learning history and write drills to it. Legacy path /api/mcp/mcp still works as an alias.