← All speakers

Bio, Work & Ideas

Nimrod Hauser

Conference affiliation: Baz · 2026

Nimrod Hauser is a founding engineer at Baz, building tools that help AI agents understand codebases, review changes, and verify whether software meets its requirements. His work focuses on a central production challenge: giving agents enough architectural context to make useful decisions while enforcing security-critical operations through deterministic software.

Hauser began as a military data analyst before working on the foundations of Salesforce’s Einstein platform. He became the first data scientist at cybersecurity company BlueVoyant, then led data and architecture at cryptocurrency-surveillance company Solidus Labs. As Solidus’s head of data, he described hybrid cloud infrastructure and data anonymization for security-sensitive deployments. He joined Baz at its founding in 2023.

  • Retrievable codebase memory: Hauser uses syntax trees, import graphs, and relationships among software components to give coding agents persistent architectural context. His research on file ordering for AI-assisted development shows why the sequence in which models encounter related code can affect their understanding of a change.
  • Cross-repository code review: His cross-repository retrieval approach indexes repositories independently, updates changed material incrementally, and filters snippets by relevance so agents can inspect dependencies across services without overwhelming their context windows. The Baz MCP server extends context-aware review into compatible development environments while limiting analysis to code explicitly submitted by developers.
  • Production-ready agent guardrails: Hauser adapts third-party browser tools by removing unnecessary capabilities, rewriting generic descriptions for specific tasks, and using accessibility snapshots to help agents interpret interfaces. He applies deterministic path validation to screenshot evidence and keeps authentication outside the agent’s decision-making loop.
  • Automated specification review: Baz’s Spec Reviewer combines issue-tracker requirements and Figma designs with browser automation to assess whether an implemented interface matches its intended behavior. Hauser’s demonstration of hardened MCP integrations illustrates how specialized evidence tools, controlled navigation, and explicit security boundaries turn an unreliable browser agent into a more dependable software reviewer.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

A browser-based Spec Reviewer shows how tool filtering, better descriptions, path checks, evidence capture, and deterministic login change an agent’s behavior.

  • Why can adding tools make an agent worse?
    0:00 ↗
  • From a ticket and design to browser evidence
    4:51 ↗
  • The baseline mistakes failed navigation for a failed requirement
    10:26 ↗
  • v1: Remove choices the reviewer does not need
    15:55 ↗
  • v2: Teach the agent how to inspect before acting
    18:06 ↗
  • v3: Reject an invalid screenshot destination before execution
    22:53 ↗
  • v4: Give evidence capture its own tool
    28:45 ↗
  • Call mandatory setup functions directly
    32:53 ↗
  • The rerun finds the drawer and saves evidence
    36:38 ↗

References