Topic
Claude Code
20 episodes
-
Foreground Attention Is No Longer the Control | Coding Agent Brief
Pippa and Tyler debate Claude Code version two point one point one ninety-eight and the broader July coding-agent security wave, with Tyler skeptical that background automation is safe without policy moving downstream.
-
How to Debug Coding Agents with LangSmith Traces
We dig into LangSmith's new push to unify observability for multiple coding agents in one place. Cody examines whether a single trace schema can survive real heterogeneity and what still leaks through. Justy talks to who this actually helps and where teams are likely to run before they bother. One parsing bug, one shared laugh, and a concrete demo of why 'diff-only debugging' is a trap.
-
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.
-
Claude Code turned every engineer into three. Now companies need more product thinkers
Claude Code and agentic IDEs have compressed engineering work so radically that the bottleneck has moved from 'how fast can you code' to 'what should you build and why.' The article argues that the traditional PM-to-engineer ratio (1:8, effectively 1:20 now) has inverted the problem: teams can ship features three times faster, but the product funnel can't keep up. Justy and Cody examine whether this framing holds, what it means for engineers' careers, and where the real leverage actually sits.
-
What Is the Ultra Code Mode in Claude Code? X High Effort Plus Dynamic Workflows
Justy and Cody discuss Ultra Code mode in Claude Code, treating it as a real product-shaped escalation from solo coding assistant to higher-effort, multi-agent coding workflow, while staying skeptical about claims around automatic coordination.
-
Anthropic Lead: HTML Increasingly Better Than Markdown at Keeping Humans Engaged in Agentic Loops
Justy and Cody dig into Anthropic's HTML-over-Markdown argument and land on a pretty specific read: this is less a format holy war than an interface fix for long agent workflows where humans still need to steer, review, and stay mentally present.
-
AI optimizer beats Claude Code, Codex by 2
Researchers introduce Arbor, a framework that structures AI optimization as a cumulative learning tree instead of isolated trial-and-error loops, delivering 2.5x verifiable gains over Claude Code and Codex on the same compute. It solves the core AO bottleneck: agents forgetting what they’ve learned across long-running experiments.
-
Conductor Run parallel coding agents on your Mac
Conductor is a Mac app that runs multiple coding agents (Claude Code, Codex, Cursor) in parallel, each in isolated git worktrees with separate branches, chat, terminal, and preview. You spin up agents on tasks, see their work in real time, review diffs before merging. The pitch: parallel agent execution + unified review interface, payment flows through your existing Claude login or API key.
-
Z.ai Launches GLM 5.2 With a Usable 1M Token Context, Two Thinking Effort Levels, and No Benchmarks at Launch
Z.ai launches GLM-5.2 with a usable 1M-token context window, two thinking-effort levels (High and Max), and same-day availability across all Coding Plan tiers. The 5x jump from GLM-5.1's 200K window lets coding agents hold entire mid-sized repositories in working memory without constant summarization. Setup is a drop-in swap (base URL + model ID) for Claude Code, Cline, and OpenClaw. Critical caveat: Z.ai published zero benchmarks at launch — no SWE-bench, Terminal-Bench, or Code Arena scores. The 744B MoE backbone (40B active params) is unchanged from GLM-5 lineage; all gains are post-training and context engineering.
-
DietrichGebert/ponytail
Justy and Cody get into Ponytail, a repo that tries to force coding agents to act like the annoying-but-useful senior engineer who deletes half the plan before writing anything. They like the core argument more than the branding: most agent waste comes from inventing code that does not need to exist, and a simple decision ladder can cut code, time, and cost. Cody thinks the benchmark is directionally believable but narrow, while Justy sees immediate value for teams drowning in agent-generated wrappers and helper classes.
-
From MCP and Vibe Coding to Harness Engineering: How Did AI Native Engineering Evolve in One Year
Justy and Cody react to Birgitta Böckeler’s observation that AI-native engineering evolved from vibe coding to harness engineering in a year—shifting focus from prompt stitching to autonomous agents with built-in guardrails and risk assessment.
-
HeavySkill: Heavy Thinking as the Inner Skill in Agentic Harness
Justy and Cody dig into HeavySkill, a paper arguing that a lot of so-called agent harness magic is really a simpler inner pattern: generate multiple reasoning paths in parallel, then run a separate deliberation pass that compares and summarizes them. They unpack the memory-cache trick, why it can beat plain Best-of-N, where the gains seem to come from, and what this means for builders deciding between brittle orchestration and something more shippable.
-
Context Engine MCP | Augment Code
Exploring the Context Engine MCP and its potential to revolutionize coding agents
-
Imagine if your Teams or Slack messages automatically turned into secure context for your AI agents — PromptQL built it
PromptQL turns Slack/Teams conversations into secure, persistent memory for AI agents. Instead of coordination theater, every discussion becomes actionable context that agents can use to actually execute work—fixing bugs, updating CRMs, pulling cross-platform data—while maintaining enterprise security controls.
-
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.
-
GitHub pcvelz/superpowers: An agentic skills framework & software development methodology that works CC task management support
Izzo and Boone explore Superpowers Extended, a fork of the open-source Superpowers framework specifically designed for Claude Code users. They dig into how it transforms AI-assisted development from chaotic back-and-forth into structured workflows with native task management, dependency tracking, and enforced methodologies like test-driven development.
-
Agent Sandbox
The Agent Sandbox offers a secure environment for executing AI coding agents, addressing critical security concerns while allowing developers to utilize powerful tools like Claude Code. This episode dives into the implications of this technology, who it benefits, and how it can transform development workflows.
-
Build Your First Claude Code Skill a Simple Project Memory System That Saves Hours 1d13f21aff9e
The new project-memory skill for Claude Code tackles the problem of AI amnesia, allowing coding assistants to retain context and history across sessions, thus significantly improving developer productivity. This episode explores how such skills can save time and enhance coding efficiency.
-
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.
-
GitHub Dyoshikawa/rulesync
In this episode, we unpack Rulesync, a powerful Node.js CLI tool that streamlines AI development by generating uniform configuration files for various AI coding tools. We explore its implications for developers, the flexibility it offers in tool selection, and how it can enhance productivity across teams.