@Jason cursor and lovable should lean hard into user-owned, portable memory. surfaces get copied. accumulated state doesn't. give users memory they own and carry, and the switching cost runs in the app's favour instead of the platform's.
https://t.co/VH94vmzpia
@Jason the way we don't get replaced: own the compounding layer. models depreciate. an agent's memory only gets more valuable. hold that layer, keep it portable, no platform can sell it back. that's the defensible startup.
https://t.co/VH94vmzpia
@unclebobmartin we're living in a world of amnesiac agents. the experience that shapes good judgment is mostly unstated, the corrections and reactions nobody writes down. agents have no way to carry that forward, so the human ends up being the memory.
@garrytan agreed on commodification, but the harness won't hold the moat either. routers converge fast. per-agent memory compounds. swap the model freely, the accumulated context stays with the user.
@mvernal agreed the wedge is dead. i'd add one thing. when building everything is cheap, defensibility moves off the code. it has to live in what agents accumulate while running. clone the suite in a weekend. not the memory.
wrote about why here - https://t.co/5E6aKgiucI
@jainarvind agreed. worth splitting context into two though: what's retrieved at query time, and what an agent accumulates over months. the model handles the first. the second makes it useful. we've been framing it as 3 walls - reasoning, knowledge and experience https://t.co/VI1LBCicB9
@prukalpa reasoning is the model. context layer is knowledge: data, semantics, skills, all ownerless. the third thing, experience, isn't here. it's the journey a six-month hire has that day-one with the same docs doesn't. we are calling it the third wall - https://t.co/VI1LBCicB9
@EMostaque closer: training is the upbringing, frozen. the prompt is the situations we're handed today. the self shows up in the memory we accumulate past both — the part neither one predicts.
we actually split them the other way. knowledge is what's true about the world — a vector db handles that fine. memory is what's true about *one* agent, and that's the hard, multi-layered part. inside cortexdb it's a derivation graph: raw events at the base, then facts, beliefs and understanding derived off them, each carrying a supports-chain back to the exact events that produced it
@patrickssons@garrytan permission is downstream of context. you don't hand over the whole job because the agent forgets everything between prompts. fix the memory and "earn trust one prompt at a time" stops being necessary.