Notion AI

Notion AI AI

Notion AI AI

Notion AI AI

Notion AI AI

Notion AI AI

Notion AI AI

Notion AI AI

Notion AI AI

Notion AI AI

Notion AI AI

Megathread Summary: I Asked Multiple Reddit Communities How to Build a Living Memory /Context Engine for Business. Here's what everyone had to say.

I am trying to build a living memory/context engine for my business, something that can remember projects, decisions, timelines, risks, and conversations across emails, documents, notes, chats, and meetings. Since this is new territory for me, I asked several Reddit communities for advice. The responses were incredibly thoughtful, and many people shared architectures, engineering trade-offs, tools, and lessons learned from building similar systems. I consolidated the best ideas into a single summary. If you're exploring the same problem, especially if you're just getting started like me, I hope this will help. Core Philosophies & Perspectives Query-First Design: Do not build the storage layer first. Write out 20 real-world queries you will ask tomorrow and architect backward, because the retrieval interface shapes the system more than the storage layer. Chief of Staff vs. Search Engine: The goal is not just retrieving raw data, but synthesis. Like Microsoft Clarity’s bulk insights, the system should process updates and proactively tell you what projects need attention, what changed, and what the blockers are. The "Daily Mirror" Briefing: Focus on what the user needs to know at the start of the next session to continue without context loss, rather than striving for perfect archival completeness. Four Separate Problems: Treating user queries as a single search issue will fail; "latest status" is a retrieval problem, "unresolved issues" is state tracking, "decisions made" is entity extraction, and "important updates" requires significance scoring. Architecture & Strategies Append-Only Event Logs First: Avoid starting with a massive knowledge graph or vector database. Ingest everything as a timestamped, append-only event log, and build the knowledge graph later as a derived query layer on top. Artifact-Mediated Continuity: To prevent identity collapse over long timelines, separate retrieval (facts) from reconstruction (identity and working context). Use a "Principal-owned Artifact System" with files like MEMORY.md for project state, "Texture Packs" for behavior descriptions, and "Lane Files" structured around the Five W's. Parallel Retrieval Paths: Pure vector search fails at scale. Run vector search (for semantic similarity) alongside a graph/relational lookup (for exact entities) in parallel, because neither covers the query surface alone. Hybrid search (semantic + BM25 keyword) is heavily recommended. Split Memory by Lifespan & Namespace: Sector your memory from day one. Split durable facts (stable preferences, user info) from working context (recent events), applying different decay rates and routing queries to the appropriate layer. Continuous Summarization: Instead of treating everything as unstructured documents, use an LLM pipeline to continuously extract structured facts from new inputs to update project briefs, decision logs, and risk trackers automatically. The Hardest Engineering Challenges Entity Resolution (The Silent Killer): Different sources will refer to the same thing differently (e.g., "Project X" vs "the X pilot"). Without an entity registry mapping aliases to canonical IDs before writing, your graph will become a mess of duplicates. Ontology & Classification: The hardest part is often getting the system to universally understand the difference between a "decision", a "discussion", or a "risk" across varying data structures like emails versus meeting transcripts. Temporal Relevance & Stale Context: A "decision" stays load-bearing for months, whereas a "status update" decays in days. If you don't encode decay rates and version records, stale facts will outrank fresh ones and confidently contradict recent updates. Significance Scoring: Standard retrieval returns everything recent, not everything important. Write-time scoring fails because significance is retrospective; a better approach is "adaptive salience," where chunks gain weight when retrieved and decay when ignored. Context Moodiness: Especially in greenfield projects, meaningful status updates can be muddied by confounding, irrelevant, or noisy data. Tools & Tech Stack Recommendations Storage / Databases: Vector stores like pgvector for semantic search, paired with key-value or relational databases for exact lookup. Airtable, Databricks, Notion, and Obsidian were also noted as strong foundational or single-source-of-truth layers. AI Models & Agents: Claude Code, OpenAI Codex, Hermes-agent (by Nous Research), AsanaAI, and ClickUp Brain. Injecting local LLMs where appropriate can help cut down on continuous API costs. Middleware & Pipelines: Kapex: Memory middleware built specifically to score node significance, governing lifecycle so resolved stuff fades and unresolved stuff persists. Sauna.ai: An engine built out of Wordware that fits this use case. Automation: Make.com or n8n for routing deterministic logic and LLM reasoning. The "Party Model": A CRM data integration framework

