← All speakers

Bio, Work & Ideas

Sachin Gupta

Conference affiliation: eBay · 2026

Sachin Gupta is a member of technical staff at eBay and the creator of HeapLens, an open-source tool for diagnosing Java and Android memory problems inside Visual Studio Code. He applies the operational discipline of financial infrastructure to AI systems: making autonomous behavior controllable, generated code reviewable, and production data systems observable.

Gupta began his career at Tata Consultancy Services in 2011, contributing to an electronic shareholder-voting application for NSDL. He subsequently developed merchandising software for Walgreens and specialty-pharmacy systems supporting prescription tracking, auditing, reporting, and manufacturer-contract compliance. Since joining eBay in 2021, he has worked on its next-generation billing platform, including seller-and-balance migration, public APIs, and reconciliation pipelines. His more recent work encompasses AI-enabled production systems, agent governance, and retrieval infrastructure.

  • HeapLens and private memory analysis. HeapLens combines a native Rust analysis engine, dominator trees, leak detection, source-code navigation, and HeapQL, a SQL-like language for querying heap objects. Its AI assistant can explain findings and generate executable queries; local-model support keeps sensitive heap data on the developer’s machine. HeapLens was selected for the SPLASH/ISSTA 2026 tool-demonstration program.
  • Feature flags for autonomous agents. Gupta applies established release controls to agent behavior, governing prompts, tools, models, memory, autonomy, and sub-agents independently. His approach combines segmented rollouts, restricted tool authorization, adjustable memory retention, staged autonomy, and runtime kill switches. Controls must be reevaluated during active conversations and inherited by child agents; otherwise, an emergency shutdown can leave an autonomous process running.
  • ReviewDebt and the cost of generated code. ReviewDebt estimates pull-request review burden using deterministic signals: change size, cross-file coupling, test evidence, ownership spread, AI-assistance indicators, and the author’s explanation. Gupta rejects opaque LLM-based judging in favor of reproducible scores and actionable reviewer guidance. Across an illustrative scan of 524 pull requests from three public repositories, structural complexity and submission volume mattered more than AI authorship alone.
  • Production retrieval-augmented generation. Gupta treats retrieval systems as continuously maintained infrastructure, emphasizing incremental indexing, deletion across derived document fragments, embedding-model migrations, and traces explaining how answers were assembled. Reliable retrieval depends on synchronizing user-facing responses with the slower, ongoing maintenance of the underlying knowledge base.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Prompt changes, tool permissions, and autonomous actions need controlled rollouts—and shutdown paths that reach conversations and child agents already in flight.

  • A small prompt change reaches everyone
    1:17 ↗
  • Four ways behavior becomes an incident
    2:31 ↗
  • Reuse release infrastructure, separate behavior surfaces
    3:42 ↗
  • Route prompt versions by cohort
    6:09 ↗
  • Separate tool permission from model selection
    6:52 ↗
  • Memory policy has four independent dimensions
    8:29 ↗
  • Control action authority and make shutdown effective
    9:10 ↗
  • Revoke email sending during a conversation
    10:22 ↗
  • Stop a runaway loop at its next decision point
    11:24 ↗
  • Put enforcement on every agent’s execution path
    12:27 ↗
  • Build the controls in operational order
    13:35 ↗
  • Measure whether the controls work
    14:18 ↗
  • Five ways installed flags fail at runtime
    15:21 ↗
  • Make control demonstrable to buyers
    16:15 ↗
  • Drill shutdown and retire temporary complexity
    16:57 ↗
  • Match release discipline to the agent’s authority
    17:47 ↗

Key ideas

Scroll to read ↓

Coding agents can increase code production faster than teams can establish trust. ReviewDebt turns the shape and evidence of a pull request into a repeatable review conversation.

  • Code production can outrun review
    0:00 ↗
  • What throughput leaves out
    2:12 ↗
  • Why the gap compounds
    4:46 ↗
  • Measure review burden from the PR
    6:00 ↗
  • Authorship clues and the missing why
    9:54 ↗
  • Turn the score into a review action
    12:25 ↗
  • Three PRs, three review conversations
    13:24 ↗
  • Volume accumulates burden even when authorship markers stay flat
    17:15 ↗
  • Make the change easier to understand
    19:55 ↗
  • Surface the score without blocking the work
    21:15 ↗
  • Start with twenty PRs and an honest review
    23:38 ↗

References