← All speakers

Gabe Cemaj

Conference affiliation: Member of Technical Staff · Anthropic · 2026

Gabe Cemaj works on Claude Managed Agents, infrastructure for running extended tasks with Claude without requiring every application developer to operate the agent runtime. His work spans model-serving infrastructure, ML observability, and agent execution: systems that must preserve progress when a running process fails and accommodate changes to the model directing the work.

On this page

From ML observability to agent execution

Gabe’s public profile identifies him as a Member of Technical Staff at Anthropic and previously the leader of Bloomberg’s ML Observability team. His open-source contributions include KServe, Hera, and Cloud Native Buildpacks.

These collaborative projects address different parts of deploying and running software. KServe provides model-serving infrastructure on Kubernetes. Hera lets developers express Argo Workflows in Python, define dependencies between tasks, and submit workflows to a Kubernetes cluster. Cloud Native Buildpacks addresses building application containers. The supplied contribution record establishes participation in these projects without assigning him sole ownership or particular features.

With Claude Managed Agents, applications define instructions, tools, and skills, start sessions, and consume events as work proceeds. Developers can steer or interrupt a running session. The platform supplies the agent loop and execution infrastructure that would otherwise need to be assembled and operated alongside the application.

Keeping progress outside the process

Gabe co-authored the Managed Agents architecture account with Lance Martin and Michael Cohen. It explains how the team moved away from placing the session, agent loop, and sandbox in a single container. When that container failed, the session could be lost; different failures also looked alike through the event stream, making diagnosis difficult.

Two changes separated the lifetime of the work from the lifetime of its execution environment:

  • Independently recoverable components: Separating the agent loop from the sandbox let either recover without requiring the entire system to restart together.
  • Persistent session history: Keeping conversation events outside the running loop allowed a replacement loop to resume from recorded work. It also let the team change context-management strategies without discarding the underlying history.

The team also kept credentials outside the sandbox running model-generated code. These are concrete infrastructure decisions about what survives a failure, what can be replaced, and where secrets are exposed.

Research agents that check and revisit their work

Gabe’s research-desk demonstration connects that infrastructure to an application. He built a chat interface over the session event stream and combined an SEC EDGAR skill, subagents, a custom tool, and shared memory. In an Nvidia analysis, an outcome grader checked the work against a rubric and prompted Claude to retry until it passed. The rubric supplied an explicit completion criterion beyond the agent simply ending its response.

He also demonstrated scheduled research and memory updates: a custom tool split one request into a separate session for each company, while deployments paired agents with schedules and resources. His demonstration of Dreaming, presented as a research preview, reviewed 30 days of past sessions to improve a memory store. Together, these examples show how he applies managed execution to research that spans multiple sessions, runs repeatedly, and carries information forward.

Read the topics behind these talks

4 conference talks

Loading more talks and highlights…

References