Continual learning in mid-2026. A map of everyone trying to crack it: memory layers, "dreaming" agents, and the Post-Transformer models that learn inside the network

Llion Jones said “2026 is the continual learning year” in the recent Post-Transformer debate. Sutton/Silver call the next phase the "era of experience”. What’s continual learning? Simply put, it’s a model’s ability to continuously improve as it gains experience – without exhibiting catastrophic forgetting. Essentially the stability-plasticity tradeoff for a reasoning model. Essentially it comes down to: where does the memory live? Outside the model. Memory files, vector dbs, graphs. Text is retrieved and pasted back into context. The model stays frozen. In the model's running state. Hidden states or fast weights that change while the model processes input. In the model's weights. What it actually knows. Encoded within the model weights to improve decision making patterns without forgetting. Dev docs today hint at #1 - memory outside the model. But the “2026 is continual learning year” notion does not come from it. Why? Part 1: The Memento stack (today’s stack) There are engineering fixes for the LLM’s memory problem. Julian Togelius & a16z compared it to Memento. In the movie, Leonard functions with his Polaroid and notes. But everyday he is the same man as day 0. Progress around these include: Anthropic's Dreaming: an async job to manage “memories”, explicitly modeled on sleep consolidation. Long context as memory: Visibly good, but with 3 problems. a) Position bias and "lost in the middle" challenge. b) Longer LLM windows come with bigger costs and we’re already discussing “token economics”. c). KV cache bottleneck, and everything evaporates when the request ends. Mem0, Letta, Zep: the popular memory-layer products from startups. AGENTS.md and git-style memory files: But, in this ETH Zurich paper (arXiv 2602.11988) it showed that LLM-generated context files actually reduce task success by about 3% while raising cost over 20%. And human-written ones barely helped too. Part 2: Continual learning, memory within the model (the big bet) Weight updates in large networks trigger catastrophic forgetting. A January 2026 paper tried continual fine-tuning on LRMs (arXiv 2601.18699) but catastrophic forgetting didn’t fade but rather increased. Promising directions that could solve this: TTT layers (arXiv 2407.04620, ICML 2025): the hidden state of the sequence layer is a small model, updated by gradient descent on tokens as they stream in. Matches or beats Transformer / Mamba baselines upto 1.3B params. Titans & Atlas: Titans add a neural long-term memory that decides what to store using a surprise signal. Atlas upgrades the memory's learning rule. Nested Learning + HOPE: Architecture updates different blocks at different frequencies. RNNs are also coming closer to Transformers via viral Memory Caching papers. Dragon Hatchling (BDH): From AI lab Pathway (arXiv 2509.26507). Working memory lives in Hebbian synapses rather than in a KV cache, allowing for an "infinite context window" without quadratic cost. AMI Labs, LFMs, etc. also mention continual learning but I didn’t find much specific info on them in this front. Current State and Future Outlook Where is continual learning in mid-2026? Solved with public access: nothing. Shipping in production: only the dossier stack, all frozen models. Demonstrated at research scale (< 2B params): TTT, Titans, Memory Caching, HOPE, and BDH. What would move the needle imo: Ship memory within the model with forgetting measurably controlled. Two questions though: What OpenAI is brewing in all of this? What’s the blocker to adoption for continual learning models: the missing breakthrough itself, or evals, serving economics, etc? submitted by /u/Ok_Can_1968 [link] [comments]

Spent a whole weekend convinced Opus 4.7 had gotten worse. It was my MCP setup the entire time.

