Speaker
Abstract
Most developers now use several coding agents at once: one for quick edits, another for long refactors, a third that a teammate recommended. Each lives in its own tool with its own setup, and none of them share what the others know. Switching means rebuilding context by hand. Handing work to a coworker usually means copy pasting code and hoping they can pick up the thread.
Omnigent provides a single interface for all of your harnesses. You can run agents like Claude Code, Codex, and Cursor side by side, share a live session with a teammate, and start an agent on your laptop then check on it from your phone while it keeps running.
This talk dives deep into how Omnigent works under the hood, how we use it to automate our own workflows, and what building it in the open has taught us.
Sponsored session
$3,250, Conference (3 days). Current pricing ends November 20th. All pass options.
QCon San Francisco 2026 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
Part of the track
Sponsored Solution Track VFrom the same track
Wednesday 18 November
10:35 Pacific LM Sponsored Simulating the Universe, 100 Times Over: Engineering Highly- Concurrent Agent Testing Andy Liang, Anvit Sinha Testing AI agents properly is surprisingly hard. Production data sources are moving targets, static datasets go stale, and pointing agents at real systems is risky and impossible to reproduce. 11:45 Pacific LM Sponsored Multi-Agent Coding with Omnigent Evelyn Hur, Denny Lee Most developers now use several coding agents at once: one for quick edits, another for long refactors, a third that a teammate recommended. Each lives in its own tool with its own setup, and none of them share what the others know. Switching means rebuilding context by hand. 13:35 Pacific LM Sponsored The Fast, The Furious and The Fatigued Christian Weber For years, achieving daily releases has been the gold standard of DevOps maturity. But what happens when you get there? According to new data from over 700 engineering leaders, high deployment frequency is increasingly masking a crisis of off-hours rework, instability, and engineer burnout.