{"slug": "memorylane", "name": "MemoryLane", "category": "ai", "category_name": "AI models and assistants", "description": "", "recommenders": 3, "commenters": 3, "warners": 0, "score": 2.558, "rising": -0.98, "first": "2026-02-17", "latest": "2026-02-26", "why": "", "why_is_quote": false, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 0, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 3, 0, 0, 0, 0, 0, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "", "kind": "", "icon": false, "domain": null, "github_repo": "github.com/deusxmachina-dev/memorylane", "official_url": "https://github.com/deusxmachina-dev/memorylane", "pricing": "", "aliases": ["MemoryLane", "memory-lane", "memorylane"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 754612001, "item_id": 47163250, "url": "https://news.ycombinator.com/item?id=47163250", "by": "__parallaxis", "date": "2026-02-26", "stance": "recommend", "quote": "MemoryLane looks really cool", "excerpt": "Hey, thanks for the kind words \u2014 and for the CLI/agent-memory idea. I haven\u2019t fully leaned into \u201cindex what the agents did in the repo\u201d yet; that\u2019s a great direction. The MCP server gets most of the love so far, but the CLI is the same pipeline (sync \u2192 chunk \u2192 embed \u2192 search), so wiring it in so agents can search their own history is totally doable. I\u2019ll keep that in mind. I have mostly used the entire API surface so", "context": "", "use_case": "screenshot-based local context", "switched_from": "", "story": "Show HN: Context Harness \u2013 Local first context engine for AI tools"}, {"id": 753431344, "item_id": 47089459, "url": "https://news.ycombinator.com/item?id=47089459", "by": "jzapletal", "date": "2026-02-20", "stance": "recommend", "quote": "all of those questions can be answered with", "excerpt": "all of those questions can be answered with https://github.com/deusXmachina-dev/memorylane", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: How to Plan a n8n Workflow"}, {"id": 752879360, "item_id": 47054960, "url": "https://news.ycombinator.com/item?id=47054960", "by": "quinncom", "date": "2026-02-17", "stance": "recommend", "quote": "it works!", "excerpt": "I've got it installed with Qwen3-VL-4B running in LM Studio on my MBP M1 Pro. (Yes, the fans are running.) GLM-OCR didn't work because it returns all text on the screen, despite the instructions asking only for a summary. Screenshots are summarized in ~28 seconds. Here's the last one: > \"The user switched to the Hacker News tab, displaying item 47049307 with a \u201cGave Claude photographic memory for $0.0002/screenshot\u201d ", "context": "testing on a MacBook Pro M1 Pro", "use_case": "screenshot summaries with MCP server for Claude", "switched_from": "", "story": "Gave Claude photographic memory for $0.0002/screenshot"}]}], "caveats": [], "who": [{"by": "quinncom", "context": "testing on a MacBook Pro M1 Pro", "url": "https://news.ycombinator.com/item?id=47054960", "date": "2026-02-17"}], "tags": [], "use_cases": ["screenshot-based local context", "screenshot summaries with mcp server for claude"], "compared": [], "makers": [{"id": 757183472, "item_id": 47323967, "url": "https://news.ycombinator.com/item?id=47323967", "by": "fidorka", "date": "2026-03-10", "stance": "recommend", "quote": "I've been building something called MemoryLane", "excerpt": "Love the local-first approach. The \"just ask it to import my Notion\" thing via browser automation is really nice. One thing I keep coming back to though - what if the tool could actually watch how you use your CRM and then suggest automations based on what it sees you doing repeatedly? I've been building something called MemoryLane (https://github.com/deusXmachina-dev/memorylane) that does exactly this - it captures ", "context": "", "use_case": "Screen-watching workflow automation", "switched_from": "", "story": "Show HN: DenchClaw \u2013 Local CRM on Top of OpenClaw"}, {"id": 757183168, "item_id": 47323948, "url": "https://news.ycombinator.com/item?id=47323948", "by": "fidorka", "date": "2026-03-10", "stance": "neutral", "quote": "I've been working on a slightly different angle with MemoryLane", "excerpt": "Agent memory is one of those things that sounds straightforward until you actually try to build it. The filesystem metaphor makes a lot of sense as a starting point. I've been working on a slightly different angle with MemoryLane (https://github.com/deusXmachina-dev/memorylane) - instead of giving agents a place to write their own memories, it captures the user's screen activity and makes it queryable. So the agent g", "context": "", "use_case": "Screen-activity memory for agents", "switched_from": "", "story": "Show HN: Agent-vfs \u2013 Virtual filesystem for AI agent memory"}, {"id": 757182432, "item_id": 47323902, "url": "https://news.ycombinator.com/item?id=47323902", "by": "fidorka", "date": "2026-03-10", "stance": "recommend", "quote": "I've been building MemoryLane", "excerpt": "Cool demo. The tricky bit with browser workflow agents is figuring out which workflows to automate in the first place. Most people don't even realize they're doing the same thing over and over - they just do it. I've been building MemoryLane (https://github.com/deusXmachina-dev/memorylane) which comes at this from the other side - it records screen activity, spots repeated patterns with AI, and then tells you \"hey yo", "context": "", "use_case": "Spotting repeated workflows", "switched_from": "", "story": "Show HN: AI agent that runs real browser workflows"}, {"id": 754610144, "item_id": 47163134, "url": "https://news.ycombinator.com/item?id=47163134", "by": "fidorka", "date": "2026-02-25", "stance": "recommend", "quote": "I built something similar to solve the context problem", "excerpt": "Hey Parker, this is really cool! Thanks for sharing. Have you tried using the entire CLI? It might also be a tool which you could compose into your workflow to have better memory of what the agents themselves did in the repo. Btw, I built something similar to solve the context problem for most of my laptop-based activity. It's slightly more heavyweight (electron app ingesting screenshots) - that being said I took man", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: Context Harness \u2013 Local first context engine for AI tools"}, {"id": 752106049, "item_id": 47006628, "url": "https://news.ycombinator.com/item?id=47006628", "by": "fidorka", "date": "2026-02-13", "stance": "neutral", "quote": "Building an electron app (https://github.com/deusXmachina-dev/memorylane-private)", "excerpt": "This is quite cool! What is it based on? Is it possible to use the same logic on other platforms (windows mac) as well? Building an electron app (https://github.com/deusXmachina-dev/memorylane-private) which does A LOT of screenshots and this looks like something which could save the users (for now mostly us the dev team :D) a lot of money.", "context": "", "use_case": "", "switched_from": "", "story": "Please delete. Did not know japanese meaning was so bad"}, {"id": 751383872, "item_id": 46961492, "url": "https://news.ycombinator.com/item?id=46961492", "by": "fidorka", "date": "2026-02-10", "stance": "recommend", "quote": "", "excerpt": "Nice work - the daily-log-first approach resonates. We hit the same \"re-onboarding Claude every morning\" problem and went a different direction with MemoryLane (https://github.com/deusXmachina-dev/memorylane): it sits in the background capturing your activity (screenshots + OCR + summaries) and makes that context available to any AI chat via MCP. Different tradeoff - Total Recall is curated (daily logs) and lean, Mem", "context": "", "use_case": "Background screen context capture", "switched_from": "", "story": "Show HN: Total Recall \u2013 write-gated memory for Claude Code"}], "threads": [{"url": "https://news.ycombinator.com/item?id=47162581", "title": "Show HN: Context Harness \u2013 Local first context engine for AI tools", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=47309953", "title": "Show HN: DenchClaw \u2013 Local CRM on Top of OpenClaw", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47273658", "title": "Show HN: Agent-vfs \u2013 Virtual filesystem for AI agent memory", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47322046", "title": "Show HN: AI agent that runs real browser workflows", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47085289", "title": "Show HN: How to Plan a n8n Workflow", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47049307", "title": "Gave Claude photographic memory for $0.0002/screenshot", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {"recommend": 3}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 754612001, "item_id": 47163250, "url": "https://news.ycombinator.com/item?id=47163250", "by": "__parallaxis", "date": "2026-02-26", "stance": "recommend", "quote": "MemoryLane looks really cool", "excerpt": "Hey, thanks for the kind words \u2014 and for the CLI/agent-memory idea. I haven\u2019t fully leaned into \u201cindex what the agents did in the repo\u201d yet; that\u2019s a great direction. The MCP server gets most of the love so far, but the CLI is the same pipeline (sync \u2192 chunk \u2192 embed \u2192 search), so wiring it in so agents can search their own history is totally doable. I\u2019ll keep that in mind. I have mostly used the entire API surface so", "context": "", "use_case": "screenshot-based local context", "switched_from": "", "story": "Show HN: Context Harness \u2013 Local first context engine for AI tools"}, {"id": 753431344, "item_id": 47089459, "url": "https://news.ycombinator.com/item?id=47089459", "by": "jzapletal", "date": "2026-02-20", "stance": "recommend", "quote": "all of those questions can be answered with", "excerpt": "all of those questions can be answered with https://github.com/deusXmachina-dev/memorylane", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: How to Plan a n8n Workflow"}, {"id": 752879360, "item_id": 47054960, "url": "https://news.ycombinator.com/item?id=47054960", "by": "quinncom", "date": "2026-02-17", "stance": "recommend", "quote": "it works!", "excerpt": "I've got it installed with Qwen3-VL-4B running in LM Studio on my MBP M1 Pro. (Yes, the fans are running.) GLM-OCR didn't work because it returns all text on the screen, despite the instructions asking only for a summary. Screenshots are summarized in ~28 seconds. Here's the last one: > \"The user switched to the Hacker News tab, displaying item 47049307 with a \u201cGave Claude photographic memory for $0.0002/screenshot\u201d ", "context": "testing on a MacBook Pro M1 Pro", "use_case": "screenshot summaries with MCP server for Claude", "switched_from": "", "story": "Gave Claude photographic memory for $0.0002/screenshot"}]}