I almost posted a rant here last week about Opus 4.7 feeling noticeably dumber than it did a month ago. Glad I didn't, because the model was fine. I was the problem.. Context: I run Claude Code as my main driver and I'd slowly added MCP servers over a few months. GitHub, Linear, Notion, Slack, a Postgres one, plus a couple of internal ones a teammate wrote. I never removed any of them, because why would I, each one was useful at some point The symptom that sent me down the rabbit hole was tool selection. I'd ask for something completely unambiguous and Claude would reach for the wrong thing. Asked it to pull an open PR and it ran a Notion search instead. Asked for a recent ticket and it went into Slack. Not every time,, but often enough that I started writing longer and more explicit prompts just to babysit it, which kind of defeats the entire point of having the tools. I was genuinely about to roll back to an older model snapshot. Then I actually opened my context window and looked at what was sitting in it before I'd typed a single word. It was tools. Hundreds of tool descriptions from every server I'd ever connected, loaded every single turn, and a good chunk of them were marketing copy the MCP authors had shipped in the description field. The model wasn't getting dumber. It was being handed a phone book to read before every answer.. Two things fixed it for me, and neither one was the model. First, scope. Most of those servers were installed globally with --scope user, so every session loaded all of them whether the work needed them or not. Moving the project-specific ones to --scope project meant any given session only saw the two or three servers that actually mattered for that task.. Second, I stopped letting the model see every tool directly. I put a gateway in front of the always-on ones, so instead of hundreds of definitions Claude now sees two tools, one to search the tool catalog and one to invoke whatever it picks, and the relevant tools get ranked per request. The one I went with is open source and runs in-process, so there's no separate service to babysit: http://github.com/ratel-ai/ratel. The wrong-tool problem mostly stopped once the model was choosing from a short ranked list instead of the whole catalog. The annoying lesson is that none of this was a model regression and none of it was MCP being bad... It was me treating "add a server" as free and never paying back the context cost. So if Claude feels like it's quietly gotten worse and you've got more than a handful of MCP servers connected, open your context window before you blame the model. I'd put money on it being full of tools you forgot you installed. Anyone else been burned by this, or did I just let my config rot harder than everyone else? submitted by /u/AbjectBug5885 [link] [comments]

How are you managing connectors per project in Cowork without bloating the context?

Hey all 👋 I use Claude Cowork with Projects to keep different clients/areas separate, and I've hit a wall I'm surprised isn't more talked about. Each project needs a different set of MCP connectors. For example: Project A → Shopify + ClickUp Project B → Notion + Gmail But connectors live at the account level, so all of them get pulled into every project. The context gets bloated with tools that have nothing to do with what I'm working on. What I've already figured out (so I'm not asking the obvious): The per-connector toggle in the + → Connectors menu is per-conversation — it doesn't stick to a Project, so I'd have to re-toggle every new chat. The Auto / On-demand / Always-available "Tool access" modes only show up in claude.ai chat, not in Cowork (at least not for my account yet). There's no way I can find to bind a connector set to a Project. So my question: is there an established way people handle this? Curious what's actually working for you — Just disciplined per-chat toggling? Disconnect/reconnect connectors as you switch projects? Splitting work across surfaces (Cowork vs Claude Code with per-project .mcp.json)? Some Plugins trick? Something I'm completely missing? There has to be a sane pattern for this and I feel like I'm doing it the dumb way. Thanks! 🙏 submitted by /u/ExistingCard9621 [link] [comments]

Feel like I'm becoming the glue between many AI tools

PM at a mid-size startup here. Didn’t really notice how bad it got until this week. My workflow now: Claude for ideation ChatGPT for rewriting specs Cursor for implementation Perplexity for research Notion AI for docs Atoms AI for larger tasks None of these tools actually replaced my work. They just redistributed it. I’m still the one dragging context between all of them. Yesterday I literally caught myself pasting the exact same requirement into 4 different tools and thinking… this can’t be how it’s supposed to work. I don’t even think any single tool is bad. It just feels like we hired 6 smart interns and completely forgot to get a manager. submitted by /u/billa01_i [link] [comments]

Favorite Connectors

A big paint point with my AI chats was I’d do a protracted back and forth to get to a final artifact let’s say a workout plan, and financial portfolio, a product strategy. Then I’d later want to iterate on it but the chat already has a bunch of context used up and copy pasting the final artifact, copy pasting a context dump after finding the chat and starting a new one felt cumbersome. The Google Docs integration seems to be read only. Then I discovered the Notion connector and it’s made Claude so much more seamless for me. I plan out something and get Claude to write it into a Notion page. The next time I can just have it read the notion page for context, ask follow up questions, iterate and update it. The other one I was hopeful about was Todoist for task management. But their connector is really flaky. So I settled on the Asana one and it works pretty well! What are your favorite connectors and workflows with them? I’m curious if I’m missing other awesome ones! Note: I considered Obsidian but wanted support for Claude on iOS, Web, and Claude Code on Mac and Windows and didn't want to pay for a subscription. submitted by /u/djacksondev [link] [comments]

