The third page
You have installed something most people badly underestimate, including most of the people using it. They treat it as a chatbot that can touch files. What it actually is: the first computer that works for you instead of in front of you. This page is the full climb, from the first minute to things that will sound made up until you do them.
Everything here is sentences typed in plain English. Nothing requires you to learn to program. It progresses in order and each level stands on the one before it, so read it top to bottom once, then live in whatever level you are on.
Read once, then move on
Three things are true, and knowing them is what lets you use everything after this section without worry. This is the whole list. It does not need to be repeated on every page, and it will not be.
It will occasionally state something false with total composure, and it works too fast for you to review everything. The answer is not nervousness, it is architecture, and your setup already has it: everything it does is recorded in a history you can rewind, a guard refuses destructive commands (you watched it refuse one during install), a second guard refuses to save passwords, and nothing it drafts to another human ever sends itself. On work that matters you make it prove things, which takes one sentence: "show me the file", "give me the source line", "write MISSING instead of guessing." Verification is a typed habit here, not a technical skill.
Your folders are not uploaded and the setup sends nothing anywhere. What you type into the conversation, and the files you point it at during a task, are processed by the model like any other use of Claude. So apply one clean rule: work with material you are allowed to work with. If you handle client secrets, patients, or anything under NDA, check your workplace policy first, the same way you would before pasting into any online tool, and know that a conversation with an AI is not privileged the way a conversation with your lawyer is. Plenty of professionals get written approval and then run this openly. Do it in the light.
Session one will impress you and also miss sometimes. The published research on hundreds of thousands of real sessions is blunt about why: practiced users succeed at roughly double the rate of first-timers, and what predicts success is knowing your own domain, not knowing how to code. You already have the hard half. The easy half, about five habits, is section four, and this page hands them to you instead of making you discover them over months.
That is the whole caution section
You now know the three real risks and the shape of the answer to each. Everything from here down is what you got this for.
No setup beyond what you have
Before any cleverness, understand what you now do in minutes that used to cost evenings. Each of these is a real, typical use, typed exactly as written, on files already sitting on your computer. No uploading, no formatting, no preparation. Pick the one that makes your shoulders drop and do it tonight.
"Read every PDF in this folder and tell me which ones mention a termination clause, an auto-renewal, or a personal guarantee. Table, with the page number for each hit."
"Here are seven months of card statements. Find everything that looks like a business expense I never invoiced or reimbursed, and total it by month." People have found four figures doing exactly this.
"Pull vendor, date, amount and due date out of every invoice in here into one spreadsheet, then flag the ones that don't match their purchase order."
"I just took over this folder from someone who left. Explain what is in it, what looks current versus abandoned, and what I should read first. Touch nothing."
"Rename every scan in this folder by what it actually is and the date inside it: lease, tax form, medical, insurance. Show me the plan before you touch anything."
"Here is the transcript. Who committed to what, by when? List every open question that nobody answered, and draft the follow-up note for my approval."
"Compare these two versions and list only what changed in substance, not formatting. For each change, tell me who it favors."
"Here is last quarter's report and this quarter's numbers. Build this quarter's the same way: same structure, same tone, every figure traced to its source file."
Notice what those have in common: none of them are writing tasks. This is the shift almost nobody has made yet. Anthropic's own published analysis of over a million sessions of its work agent found that more than nine in ten sessions were not software development: they were operations, research, document work, admin. The people getting the most out of the most powerful work tool in history are, increasingly, people like you working on things like these.
The reframe
Here is the idea that changes what your computer is. Software has always been built for a million users, so it fits nobody exactly. You now employ something that writes working programs on request, which means software can be built for exactly one user: you. You never look at the code, the same way you never look inside your microwave. You describe the tool; it exists twenty minutes later; it is yours forever, offline, free of subscriptions.
A teacher has it read exit tickets and show, each morning, which students actually understood yesterday's lesson. A physical therapist gets an intake summarizer that turns rambling patient emails into structured histories. A landlord gets one page showing every unit, lease end, and open repair, built from the folder of PDFs he already had. None of these products exist to buy. All of them are an evening's request.
Every trade has one: the checklist that lives in your head, the calculation you redo weekly in a scratch spreadsheet, the seventeen-step export ritual. Those are programs waiting to be asked for. A recruiter turned "compare this resume against the role" into a one-command scorer. An accountant turned month-end close into a checklist that checks itself against the actual files and says what is missing.
This goes further than personal tools. People with no engineering background have shipped public, working websites this way: a property-price explorer with thousands of generated pages, community sites rebuilt in an afternoon, calculators their whole industry now uses. You do not have to want this. But know the ceiling is not "handy scripts." The ceiling is things people mistake for a funded team's work.
Five habits, one week to install
Everything above works out of the box. What separates the people who get ten times more out of the same tool is a handful of habits, each costing one extra sentence. They are not discoverable by using it, and two of them are the opposite of what feels natural. Here they are, so you skip the months of discovering them.
Anything that changes files: plan first, action second. You lose ten seconds, avoid the entire category of "that is not what I meant", and learn how it thinks, which teaches you how to ask better.
Most people describe the task. The best results come from describing the result: what must be true when it is done. That single addition gives it something to check its own work against, and it will, iterating on its own until it passes.
Pointed at nothing, it produces generic. Pointed at your last six real examples first, it produces yours. This is the entire fix for "it does not sound like us."
The counter-intuitive one, worth more than the rest of this section. Its attention is finite; a conversation that has been running for days is full of noise competing with your question. Watch the context bar in your status line fill, and when a job is done, have it write a handoff file and start clean. Files survive restarts. The chat was the disposable part.
It is agreeable by default and will build your bad idea beautifully. Asked for the objection, it becomes something much rarer than an assistant: a colleague.
Why month three beats week one
Chatbots reset to zero every conversation. Your setup does not: it has a standing brief it reads every session, a memory it writes to, and scripts that keep both honest. Feed that memory deliberately for a month and something strange happens: it starts catching things you forgot. Your own stated preferences, quoted back at the exact moment you were about to violate them. That is the point where people stop calling it a tool.
A blank instructions file is hard to write. Being asked good questions is easy. One session of this and you never explain your basics again: how your folders work, what a finished job looks like, what it must never touch, which client insists on which format.
The moment you correct it is the moment worth money. Follow any correction with one sentence and the mistake becomes unrepeatable. Do this for a month and you have built the thing no product on earth sells: an assistant trained on your actual standards.
A rule with a reason survives situations you did not anticipate. It also turns your memory into something better than notes: a record of why every decision went the way it did, retrievable in seconds, forever.
Here is the discipline the enthusiasts skip: a memory that only accumulates gets longer; one that gets re-verified gets smarter. Five rules get full attention each. Two hundred get a fraction. Your bundle ships the audit script; using it monthly is what keeps month six better than month three instead of worse.
"Please remember not to touch that folder" is hope. A guard that refuses is a fact. Your setup ships with three guards already wired; this habit is how you add your own, and it is the single most professional move in this entire page.
The evenings come back
Everything so far happens while you watch. This level is where that stops being required. Work can now run on a schedule, in the background, or in the cloud with your laptop closed, and report to you when it is done or when it needs a decision. This is the part that sounds like the future and is, as of this year, completely ordinary.
The single most popular automation among serious users, across every profession. Overnight, an agent reads what changed: your project folders, your exported inbox, the news in your field, whatever you point it at. At seven a.m. there is one page waiting: what moved, what needs a decision, what can be safely ignored. People describe this one habit as the end of the thirty-minute morning triage, permanently.
A weekly agent that grooms what you never get to: downloads sorted, duplicates found and listed (never deleted; your delete guard sees to that), screenshots named by what is in them, receipts filed by month, a one-line report of what it proposes. You approve with one word. Your computer becomes a place someone tidies.
A standing agent that reads your industry so you do not have to: new regulations for the compliance officer, new listings matching a saved brief for the buyer's agent, new papers for the clinician, competitor pricing for the founder. Every claim carries its source link, and it is told to say "nothing worth your time today" when that is the truth, which is what keeps it readable in month four.
The pattern the careful professionals converged on: the agent reads, sorts by what actually requires you, and drafts replies in your voice, learned from your own sent mail. You approve each one. Nothing sends itself, ever. That one bright line is what makes it safe to hand over the rest, and your setup draws it for you: the inbox-triage agent that ships in your bundle is architecturally unable to send.
Scheduled sessions can run in the cloud, and the same setup is reachable from the Claude app on your phone. Started a long job at your desk? It keeps going after you leave, and pings your phone when it needs a decision. The desk stopped being where the work is.
From assistant to organisation
One session is an assistant. Several, each with a written role, running at once under a coordinator, is an organisation, and you are its only human. This is not a metaphor and it is not enterprise software: your bundle ships the whole structure as plain files you can read. A chief that routes and holds the plan. A production hand for the long file-heavy jobs. A researcher that verifies instead of believes. A librarian that can prove your backups are real before anything gets deleted.
Monday morning, three terminal tabs. One agent is turning fifty pages of interview notes into a findings memo. Another is reconciling a quarter of receipts against statements. A third is researching the four vendors you shortlisted, with sources. Each tab is named by what it is doing, and the glyph in the title tells you working / waiting / needs you. You are reading none of it. You are making coffee.
The published version of this, from inside the company that makes Claude: a single non-engineer runs an ad pipeline where subagents read performance data, flag the losers, and generate hundreds of compliant new variants. Work that was a department is one person with a well-briefed crew. That pattern is not theirs. It is anyone's.
An agent with a charter (its lane, its boundaries, what it must never do, how it is judged) behaves like a trustworthy specialist. An agent without one behaves like an enthusiastic temp. The difference is a text file, and yours ship pre-written: read one and you will immediately see how to write your own.
Lanes with no overlap, and one writer per shared thing, whether that is a folder, a document, or the browser. Your setup enforces the browser one mechanically (one session waits while the other finishes; you never see the collision that did not happen). The rest is the multi-agent skill in your bundle, loaded automatically when a fleet runs.
All shipping, all today
Everything in this section exists right now, in the tool you just installed or one setting away from it. This is what the most advanced individual users on earth are doing this month, and the honest headline is that none of it requires anything you have not already learned on this page.
With the Claude extension in Chrome, it sees the page and clicks, types, and fills forms, behind your logins, across tabs. Professionals record a fiddly recurring task once (pulling a report out of a portal that has no export button, updating the same three fields across two systems) and then it repeats on demand or on a schedule. Give it the errand, not the instructions.
Voice input works in the terminal, and speaking is three or four times faster than typing. The advanced pattern is the morning walk debrief: ten minutes of rambling about the day ahead becomes, by the time you are home, a prioritized plan with the calendar checked and the first two emails drafted for approval.
Between sessions, an agent can be set to reread its own memory and transcripts and reorganize: merge duplicates, retire stale entries, extract the pattern from five one-off lessons. People who run this describe coming back to an assistant that got tidier overnight. You built the manual version of this habit in section five; this is that habit, automated and pointed at itself.
The furthest edge that is still ordinary practice: agents that watch the small machinery of your setup (the scheduled briefing, the backup, the housekeeper) and fix what breaks, restarting what died and reporting what they did. The system stops being something you maintain and becomes something that maintains itself, and tells you so.
Corporate legal teams run contract review this way, built by lawyers who do not code. Physicians report insurance appeal letters that took half an hour now taking five minutes. Analysts point it at a workbook and watch it trace every formula across fourteen tabs before touching anything. Verified US teachers currently get the full tool free, and use it to read exit tickets and adjust tomorrow's lesson tonight. Anthropic's published economic index has roughly half of occupations already using this class of tool on a meaningful share of their tasks. The bleeding edge is not a place. It is a head start, and it is currently for sale to whoever takes it seriously first.
All of them cost nothing to fix
The on-ramp
This is the whole curriculum, paced so each week installs one level from this page. An hour or two a week. By the end you are not "using AI." You are running the kind of setup that people write breathless articles about, and it will feel normal, which is the strangest part.
Where this ends up
The briefing is on your screen before you sit down: what moved overnight, what is blocked on you, three things that matter. The folder of intake documents that arrived at 6am is already sorted, summarized, and cross-checked, with two discrepancies flagged and sourced. A draft of the awkward reply is waiting in your voice, unsent, because nothing sends itself. The tool you asked for in March, the one no company sells because only you need it, quietly did its job again. An agent you briefed once, in a text file, in your own words, spent the night reading your field and concluded, honestly, that nothing needs you today.
None of that is the future. Every piece of it is on this page, and the download you already ran is the infrastructure for all of it. The only thing between you and that Tuesday is four weeks of ordinary evenings.
The manual for the machine is now the smallest part of what you know. What you actually learned here is a way of working: write things down where it can read them, ask to see before you ask to act, give it a way to check itself, and let it carry everything that never needed your judgment in the first place. That way of working is about to be the professional norm. You just got there early.