Chris Chabot
Chris Chabot, Member of Technical Staff, building agent platforms
I design and build the systems that take agents from demonstration to infrastructure: runtime and orchestration, SDK contracts, memory and permissioning, and the evaluation and verification that decide what ships.
Selected work
Porting an agent by making omissions visible
A production coding agent of about 340,000 lines of Python, built by my colleagues, moved to TypeScript with one requirement: byte-identical behaviour in everything not specific to the new platform. I designed the method and directed the agents: a formal model, a checklist generated from the syntax tree, clean-context review, then replay.
designed, directed, reviewed, verified
Testing a release without turning every release into a research project
Release qualification for an agent-native cloud platform, designed around what a customer actually does. Evidence comes in layers, from a certified core to real browser journeys through sample apps, and a result is reused only where it still applies.
designed, verified, operated
What should be identical in a five-language agent SDK
Five languages have no single implementation to share, so the contract had to be data: fixtures for wire shapes, error codes and verified identity that the SDKs' own tests read.
designed, led
Did your agent experiment test what you think it tested?
Before asking whether a change helped an agent, I want to know whether the comparison actually contains the change. The tooling here treats each run's configuration as a claim to be checked, and keeps corrections beside the original record rather than over it.
designed, built
Giving an agent project a durable owner
What changes when a coding conversation becomes a project that keeps running while you are elsewhere, and what a coordinator and its workers need in order to stay useful when there are a hundred of them.
designed, directed
Making an agent’s memory useful without slowing its next reply
Memory has to be isolated by tenant, keep the current fact in front, and stay out of the way of the next reply.
designed, built
What a tool-call approval actually approves
An approval should mean one tool call, with these exact inputs, in this thread and turn, under this version of the policy, once.
designed, built
Earlier products, open source and standards
Apache Shindig
Chief author of the PHP implementation of the OpenSocial container; PMC member and committer.
built, from 2008
OpenSocial
A common API for social applications across participating networks.
co-authored, 2007 to 2008
Portable Contacts
A simple XML and JSON protocol for address books and friends lists over HTTP.
co-authored, 2008
OAuth 2.0
The framework for granting applications limited, scoped access to an HTTP service.
contributed, 2012
OpenID Connect
An interoperable answer to "who signed in?" on top of OAuth 2.0.
contributed, 2014
Google+
Founding member of the project; led the platform's developer launch and API ecosystem.
contributed, led, from 2010
Latest writing
A browser for agents needs more than one score
A Rust browser engine built for agents, compared with Chrome across 1,024 sites, and why text, links, pixels and scripts each need their own result.
Agent systemsEvaluationPlatforms
A browser that writes down the form instead of sending it
An agent-first browser engine runs a click the way page code expects, then records a form submission and stops, leaving network access, protocol transport, threads and session state with the application that embeds it.
BrowsersAgent systemsRuntimeArchitecture
A catalogue import is not finished when the upload ends
A large book import passes through a source fixture, uploaded objects, an activated generation and a reader's filtered view, and each has its own count. Why a check has to name which count it means, and how to verify one without uploading again.
DataImportsVerificationFerrite
A deadline has to live outside the code it limits
A handler that never yields defeats timers inside the isolate, so the deadline for agent-generated JavaScript has to be a process kill from outside it.
Agent systemsPlatformsSecurity
A desktop can look correct and still lose your work
A Firefox Undo that could take a whole note sat beside 5,550 passing screenshot comparisons. What pixel checks, behavioural journeys, store readback and honest reports each catch in a React rebuild of macOS Catalina.
VerificationBrowsersReact
Public code
mem0-rsmem0-tsagent-switchboardcodex-swiftopen-cloudcode-searchsevere-testingshindig-php
