An Exploded View publication
This week's theme
The biggest labs are lobbying Washington over how fast AI should move, while the practical stories below are about building your own agents and second brain.
A 23-minute read · 14 storiesIn this issue
OpenAI and Anthropic, two direct rivals, have jointly asked the US government to consider slowing parts of the AI race, according to a Washington Post report picked up by Google News. When two competing labs ask together for the brakes to be considered, that says more about how the people building this technology see the risk than any outside critic could.
Andrew Ng just backed one specific bet on how AI changes learning, with real money behind it, and that is worth watching. He built Coursera and helped start Google's early AI research group, so when he stakes a new company on one big idea, it says something about where the harder problems in this market really are.
The company is called LearnVector, launched in 2026 out of Mountain View, California, with Coursera investing $100 million into it. Ng is founder and chief executive, and his mission statement for the company is blunt: 'accelerate human development.' His resume backs the bet. He co-founded Coursera, co-founded Google Brain (Google's early AI research group), and founded the education site DeepLearning.AI. LearnVector plans to work closely with both Coursera and Udemy, another large online course company, to bring their libraries of vetted teaching material into whatever it builds.
Ng draws a direct line to his own history. Fifteen years ago, he says, Coursera and online courses changed education by opening up where people could learn, expanding access far beyond a physical classroom. But that barely changed how people learn: courses are still taught the same way to everyone who shows up, in the same fixed order. He says AI now gives a real chance to fix that second half of the problem, building what he calls 'a custom learning guide for each person.'
His argument for why this matters is about economics, not just technology. Good teaching has always been rationed by cost, geography, and time. One student with a great personal tutor learns faster than the same student sitting in a large classroom, and everyone has always known that. Schools built classrooms anyway, because no one could afford to give each person their own tutor. That was never a limit of how people learn. It was a limit of what could be paid for. He is specific about where plain chatbots fail too: research shows chatbots without guardrails (limits on what the AI is allowed to do) actually harm learning. Letting a chatbot hand you a finished answer means you retain less of it yourself, a pattern researchers call 'cognitive offloading.' A chatbot can also simply be wrong, so trusting one for real learning is risky on its own.
LearnVector's answer is to build a genuine one-to-one learning experience rather than another chatbot. The product is meant to plan a learning path together with the student, adapt as it learns how that person actually learns, and stay patient with them until they master a skill, rather than moving on the moment they get an answer. Ng frames this as a shift from one-to-many teaching to one-to-one. 'A chatbot can give you an answer, but an answer is not an education,' Ng writes, drawing the line between the two directly.
LearnVector is still heads-down building, with a product to show by early 2027, not before. The team is small and works on-site in Mountain View, hiring for a short list of open roles. The AI Engineer role is described as building the agentic systems (AI that takes several steps on its own) at the core of the product, helping it understand learners and plan a path with them. The Learning Engineer role calls for applying expertise in teaching to build engaging products, informed by the science of how people actually learn. The Learning Scientist role is tasked with inventing new ways to teach using agentic AI, and rigorously measuring whether users are actually developing and keeping new skills, not just passing a test. The job posting describes the team as small and fast-moving, made up of experienced builders passionate about AI and human development. Ng closes his announcement thanking Coursera's Greg Hart and the wider Coursera team for backing the new company.
Outside your usual reading: Meta's Ray-Ban smart glasses can secretly record video hands-free, and a wave of prank and pickup-artist clips filmed without consent earned them the nickname 'pervert glasses.' Instagram head Adam Mosseri says the app will remove that content, and Meta has already pulled creator accounts that broke the rule. Worth remembering if you ever build hardware with a built-in camera: trust breaks before habits form.
Anthropic says its Claude Mythos model helped uncover real vulnerabilities in a post-quantum cryptography scheme (encryption designed to survive future quantum computers). That is the entire claim available here, since the underlying article did not load. Still worth flagging: it points to AI models doing real security research, not just writing code.
Meta chief executive Mark Zuckerberg is pushing back on a growing push in Washington to ban Chinese-made AI models. The specific case he makes was not available beyond the headline here. Worth tracking either way, since a ban would directly affect which models and tools you are allowed to use.
Outside your usual reading: a small logic puzzle explains a rule you have probably used without noticing. Python's all() function checks every item in a list and returns true when the list is empty. That is not an arbitrary choice. True is the 'identity' value for AND (the logic test where every condition must hold), meaning combining it with anything else leaves that thing unchanged. The same reasoning is why summing an empty list gives zero, and why any() on an empty list gives false.
Microsoft's chief executive argues AI creates two kinds of company capital, and the loop between them is the real advantage.
This is worth your attention because it names the strategic question sitting under every AI decision you will make as a founder: what should your venture keep and grow itself, and what can it safely hand to an AI model. Satya Nadella, the chief executive of Microsoft, laid out his answer in a post Elon Musk resurfaced on X (the social platform) on 2026-06-14. Nadella runs one of the largest companies in the world, so his framing carries real weight, not just theory.
Nadella's starting point is that this shift is not like the earlier ones. Past waves of computing, from spreadsheets to the internet, made human workers more capable using digital tools, but the tools stayed tools. What is new now, in his words, is a real 'cognitive loop' between people and digital systems. Each side can make the other better, continuously, rather than one simply serving the other. That changes what a company even is, in his view. The old question was which software to buy. The new one is whether a firm is building a system that keeps learning from its own people, or just renting a model that learns from everyone equally, handing every competitor the same advantage.
He splits what a company owns into two kinds of capital. Human capital is the knowledge, judgment, relationships, ingenuity, and pattern recognition inside its people. Token capital is his term for the AI capability a firm builds and owns itself, named for tokens (the small chunks of text, each roughly three quarters of a word, that AI models process). His central claim is that growing token capital does not make human capital less valuable. It makes it more valuable, because people are the ones who set ambitious goals, connect ideas across fields, build relationships, and recognize which patterns actually matter. Without a person directing it, he writes, you just have compute (the chips and time needed to run a model) running in circles.
The practical move, in his account, is building a learning loop. A company's own work keeps teaching its AI systems, so human capital and token capital compound together over time. Every workflow the company improves generates a better training signal. That speeds up how fast the firm builds knowledge unique to it, the kind a rival cannot easily copy. Two concrete pieces make this real. Private evals are tests built around whether a model is actually getting better at outcomes the business cares about. That is different from its score on public leaderboards everyone else also chases. Private reinforcement learning environments are extra rounds of training that use a company's own real work as the practice material. The model keeps improving on that firm's actual problems this way, and its know-how becomes something employees can search, instead of something they have to remember or re-discover.
Nadella adds one test for whether a company truly controls this, instead of just renting it. A firm should be able to swap its underlying 'generalist' model for a newer one. It should not lose the years of company-specific expertise its own learning system has built up in the process. He also names the downside directly. If only a handful of AI models end up capturing most of the economic value companies create, he expects the public will not accept it.
His prescription is to build what he calls a frontier ecosystem: a wide base of companies and tools around AI, not one dominant model that captures everything. That way gains spread across many firms, instead of pooling in a few. For a solo founder building with AI, the practical read is blunt. The advantage is not which model you subscribe to. Any competitor can rent the same one. It is the loop you build on top of it, turning your own accumulated work into an asset a rented model can never copy. That is the difference between a company that gets smarter from its own work every day, and one that just pays a subscription for intelligence every rival can also buy.
Without human direction, you have compute running in circles.via Satya Nadella (via @elonmusk on X) →
A legendary engineer's plain text editor beat every fancy setup, a reminder that tools matter less than the problem you pick.
This is worth reading as a check on your own instincts. Founder time is the scarcest thing you have, and it is tempting to spend it perfecting tools instead of shipping the actual work.
The story comes from a former Facebook engineer describing a colleague he calls Bob, a 'legendary' engineer who shipped Facebook Groups among other features and won hackathon after hackathon. At the time, the author called himself a 'massive productivity nerd.' He ran a custom Vim setup with his own syntax highlighting and snippets for Hack, Facebook's own dialect of the PHP programming language. His setup also included tmux (a tool for running multiple terminal sessions at once) over mosh (a remote connection tool), custom shortcuts for Facebook's PHP debugger, and elaborate git aliases.
Sitting next to Bob at a hackathon, the author expected to learn Bob's secret. Instead Bob opened plain, unmodified Sublime Text, a basic text editor, with none of that setup. Half the code was colored wrong because the syntax highlighting was not even configured properly. Bob used no live reloading and no debugger. Instead he sprinkled print statements through the code and patiently read the logs they produced. Bob won the hackathon that day anyway. The author believes Bob was building an early version of the buy and sell posts inside Facebook Groups, the feature that later grew into Facebook Marketplace.
The author's takeaway: he was so focused on how Bob worked that he nearly missed what Bob was building. Bob's product taste and instinct for the right problem mattered more than any editor setup ever could. He connects this to a pattern he still sees today: a constant stream of new tools and workflows on X, each one promising to change everything, when what actually matters most is picking the right problem to solve.
His product taste and intuition were more important than the editor setup he used.via frantic.im →
A framework for turning yourself from a prompter into someone who designs systems that prompt the agent for you.
This lands on your desk because it is close to the shift you are already making with your own loop and cron setups, so it works as a gut check on whether you are missing a step. A builder posting as Codez laid out a 14-step roadmap for moving from typing prompts by hand to designing small systems that prompt a coding agent for you. His claim: nine out of ten developers still write a prompt, read the answer, then write the next one, with no automation, no saved state file, no automatic check, and nothing running the work on a schedule.
The roadmap draws on Anthropic's own engineering notes, a long piece by Addy Osmani, and recent measurement studies. One number stands out: Anthropic says its engineers now merge eight times as much code per day as they did in 2024, though Anthropic itself calls that figure "almost certainly an overstatement of the true productivity gain." The point survives the caveat. The work has shifted from typing each prompt yourself to building the loop, the small system that finds the work, hands it to the agent, checks the result, records what happened, and decides the next move on its own, without you sitting in the chair the whole time.
Before building one, the roadmap sets four conditions, and missing any single one means the loop costs more than it saves. First, the task has to repeat, ideally at least weekly, so the setup time pays for itself. Second, something has to be able to fail the work without you watching: a test suite, a type checker (a tool that checks your code's structure before it runs), a linter (a tool that checks code style automatically), or a full build. Third, your token budget (how many chunks of text, each about three quarters of a word, you can afford to spend) has to absorb the waste, since loops re-read context and retry even on runs that ship nothing. Fourth, the agent needs a senior engineer's tools: logs, a place to run the code it just wrote, and a way to see what actually breaks.
The economics split by budget more than by skill. Teams with repetitive, machine-checkable work, and room to spend on tokens, gain the most: routine dependency updates, style fixes applied automatically, and turning bug reports into draft fixes on a codebase with strong existing tests. A solo builder on a flat consumer plan should be careful, because the token bill often arrives before the payoff does, and a loop with no real check just has the agent agreeing with itself on repeat. The roadmap's 30-second gut check for any one task: does it happen at least weekly, can a test or build reject bad output, can the agent run the code it just changed, does the loop have a hard stop on budget or time, and does a person review anything before it merges or ships? Good starter loops: catching failed automatic tests overnight and drafting fixes, opening pull requests for routine dependency bumps, and auto-fixing style issues whenever a change is proposed. Bad starter loops: rewriting architecture, anything touching login or payments, production releases, and any task where "done" is a judgment call rather than a pass or fail.
The roadmap is also honest about who should stay away for now: anyone working on code with no automated check, solo builders on a flat consumer plan, and any team whose real bottleneck is review capacity rather than typing speed, since a loop just produces more code for an already backed-up queue. Async-first teams already running multiple agents at once are named as the best fit, because for them a loop is the missing layer that decides which step runs when. The source's own honest summary: loop engineering is real, but most developers do not need it yet, and for a one-off task, a single well-aimed prompt still wins. For your own cron and loop setups, the useful test is not whether the idea is trendy, but whether each one you already run would survive this same checklist today.
almost certainly an overstatement of the true productivity gain.via @0xCodez on X →
The exact plugin stack one builder uses to make Obsidian the memory and Claude the reasoning layer.
This is worth full attention because it maps closely onto the vault and Claude memory setup you already run, so it doubles as a direct source of ideas to copy or skip. A builder posting as rari laid out, plugin by plugin, how he turned Obsidian (a notes app) plus Claude into what he calls a second brain: Obsidian holds the memory, Claude does the reasoning on top of it, instead of Obsidian staying a plain filing cabinet and Claude staying a chat window that forgets everything the next day.
Ten plugins do the groundwork. Smart Connections surfaces old notes relevant to whatever you are working on right now, instead of only the file you have open, so research, meeting notes, and old project docs can resurface when useful. Copilot puts an AI chat window inside Obsidian itself, so notes and the conversation about them live in one place. Templater forces every note, daily notes, meeting notes, project pages, content briefs, research summaries, to start from the same structure. Dataview turns tagged notes into live lists and tables built from tags, dates, and status, which matters because it gives an AI something structured to reason over instead of loose prose. Tasks attaches due dates, priorities, and recurring to-dos directly to the notes they belong to. Periodic Notes and Calendar build the daily, weekly, monthly, and quarterly notes that give an AI a timeline of what you were doing and when. Kanban boards track content pipelines, project stages, and research queues visually, and Claude can update the board and suggest the next move. Obsidian Git keeps a version history of the whole vault, so nothing is lost for good. Obsidian CLI opens the vault to the command line, which is what lets an agent like Claude Code search, edit, and manage it directly instead of you copying files by hand.
On top of the plugins sit ten workflows. Each morning, Claude reads recent daily notes, open tasks, and active projects, then writes a short note on what needs attention, what is overdue, and what to focus on first, so there is no time lost deciding where to start. After a meeting, rough notes get turned into a summary with decisions, action items, owners, and links to the related project. When an article, transcript, or idea gets saved, Claude turns it into a research note with key points, useful quotes, related notes, possible contradictions, tags, and follow-up questions, so the material stays reusable instead of sitting unread. Every Friday, a weekly review pulls together completed work, missed tasks, active projects, recurring problems, and ideas worth saving into one summary instead of a manual re-read of the whole week. A new idea gets checked against the vault for related notes he would not have thought to search for by hand. A new project gets a starting structure built automatically: overview, goals, constraints, milestones, related notes, and open questions. Once a month, a vault audit catches notes with no links, inconsistent tags, old projects, and missing metadata before the vault turns into a messy archive. Finished books get one note with highlights, connected to related projects, past ideas, and other books. Before writing a post or proposal, Claude searches the vault for supporting examples, past notes, research, and counterarguments. Before an important decision, a decision note records the situation, the options, the assumptions, the risks, and the final call, so patterns in his own decision-making become visible later.
The advanced layer is the part most directly comparable to a Claude Code plus memory setup: the vault becomes Claude's long-term memory, so every task starts already knowing where the vault lives, how it is structured, and what conventions it follows. An MCP server (a standard way to plug tools into an AI model) then lets Claude search and read the vault as part of its normal workflow, rather than you opening and pasting files by hand, and the source calls this the bridge between notes and full automation.
None of this needs custom code. Every piece here, plugins, templates, and the MCP server, is markdown and configuration a person without a software background could install and edit, which is the same bar the file-agent pitch elsewhere in today's edition is making from a different angle: the second brain is not the hard part anymore, wiring it to check itself is.
Obsidian becomes the memory layer. Claude becomes the reasoning layer.via @0xwhrrari on X →
A claim that a working AI agent takes 30 minutes, no code, using only Claude.
This is on your desk as a sanity check on how far the bar for building an AI agent has fallen, not as a guarantee the pitch is accurate: take the 30-minute framing with a grain of salt, but the underlying distinction between a chatbot and an agent is worth having straight.
The pitch, from a builder posting as Khairallah AL-Awady, is that you can build a working AI agent using only Claude, no code, no API keys, and no terminal commands. His plain definition: a chatbot answers one question and waits for your next instruction; an agent runs a whole sequence on its own, research, pick an angle, outline, draft, review, on a single instruction, and hands back a finished result instead of four separate steps you approve one at a time. He lays out three no-code types. A Chat Agent is a Claude Project whose system prompt (the fixed instructions that sit behind a Project) locks in a multi-step workflow. A File Agent is a Cowork (Claude's tool for handing off whole tasks rather than chatting) job that works through every file in a folder on its own. A Scheduled Agent is a Cowork job set to run on a timer with no input from you at all, for example waking at 7am to check email and save a morning briefing.
The first full build is a Research-to-Article Agent, and it is the one given in the most detail. You create a Claude Project, name it, and paste in a system prompt that runs five steps end to end without stopping for approval in between: search the web for sources and pull out the key insights and numbers; pick the sharpest angle by asking what the reader already believes and how to challenge it; build a detailed outline with a hook and sections with specific data for each; write a full 2,000 to 3,000 word draft in short paragraphs, with the key insight bolded in every section; then review the draft against a short checklist before handing back a finished piece with a suggested title. Feed it a three-word topic, "AI agents for beginners," and it is supposed to return a complete, edited article without the manual research and writing that would otherwise take you time.
The second build is a File Processing Agent. You open the Cowork tab, grant it access to a folder, for example Downloads, and give one instruction: read every PDF inside, pull a summary and the top action items from each, save each as its own file, then build one master file that combines every summary sorted by date. For twenty PDFs, the claim is two to three hours of manual reading and note-taking saved in one pass. The third build, a Scheduled Morning Agent that wakes on its own, checks email, and saves a daily briefing, is introduced by name but the source cuts off before it lays out the actual steps, so that one is a promise rather than a finished recipe.
The honest read: the three-type breakdown, chat agent, file agent, scheduled agent, is a genuinely useful way to sort any agent idea you have, even if a real build usually takes longer than fifteen minutes and needs more editing of the system prompt than the pitch admits. The bar for a non-technical person to build something that used to need code has dropped this low. Whether it holds up on a messy real folder of PDFs instead of a tidy demo is the part worth testing yourself before you trust it with real work.
No API keys.via @eng_khairallah1 on X →
Anthropic released 11 free plugins for Cowork (its tool for handing Claude whole tasks, not just chat), prepackaged for specific jobs: sales, legal, finance, product management, and more. Each bundles ready-made skills, slash commands, and connections to tools like Slack, Notion, and Jira, and you can edit them to match how your own team works. A useful reference now that you build custom agents and skills across your own projects.
A LinkedIn roundup ranks the top AI projects on GitHub (a site where code is shared and starred) by star count: the coding agent OpenClaw leads at 278,000 stars, ahead of Opencode (118,000), Claude Code (75,000), Superpowers (73,000), and Codex (63,000). Other categories cover agent tools like Firecrawl and infrastructure like Open WebUI. A fast way to check whether anything in your own stack is already being out-starred by something newer.
Mark Zuckerberg (@finkd) posted a pointer to his own opinion piece in the Wall Street Journal, then added: he wrote it to explain why he believes AI's future is for everyone, and more is coming about what he calls a positive vision for a world with superintelligence (AI that could exceed human ability at most tasks).
Two rivals agree the race is dangerous, and neither one plans to stop.
How this edition came together — from bookmarks and feeds to the page.
Where they came from
On the cutting-room floor — 26 links read but not run this week
Quality over volume: most links get a second look and a pass. The ones that made it earned their place.
The week's AI signal in 23 minutes — what happened, why it matters, and what to do with it. Curated by someone who actually builds, not a feed algorithm.