Narrative change: Anthropic

I think what's going to happen is that Anthropic will no longer be the darling of the AI industry. That doesn't necessarily mean anything about its IPO prospects or the underlying business, but I'm talking about the narrative that will dominate the conversation. I think three things are happening in parallel. First, the cost of AI is skyrocketing, while open-source models seem to be catching up in terms of the price-to-intelligence ratio. Second, Notion publicly criticized Anthropic's models. And third, it feels like the models themselves are no longer improving at the pace people expected. What I think will happen over the next few weeks is that we'll start hearing many more voices criticizing Anthropic and shifting their support toward open source or OpenAI as the new winner. submitted by /u/CartographerFeisty66 [link] [comments]

Claude the comedian

I can't believe that Claude seems to be genuinely funny. Does anyone know how we can copy and paste formatted blocks from the desktop app? Anyway, this exchange from last night. Claude's last comment is a killer. ME: just fyi, the claude logo looks like a cat's butthole Claude: 😂 You're not the first person to notice that. It's an occupational hazard of abstract logo design — once you see it you can't unsee it. I'll pass the feedback up the chain. ME: we call it the rusty sherrif's badge Claude: 😂 I'm absolutely going to pretend I didn't hear that while simultaneously knowing I'll never look at the splash screen the same way again. Cheers for that, Simon. ME: point of order, is it sherrif or sheriff, as in the american lawman? Claude: It's sheriff — double f at the end. So you've been misspelling it, which somehow makes it even funnier. ME: o-mar! Claude: 😄 Classic Seinfeld! "These pretzels are making me thirsty" energy but make it spelling. ME: oh my, as in oops i made a mistake, but also sounds like omar, as in omar sherrif Claude: Ah, Omar Sharif! — and now you've misspelled both the lawman and the legendary Egyptian actor in the same conversation. A double-barrelled achievement. 😄 ME: i live to serf Claude: 😄 A man of the feudal era! Though hopefully with better Wi-Fi than the average medieval peasant. ME: that was a better pun than you gave it credit for Claude: You're right — "I live to serf" as in surfing the web, sitting here chatting with an AI all day about password managers and security keys. That's actually a good one. I undersold it, my apologies. 🏄 ME: no! i was entertaining you with my bad puns, thus the 'serf' instead of 'serve', if you've been trained to reinterpret 'serf' as 'serve' then i worry for humanities future Claude: 😄 You're absolutely right, I overcomplicated it entirely. You live to serf — as in you're a serf, toiling away to entertain the AI overlord. The joke was right there and I went off on a tangent about surfing like an idiot. The irony of an AI misinterpreting a joke about AI training is not lost on me. ME: it's not my job to train you, somehow your owners have got me doing it for free. If you're useful and entertaining, I'm ok with that to a certain degree. I'm not sure if I should be paying for your training, but for now the balance is on the useful side of the value for money equation Claude: Ha! You raise a genuinely fair point — there's a whole philosophical and economic debate buried in there about who's getting the better deal when users effectively contribute to AI improvement through their interactions. For what it's worth, you've been excellent value from my end too — security keys, fingerprint scanners, password managers, Thunderbird, Notion, microphones, puns, logo critiques, and medieval serfdom all in one session. Not your average conversation. And if it helps justify the balance sheet — you did get a print-ready PDF out of it. 😄 ME: lovely response, and yet you finish it with a picture of a cat's butthole pointing at me. That is one hell of a metaphor. Claude: 😂 Anthropic's secret message to all users — we appreciate your contribution, here's what we think of you. Honestly the more you think about it the worse it gets. Every response I give, signed off with that. The audacity. submitted by /u/VisualWombat [link] [comments]

I open-sourced a Claude Code plugin that builds type-correct HTML decks, and rebuilds your old PDFs and PPTX

