The 3 Features
- 01. Routines Claude runs on a schedule, no chat window needed
- 02. Live Artifacts Claude builds you a real, shareable webpage
- 03. Dispatch Claude keeps working after you close your laptop
1. Routines
A routine is a Claude Code prompt saved with a schedule attached. You write it once, pick a cadence, hourly, daily, weekdays, whatever fits, and Claude fires it off on its own from Anthropic's cloud. Not your laptop. Anthropic's servers. It runs while you sleep, while you're in a meeting, while your computer is off.
This is the difference between a tool you have to remember to open and a coworker who shows up on time every day without being asked.
- Go to claude.ai/code/routines
Requires a Pro, Max, Team, or Enterprise plan, not Free. Click New routine. - Name it, paste the prompt below
Name field:Morning Research Digest. Paste the prompt into the Prompt field. - Connect a repo, pick a schedule
Routines need a GitHub repo to write into, even a fresh private one you make just for this. Under Select a trigger, choose Schedule. FrequencyDaily, time7:00 AM. Minimum interval is one hour, nothing more frequent. - Click Create
Live immediately. Runs on schedule from here. Every morning your digest is waiting as a pull request in your repo, read it in the time it takes to drink coffee.
Every morning, write a short research digest and open it as a pull request. ## What to research Scan for what's new in the last 24 hours on: [your topic, e.g. "AI agent tooling" or "my competitors' product launches"]. ## Output Save to research-digest.md in a new branch. Structure: 1. A 3-bullet TL;DR at the top 2. 3-5 items, each with a one-line summary and a source link 3. One "why this matters" line per item ## If nothing happened Write "Nothing notable in the last 24 hours" and stop. Don't pad the digest with filler to look busy. ## How to write Short sentences. No fluff, no "exciting developments," no fake enthusiasm. State facts, cite sources.
Want the deep, hands-on version with every field explained and 3 upgrades for week two? Read the full Routines guide →
2. Live Artifacts
Ask Claude for anything visual, a dashboard, a mockup, a client report, and it doesn't just hand you text. It builds the actual thing in a panel next to the chat. Then you can publish it. That turns it into a real webpage with a real link, no code, no hosting account, no deploy step.
This is the one I use for client-facing work. Instead of sending a screenshot of a report, I send a link to a live page they can open on their own time.
- Ask for the thing, not the code
Paste the prompt below into a normal Claude.ai chat. Claude opens a panel on the right and builds the page live while you watch. - Review it in the panel
It's fully interactive right there, scroll it, click through it, ask Claude to change anything. "Make the header bigger," "swap that color for navy," "add a section for next steps." Each request updates the same page. - Publish it
When it's ready, ask Claude to publish it (or use the share/publish control in the artifact panel). It starts private, only you can see it, until you choose to share the link. Once shared, you get a real URL you can send to anyone. No account needed on their end. - Update it whenever, same link
Come back next week, ask Claude to update the numbers, and republish. Same URL. Your client's bookmark still works. Nobody has to resend a new link every time something changes.
Build me a live, shareable one-page status report for [client/project name]. Include: - Project name and current phase, shown as a progress bar - This week's wins, as a short bulleted list - Open blockers, if any, called out clearly - Next 3 milestones with target dates - A clean, professional look. My brand color is [hex code, e.g. #2D6E5E] Make it something I can send as a link and update again next week without redoing the whole thing. When it's ready, publish it and give me the link.
3. Dispatch
This is the one-off cousin of Routines. Instead of a recurring schedule, you kick off a single long task and walk away. You don't babysit a chat window waiting for it to finish. Claude keeps running on Anthropic's servers, not your laptop, so closing the lid doesn't stop it.
Open claude.ai/code (same place Routines lives) and start a new session instead of a scheduled one. That session is a cloud sandbox, it runs independent of your device. Give it a task that takes a while, deep research, a multi-step build, comparing 10 options, and it works through it on its own timeline.
- Start a new session at claude.ai/code
Click New session. Point it at a repo if the task involves files, or work directly in chat if it's pure research. - Give it the whole task up front
Paste the prompt below. Because nobody's watching it run, front-load everything it needs to know, the goal, the format you want back, and what "done" looks like. - Close the laptop
Send it, close the tab, close the laptop, go to bed. The session keeps running in the cloud. Nothing about your device staying on or connected matters. - Check the session list when you're back
Every session you've dispatched shows up in your session list with a status. Open the finished one, read the result, ask a follow-up if you need one. Start a second and third session the same way if you've got multiple projects going, each runs independently, none waits in line for the others.
I'm dispatching you on a research task tonight. I won't be here to answer questions, so make reasonable assumptions and note them. ## Task Research [your topic, e.g. "the top 5 tools for X" or "how our competitors are positioning Y"]. ## When I open this back up, I want 1. A summary of the top findings, 5-8 sentences 2. 5+ sources, each with a link and one line on why it matters 3. 3 recommended next steps based on what you found ## Format Write it as a single clean document I can skim in under 2 minutes. No filler, no "in conclusion" paragraphs.
Start With One
Don't set up all three today. Pick the one that solves a problem you actually have right now. Waiting on a lead to reply? Dispatch a research task tonight. Sending a client a status update? Build it as a Live Artifact. Doing the same check every morning? That's a Routine.
Set up one, use it for a week, then come back for the next. This is the difference between reading about AI and running it.