Hype Check · Ras Mic

Worth your time?

Name: Is "I replaced myself with these loops" worth watching? Hype 32/100 | Clip'd
Item: I replaced myself with these loops
Rating: 68
Author: Clip'd

I replaced myself with these loops by Ras Mic

Watch on YouTube

Hype score · lower is better

32/100

Useful but promotional

Teaches: a practical, example-driven walkthrough of automated 'loop' workflows that meaningfully automates PR creation, with a light product plug.

Substance65

Proof55

Pitch pressure25

Claim inflation30

The 15-second version

Post it, send it, settle the argument.

Download clip

Receipts

Why this score

Scored from the transcript, summary, and output signals.

Title partialTitle promises he 'replaced' himself; video documents heavy automation (75 PRs and two-loop system) but shows he still writes tickets and does final human review, so it automates a lot but does not fully replace him.

Skip the video

The short version

Kept by Clip'd

The creator describes a two-loop automation that shipped 75+ PRs using Fable 5, cloud agents (Cursor Cloud or Devon), and a code-review loop with GPile. The first loop has an agent write code, use a cloud desktop to run and record tests (computer use) until a clear success state is achieved. The second loop pushes a PR to GitHub and uses GPile's /gp loop skill to iterate until a five-out-of-five review score, after which a human performs a light review and merges.

Keep the lesson

What it teaches

Use small, testable success states as the loop's exit condition. Apply this when automating bug fixes or feature builds: define a binary or easily-checked desired state (example: streaming shows incremental text) and require the agent to produce a recorded proof. Do not use vague success criteria or long subjective che
Split automation into focused loops: one for build+verify, one for review+acceptance. Apply this when you want autonomous agents to produce production-ready code without full human debugging every run. Avoid trying to make a single mega-loop that handles both testing and review simultaneously; it makes debugging and fa
Use cloud desktop 'computer use' for reproducible end-to-end checks, especially when tests require UI interaction, 2FA, or external services. Apply this when local machines cannot emulate the environment or when you need recorded proof for reviewers. The common mistake is running these heavy tasks locally and burning r

Jump straight there

Key moments

0:00Bold claim: the video opens by stating 75+ PRs shipped, setting the expectation that this is a repeatable, production-ready workflow.
1:17Tool choice explained: Ross explains why he uses Linear (not GitHub issues) to record precise expected vs actual behavior that the agent will act on.
4:47Agent pickup demo: assigning a Linear ticket to Cursor and watching the agent begin examining issue PLO26 demonstrates automatic handoff to a cloud agent.
6:32Computer use + recording: the agent runs the app on a cloud desktop and records a video to show whether the fix reproduces or resolves the bug.
7:38Fail-to-loop example: a recorded test where the agent marks the run as failed (permission question) shows the loop's value, iterate until success state.
10:21PRs include demo video: the agent posts a demo video in the GitHub PR so reviewers can see the fix working before reading code.

Lines worth keeping

Quotes

I shipped over 75 PRs using Fable 5 and Loops.0:00
most agents suck at design.3:01
I definitely think Fable 5 is the reason why this works.16:57

Clip'd

Skip the video. Keep the lesson.

Score your next video free

The Hype Board