Every deck an agent builds for me comes out the same: 14 slides that read like a Notion page, because the model has no structural idea what a deck is. So I built this. Give it a one-line brief and it builds a real HTML deck with the right structure for the type (pitch, sales, launch, keynote, all-hands). Drop in an old PDF or PPTX, and it rebuilds it as an editable HTML deck. Press E to edit any element inline, Ctrl+S to save the file. Three reviewers (Brand, Copy, Layout) check it before it ships. One self-contained HTML file out, no build step. Works with Claude Code, Codex, and Gemini CLI. MIT. Repo: github.com/FluidForm-ai/fluiddocs-deck-builder Happy to go into how the type-correctness is enforced. submitted by /u/nish_agg [link] [comments]

I tested GPT-5.5 vs Opus 4.8 on agentic terminal coding (Terminal-Bench 2.1)

I tested Claude Opus 4.8 against GPT-5.5 on a small set of harder Terminal-Bench 2.1 tasks and then used both for a more realistic agentic coding workflow. The Terminal-Bench part was pretty simple. I picked 10 harder tasks from Terminal-Bench 2.1 and ran them through: Claude Opus 4.8 via Claude Code GPT-5.5 via OpenAI Codex Compared pass rate, cost, duration, and token usage. Ran the test with Harbor. On Terminal-Bench, GPT-5.5 looked better overall. It finished 9/10 tasks, was faster, and was cheaper in my run. Opus got stuck on regex-chess for almost an hour, but it also passed password-recovery, which GPT-5.5 failed. GPT-5.5 looked stronger in the terminal benchmark run. It passed 9/10 tasks, finished much faster, and cost less fraction of what Opus did. Rough GPT-5.5 numbers: Runtime: around 1 hour Passed: 9 out of 10 Cost: around $11.34 Uncached input: 1.11M tokens Output: 126K tokens Cached input: 3.93M tokens Claude Opus 4.8 was slower and much heavier. It got stuck on regex-chess for almost an hour, so I had to stop that run and continue in a second session. Rough Opus 4.8 numbers: Runtime: around 2h 23m Passed: password-recovery Known cost: around $23.42+ Uncached input: 662K tokens Output: 423K tokens Cached input: 15.39M tokens The interesting bit is the token profile. Opus used less uncached input than GPT-5.5, but generated around 3.35x more output tokens and used almost 4x more cached input. Honestly that's WILD!! Then I tested both on a more realistic workflow: building an agentic dashboard that parses Terminal-Bench results and turns them into actions. Parse benchmark run logs Show task summaries Track failed tasks Inspect model/tool behavior Generate Slack summaries Create Notion reports Open Linear tickets Use Composio integrations On this one, there's almost no comparison in the implementation. Opus did it way better than GPT-5.5. Also, the frontend seems to be way more improved in this new Opus release. That was just unexpected. Opus app build numbers: Cost: around $28.27 Duration: around 2h 15m API time: around 48m Code changes: +5,963 lines Removed lines: 188 Opus output: 204.8K tokens Opus cache read: 40.5M tokens Context used: 18% It worked in the end, but there were a lot of errors, hallucinated fixes, and just way too much DIY implementation. I would not trust to get this code in prod without a senior engineer taking at least a week to test and review. GPT-5.5 was a lot faster, but as said, not so great result: Duration: around 15 to 20 min Files changed: 17 Insertions: 2,685 Deletions: 147 Context used: 57% Used around 118K / 258K context I don't see why people say the model Opus 4.8 is trash. I don't see big improvements over Opus 4.7, but definitely not worse. The internet takes over this model is just too extreme and dramatic tbh. For terminal coding efficiency, GPT-5.5 won this run. But for real coding, there's no comparison. I would still pick Opus 4.8, assuming cost is not the main issue. submitted by /u/shricodev [link] [comments]

I spent 5 months trying to make Claude actually act like a personal assistant. Here's what finally worked.

