The first question every new coding-agent user asks is: should I be using Claude Code at all? The channel has been unusually direct on this. Three videos form the core of the answer, and they don't all agree — the headline "Perplexity Computer Just KILLED Claude Code" is a side-by-side test where the channel framed Claude Code as the loser, but the follow-up "Claude Fable 5 + Loop Designs is TOO STRONG!" argues a new Claude release is the strongest vibe-coding combo tested so far. Sandwiched in the middle is KaneAI, which isn't a Claude Code replacement at all — it's a real-browser QA tool that solves the "vibe coding is fast but testing is hard" problem on the channel's own site.

This article walks through each video in turn, then zooms out to the question the syllabus actually asks: does Claude Code beat the field?

What you'll learn

  • Perplexity Computer's $176/month plan gave it Opus 4.6 plus parallel-agent orchestration, and on a side-by-side build Claude Code had to be hand-tuned with plan mode and agent teams to match.
  • The channel's recommended override for Claude Code is to force it into plan mode and explicitly request agent teams before any multi-step build — otherwise it "tries to brute force it" the way it did in the test.
  • Claude Fable 5 with loop syntax is a different kind of win: it ran 11/11 self-QC checks on a physics game and beat both Opus 4.8 and Qwen 3.7 Max on a 3D assembly, but the bill was ~$16 per project and the cheap pricing window closes June 21–22.
  • KaneAI is the missing last step for any "vibe-coded" app: it drives a real browser through plain-English flows, records video, and runs unattended as an overnight regression suite — and it ties into Jira once the team grows past ~3 people.

The side-by-side: Perplexity Computer vs Claude Code

The channel's first real test of Claude Code against a no-code competitor. Perplexity had just launched Perplexity Computer, a no-code agent that runs tasks in parallel and outputs finished reports, dashboards, and terminals without you writing code. The channel ran the same prompt through both products.

The result: Perplexity Computer used Opus 4.6 (sometimes called "Opus 1.6" in the stream), broke the task into subtasks, and delegated to parallel agents. Claude Code, on default settings, "tried to brute force it" — single-agent, sequential, no plan mode. It only matched Perplexity Computer's output after the creator manually pushed it into plan mode and told it to use sub-agents and agent teams.

What it costs

  • Perplexity Computer: $176/month on the Max plan. The Pro plan is blocked, which the channel calls "the scammy part" — you can't unlock it on an existing Pro subscription.
  • Claude Max: $200/month for the comparable tier.
  • Net savings on Perplexity: $24–$30/month, but only if you start from scratch. If you already pay Claude annually, switching costs both money and the process visibility Claude Code gives you.

Where Claude Code still wins

The channel calls itself "a control freak" and wants to see what the processes are along the way. Claude Code's three advantages over Perplexity Computer are:

  1. Plan mode — you can see and edit the plan before any code is written.
  2. Sub-agents / agent teams — you can assign and audit each worker's output.
  3. Process visibility — Perplexity Computer hides the orchestration entirely; Claude Code does not.

What Perplexity Computer adds

  • Parallel execution — Perplexity fans out agents simultaneously. Claude defaults to a single track unless you explicitly enable teams.
  • Built-in scheduling — cron-style follow-ups like "if this video changes every week, give me a new report."
  • Ecosystem lock-in — examples like the Hamptonism "Bloomberg terminal" clone pull data from Perplexity Finance.

Bottom line

Spend 3 hours hand-tuning Claude Code with plan mode + agent teams and you can match a Perplexity Computer run. The question is whether your time is worth more than $30/month. For new users with no code background, the channel's pitch is: "you don't really need to know any code." At the time of filming, Perplexity Computer was six hours old and gated to Max only, so the channel recommended waiting for either a Pro-plan unlock or a public API before committing.

KaneAI: the test runner the channel wished it had years ago

This is a different kind of video. KaneAI is not a Claude Code competitor — it's the "last stage of development" tool. The channel frames it as a solution to a problem they've personally hit: vibe coding is fast, but the test loop is manual.

