← All speakers

Bio, Work & Ideas

Zack Proser

Conference affiliation: WorkOS · 2026

Zack Proser is an applied AI engineer at WorkOS who builds systems that make software agents more reliable, secure, and practical to supervise. His work spans developer infrastructure, enterprise identity, retrieval-augmented generation, and a central challenge of automated software development: protecting the human attention required to judge whether an agent’s work is actually good.

Proser began his software career at BrightContext and subsequently worked at Cloudmark and Cloudflare. At Cloudflare, he described deploying Workers across production websites and APIs to address security and compliance requirements.

At Gruntwork, he helped build git-xargs, an open-source tool for coordinating changes across GitHub repositories. His 2021 introduction to the project explained how it automates maintenance tasks, commits, and pull requests across distributed codebases.

He subsequently worked at Pinecone, focusing on vector databases, embeddings, and evaluating production retrieval-augmented generation systems. At WorkOS, he moved from developer education into applied AI, developing internal workflows and writing about authentication for MCP servers and a documentation server that gives agents access to WorkOS resources. He also coauthored Identity Management for Agentic AI, addressing authentication, authorization, and security for software agents.

  • Human attention is the operational bottleneck. Proser argues that agent throughput means little when engineers cannot adequately review the resulting work. His approach to sustainable agent supervision combines Slack and Linear integrations, voice interaction, remote oversight, and deliberate breaks. He cautions engineers to delegate only work they understand well enough to evaluate.
  • Closed-loop verification makes autonomy useful. When an internal writing assistant mishandled acronyms including SCIM and SSO, Proser connected a coding agent to the affected Slack workflow and issue-tracking context. The agent implemented a fix, exercised the system, and checked the result. He supplements these feedback loops with verification gates including linting, builds, unit tests, browser checks, and independent review.
  • Agent skills should preserve judgment without bloating context. In an open-source workshop developed with Nick Nisi, Proser demonstrates reusable skills built from concise instructions, deterministic scripts, and selectively loaded references. He favors progressive context disclosure and reviewing completed agent sessions to identify repeated friction worth encoding into future workflows.
  • Typed workflows make flexible agents dependable. In a TypeScript workshop co-led with Nisi, he demonstrates conversational agents backed by explicit workflow stages, structured outputs, schema validation, and inspectable integrations. His design separates the flexibility of natural-language interaction from the more predictable execution needed in production.

His writing on making agent-generated prose publishable applies the same standards to content: factual grounding, voice checks, independent criticism, and safeguards against unsupported claims.

Read the topics behind these talks

3 conference talks

Key ideas

Scroll to read ↓

A workplace-frustration meme generator shows how typed workflows, runtime schemas, inspectable steps, and an agent interface fit together in Mastra.

  • Turn a workplace frustration into a meme
    0:25 ↗
  • Put explicit structure around model decisions
    2:57 ↗
  • Give the model context, then define the exercise
    8:14 ↗
  • Choose who controls the sequence
    14:33 ↗
  • Finalize a workflow before running it
    28:43 ↗
  • Improve coding context without prescribing an editor
    35:49 ↗
  • Separate execution engines, schemas, and retries
    42:29 ↗
  • Inspect the first structured result
    53:07 ↗
  • Carry the template's caption slots forward
    1:00:45 ↗
  • Debug the external service before blaming the model
    1:07:16 ↗
  • Watch a conversation become an authenticated transaction
    1:19:07 ↗
  • Trace a complete meme through four steps
    1:24:31 ↗
  • Apply the pattern, and inspect what gets generated
    1:31:47 ↗
  • Finish with chat, inspection, and persistence
    1:41:52 ↗

Key ideas

Scroll to read ↓

Build a repository-review skill, give it deterministic inputs and selective references, then carry the same techniques into evaluation, team distribution, creative tools and recurring automation.

  • Explain the repository again
    1:43 ↗
  • Give a repository review something specific to check
    5:13 ↗
  • A skill is a package with a routing description
    7:46 ↗
  • Install, invoke and inspect
    11:20 ↗
  • Supply the Git output instead of asking how to fetch it
    16:04 ↗
  • Separate permanent preferences from shared procedures
    20:11 ↗
  • Test selection, task quality and context boundaries
    29:31 ↗
  • Use the same package for slides, images and reviews
    35:42 ↗
  • Ground the roast, then load only the references it needs
    40:43 ↗
  • Turn uncertainty and repeated friction into inputs
    46:19 ↗
  • Keep useful memory and justify repository scores
    54:25 ↗
  • A vague feature becomes a contract
    58:34 ↗
  • Extend the analysis and move the package
    1:03:28 ↗
  • Ship the skill inside a product—and test whether it helps
    1:06:39 ↗
  • Two API calls become an animation workflow
    1:10:31 ↗
  • The finished roast still needs judgment
    1:14:41 ↗
  • Close the loop from Slack request to work
    1:19:34 ↗

Key ideas

Scroll to read ↓

Closing an agent’s verification loop can save a developer a round trip. Making that gain sustainable requires filtering interruptions, preserving judgment, and spending some of the recovered time away from the desk.

  • Why does getting more done leave you exhausted?
    0:16 ↗
  • Execution scales faster than judgment
    2:42 ↗
  • Filter incoming work, then lower the cost of directing it
    5:59 ↗
  • Leave the desk without moving the execution
    8:15 ↗
  • Make independence depend on verification
    11:09 ↗
  • A working day with mobile feedback
    12:03 ↗
  • Use the week’s friction to improve next week’s tools
    13:22 ↗
  • Include the person in the system
    15:30 ↗
  • Build the judgment you need to delegate
    17:36 ↗
  • Extract the useful parts of noisy session logs
    20:08 ↗
  • An overnight queue still creates morning review
    21:31 ↗
  • Speak instructions, read results—or stay in conversation
    22:16 ↗
  • Whole-stack changes still demand concentrated attention
    23:39 ↗

References