InAutocomplete. Real World AIbyMarco Kotrotsos·2d agoSynthetic Training Data Is Easy. Knowing It Isn’t Garbage Is Hard.Start with a failure you understand, then build examples whose success can actually be checked.
Marco Kotrotsos·5d agoYour Agent’s Memory Can Keep an Attack AliveA poisoned memory can outlast the conversation that created it. Here is how to test the full recovery path.A response icon1A response icon1
Marco Kotrotsos·6d agoStop Debugging the Prompt. Replay the Agent’s Bad Decisions.Find the first consequential mistake before rewriting instructions that may have worked perfectly.A response icon1A response icon1
Marco Kotrotsos·Oct 10Someone Built an AI Torture Chamber. What Did It Actually Prove?The viral project, the backlash, and the research revision that complicates the story.
Marco Kotrotsos·Oct 10Please Stop Bullying the AutocompleteAnthropic’s new cruelty rule sounds like a punchline. The reasoning behind it deserves a closer look.A response icon1A response icon1
Marco Kotrotsos·Oct 6Your private repository has a public screenshot problemWhat PixelLeak reveals about coding agents, review artifacts and the permissions between them.
Marco Kotrotsos·Oct 4No, that local decision model is not better than JevOur local routing demo worked. Then we checked it against the evidence in real documents.
Marco Kotrotsos·Oct 1We Built an AI Incident Register. Now You Can Audit Its History.How we built Agent Did What? with Codex, and why every saved account needs a date, its own evidence, and a way back.A response icon1A response icon1
Marco Kotrotsos·Sep 30Your Million-Token Context Window Comes With a Pricing CliffHow 1.1% more input can nearly double a GPT-6.1 Sol request cost, and what to measure before changing your agent.A response icon1A response icon1
Marco Kotrotsos·Sep 30Your AI Agent Did What?Introducing agentdidwhat.com: what happened, who operated the agent, and what the sources actually establish.A response icon1A response icon1