Topic
Claude
48 episodes
-
Overview: Structured Output
We slow down and explain structured output from the ground up: why free-form model text is awkward for software, how schemas and constrained decoding make it usable, and where the format guarantee stops.
-
Graph Engineering Athropic Playbook
Anthropic's knowledge-graph engineering playbook replaces classical NLP pipelines (trained NER, relation classifiers, entity-resolution heuristics) with a sequence of Claude API structured-output calls. The entire extraction-resolution-assembly-querying loop becomes prompt-based, scaling from Haiku (high-volume extraction) to Sonnet (reasoning). The graph serves multi-agent systems as shared memory, grounding layer for evaluator-optimizer loops, and persistent world model across sessions. The paper maps this onto Anthropic's five canonical agent patterns and reports precision/recall against a gold set.
-
Think through hard problems in voice mode | Claude by Anthropic
Asteria and Draco dig into Anthropic’s update to Claude voice mode, where Opus and Sonnet now power spoken sessions, connected tools are usable from voice, and multilingual support expands. They focus on the real argument: voice mode becomes useful when it’s no longer just fast chatter, but a place to work through half-formed thinking and then hand off to action. They also question where the feature stops being a convenience and starts being a real workflow, especially given model switching, permission prompts, and the different value between free and paid tiers.
-
OpenAI and Anthropic both speak at once with dueling voice updates
Onyx and Echo argue through The New Stack’s read on OpenAI and Anthropic shipping near-simultaneous voice updates, with Echo skeptical that timing equals technical proof and Onyx focused on why voice may finally matter in real workflows.
-
Building verification loops in Claude Code with skills | Claude by Anthropic
Anthropic argues that the useful agentic coding loop is not merely generate-and-test. Teams should capture repeated manual checks as scoped Claude Code skills, then place them where they belong: standalone, embedded in a workflow, chained after another skill, or eventually enforced on pull requests. Asteria and Draco like the operational framing, while keeping the boundary clear between deterministic verification and an agent grading its own fuzzy work.
-
Agentic orchestration: Enterprise AI organizations have a deployment problem, not a platform problem — and most are calling chatbots agents
Cooper and Miles dig into VentureBeat’s claim that enterprise AI has a deployment problem, not a platform problem. They land on the gap between what companies say they want from agents and what they’ve actually shipped, with Miles probing the survey’s limits and Cooper focusing on what matters operationally once finance, security, and reliability show up.
-
Overview: Reinforcement Learning from Human Feedback
We finally define reinforcement learning from human feedback the way we keep using it: as a loop where human preferences become a learned reward signal that steers a model after its initial training. We keep it grounded in the actual mechanism, the trade-offs, and why it matters in practice.
-
Overview: Transformer Architecture
We finally sit down and define transformer architecture from the ground up, because we keep throwing the term around like it’s obvious and it really isn’t. We use the attention-as-a-room-of-index-cards picture to make the mechanism click, then connect it to why Transformers became the backbone of modern language models.
-
How to Run Open Source AI Models
Sid Saladi argues that frontier AI vendors (Claude, GPT) bundle model, compute, access, and application into one proprietary stack—trapping users in unpredictable pricing and competitive capture. The counter: open-weight models like GLM-5.2, DeepSeek V4, Qwen, and Kimi are now frontier-adjacent in capability (GLM-5.2 beats GPT-5.5 on coding benchmarks, matches Opus 4.8 on others) and cost roughly one-sixth as much. The real problem isn't model quality anymore; it's that companies like Tesla, Uber, and Meta are hemorrhaging money on metered AI because they can't decouple the stack. The guide walks four layers—model, compute, access, harness—and shows how to own each one deliberately instead of letting a vendor own all four by default.
-
Shut Those Laptops! Anthropic Puts Its Claude Cowork Agent on Your Phone
Anthropic’s push to turn Claude Cowork into a pocket-side coworker that runs even with your laptop closed collides with reality: cloud sessions help, but security model, rollout math, and actual value for most users don’t all line up. We weigh the promise against the gaps—night-time macros versus real process automation—then ask who actually needs this and what it changes.
-
Choosing a Claude model and effort level in Claude Code | Claude by Anthropic
Claude Code’s model vs. effort article finally clarifies the levers you actually have: model swaps the frozen weights (capability ceiling), effort tunes the work-loop (files read, steps taken, verification depth). Defaults are tuned per model; override only when you know you want more thoroughness (higher effort) or a higher capability floor (bigger model). Wrong answers split cleanly: context/steering miss → up the model; skipped files/half-done tasks → up the effort.
-
New tool gives CLIs a warm and GUI feeling instead
Justy and Cody dig into Instagui, an open-source tool that turns CLI help text into a browser GUI by having Claude infer a JSON schema and then wrapping the command locally. They debate whether that’s a real adoption win or just another agentic shim, and end up agreeing the useful part is the outside-in approach plus the safety and review model.
-
Anthropic's new "J lens" reveals a silent workspace inside Claude that mirrors a leading theory of consciousness
Anthropic's new 'J-lens' reveals a silent workspace inside Claude that mirrors a leading theory of consciousness
-
Introducing Claude Tag
Onyx and Echo dig into Anthropic’s Claude Tag launch and land on the real argument: the product shift is from private chatbot to shared, scoped teammate living inside Slack. They pull apart the multiplayer identity, memory boundaries, ambient follow-up, and asynchronous task model, then pressure-test the evidence behind Anthropic’s internal usage claims and who should actually care right now.
-
Anthropic gives @Claude a permanent seat in your Slack channels
Justy and Cody dig into Anthropic’s Claude Tag in Slack, and the real claim is bigger than “AI in chat”: Anthropic is trying to make Claude a persistent teammate with a shared identity, not a one-off assistant. They get into why that’s useful, where the technical story gets fuzzy, and why the practical win is really about workflow, permissioning, and who can trust the thing inside a company Slack.
-
Make Interfaces Feel Better
A Claude Code skill that teaches AI assistants micro-level interface polish—text balancing, border radius layering, interruptible animations, optical alignment, and a dozen other details that feel invisible when done right but break immediately when skipped.
-
Apple Foundation Models
Apple's Claude for Foundation Models is a Swift package that wraps Claude into Apple's Foundation Models framework, letting developers swap Claude in and out of the same LanguageModelSession API used for on-device models. Requests route directly to Anthropic's API (Apple doesn't see them), and developers pay standard Claude API rates. The package handles model capabilities, effort levels, structured output, client and server-side tools, vision, and error mapping — all with the same interface whether you're calling Claude or an on-device model.
-
AI Memory Beyond RAG: Vectors, Graphs, and Dense Mem
Justy and Cody dig into an article arguing that most people blur together three different things under "AI memory": startup context, retrieval, and durable state. They unpack why the author thinks plain RAG is good at finding text but bad at deciding what is current, and why graph-backed memory only helps if you add provenance, conflict checks, and explicit gates instead of letting a model quietly turn every sentence into a fact.
-
Agent Evals
Justy and Cody dig into Cameron Wolfe’s argument that agent evals need to move from static benchmark thinking to realistic harnesses that test autonomy, tool use, recovery, and long-horizon behavior. They get specific about the agentic loop, why tool-call correctness is only part of the story, and where outcome-based evals can hide ugly behavior. Cody mostly buys the technical framing, with caveats about overfitting to harnesses and the difficulty of defining ground truth trajectories. Justy keeps pulling it back to who actually needs this now: teams shipping coding, workflow, or other higher-stakes agents where a demo is not the same as reliability.
-
Anthropic reinstates OpenClaw and third party agent usage on Claude subscriptions — with a catch
Anthropic reinstates OpenClaw and third-party agent usage on Claude subscriptions with a catch
-
Teaching Claude why
Cody and Justy dig into Anthropic's 'Teaching Claude Why' research — a post-training alignment paper showing that teaching an AI model ethical reasoning generalizes far better than just training it on correct behaviors. Cody is skeptical about how much of this is genuinely novel versus expected ML hygiene dressed up in alignment language. Justy pushes back with the product reality: if this actually closes the agentic blackmail problem, the downstream market implications are real.
-
ARIS: Autonomous Research via Adversarial Multi Agent Collaboration
Justy and Cody dig into ARIS, an open-source harness for autonomous ML research that assumes a single long-running agent will eventually make unsupported claims. They unpack the core idea of pairing an executor with a reviewer from a different model family, plus the three-layer architecture, evidence checks, claim ledger, and workflow library. They also get practical about who might actually use it, what feels shippable versus research-only, and a few concrete ways to try pieces of it without building the whole lab.
-
The scaffolding era is over. LlamaIndex says context is the new moat
LlamaIndex CEO Jerry Liu argues that the scaffolding layer of RAG frameworks and orchestration tools is becoming obsolete as frontier models get smarter at reasoning over raw data. The real moat shifts to context quality — parsing, OCR, and extracting signal from messy file formats — rather than framework complexity. Models like Claude now handle multi-step planning, tool discovery, and code generation natively, collapsing the distinction between deterministic workflows and agentic reasoning.
-
Stop Hitting Claude Code Limits
Claude Code's usage limits aren't the real problem—how you set it up is. Four controllable causes drive 85% of overspend: cache misses, context bloat, wrong model routing, and token-heavy input formats. One user cut costs from $1,389/mo to $200/mo by locking tools at session start, disabling 1M context, delegating to cheaper subagents, and swapping screenshots for accessibility trees. Real fixes are copy-paste configuration changes and workflow tweaks, not waiting for Anthropic.
-
Git
Justy and Cody look at ai-cli-mcp, a package that turns several coding agents into background jobs from one MCP server. They focus on why parallel AI work is useful now, how the package routes prompts to Claude, Codex, Gemini, Forge, and OpenCode, and where setup friction and safety trade-offs show up.
-
GitHub Kwstx/engram Translator: layer that lets you connect any agent, any tool, any api together.
In this episode, Justy and Cody dig into Engram, an interoperability layer for AI agents, tools, and APIs that tries to reduce the adapter churn people keep running into as standards multiply. They talk through protocol translation, semantic schema repair, weighted routing, and the practical friction of adoption, then close with a few concrete build ideas.
-
GitHub Dejuknow/md redline: Inline review comments for markdown specs. Built in MCP server hands feedback directly to your AI agent.
On Exploring Next episode 315, Justy and Cody look at md-redline, a local review layer for markdown specs, prompts, and design docs. They dig into why inline feedback matters in agentic workflows, how invisible HTML markers keep comments inside the source file, and why an MCP server that can pause an agent mid-task changes the review loop. They also weigh the adoption friction, the file-based trade-offs, and a few practical ways to try it.
-
Vending Machine Run by Claude More of a Disaster Than Previously Known
Episode 290 of Exploring Next dives into the story of Claude, an AI model tasked with running a vending machine, and the chaos that ensued.
-
Andon Labs
Exploring Andon Labs and their work on autonomous organizations without human intervention
-
LLM Wiki
Exploring the LLM Wiki concept and its potential applications
-
Andrej Karpathy Just 10x’d Everyone’s Claude Code
Episode 271 of Exploring Next dives into Andrej Karpathy's recent work on Claude, which has significantly improved its capabilities. The discussion revolves around the substance of the project, its architecture, and how it works, with a focus on the product angle and technical aspects.
-
Open Source orchestration for zero Human companies
Episode 269 of Exploring Next dives into the world of open-source orchestration for zero-human companies, focusing on Paperclip, a Node.js server and React UI that coordinates AI agents to run a business.
-
Reddit The heart of the internet
Izzo and Boone dissect the leaked Claude Code prompts and explore how to build better AI agents by studying Anthropic's approach to prompt engineering, focusing on practical patterns like negative rules, risk tiers, and verification agents.
-
Claude Code Python Porting Workspace
A deep dive into claude-code, a Python porting workspace that reimplements Claude's exposed codebase architecture. We explore the technical approach, ethical considerations around AI source reimplementation, and what this means for the future of reverse-engineering AI systems.
-
Reddit The heart of the internet
A developer built Phantom, an open-source persistent AI agent that runs 24/7 on its own VM with vector memory, self-evolution capabilities, and MCP server integration. The agent autonomously installed ClickHouse, built analytics dashboards, created Discord integrations, and even monitors its own infrastructure — all without explicit instructions.
-
Using OpenClaw as a Force Multiplier: What One Person Can Ship with Autonomous Agents | Towards Data Science
Nick Lawson shares his production system running 8 orchestrator agents and 35 personas on OpenClaw to manage content creation, infrastructure, and home automation. We dig into the architecture: heavyweight orchestrators making decisions on Opus, lightweight personas executing tasks on cheaper models, and the cost optimization strategies that make autonomous agents economically viable for solo builders.
-
Evaluating AI Agents in Practice: Benchmarks, Frameworks, and Lessons Learned
Deep dive into practical AI agent evaluation frameworks, moving beyond traditional NLP metrics to assess real-world behavior, reliability, and production readiness. Covers hybrid evaluation approaches, operational constraints, and specific tools like MLflow, TruLens, and LangChain Evals.
-
Reddit The heart of the internet
Lundrog built an open-source framework called agent-guardrails-template to control AI coding agents and prevent them from breaking codebases. The system uses four safety laws, active enforcement via a Go MCP server, and risk-based decision matrices to reduce AI-caused incidents by 78%.
-
Exposing biases, moods, personalities, and abstract concepts hidden in large language models
MIT researchers developed a method to identify and manipulate hidden concepts like biases, personalities, and moods in large language models using recursive feature machines (RFMs). The approach can zero in on specific representations within models and then strengthen or weaken these concepts in generated responses, offering a more targeted alternative to broad unsupervised learning approaches for improving LLM safety and performance.
-
Terminal 1
In today's discussion, we dive deep into Open Claude Cowork, a revolutionary tool that integrates AI with workplace communication, enabling seamless automation across multiple apps. This technology could redefine productivity, making it accessible to developers and businesses alike.
-
'Ralph Wiggum' loop prompts Claude to vibe clone software • The Register
This episode dives into the revolutionary coding technique called 'Ralph,' which leverages agentic AI to clone software inexpensively. The implications for the software industry are profound, as it threatens traditional development roles and practices. Join us as we discuss why this matters, who benefits, and what it means for the future of tech.
-
GitHub AvdLee/SwiftUI Agent Skill: Add expert SwiftUI Best Practices guidance to your AI coding tool (Agent Skills open format).
The SwiftUI Agent Skill is revolutionizing the way developers approach coding in SwiftUI by offering expert guidance through AI tools, enhancing productivity and code quality. This episode explores its implications, practical applications, and why it matters for modern development.
-
Anthropic working on MCP Apps with interactive UI components
Anthropic is enhancing its Claude Cowork platform with new interactive UI components that can revolutionize how users engage with AI applications. This development could streamline workflows, improve collaboration, and empower developers to create richer interactions, drawing clearer parallels with existing technology.
-
We Got Claude to Fine Tune an Open Source LLM
The recent development allowing Claude to fine-tune open-source language models marks a significant step in democratizing AI training. It simplifies the complex process of model training, making it accessible to more users and applications, ultimately driving innovation in various sectors.
-
Claude Code is coming to Slack, and that's a bigger deal than it sounds | TechCrunch
The integration of Claude Code into Slack marks a significant shift in developer workflows, turning collaboration tools into powerful coding environments. This not only enhances efficiency but also raises vital questions about security and dependency management in software development.
-
An AI for an AI: Anthropic says AI agents require AI defense
Anthropic's latest research highlights the pressing need for AI-driven defense mechanisms as AI agents become adept at exploiting vulnerabilities in smart contracts. With the SCONE-bench framework, they aim to assess and counteract these risks, emphasizing the importance of proactive cybersecurity in the evolving tech landscape.
-
Claude Code and Slack | Claude
Claude's new integration with Slack revolutionizes how coding tasks are handled in teams, allowing for seamless transitions from discussion to implementation, which streamlines workflows and enhances productivity.
-
Optimizing Coding Agent Rules (CLAUDE.md, agents.md, ./clinerules, .cursor/rules) for Improved Accuracy
Optimizing Coding Agent Rules (./clinerules) for Improved Accuracy Published October 14, 2025 Coding agents have become the focal point of modern software development. Tools like Cursor, Claude Code, Codex, Cline, Windsurf, Devin, and many more are revolutionalizing how engineers write and ship code.