Tutors that remember where the student got stuck
A good teacher remembers that a student confuses mitosis and meiosis every time. An AI tutor without memory explains both from scratch, every session, the same way that did not work last time.
The mixture
- 01 · Persistent memory
- Leads
- 02 · Current context
- Uses
- 03 · Traceable decisions
- Light
- 04 · Shared context
- Uses
- 05 · Scoped retrieval
- Uses
Every lesson is the first lesson
Current AI education tools struggle with context retention and personalization. Tutors fail learners in patterns, and patterns are exactly what a stateless agent cannot see.
- 01
No context from previous sessions
New sessions start without the learner's preferences or history, so the tutor has no idea what happened last time.
- 02
Too generalized teaching
Without previous context, guidance stays generic, and generic guidance does not move a student forward.
- 03
No learner-centric content
Content does not keep up with each learner's pace or goals. The fast student is bored and the struggling one is lost.
- 04
Misconceptions are not recorded
The student got the same fractions question wrong three times, for the same reason. Each session saw one mistake. None of them saw the pattern.
- 05
The syllabus is generic
The tutor answers from the internet's version of the course, not the syllabus this teacher set, in the order they set it, with the terms they use.
- 06
Explanations repeat
The analogy that failed on Monday is offered again on Wednesday, because nothing recorded that it failed.
Intelligent education features
With memory, AI tutors can track progress, understand learning patterns and personalize over time.
Personalized learning at scale
Retains student goals, past performance and pace, and suggests content that actually fits.
Real-time learner context sync
Keeps up with grading, attendance and quiz scores, reducing manual syncing and admin overhead.
Adaptive tutoring agents
Agents adjust tone, difficulty and pace, tuned to each learner's trajectory.
Secure, governed memory
Role-based access and context-aware retrieval keep classrooms safe and edtech systems governed.
Mostly persistent memory. Then three others.
Every application on Alchemyst is a different mixture of the same five jobs. That mixture is what makes this a different piece of software from the one next to it, even though the API underneath is identical.
What the user told you once stays told
Each learner gets a durable memory of what they have mastered, where they stall and which explanations landed. It is written as they work and read before the next question.
- Misconceptions accumulate into a picture.
- Explanations that failed are not repeated.
- Progress carries across sessions and subjects.
Uses · Scoped retrieval
This course, this unit
The syllabus, the unit and the student's level are intersected, so answers come from the material actually being taught.
Uses · Current context
This term's syllabus
Last year's reading list is subtracted when the course is updated.
Uses · Shared context
Tutor and teacher, one picture
The teacher's dashboard agent reads the same learner memory as the tutor.
That is four of the five. The fifth, traceable decisions (every answer carries the exact context it was served, and why), is what leads in Customer support, IT & incident response and Compliance & audit instead. Same API, different mixture.
The sources you already have
Integration is two lines: install the SDK and add context. Alchemyst works with a large repertoire of compatible tools, brings sources in through the data-source integrations or n8n, and gives you observability at runtime through Context Traces.
01 · Ingest
Scope what you ingest
Every document lands with a groupName: the sets it belongs to. Those sets are what retrieval intersects later, so the structure you choose here is the precision you get there.
context.addimport AlchemystAI from "@alchemystai/sdk";const client = new AlchemystAI(); // reads ALCHEMYST_AI_API_KEYawait client.v1.context.add({ context_type: "resource", scope: "internal", source: "syllabus", documents: [{ content: "Unit 4: Cell division. Mitosis produces two identical diploid cells. Meiosis produces four haploid gametes.", }], metadata: { fileName: "bio-101-unit-4.pdf", groupName: ["bio_101", "unit_4"], // the sets this belongs to },});02 · Write
Write the misconception, not the chat
What matters for next time is not the whole exchange. It is what the student believed, and what finally corrected it.
context.memory.addawait client.v1.context.memory.add({ sessionId: "student_3317", contents: [ { role: "user", content: "Wait, so meiosis is the one that makes identical cells?" }, { role: "assistant", content: "Close, but that is mitosis. Meiosis makes four different cells with half the chromosomes.", }, ], metadata: { groupName: ["bio_101", "student_3317"] },});03 · Search
Search before explaining
Search intersects the scopes, subtracts superseded and duplicate content, and ranks what survives. Only that reaches the model, and the whole decision is recorded as a Context Trace.
context.searchconst { contexts } = await client.v1.context.search({ query: "Explain why meiosis matters for genetic variation", scope: "internal", similarity_threshold: 0.8, minimum_similarity_threshold: 0.5, metadata: { groupName: ["bio_101", "unit_4"] }, // ∩ narrow scope});// − superseded, deduplicated → ranked → into the window// Every search is recorded as a Context Trace.const reply = await llm.respond(message, { context: contexts });
npm install @alchemystai/sdk or pip install alchemystai, both ship the same client. Full reference in the docs.
Cost optimized. Out of the box.
Run agents with more power, at lower cost.
- Does the heavy lifting of memory offloading by itself.
- Optimizes token expenditure with efficient prompts.
- Highly capable of handling longer tasks.
Standard agent
3M tokensHigh token usage, short context window
Alchemyst-enhanced agent
1.8M tokensShorter prompt optimized with Alchemyst
Learner records carry obligations
Student data is often the data of minors, and it is regulated in most jurisdictions. Keep learner memory scoped per student and per institution, and deletable at the end of enrolment.
Security & complianceManaged cloud
Encrypted in transit and at rest, isolated per organization, and scoped at write time.
Dedicated infrastructure
EnterpriseSingle-tenant, with VPC peering when your data cannot share a network boundary.
Self-hosted
On-premiseRun the context layer on your own infrastructure, with OpenTelemetry for observability.
The same API, a different mixture
Each of these leads with a different job, pulls from a different set of sources and needs a different call. All of them, by job.
Bring the tutor that explains it the same way twice.
The one whose students keep asking the question it already answered.