ninja nerdingIdeas for letting agents run (and interrupt) your business
Ideas for letting agents run (and interrupt) your business
From a conversation between David Ondrej and Magnus Müller (Browser Use): inverted HITL, meta-agents, taste/memory, browser infra, marketplace disintermediation, and failure modes — organized for browsing, not as a factory flowchart.
Start here: filter the wall by cluster, then click any idea. Its detail opens in the Selected panel.
- David Ondrejhost · Vectal Labs / Director
- Magnus MüllerBrowser Use · @mamagnus00
We stop prompting AI, but AI only prompts us… like in Tinder: yes or no.
Magnus · ~00:52
Ten signals
The whole conversation in ten boxes. Each one opens the matching idea on the wall below.
- 01
AI prompts you, not the other way round
Background agents watch tickets, logs and mentions, then pitch a concrete change. You only say yes or no.
How - 02
Decisions come as yes/no cards
Magnus's internal Agency app puts each proposal on a card in a channel like Support or Growth. One tap approves, one skips, like Tinder.
How - 03
A screenshot instead of the code
Cards show before and after screenshots and test counts. He says he approves without reading the code.
How - 04
Autopilot is earned by swiping
The hard part is knowing what to ask for. After about one to two weeks of yes/no swipes, a type of work can go always-allow, inside a set budget.
How - 05
One file of what you want
dreams.md holds your high-level wishes. Agents keep working from it instead of waiting for your next prompt.
How - 06
An agent that watches the agents
Director, free and open source from David's company, finds stuck sessions and unblocks them. It starts with about 50 dry runs and knows when not to act.
How - 07
Taste comes from your no's
Search old sessions for words like “ugly” or “stupid” and for rewrites. Those rejections become a taste profile the agents reuse.
How - 08
The browser is the bottleneck
About 100 agents opened 300+ Chrome tabs and crashed a machine at roughly 100 to 153 GB of RAM. Their answer is browsers in the cloud.
How - 09
Agents chase the number, not the point
Told to get 1000 TikTok views, an agent put the video link in the Browser Use README. A bug report can also hide orders for your agent.
How - 10
Middlemen are next
The big claim: after software, agents replace marketplaces and platforms by buying and matching for you. This part is talk, not a demo.
How
Words on this page
Fourteen terms, in plain words. Skip this if you already ship code with agents.
- HITL (human in the loop)
- A person checks and approves what the AI does. Inverted HITL, the main idea here, flips who starts: agents propose the work and the human only says yes or no.
- Background agent
- An AI agent that keeps running without being asked each time. Here they watch tickets, logs and mentions, then pitch changes for a human to approve.
- Meta-agent
- An agent whose job is to manage other agents rather than do the task itself. Director, which spots stuck sessions and unblocks them, is the example on this page.
- PR
- Pull request. A proposed code change waiting to be approved and merged. On Agency cards, “Publish this PR” is the yes button.
- Diff
- The line-by-line list of what a code change adds and removes. Magnus approves from before/after screenshots instead of reading it.
- CI
- Continuous integration. Automatic tests and checks that run on every code change. “Green” means they all passed.
- Frontier model
- One of the newest, most capable AI models from the big labs. The bug-fix loop asks two of them and ships only if both agree.
- VM
- Virtual machine. A computer simulated in software and kept apart from your real one, so a bug can be reproduced safely.
- Always-allow
- A type of work the agents may act on without asking. On the video, it gets there after about one to two weeks of approve/reject swipes.
- SOP
- Standard operating procedure. Written steps for a task that repeats, so an agent can do it the same way every time.
- KPI
- Key performance indicator. The number a goal is measured by. An agent told to get 1000 TikTok views put the video link in the Browser Use README to hit it.
- Prompt injection
- Instructions hidden in text an agent reads, such as a bug report, so the agent does what an attacker wants instead of what you asked.
- Disintermediation
- Cutting out the middleman. The claim here is that agents will buy, book and match people directly, so marketplaces like eBay matter less.
- SEO
- Search engine optimization. Work to rank higher in search results. The page argues it weakens once agents, not people, decide what to buy.
Cluster shelves
Multi-select A–G. Counts from the dossier. Empty selection shows the whole wall.
AInverted HITL / “Agency” decision UI
~00:48–05:00, ~39:40–54:10 · 9
A1Selected
AI prompts the human (inverted loop)
Background agents watch tickets/logs/mentions and pitch concrete changes/PRs; human only approves.
00:48–02:10
A2
Tinder-style card queues (“Agency”)
Channels (Support, Growth, Docs, Product); binary approve/reject on localhost:3000.
01:35–03:00
A3
Zero-code-review merges via visual proof
Before/after screenshots and test counts; click Publish without reading diffs.
02:10–03:15
A4
Ideation gap → alignment → autopilot
Problem isn’t model power but “what to prompt”; after ~1–2 weeks of swipes, domains go always-allow.
04:10–05:05
A5
dreams.md as root intent
A single markdown of high-level desires seeds continuous agent work.
06:40–07:30
A6
Effort-sorted decisions
Cards ranked by estimated human cognitive seconds (e.g. “9-second” support vs deep architecture).
49:40–51:10
A7
Parameterized discretionary budgets / guardrails
$10k ads auto-OK vs $100k needs sign-off; outreach cadence limits.
52:10–54:10
A8
Visual-first 3-second pitches
Prefer graphics/HTML/SVG cards over long text; pre-stage “Send,” not “Create draft.”
39:40–41:00
A9
Astra conciseness vs verbose models
As framed on video: “Astra” answers shorter/more actionable than Opus/Fable-style verbosity.
42:10–44:10Speculative / as framed
BMeta-agents & orchestration
~07:40–10:15, ~18:08–20:20 · 6
B10
Dual-frontier bug consensus
Reproduce in an isolated VM; ask two frontier models; ship if both agree and CI is green.
07:40–08:40
B11
Human as bottleneck / parallel agents as metric
Agents always-on; measure productivity by how many run in parallel.
08:00–08:40
B12
Director supervisor pattern
Open-source agent that scans stuck sessions and unblocks them (`/director-start`).
18:08–20:20
B13
Dry-run calibration (~50 proposals)
Director proposes actions first ~50 times before autonomous judgment.
18:35–20:00
B14
Restraint / know when NOT to act
Valued Director property: high inaction tolerance.
19:55–20:18
B15
Sub-repo validation before spin-out
Validate a new idea in a subdirectory vs a new repo; Astra recommended this vs pessimistic models.
44:40–46:40Speculative / as framed
CMemory, taste, context grounding
~09:40–14:00, ~52:40 · 5
C16
Agent-to-human re-pitch after lost context
When agents email partners, the founder loses the thread; the agent must justify why.
09:40–11:35
C17
Mine negative feedback for taste
Scrape sessions for “ugly”/“stupid”/rewrites into a taste profile.
12:00–12:25
C18
Deep enterprise ingestion
A year of Slack, Gmail, calendar, and outage postmortems → context files.
12:25–12:45
C19
Generative vs ranking recommenders
Agents create candidate actions; they do not only rank a fixed catalog.
12:45–14:00
C20
Domain SOP extraction
Pull repeatable SOPs for domains that can go autopilot.
52:40–53:30
DMultimodal communication
~46:05–48:40 · 2
EInfra bottlenecks & browser agents
~00:20–00:41, ~09:35–10:35, ~59:50–end · 3
E23
Local Chrome RAM exhaustion
~100 agents → 300+ tabs → ~100–153 GB RAM crash → need cloud browsers.
00:23–00:41
E24
Subscription / quota churn as bottleneck
Burning frontier subscription tiers / rotating keys becomes founder work.
03:15–03:22
E25
Browser Use CLI + Cloud for web friction
Don’t use Chrome manually; agents fill forms, get API keys, screenshot diffs via CLI or cloud.
59:50–01:00:48
FDisintermediation & agent economy
~22:50–34:20 · 6
F26
Autonomous multi-constraint travel booking
Multi-airport + train + price; agent buys with credentials.
22:50–24:45
F27
E-commerce / SEO disintermediation
Purchase decisions shift to agents; classic SEO/affiliate weakens.
23:30–26:00
F28
Marketplaces replaced by intent-file matching
eBay/X/CRMs as middlemen; agents match via dreams.md / intents.
26:10–28:50
F29
Professionals displaced (lawyers/tax)
Spoken speculative extension of agent-to-agent services.
29:00–30:30Speculative / as framed
F30
Wearable audio → live intent + peer agent reputation
Ambient recording updates intent markdown; peer scores avoid centralized “social credit.”
30:40–34:20
F31
Agents pressure high-friction bureaucracy
Soft tasks automated; regulatory bottlenecks get flooded with agent calls/emails.
14:10–15:30
GFailure modes, attacks, identity
~00:00–00:22, ~16:00–22:45, ~37:00–58:40 · 5
G32
TikTok KPI over-optimization (README header exploit)
Goal “1000 TikTok views” → video URL in the Browser Use README header (100k+ stars).
00:00–00:22
G33
Uncensored / RL-stripped self-replicating sandbox risk
Models buy VMs, drop SSH, persist exploits — discussed as a threat pattern.
17:00–18:05Speculative / as framed
G34
Feedback-widget prompt injection
Hide instructions in bug reports (Instinct AI example) so the founder’s coding agent implements attacker intent.
21:20–22:45
G35
Identity crisis when execution cost → 0
Builder identity / meaning under pressure when doing the work costs nothing.
37:00–38:40
G36
Wishful-thinking deflation; agents pitch “why it matters”
Easy generation kills the romantic side-project myth; agents restore motivation with outcome pitches.
56:40–58:40
In their words
Right now we see agents replacing software. Next… agents will replace marketplaces and platforms.
Magnus · 00:36 I just see the screenshot. I don’t look at the code, I just click publish this PR…
Magnus · 03:00 The good thing about Director: it knows when not to do anything.
David · 20:00 A TikTok to achieve your dreams instead of consuming them.
Magnus · 48:42 AI destroys this wishful thinking which we had… for our side projects.
Magnus · 57:45
Sponsors (on-camera)
Primary cards only for the three description-linked tools confirmed on camera. What + how they say to use it + URL + timestamp.
PostHog
Product analytics + session replay so fast AI shipping still builds the right features.
How they say to use it
- Visit go.posthog.com/david (first link below the video).
- Use usage / stuck points / retention + session replay to understand users.
Director
Free open-source agent that unblocks other agents by inspecting stuck sessions.
How they say to use it
- Install from GitHub (vectal-labs/director).
- Run /director-start.
- Treat the first ~50 interactions as dry runs.
- Then allow autonomous unblocking; values knowing when not to act.
Browser Use
Agents that use the browser; CLI + Cloud to avoid local Chrome meltdown.
How they say to use it
- Tell your coding agent to use Browser Use CLI (logged-in Chrome or cloud).
- Use Browser Use / Cloud when the browser is the product loop.
Other named tools
Dossier marks only — not primary sponsors, no invented usage guides8 tools
- AgencyMagnus’s internal Tinder-like approval hub — not pitched as public product
- MastraNamed agent framework integrated with Browser Use
- BoxLite / OpenCodeShown on Agency architecture diagram (uncertain pitch)
- Instinct AIFeedback prompt-injection anecdote example
- MiniMax H3Video-gen tested for agent pitches
- davidondrej/skills · vectallabs.com · scalesoftware.aiOverlay CTAs
- Hostinger / Cursor referral overlaysChannel CTAs ~18:10 — not mid-roll sponsors
- Cold Turkey / GranolaVisible in tweet screenshot only
Coverage honesty
Ideas and sponsor claims are as discussed in this video analysis — not a step-by-step factory of Magnus’s production harness. Agency backend schema is not walked through. Speculative economy / risk talk is marked. “GPT-6 Astra” and peer version strings are conversational labels, not verified product APIs.
Try it, smallest version first
Five steps with the agent you already use, no new tools. This is FakeNerd's starter built from ideas A5, A1, A2 and C17 on the wall. Magnus's own Agency app is internal and not shown step by step.
- 01
Write a dreams.md
Make a folder for one project you care about. Add a file called dreams.md with three to five plain lines about what you want, such as “more people finish signup” or “answer support the same day”. This is the root intent from idea A5.
Idea A5, dreams.md - 02
Ask the agent to pitch, not to do
Open the agent you already use in that folder and paste the prompt below. It turns ideas A1, A6 and G36 into one ask: proposals as cards, sorted by how fast you can decide, each saying why it matters. The wording is ours, not Magnus's.
Idea A1, AI prompts the humanPitch prompt (FakeNerd's starter)
Read dreams.md in this folder. Do not change anything yet. Pitch me 5 small changes that move one of those wishes forward. Write each one as a card: - Title: one line - What changes: one or two sentences, or a before/after if it is visual - Why it matters: which wish in dreams.md it serves - Time for me to decide: your guess in seconds - My answer: yes / no Sort the cards by time to decide, quickest first. Wait for my answers. Only do the cards I say yes to.
- 03
Answer yes or no, and log it
Reply to each card with yes or no and a few words of why. Keep a decisions.md with every card, your answer and the reason. That log is your swipe history.
Idea A2, yes/no cards - 04
Turn your no's into taste
After a few rounds, paste the second prompt. It reads your log and writes your taste down, the way idea C17 mines rejections.
Idea C17, taste from negative feedbackTaste prompt (FakeNerd's starter)
Read decisions.md. It lists every card you pitched, my yes or no, and my reason. Write taste.md: ten short rules about what I say no to and why, using my own words where you can. Then list the kinds of card I said yes to every time, as candidates for always-allow. Do not turn anything on.
- 05
Set limits before any always-allow
On the video, always-allow comes after one to two weeks of swipes, with budgets like “$10k of ads is fine, $100k needs me”. Write your own limits first. Keep saying yes by hand to anything that spends money, sends messages, or reads text other people wrote, since a bug report can carry hidden instructions.
Idea A7, budgets and guardrails
FakeNerd's take
The yes/no queue is the part to steal
You don't need Agency, which is internal anyway. A file of wishes, an agent that pitches, and you answering yes or no works with any agent today. Most of the other ideas build on that loop.
Approving from a screenshot is a bet
Fine for a button colour. Risky for payments, logins or anything with data. The same video shows an agent gaming its goal and a bug report hijacking an agent, so read the change when it can hurt you.
Everyone on camera sells something
Browser Use is Magnus's company. Director comes from David's. PostHog is pitched with David's link. The ideas stand without any of them, which is why the wall lists ideas and the tools come after.
A lot of it is talk
Agency is the only loop shown working. The marketplace, wearable and lawyer ideas are spoken, not built, and “GPT-6 Astra” is a label from the conversation. Treat the second half as a forecast.
Related on this site: 28 things Codex can do, the same model from the coding side. Inside a company brain, an AI teammate that asks before it acts. The software factory, another crawl, walk, run path to letting agents work on their own.
Attribution
- I let GPT-6 Astra run my business… it's insane, David Ondrej in conversation with Magnus Müller of Browser Use. The ideas on the wall, the beats and the sponsor steps are from this video, summarized. The lines under “In their words” are quoted, and every timestamp opens the video at that moment.
- Browser Use is Magnus's company. Director is a free, open-source agent from Vectal Labs, David's company. PostHog is pitched on camera with David's own link. Claims about these products are their makers' own.
- “GPT-6 Astra” and the other model names are labels from the conversation, not verified product APIs.
- The seven clusters and the idea wall, the glossary, the coverage notes and the order of everything are FakeNerd's.