Delivery rules
A folder layout and a file naming pattern you give the agent at the start of a task..
The pack goes out by email rather than as a download. Signed in, it goes to your account address; otherwise tell us where to send it.
Agent workshop for beginners
Most people learn to run an AI agent by losing a folder, filling a drive, or finding out hours later that nothing was happening. Copedal is the route experienced users already follow, written down so you can skip the expensive part.
Learn · first path
Six steps in the order they pay off. Each one removes a mistake that beginners usually find out about the hard way. Open a step to get the full checklist.
One dedicated folder for everything the agent touches. A mistake then has a boundary, and you always know where to look.
Decide where finished files go and how they are named, then tell the agent at the start of every task. The template is in the Tools section.
Point caches, downloads and project folders at a second drive before the first long job, not after the warning appears.
A quick question, a full explanation and a task to execute are three different requests. Say which one you mean on every message.
A finished task and a stalled task look the same in a quiet chat. Track progress somewhere the agent cannot report for itself.
Snapshot before anything is deleted or overwritten, so a wrong decision costs a minute and not a week.
Learn · common detours
The mistakes below come up again and again. Every row points at the tool that removes it.
| Detour | What it costs you | Fix |
|---|---|---|
| System drive fills up | Everything slows down or stops, and cleanup eats an afternoon. | Step 3 · Drive mover |
| Files with random names in random places | You cannot find or hand over what the agent made. | Step 2 · Delivery rules |
| Reply too long, too short, or too eager | Wasted tokens, or edits you never asked for. | Step 4 · Reply gears |
| Silent stall | Hours of waiting on work that stopped early. | Step 5 · Brake Board |
| Wrong files deleted | Lost work, sometimes unrecoverable. | Step 6 · Brake Recovery |
| Agent will not open | You are stuck with no agent to fix the agent. | Rescue plan |
Tools
Free and narrow on purpose. Two are full guides, one is a design note with a script you can use today, and the template below is ready to copy.
A folder layout and a file naming pattern you give the agent at the start of a task..
The pack goes out by email rather than as a download. Signed in, it goes to your account address; otherwise tell us where to send it.
Move space-hungry folders off the system drive, leave a junction behind, and point the agent at the new location.
Pick the style of each reply with the key you press to send.
When your agent will not open or type: name the layer that broke, then repair it with a second agent and a terminal you trust.
agent-work/
2026-11-12_report-draft/
inputs/ what you gave the agent
outputs/ the only place finished files go
logs/ notes and run history
File name: YYYYMMDD_project_what-it-is_v01.ext
Example: 20261112_q4-review_summary_v01.docx
Rules: never overwrite a version, add v02. Never delete
anything. Tell me the full path of every file you create.
Want the full pack — folder layout, naming rule, the prompt to paste, and a pre-flight checklist — as one file you can keep? Leave an email and it lands in your inbox.
One email with the download, then occasional notes on agent safety. Unsubscribe in one click.
Skills library
Each one is a procedure with a trigger, a working route and a definition of done. They are not one-shot prompts — they are what stops an agent from quietly ruining an afternoon. All of them are published here.
Feeds and notes into a published piece: article assets, image sets, talking-head scripts, and the pre-flight each platform actually needs.
Script to finished cut: aspect lock, voice, subtitles, B-roll, and a measured pass before export.
Placement, naming, versioning, a delivery check — the part that decides whether you can find what you made.
Move what you learned out of the chat and into files a later session can actually read.
Brake · products
Two products for the detours a small tool cannot fix. Both are in development, and neither is open for signups yet.
Status: private prototype, not ready for testers. No release date announced, and pricing is not decided.
Join the Board waitlistStatus: design stage. Data stays on your machine; it monitors and never intervenes. No release date announced, and pricing is not decided.
Join the Recovery waitlistMonitor only. Brake watches and keeps a way back. It never changes how your agent runs or what it decides.
Quiz
Three questions. You get your biggest risk and the part of this site to read first.
Want the full checklist for that step, plus the rest of the path, in one email? Leave an address and it arrives with the confirmation link.
One email, then occasional notes. Unsubscribe in one click.
No drip course, no daily tips. You get the download you asked for, and a note when a new step or tool goes live.
We store your address with our email provider only. See the privacy page for what is collected and how to delete it.