Latent Space

Quinn Slack on Parallel Coding Agents

Quinn Slack· Co-founder at Amp
·~40 min·English·Latent Space
AgentsAI InfrastructureAI Company
TL;DR

Quinn Slack explains how Amp rebuilt its workflow around remote "orbs" — cloud agents that run in parallel — and, for a small trusted team, dropped local dev, mandatory code review, and much of classic CI.

01The Shift

Orbs, and the End of Local Dev

Amp rebuilt itself around "orbs" — coding agents that run remotely in the cloud, so you can close your laptop and run many tasks at once instead of one at a time on your machine.

You can shut your laptop. You can do a 100 things in parallel.

— Quinn Slack, Latent Space
Key Insight
Parallelism only pays off once the friction of spinning up an environment drops to near zero. By making the remote dev server, ports, and desktop "just work," Amp removed the reason a developer would still reach for local dev at all.
02Product Strategy

More Known for Killing Features

Amp deliberately removes features — it was an early mover in killing its editor extension — to keep everyone on one blessed path rather than maintaining the old ways of working.

we were more known for killing features than for adding features.

— Quinn Slack, Latent Space
Key Insight
When the technology cycle is measured in months rather than years, keeping a user on the old feature is not neutral — it is negative. Removing features is how Amp pulls customers onto the frontier before a competitor makes their current setup look obsolete.
03Trust over Process

No Mandatory Code Review Before Main

Amp dropped mandatory pre-merge code review for its small team and replaced the safety it provided with deep trust plus fast recovery — shipping a fix within minutes of a bad signal.

Yeah, it's dead. It's been dead ever since we started working on AMP.

— Quinn Slack, Latent Space
Key Insight
This trades "mean time before failure" for "mean time before recovery." It is a bet that a 20-person team where everyone is a trusted, accountable owner can catch problems in production faster than a review gate could have caught them beforehand — a bet that only holds for a team this aligned.
04Security Inversion

The Cloud Agent Is the Secure One

Running an agent in a cloud orb with a short-lived, scoped token is more secure than a CLI agent on a laptop that inherits whatever access the developer already has.

it feels like a CLI coding agent is a really insecure thing and you want to be moving to the cloud.

— Quinn Slack, Latent Space
Key Insight
Because both developers and security teams win — one gets frictionless parallelism, the other gets least-privilege access — Slack argues the shift will move faster than people expect. Security is usually the brake on cloud moves; here it becomes an accelerator.
05The Test Loop

CI's Days Are Numbered

With the agent already running tests in a reproducible sandbox, Slack expects classic CI to fade — while the sandbox underneath it, sold by companies like E2B and Daytona, keeps growing.

half the AMP team is like, "Guys, we don't need CI."

— Quinn Slack, Latent Space
Key Insight
The piece of CI worth keeping is not the pipeline but the reproducible environment. The reason CI does not disappear entirely is that you cannot yet trust an agent to be exhaustive on a large codebase — so a deterministic "run everything" stage still earns its place.
06Dev Infrastructure

GitHub Dies with a Whimper

Slack's team barely touches GitHub anymore — no issues, no pull requests, and looking to leave Actions — moving instead to ad hoc repositories hosted inside Amp.

We just don't even think of GitHub anymore. We're not using issues. We're not using pull requests.

— Quinn Slack, Latent Space
Key Insight
Incumbent tools rarely get replaced in a dramatic switch; they get quietly routed around until one day nobody remembers to open them. Once agents generate and run the work, the human-facing surfaces of GitHub — issues, PRs, reviews — lose their reason to exist first.
07Software Itself

The Agent Is the Ultimate Settings Screen

Instead of shipping settings screens, integrations, and MCP plumbing, Amp lets an agent (and the code itself) be the way you customize software — fork it and change whatever you want.

an agent is the ultimate settings screen for any software and code is the ultimate setting screen for any software.

— Quinn Slack, Latent Space
Key Insight
If any user can reshape an app with their own agent, the configuration surface a vendor used to build and sell collapses into the code itself. Slack calls the shippable version of this "jellyware" — forkable, customizable, softer than a released product but firmer than a one-off vibe-coded script.
08Company Design

Twenty Co-founders, No PMs

After spinning Amp out of Sourcegraph, Slack runs a profitable 20-person team where everyone is trusted with everything, and argues the old split between product people and overhead roles no longer makes sense.

10% of the people are thinking about how to make a great product and the other 90% are thinking about the overhead

— Quinn Slack, Latent Space
Key Insight
When agents absorb the sales, support, and process work that used to require headcount, a company can stay small and keep almost everyone on the product itself. It echoes the "small handful of people" bet others are now making — but it depends on being able to trust every single person you hire.