Copedal

Agent workshop for beginners

Let your agent do the work. Keep your files.

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

Safe agent work, from day one

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.

  1. Give the agent its own workspace

    One dedicated folder for everything the agent touches. A mistake then has a boundary, and you always know where to look.

    Detour avoidedSearching the whole drive for a file the agent made.
  2. Write the delivery rule once

    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.

    Detour avoidedTen versions with names like final_new_2.
  3. Keep heavy files off the system drive

    Point caches, downloads and project folders at a second drive before the first long job, not after the warning appears.

    Detour avoidedA full system drive that stops everything.
  4. Choose how the agent should answer

    A quick question, a full explanation and a task to execute are three different requests. Say which one you mean on every message.

    Detour avoidedAn agent that starts editing files when you only wanted an opinion.
  5. Watch progress from outside the agent

    A finished task and a stalled task look the same in a quiet chat. Track progress somewhere the agent cannot report for itself.

    Detour avoidedFinding out after hours that nothing was running.
  6. Keep a way back

    Snapshot before anything is deleted or overwritten, so a wrong decision costs a minute and not a week.

    Detour avoidedPermanently losing files an agent removed by mistake.

Learn · common detours

Each detour has a fix

The mistakes below come up again and again. Every row points at the tool that removes it.

DetourWhat it costs youFix
System drive fills upEverything slows down or stops, and cleanup eats an afternoon.Step 3 · Drive mover
Files with random names in random placesYou cannot find or hand over what the agent made.Step 2 · Delivery rules
Reply too long, too short, or too eagerWasted tokens, or edits you never asked for.Step 4 · Reply gears
Silent stallHours of waiting on work that stopped early.Step 5 · Brake Board
Wrong files deletedLost work, sometimes unrecoverable.Step 6 · Brake Recovery
Agent will not openYou are stuck with no agent to fix the agent.Rescue plan

Tools

Small tools, one for each detour

Free and narrow on purpose. The delivery template is ready to copy today. The rest are marked with where they stand.

Ready

Delivery rules

A folder layout and a file naming pattern you give the agent at the start of a task.

Guide planned

Drive mover

Move space-hungry folders off the system drive and point the agent at the new location.

In design

Reply gears

Pick the style of each reply with the key you press to send.

Enter normal reply
Shift+Enter concise reply
Ctrl+Enter run it as a task
Guide planned

Rescue plan

When your agent will not open or type, borrow the free tier of another agent to repair it.

Delivery rules · copy and paste into your first message
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.

Skills library

36 skills, written while doing the work

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.

7 skills

Content & publishing

Feeds and notes into a published piece: article assets, image sets, talking-head scripts, and the pre-flight each platform actually needs.

7 skills

Video & audio

Script to finished cut: aspect lock, voice, subtitles, B-roll, and a measured pass before export.

5 skills

Files & workspace

Placement, naming, versioning, a delivery check — the part that decides whether you can find what you made.

5 skills

Memory & knowledge

Move what you learned out of the chat and into files a later session can actually read.

Browse the 36 skills

Brake · products

The brake layer for your agent

Two products for the detours a small tool cannot fix. Both are in development, and neither is open for signups yet.

In development

Brake Board

  • Progress bars for each task, across several sessions at once
  • Detects stalls and idle spinning from outside the agent
  • Tracks deliverables by location, name and size

Status: private prototype, not ready for testers. No release date announced, and pricing is not decided.

Join the Board waitlist
In planning

Brake Recovery

  • Takes a snapshot before a risky operation runs
  • Keeps a timeline of what the agent changed
  • Restores files an agent deleted by mistake

Status: design stage. Data stays on your machine; it monitors and never intervenes. No release date announced, and pricing is not decided.

Join the Recovery waitlist

Monitor only. Brake watches and keeps a way back. It never changes how your agent runs or what it decides.

Quiz

Which detour is costing you most?

Three questions. You get your biggest risk and the part of this site to read first.

What went wrong the last time?
What worries you most?
How do you check on your agent today?

One short email when a step gets its full write-up.

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.