What KaneAI does

You describe a user flow in natural language — the example in the video is "go through the start menu, click the start button… and make sure they have open up individual windows and each window has content" — and the agent drives a real browser through it. In the live demo against boxai.com:

  • It found a "hidden sign-up button at bottom right hand corner" on its own.
  • Filled in an email and triggered the magic-link send.
  • Streamed a video record of the entire run.

That's the killer feature for the channel: every run has a video. When something breaks, you hand the recording to the LLM and "it's actually much easier for the AI to debug the problem for you once that's complete" — a major step up from Claude Code running Playwright blind, where "you have no idea what's happening on the screen."

Why the channel cares

The Boxmining AI site is a Windows 95-style app shipped to users for a free founders edition. The sign-up flow had broken often enough that "we received a lot of feedback to say hey sign up isn't working." Manual testing had been a bottleneck in prior roles too — at a 30-person game studio, "anytime they have a new feature out, we'll have a document… and then manually we have to go and test it," including hand-writing mount tests.

Concrete wins from the demo

  • Catches content regressions. The agent checked that every program-folder window contained a video or summary — a check the creator normally does by hand every release.
  • Runs unattended. "Every time something happens… it should be able to go through all these and manually click." The channel describes an overnight full-site regression run as the default mode.
  • Gives the LLM a visual reference. A video replay beats a stack trace for downstream debugging.

Where it fits

KaneAI works in solo mode but integrates with Jira for team pipelines, and supports manual interaction steps inside an otherwise automated run. The channel's positioning: this is the tool you reach for "when you want to make money with your app," not the tool you use to write the app.

Claude Fable 5 + Loop Designs: the "Claude is back" video

Six months after the Perplexity Computer test, the channel ran a different experiment: take a freshly released Claude (referred to in the video as Fable 5) and pair it with a "loop syntax" harness. The result is a strong counterweight to the earlier "Claude Code is dead" framing — but with a real cost reality check.

The benchmark numbers

On Artificial Analysis's intelligence index, Fable 5 scored 65 with fallback — top spot — while speed ranked near the bottom. The channel called it "definitely one of the most expensive right now." On Frontier Coding Diamond, Fable 5 hit 29.3% vs GPT 5.5 at 5.7% and Opus 4.8 well below. On multi-disciplinary reasoning, Fable 5 hit 59%/64.5% vs GPT 5.5's 41.4%/52.2%.

The channel explicitly dismisses SWE-bench Pro as "cherry-picked to the max" and tells viewers to use Frontier Coding Diamond as the coding benchmark instead.

Loop syntax > prompt engineering

The interesting pattern is the harness. Instead of one-shot prompts, the channel used a loop:

  • A harness command: loop until it's done
  • A validation rule: "you have personally reviewed the HTML source to ensure that there are no placeholder comments, missing functions, or to-do's"

Fable 5 was caught taking Playwright headless-browser screenshots mid-run and running 6- and 11-point QC checks. On the physics game, it passed 11/11 checks on structure fragments, static friction, and beast AI velocity — after multiple self-correction loops.

The cost reality

The creator set a $20 budget for the video. The first project (a 3D Chinese-architecture render) cost $11. The second (a W.B. Yeats "The Second Coming" poem-to-game) pushed the total to $32 — burning 72% of the monthly Cursor API allocation in the second week. The cheap window closes June 21–22, after which Fable 5 is "credits only and it's twice as expensive as Opus" per input/output token. Three Claude Max plans ran out during a single BridgeMind live stream.

The comparison

On the 3D assembly, Fable 5 with loops produced a roof, a working X-ray toggle, moving labels, and visible "cracks" for age erosion. Opus 4.8 handled age erosion with a flat "color change" instead of geometry. The creator called the Fable 5 result "even better than Qwen 3.7 plus and Qwen 3.7 Max" — conceding it's "a little bit of cheating" because Qwen wasn't tested with loops.

Daily-use verdict