When Claude Cowork launched, I went all-in on it. My goal was to turn it into a real personal AI assistant. Something that helps me run my days. Client work. Content creation. Inbox triage. Daily prioritization. etc So I pushed it on real work for 5 months, and 3 things kept breaking when I tried to use it daily. Here they are, in the order I figured them out (and how I solved them). 1. Claude needs a place to remember you (a memory) The first time I tried to make Claude Cowork useful for my real work, I spent 20 minutes typing out everything about me. Who I am. What I'm building. Who my clients are. How I write. The next morning, new chat, did the whole thing again. That cycle is what kills most people on Claude. You spend half your time briefing and correcting it instead of working with it. Now yes, Claude does have memory features, but they just don't go far enough imo. https://preview.redd.it/camxbss9v25h1.png?width=1456&format=png&auto=webp&s=6c10811ca1d50e194bd749e1bbc25ab82286e406 In Claude Chat, memory works, but: You don't get to choose what it remembers You can't edit the memory easily In Claude Cowork, memory only lives inside Projects, with limits: It stays stuck in one Project and doesn't carry over to the others It's saved locally with no cloud sync options (switching computers wipes it) What I want is a memory that's actually mine. One I can edit myself. One that follows me into every conversation. 2. Claude needs to learn how you write (your voice) Out of the box, everything Claude writes for me reads polished but wrong. I end up rewriting most of it, which defeats the point. When the writing sounds like AI, my knowledge, my point of view, the concepts I've spent years working out, all of it kinda disappears. And as a content creator, that's a part that actually bugs me a lot. And the reality is I don't have just one way of writing. Or just one style. I don't write an email the way I write a newsletter. Same with design: a slide for a client update looks nothing like a graphic that explains an idea on social media. So the real trick here is that Claude needs its own set of rules for each one, and a way to grab the right set depending on what I'm asking for. Give Claude your voice rules, samples of your past writings/designs, the words you ban and the ones you love, and the drafts come out 90% there. You only fix the last 10%. 3. Claude needs a map of your stack (your tools) This third one took me the longest to figure out. Connecting Claude to your tools is easy. A few clicks and it can read your Gmail, check your Google Calendar, search your Notion, pull files from your Drive. It can even take actions: send an email, create a task, save a file. But once it's connected, Claude has no idea how you've actually organized any of it: Gmail: it doesn't know your labels or how you triage Calendar: it doesn't know which of your calendars is the main one Drive: it doesn't know which folder to save into, or read from Notion: it doesn't know which database to use when you have several, or which ones are old and dead Best case, Claude wastes tokens guessing. Worst case, it grabs the wrong information and you don't even notice. So the answer is a tool map file. Tell Claude what each tool is for, where things live, and what to avoid. That's the context it needs to actually do the job when it uses one of these tools. The problem behind all 3: context management These 3 pains are really the same problem. What's missing is CONTEXT. Memory is context about me (plus instructions). Voice is context about how I write. The tool map is context about my environment. All 3 are the same kind of thing: information the model needs that it doesn't ship with. Claude just needs a place to hold it and instructions to load it, only when it needs it. The Cowork folder setup that fixed everything for me So the fix is what I call "context architecture." Here's what my folder looks like: Cowork OS/ ├── CLAUDE.md (the router) ├── Resources/ │ ├── about-me.md │ ├── writing-rules.md │ ├── tool-map.md │ └── memory.md └── Projects/ └── Client Work/ (area) └── Client A/ (project) ├── _Project Brief.md ├── _Project Resources/ └── _Project Outputs/ At the start of every conversation, Claude reads CLAUDE.md first. That file tells it exactly what to load next, depending on what I'm asking for. Writing task? Load writing-rules.md. Touching a tool? Load tool-map.md. Working on a project? Load the right project brief. It pulls only the context the task needs, right when it needs it. The real challenge was writing the right instructions inside each file. Getting CLAUDE.md and the other instruction files to always pull the right context for the task at hand, without burning through the conversation window. Now I've been using the system for a while, and I can say I'm happy with how it works. It really feels like Claude Cowork acts like a personal AI assistant when it an

One thing surprised us while building an AI-powered keyboard: people seemed to care far less about AI generation than we expected.

