Run Claude Code

Bonjour — this is Liam, in for Bear. Run Claude Code. Open Claude Code in the folder that holds your work and the Brutalist skills. One flag keeps it running unattended. Let me show you the command.

1:53 video2 min readWatch on YouTube

Run Claude Code

Bonjour — this is Liam, in for Bear. Run Claude Code. Open Claude Code in the folder that holds your work and the Brutalist skills. One flag keeps it running unattended. Let me show you the command.

Topic: BRUTALIST — OPEN SOURCE


Chapters

0:00 Introduction 0:11 Act 1 0:22 Act 2 0:35 Act 3 0:50 Act 4 1:03 Act 5


YOUR TURN


@NikBearBrown


Sources and citations: see the reel's SOURCES.md in the open textbook.

▶ The full series playlist — Brutalist https://www.youtube.com/playlist?list=PLG9H-C6rp5RU

What this video covers

  • 0:00 — Introduction
  • 0:11 — Act 1
  • 0:22 — Act 2
  • 0:35 — Act 3
  • 0:50 — Act 4
  • 1:03 — Act 5

Transcript

A lightly formatted transcript of the video, with timestamps so you can jump to any section on YouTube.

Introduction

[0:00] Bonjour, this is Liam in for Bear. Run Claude code. Open Claude code in the folder that holds your work in the Brutalist skills. One flag keeps it running unattended. Let me show you the command. Open Claude code in the folder

Act 1

[0:12] That holds your work. That folder needs to be the parent of both your project files and the Brutalist Art Toolkit. Claude needs to see both to run the skills, the work, and the machinery.

Act 2

[0:22] Prefix the command with caffeinate. Caffeinate is a Mac OS built-in that prevents the display and CPU from sleeping. A build that takes 40 minutes does not survive a screen lock without it. One word, big difference. The flag

Act 3

[0:36] Is dangerously skip permissions. It tells Claude code not to pause and ask permission for each file write, FFmpeg call, or NPM command. The pipeline meets the seatbelt rules, get tracked regenerable outputs, so the flag is appropriate here.

Act 4

[0:50] The full command, caffeinate Claude dangerously skip permissions. Run it from the parent folder. Paste your build prompt, walk away. The whole pipeline, audio, remotion, compile, QC, runs while you do something else. The entry point

Act 5

[1:03] Is {slash} art. Every skill, every build stage, every QC gate runs through the art script in Brutalist Art {slash}. You do not call Python or NPX directly. Art resolves its own home and auto loads the environment file. The verdict, caffeinate Claude dangerously skip permissions. Three words that let the pipeline run overnight. One entry point, {slash} art, drives all the stages. You set it up once and it runs while you sleep. Your turn. Ask Claude this, "I am going to run you with caffeinate and dangerously skip permissions. Read my build prompt MD and execute the pipeline for my reel. Run the stages in order, audio first, then remotion, then compile. Log everything to build.log.md. That is the overnight build prompt. Paste it in after you have a beat sheet ready and walk away." Run Claude code Brutalist at Nick Bear Brown. Liam in for Bear.

More from Claude Basics

Nik Bear Brown Poet and Songwriter