← All speakers

Bio, Work & Ideas

Luke Alvoeiro

Conference affiliation: Factory · 2026

Luke Alvoeiro is a technical and product lead at Factory and the creator of Goose, the open-source coding agent he began developing at Block. He builds autonomous software-engineering systems around a specific constraint: capable models cannot finish ambitious projects reliably if every decision, code change, and test still demands human attention.

Alvoeiro attended Middlebury College and spent three and a half years at Block, helping shape its AI developer strategy and initiating Goose, which enables agents to execute, edit, and test software. He subsequently joined Factory, where he leads development of the core agent harness and works on Factory Missions, a system for coordinating extended engineering projects.

How he makes agent autonomy dependable

  • Human attention as the bottleneck. Alvoeiro wants engineers to set objectives and architectural direction while agents execute asynchronously. Mission Control surfaces progress, worker activity, validation results, and spending without requiring constant oversight.
  • Independent validation before and after implementation. Missions begins with validation contracts that define expected behavior before coding starts. An orchestrator plans milestones; fresh-context workers implement features; separate validators inspect code and operate applications through complete user workflows. Failures generate corrective assignments, preventing agents from treating tests shaped by their own mistaken assumptions as proof of success.
  • Selective parallelism. Alvoeiro sequences agents that modify the same codebase, avoiding conflicting edits and inconsistent architectural decisions, while parallelizing read-only research and code review. Git commits and structured handoffs preserve completed work, unresolved issues, and execution results between sessions.
  • Role-specific model selection. Planning, implementation, and verification require different capabilities, so Factory’s Missions architecture can assign each responsibility to a different model or provider. Alvoeiro keeps orchestration adaptable through prompts, reusable skills, and conventions such as AGENTS.md, with deterministic controls enforcing validation and project continuity.

His progression from Goose to Factory Missions expands the challenge from making one coding agent productive to making multiple agents accountable for finished, working software.

Talks by Luke Alvoeiro

1 talk

Key ideas

Scroll to read ↓

Luke Alvoeiro explains how Factory’s Missions combines upfront validation contracts, specialized agent roles, structured handoffs, and carefully limited parallelism to execute software projects over hours or days.

  • Treat human attention as the limiting resource: let people set goals and approve scope while a structured agent system manages extended execution. 0:15 ↗ 1:17 ↗ 3:23 ↗
  • Separate orchestration, implementation, and validation so planning, coding, and independent review do not share the same responsibilities or implementation bias. 4:27 ↗ 5:34 ↗
  • Write a validation contract before coding, then combine conventional scrutiny with live end-to-end user testing at milestone boundaries. 5:34 ↗ 6:42 ↗ 7:38 ↗
  • Use structured handoffs to preserve completed work, unfinished tasks, command results, discovered issues, and procedural compliance across agents. 7:38 ↗ 8:43 ↗
  • Keep code-changing execution serial, reserving parallelism for read-only research and review to reduce conflicts and coordination overhead. 8:43 ↗ 9:50 ↗
  • Assign models according to role-specific strengths and keep orchestration in adaptable prompts and skills, with deterministic code enforcing essential operational safeguards. 10:45 ↗ 11:42 ↗ 14:00 ↗ 15:04 ↗

References