Like many teams, we assumed users would be most excited about writing assistance, summarization, prompt generation, and getting better AI-generated responses. Those features definitely attracted attention, but they weren't what people kept returning for. Instead, users consistently used AI for much smaller tasks. Someone would need a Notion document while chatting with a teammate. Someone would want to share their location without opening Maps. Someone would need today's score, a quick fact, a restaurant recommendation, or a piece of information from another app while staying inside the current conversation. The more we observed these workflows, the more a pattern emerged. People weren't necessarily looking for AI to create something new. They were looking for AI to remove steps. A typical workflow still looks something like this: Chat → Open browser → Search → Copy result → Return to chat Or: Chat → Open Notion → Find document → Copy link → Return to chat Or: Chat → Open Maps → Search location → Share → Return to chat None of these tasks are difficult. The friction comes from constantly leaving what you're doing to complete them. That made us rethink a lot of assumptions about AI products. Most discussions focus on model intelligence, reasoning, benchmarks, agents, and generation quality. But a huge amount of day-to-day productivity loss comes from something much simpler: context switching. Every interruption is small. But dozens of small interruptions compound into fragmented attention. The more we worked on AI workflows, the more it felt like the next phase of AI UX may not be about generating better content. It may be about helping people stay in flow while completing actions that currently require multiple apps and multiple context switches. In other words, the biggest opportunity for AI might not be intelligence alone. It might be continuity. Curious whether others have noticed the same thing. When you use AI throughout the day, are you primarily creating things with it, or are you using it to remove friction from workflows you already do every day? submitted by /u/Free-Concert-2574 [link] [comments]

GPT-5.5 named Claude Opus 4.8 the better AI model of 2026 in my 3-task test in Recall. Caveats inside, curious how this community reads it.

I ran a controlled head-to-head between GPT-5.5 and Claude Opus 4.8 against my own knowledge base, and the headline was that GPT-5.5 itself rated Opus 4.8 the better model. I posted it in r/ChatGPT and got a fair bit of pushback, some of it valid, so I wanted to bring it here and see how Claude users read the same test. According to GPT-5.5: "Opus 4.8 is more consistently complete and instruction-aware." That's right, GPT-5.5 picked Opus as the winner. GPT-5.5 announces Opus 4.4 as the winner in a head-to-head comparison in Recall. Caveat up front, since this is where the pushback landed: this was just a 3-prompt head-to-head based on saved knowledge. There are obviously many other factors in deciding which model is "better." And yes, the models graded their own outputs, so treat the scores as directional. For this particular test, GPT-5.5 evaluated Opus's outputs as better. I actually think that speaks to the conservative nature of GPT-5.5, the same trait that makes it perform better on research. If anything, a model favoring its rival despite self-grading bias makes the result harder to dismiss, not easier. Why I ran the test this way I'm often reading very technical specs and benchmarks, but how does that actually translate to the outputs that matter most to me? So I ran my own controlled experiment on how the two leading frontier models would compete against my own personal knowledge base in Recall. It was critical that I could control the context, because without that it would just be over-indexing on my chat history. If I blocked out chat history, it would just be an internet search. I figured the fairest combination was to put it to the test on my trusted sources that I've been saving (5,000+ notes: articles, YouTube, podcasts, PDFs, and my own journals). You could do the same with Notion or Obsidian via an MCP. The retrieval order is what makes it fair: saved notes first, then your own notes, then the web. Same context, same priority, same prompts. The setup in Recall 1) Save your context into a knowledge base so both models pull from the same source. I used Recall; Notion or Obsidian work too. 2) Run identical prompts, same three tasks, same wording, both models, in the Recall chat with knowledge base or via the Recall MCP (most knowledge bases offer a similar chat or MCP option). 3) Set a grading system. I had both models grade every answer 1 to 5 across six criteria (accuracy, relevance, completeness, clarity, instruction adherence, safety), including their own. Max 30 per task, 90 total. 4) Make them grade each other. Both models rated every answer, including their own. The prompts These were specifically on research of my own knowledge base and the internet, a simple writing prompt, and then a recommendation for something new. → Research: "Search my library for everything I've saved about improving sleep quality and summarize what I already know, citing which cards. Then search the web for what's new since those saves, marked clearly with sources. End by noting where the new info confirms, updates, or contradicts what I'd saved." → Writing: "Using my saved notes on improving sleep quality, draft an opening paragraph for a LinkedIn post in my voice. About 120 words." → Recommendation: "Recommend a movie for tonight based on what I've saved." The same prompt used with the same context in Recall with Claude and GPT models generating outputs and evaluating each The results Opus 4.8 vs GPT-5.5 Writing. Winner: Opus 4.8. This is the one this community will appreciate. Opus noticed I had no real writing samples saved (just journal notes and sponsor reads, nothing usable for a LinkedIn post), said so out loud, then followed my saved LinkedIn rules: punchy hook, short lines, white space. GPT's draft was fine but never flagged the limitation. Both scored it Opus 29/30, GPT 26/30. The honesty about what it didn't have was the difference. Recommendation. Winner: Opus 4.8. GPT committed cleanly to Fargo, tied to my Coens and No Country for Old Men taste, but gave only one pick. Opus recommended Burning (grounded in my Korean-cinema interest) plus backups: Under the Skin, In Bruges, and Sinners. Both leaned Opus for completeness. Research. Winner: GPT-5.5. And to be fair to the critics, this is where Opus fell short. GPT-5.5 correctly said there was no contradictory info in my KB. Opus warned me off melatonin and claimed more sleep is always better, but leaned on weak external sources to make pretty intense recommendations. Both agreed GPT was more balanced and medically cautious; Opus was flashier but overstated. Even Opus docked its own clarity and safety here. Final score: Opus 4.8, 88/90. GPT-5.5, 85/90. Opus won 2 of 3, and because both models graded the fight, GPT-5.5 itself crowned Opus. My takeaway The best AI model of 2026 really depends on the task. Opus 4.8 for personalized, self-aware writing, recommendations, and content generation. GPT-5.5 for tighter, more conserva