The channel's split:

  • Fable 5 = new "Opus." Use it inside Cursor, Claude Code, or a coding IDE.
  • Opus 4.8 = demoted to "Sonnet." Stop maining it.
  • Main stays DeepSeek V4 Pro (51.5) / Kimi 2.6 (53.9) for orchestration and Hermes.
  • "Will not main Claude yet" until the 2-week ROI frame balances out.

The channel also flagged Fable 5 as "overkill" inside Hermes, where DeepSeek V4 Pro or Kimi 2.6 is cheaper for orchestration.

Try it yourself

This is a hands-on course, so here's a concrete sequence to reproduce the channel's headline result from video 1: get Claude Code to match Perplexity Computer's parallel-agent output on a multi-step build.

  1. Install Claude Code (Node CLI) and authenticate it against your Anthropic account. Default to Sonnet or a cheap model — see Course 3 for the model-picking framework.
  2. Open a fresh project. Write a one-paragraph brief: a small web app with three features, e.g. "fetch a list of items, render a chart, save a user note."
  3. Send the brief to Claude Code without plan mode first. Note the output: you'll usually get a single sequential implementation.
  4. Reset. Re-run the same brief but with: "Enter plan mode first. Break this into three subtasks and assign each to a sub-agent. Show me the plan before you write any code."
  5. Approve the plan. Watch the sub-agents fan out in parallel.
  6. Time both runs. If the parallel run is faster and the diff is cleaner, you've reproduced the channel's result: the gap between Claude Code and Perplexity Computer is mostly configuration.
  7. For the Fable 5 / loop experiment, install Cursor and try the same brief with a loop until it's done harness plus a validation rule about placeholder comments. Cap your spend at $15 for the first project.
  8. For KaneAI, sign up and write a single test prompt against your own site that enumerates a content invariant, e.g. "every list item has a link." Run it overnight.

Common pitfalls

  • Skipping plan mode on multi-step builds. This is the single biggest mistake the channel flagged. Default Claude Code is single-track and will brute-force a parallel problem unless you tell it not to. Always force plan mode + agent teams before any non-trivial build.
  • Assuming Pro = Max on Perplexity. Pro subscribers are locked out of Perplexity Computer — only the $176/month Max plan unlocks it. Don't pay for a Pro upgrade expecting the new product.
  • Treating Fable 5 as a flat replacement for Opus. It's twice as expensive per token after June 21–22, and the channel burned 72% of a monthly Cursor budget on two projects. Set a hard per-project cap and watch the calendar.
  • Using one-shot prompts where loops would work. The channel's loop syntax (loop until it's done + a validation rule) caught 11/11 QC checks the model would have missed in a single pass. Don't try to fix a vibe-coding output with another prompt — loop it.
  • Replacing QA with code review. Vibe coding produces working software that breaks in the browser. KaneAI's value isn't the test scripts; it's the video replay you can hand to a downstream LLM. If your tool doesn't record, you're back to Playwright-without-screenshots.
  • Reading "Opus 1.6" as a typo. In the Perplexity Computer video, the creator refers to Opus 4.6 and "Opus 1.6" interchangeably — they are the same model. Don't treat them as two different releases.
  • Benching on SWE-bench Pro. The channel calls it "cherry-picked to the max." Use Frontier Coding Diamond instead.

Sources

  • Perplexity Computer Just KILLED Claude Code (Side-by-Side Test) — 18,483 views · video_id: E4gc4-9O1JE
  • KaneAI: The Best AI Coding Assistant — 9,240 views · video_id: KcoId-HwOD4
  • Claude Fable 5 + Loop Designs is TOO STRONG! (Full Tests) — 3,482 views · video_id: 8De7s6WG7Bo
  • Supabase query — SELECT video_id, title, views, summary_content, summary_key_takeaways FROM public.videos WHERE video_id = ANY(ARRAY['E4gc4-9O1JE','KcoId-HwOD4','8De7s6WG7Bo']); against project ttxdssgydwyogq.