Twitter/X

On 2026-06-08 Ramya Chinnadurai (@code_rams) outlined a 7-step stack for putting…

2026-06-08 · 15:34 UTC ·@code_rams ·1 min read

Brief

Ramya Chinnadurai (@code_rams) presents a 7-step blueprint for running Claude unattended that pairs an 'engine' (automation) with a 'brake' (safety). The engine covers /loop, staged promotion, token budgeting, and a concrete stop condition; the brake requires red‑teaming, output ship‑checks, and permission scoping so automated runs don’t create irreversible mistakes.

Why it matters

On 2026-06-08 Ramya Chinnadurai (@code_rams) outlined a 7-step stack for putting Claude on autopilot: 4 engine steps and 3 brake steps.

Key details

  • Engine steps: /loop (start in a throwaway session), promote (session → desktop → cloud), budget (cap tokens & match model per fire), /goal (give the loop a real stop condition). Brake steps: red-team the plan, ship-check outputs vs promises, scope permissions by cost to undo.
Cleaned source text

Putting Claude on autopilot is the easy half. The half nobody sells you is the brake.

Wrote the honest version: a 7-step stack for running Claude while you sleep without waking up to a mess.

The engine, runs it:

→ /loop, find it in a throwaway session first

→ promote, session then desktop then cloud, earn each tier

→ budget, cap tokens and match the model on every fire

→ /goal, give the loop a real stop condition

The brake, keeps it safe:

→ red-team the plan before the loop runs it

→ ship-check the output against what you promised

→ scope permissions by cost to undo

4 steps are the engine.

3 are the brake.

You need both.

Full breakdown in the article.👇

Ramya Chinnadurai 🚀 (@code_rams)

Article

How to put Claude on autopilot without waking up to a mess

Putting Claude on autopilot is the easy half.

You set a schedule. It fires at 7am while you are drinking morning coffee. It runs, it writes, it ships something. The dashboard says success.

— https://nitter.net/code_rams/status/2063960920695468265#m