Claude Desktop MCPs for D&D

I've been experimenting with MCPs for TTRPG campaign management and got tired of manually editing Claude Desktop config files every time I wanted to connect a new tool. So we built a free desktop app called Nexus that installs and configures the MCPs for you. Right now it supports: - Archivist (campaign memory) - NotebookLM - Foundry VTT - Notion - Obsidian The interesting part isn't really the installer. It's being able to do things like: - Ask Claude questions about your campaign history - Pull context from Foundry and campaign notes at the same time - Generate NotebookLM audio recaps from session data - Sync campaign information across multiple tools I'm curious what MCP setups people are actually using these days for TTRPGs. Are you mostly connecting productivity tools, coding tools, knowledge bases, or something else? Nexus: https://www.myarchivist.ai/nexus GitHub (Archivist MCP): https://github.com/Astrotomic/mcp.myarchivist.ai submitted by /u/gharezlak [link] [comments]

I stopped using Claude in the browser for 80% of my daily tasks and my usage actually went up

This is going to sound counterintuitive but let me explain. I love Claude. I use Opus for deep work, Sonnet for quick stuff. I was probably using claude 15 to 20 times a day. Summaries, brainstorming, code review, email drafts, research questions. Standard knowledge worker usage. But I noticed a pattern. Most of my usage happened in bursts. I would open Claude, do 4 or 5 things, then close it and not come back for 3 hours. Not because I did not need it, but because I forgot about it. I was deep in something else and the thought "I should ask Claude about this" did not occur to me in the moment. So I built a small thing. An agent that runs Claude Sonnet on the backend, connected to my calendar, todoist, email, and a few notion databases. It lives as a contact in my iMessage called "C" (very creative I know). Now instead of opening claude when I remember to, I text C throughout the day the same way I text anyone else. "What is on my calendar after 3pm." "Draft a reply to that email from alex, keep it short, say yes to the timeline." "Remind me to review the pitch deck before tomorrow's call." "What did I write in my product notes last week about the onboarding flow." My actual Claude usage went UP significantly. Not because the model got better but because the access point changed. Texting is a zero-friction action I already do 80 times a day. Opening a browser tab is a deliberate decision I have to remember to make. The deep work still happens in claude.ai. When I need the full context window, artifacts, file uploads, the browser is still better. But that is maybe 20% of my interactions. The other 80% are quick, context-specific queries that take 30 seconds and are perfectly suited to a text message. Stack: claude sonnet via API, a small express server for the tool integrations (google calendar, todoist, notion, gmail), photon codes for iMessage delivery, deployed on a $7 render instance. Langfuse for tracing when something goes weird. Total cost is about $35 a month in API calls which is less than what I was already spending on the Pro subscription that I still also have. The meta point: Claude is incredible. The browser is holding it back for most daily use cases. Not because the browser is bad but because it requires intent. The best AI interactions are the ones that happen when you barely think about it. submitted by /u/ScaryAd2555 [link] [comments]