---
schema: 1
type: term
title: '**run loop**'
description: >-
  **run loop** — the ongoing cycle in which an agent continuously takes in
  context and acts on a user's behalf, rather than performing a single one-shot
  response to a request. In the channel's material, it is part of Mike Krieger's
  vocabulary for what makes a product \agent-native\ as opposed to a traditional
  application.
canonical: 'https://liquidgold.cc/channel/everyinc/explore/term/run-loop-1c6ad9cc0e9c'
markdown: 'https://liquidgold.cc/channel/everyinc/explore/term/run-loop-1c6ad9cc0e9c.md'
llms: null
parent: 'https://liquidgold.cc/channel/everyinc/llms.txt'
channel: everyinc
updated: '2026-10-23T22:12:35.346Z'
language: null
children: []
---


# \*\*run loop\*\*

Canonical: https://liquidgold.cc/channel/everyinc/explore/term/run-loop-1c6ad9cc0e9c

Parent: [Channel index](https://liquidgold.cc/channel/everyinc/llms.txt)

## Definition

**run loop** — the ongoing cycle in which an agent continuously takes in context and acts on a user's behalf, rather than performing a single one-shot response to a request. In the channel's material, it is part of Mike Krieger's vocabulary for what makes a product \agent-native\ as opposed to a traditional application.

\In this channel's material on building \agent-native products\, the term \run loop\ comes up as part of the vocabulary Mike Krieger uses when describing how software built around AI agents behaves differently from traditional applications — where a product responds to a user action, does one thing, and stops.\\In that framing, an agent-native product keeps \running in a loop\: it takes in context, acts on it, and continues working on the user's behalf rather than requiring a new instruction for every step. This is one of the design shifts Krieger discusses when explaining what changes when you build for agents — and what questions, like personal agents, will define the near future.\\- A \run loop\ describes the ongoing cycle of an agent working on a user's behalf, rather than a one-shot request-and-response interaction.\- It appears in the interview as part of the broader contrast between traditional products and \agent-native\ design.\- Understanding it helps when evaluating how agentic browsers and agent-native products actually behave.\