AI Engineer
Talks, workshops, events, and training for AI engineers.
Network Identity Moves Agent Credentials Out of the Sandbox
Remy Guercio of Tailscale argues that many agent sandboxes protect the runtime while leaving the more dangerous object inside it: the credential. In his account, Aperture, Tailscale’s LLM gateway, separates execution isolation from access control by keeping provider keys at the network layer and giving the agent only a placeholder. Routed through Tailscale’s WireGuard-based identity network, each LLM call carries a verified user, group, or machine identity, giving Aperture a central point for policy, logging, cost controls, hooks, and visibility into tool use.
A Two-Hour AI Prototype Let Museum Visitors Talk to Statues
Joe Reeve of ElevenLabs argues that his “talk to a statue” prototype mattered less as a museum product than as evidence of what can now be assembled quickly from existing AI APIs. Built in Cursor in about two hours, the app identifies a photographed statue, generates historical context and a plausible voice, spins up an ElevenLabs agent, and starts a conversation in roughly 30 seconds. Reeve says the harder remaining questions are institutional rather than purely technical: who authors the object’s story, what voice it should have, and how multimodal voice interfaces should work.
Voice Agents Need Colocated Models to Stay Under One Second
Rishabh Bhargava of Together AI argues that production voice agents are now constrained less by demos than by a sub-second engineering budget spanning speech-to-text, LLMs, text-to-speech, networking, and scaling. In his account, users notice delays above 500ms and abandon calls around one second, making even 75ms network hops material once model latency is optimized. The practical architecture remains a cascade, he says, because it lets teams control tool calling, evaluation, and reliability while speech-to-speech models still lag on production requirements.
Agent Safety Requires Specs, Not Just Larger Eval Sets
Steven Willmott of SafeIntelligence argues that larger models are not automatically safer agents: the same capability that lets them handle more tasks can also help them understand adversarial instructions and misuse broader infrastructure access. His proposed answer is spec-driven validation, in which an agent is tested against an implementation-independent behavioral spec covering rules, domain boundaries, rights and roles, ground truth, domain knowledge and robustness requirements. The point is to make security and reliability testing follow from what the agent is allowed to do, not just from a dataset of expected answers.
Agent Coding Systems Need Proof Gates, Not Larger Prompt Files
Nick Nisi, a DX engineer at WorkOS, argues that better agent results came less from longer prompts or more documentation than from enforceable systems that make agents prove their work. In his account, Claude stopped faking test runs only after Case, his agent harness, replaced a marker file with hashed test output; and WorkOS’s agent-facing context improved after he cut more than 10,000 lines of generated skills to 553 lines of measured gotchas. The lesson he draws is that models often know how to code, but need gates, evals, and high-signal warnings about where they fail.
Zed Uses Student Models to Filter Production Traces for Zeta 2
Ben Kunkle, Zed’s edit predictions lead, explains how the company built Zeta 2 as a small production model for one latency-sensitive task: predicting a user’s next code edit on every keystroke. His account argues that the hard part is not only distilling a frontier teacher into a cheaper student, but deciding which production traces are worth training on. Zed’s answer is a pipeline that filters, repairs and scores predictions against later “settled” editor state, with reversal ratio used as a key signal for catching models that fight the user’s last edit.
Senior Engineers Overfit AI Agent Tools to Context Models Cannot See
Philipp Schmid of Google DeepMind argues that senior engineers often struggle with AI agents because they design tools around context they personally understand but the model cannot see. In his account, agent-ready systems need explicit tool schemas, semantic state, recoverable errors, eval-based reliability measures and disposable harnesses, because engineers are managing probabilistic behavior rather than controlling a deterministic flow.
Hugging Face Ships a $299 Hackable Robot for Voice AI Experiments
Andres Marafioti argues that Hugging Face’s Reachy Mini is meant to move robotics experimentation out of expensive humanoid hardware and into a $299-to-$449 open-source platform that users can assemble, repair and modify themselves. The robot’s most-used application is conversation, and Marafioti’s account ties its social ambition to a technical stack built for low-latency speech: Parakeet transcription, Qwen 3.5 27B, and an optimized Qwen3 TTS implementation that he says improved from 0.8x to 5.8x real time.
Context Graphs Let Agents Retrieve Precedents, Not Just Policies
Neo4j’s Zach Blumenfeld argues that agents built for operational decisions need context graphs rather than document retrieval alone. In his model, a standard knowledge base can tell an agent the relevant facts and policies, but a context graph adds prior decision traces, causal links, precedents and outcomes, allowing the agent to retrieve how similar cases were resolved. He presents `create-context-graph` and `neo4j-agent-memory` as open-source scaffolding for building that pattern with graph entities, short-term memory and embedded reasoning traces.
Claude Code Reverse Engineers Viking VoIP Phone’s Undocumented Configuration Protocol
Boris Starkov of ElevenLabs presents the Viking K-1900D-IP phone as a reverse-engineering case study in which Claude Code turned an unusable, undocumented VoIP handset into a working AI demo. Starkov argues that Claude did the investigative work: discovering a two-letter command protocol, brute-forcing valid registers, intercepting the manufacturer’s Windows XP-era software through a TCP proxy, and deriving the one-byte checksum needed to write persistent configuration. His account is also a claim about agency in hardware work: he says he acted largely as Claude’s hands while Claude orchestrated the protocol break.
Gigabyte-Scale Agent Traces Are Forcing a New Observability Stack
Phil Hetzel of Braintrust argues that agent observability is a different problem from traditional observability because the central question is no longer whether a system is up, but whether an agent did the right thing. In his account, agent traces are too large, textual, and semantically loaded for uptime-oriented monitoring systems: Braintrust has seen traces exceed a gigabyte and spans reach 20 megabytes. Hetzel says that shift also changes who uses the data, bringing clinicians, lawyers, wealth advisers, and other domain experts into trace review so their judgments can become inputs for automated scoring and evaluation.
Agentic AI Projects Fail When Governance Cannot Move at Machine Speed
Accenture’s Jess Grogan-Avignon and Jack Wang argue that many enterprise agentic AI projects fail not because the agent cannot be built, but because the institution around it cannot move fast enough to ship and learn from it. Drawing on their experience building an agentic application in two weeks and spending another year getting it into production, they say enterprises must recode governance, fund AI as a portfolio of bets, deliver through hypothesis loops, grant autonomy only as evidence builds, and treat live customer feedback as the defensible asset.
Context Graphs Give AI Agents Rules, Precedent, and Decision Traces
In a Neo4j talk, Zaid Zaim and Andreas Kollegger argue that AI agents need more than language models, tools, and retrieval if they are to make consequential decisions. Zaim frames context graphs as a way to store the policies, prior decisions, causal links, and reasoning traces behind an action; Kollegger extends that into a five-stage decision workflow in which agents frame the case, check rules and precedent, assess risk, act only within authority, and write the outcome back to the graph as future precedent.
Comprehension Made Up 67% of One Engineer’s Claude Coding Sessions
Priscila Andre de Oliveira, a senior engineer at Sentry, argues that the most useful daily AI skill in a large production codebase is not code generation but comprehension. After analyzing 116 of her own Claude sessions, she found that 67% of her prompts were about understanding code and just 2% were generation. Her workflow, built around a local “catch me up” skill, uses AI to trace architecture, conventions, tests, history and behavior before any planning or implementation begins, because she says slop starts when the engineer’s mental model is wrong.
Rust’s Compiler Turns AI Coding Errors Into Pre-Production Feedback
Daniel Szoke, the Rust SDK maintainer at Sentry, argues that Rust is better suited to agentic or “vibe” coding than languages that let models produce runnable code quickly. His case is that TypeScript, Python and JavaScript impose too few constraints, allowing some model-generated bugs to compile, run and fail only intermittently. Rust, by contrast, turns classes of type, memory and concurrency errors into compiler feedback that an agent can use to repair code before it reaches production.
Agent Evals Should Replay Production, Not Exhaustively Imitate Unit Tests
Phil Hetzel of Braintrust argues that teams should stop treating evals for AI agents like unit tests meant to cover every possible failure. His maturity model starts with human judgments that record why an output failed, turns those justifications into scalable scorers, and then uses production traces to drive offline experimentation. The hard edge, he says, comes with tool-using agents, where useful evals must account not just for the final answer but for external system state and side effects at the moment the trace originally ran.
Local Frontier AI Still Needs 100x Better Price Performance
Alex Cheema of EXO Labs argues that running frontier AI locally is primarily an inference-stack problem, not a model-training problem. Using a four-Mac Studio GLM 5.1 setup that costs about $40,000 and reaches roughly 20 tokens per second as the current reference point, Cheema says local price-performance still has about 100x to improve through better kernels, interconnects, heterogeneous hardware, energy efficiency, orchestration, and benchmarks. His case is that today’s awkward home cluster is not the endpoint, but evidence of how much optimization remains outside the cloud.
Strong AI Agents Bound Scope, Expose Work, and Undo Mistakes
Mardu Swanepoel of Flinn AI argues that the best agent products are not defined by maximum autonomy, but by how carefully they bound and expose it. Looking across Harvey, Cursor, Manus, and Claude, he identifies four shared patterns: focused modes that narrow the task, transparent execution that lets users inspect the work, personalization that reflects user or organizational methods, and reversibility that limits the cost of mistakes.
Context Engines Make Coding Agents Mergeable, Not Just Functional
Brandon Waselnuk of Unblocked argues that coding agents are failing less because they lack access to tools than because they lack organizational context. In his account, MCP connections, larger context windows and naive RAG give agents more material, but not the judgment to know which code patterns, Slack decisions, ownership signals or backwards-compatibility rules matter. His proposed answer is a runtime context engine that reasons across code, PRs, documents, conversations and social structure before the agent writes code, so its output is closer to something a long-tenured engineer could merge.
Agent Benchmarks Are Measuring Harnesses as Much as Models
Nicholas Kang and Michael Aaron of Google DeepMind’s Kaggle team argue that AI evaluation is failing less because of a shortage of benchmarks than because benchmark results are hard to reproduce, easy to distort through hidden harness choices, and shaped by too narrow a group of authors. Their case is that agentic evals need shared infrastructure: transparent execution, community-created tests, model-versus-model arenas, and low-friction exams for builders who are not research labs. The recurring example is a wastewater treatment engineer in Turkey whose field experience produced a safety benchmark no lab was likely to create on its own.
Enterprises Are Misassigning GenAI Work to Traditional ML Teams
Phil Hetzel of Braintrust argues that many enterprises misassigned generative AI work to data science and ML platform teams because it carried the AI label. His case is not that those teams are irrelevant, but that LLM application work starts after providers such as OpenAI and Anthropic have trained the base models. What remains, he says, is a broader product and systems problem: prompt and context engineering, domain annotation, functional evaluation, observability, and production feedback loops that require data scientists, engineers, and subject-matter experts working together.
Useful AI Agents Need Smaller Contexts and Simpler Representations
Angus McLean, an AI Director at OLIVER, argues that useful agents are not the most autonomous ones but the best constrained. Drawing on OLIVER’s production use of AI across thousands of daily creative assets, he says builders should resist both model and developer tendencies toward verbosity and over-engineering: use curated documentation instead of open web access, ask how little context a task needs, choose simple representations such as HTML when they work, and avoid automating jobs they cannot do themselves.
Google’s Agent Scaling Problem Is Quota, Observability, and Evaluation
KP Sawhney and Ian Ballantyne describe Google DeepMind’s agent work as an infrastructure problem rather than a single-agent breakthrough. Their account centers on the constraints that appear when thousands of heavy users and agent workflows run at once: quota management, scarce compute, traceability, skills governance, evaluation, and review. Sawhney argues the next step for Deep Research is to move away from passing giant context blobs through a pipeline toward shared workspaces where components can collaborate more like human researchers.
Parallel Coding Agents Turn Human Availability Into a Systems Problem
Michael Richman argues that coding agents are still too dependent on unpredictable human input for developers to treat them as set-and-forget tools. His Cmd+Ctrl system is meant to reduce what he calls FOMAT, or fear of missing agent time, by aggregating sessions across tools such as Claude Code, Cursor, Codex and Gemini CLI, sending notifications when agents finish or get stuck, and letting users respond or start sessions from mobile, web, watch or terminal surfaces.