// roost · for devs running Claude Code across clients
Roost tiles a session per project, reopens each where you left off, and starts the ones that matter when you sign in.
Free, no account · Windows 10/11 or Mac · Claude Code or any CLI · First install? Setup guide
96-second demo, no sound. The opening and the ending are AI-generated, with flashing lights in the last 20 seconds.
When you freelance across half a dozen repos, every morning starts the same way: open a terminal, cd into a project, start Claude, drag the window somewhere useful — then do it again, and again. By the fourth project you’ve skipped one, and it’s always the client you least wanted to keep waiting. The setup between you and the work is where the day leaks out.
// how it works
Group projects by client and drag them where they belong — or point Roost at a folder and it finds every project inside it for you.
The project opens in the right place, on the right screen, already pointed at the right work. Nothing to type and no windows to arrange.
Projects marked for startup launch themselves when you sign in to your computer — each with an optional standing first instruction handed straight to Claude.
Every project in one place, and each one carries on from where it stopped rather than starting over. Roost sits in the tray and keeps track while you work.




// you're already the IT guy
Every client has a question that isn’t code. Why is the email down? Can you look at Mum’s iPhone? What do I send the accountant? You could open Claude Desktop and have a chat about it. Or hand it to Roost: say it in plain words, and it asks the boring questions, agrees a plan, does the work and leaves you the files you actually send on.
58 seconds, no sound. An example job made with Roost: an Exchange server stops receiving outside mail, and the work ends in a handover document, a note for staff and a saved recipe. Not a customer’s incident.
Example request: “Mail from outside has stopped arriving for the office.”
Claude works through it with you, then leaves a handover for the night engineer and a plain note for staff. You hit send and look calm.
Example request: “I need to send my tax info across.”
Claude works out what is needed, asks for what is missing and drafts the email, ready to send. You stay out of the shoebox.
Example request: “Mum’s iPhone keeps dropping off the Wi-Fi.”
A step-by-step she can follow, in plain words, without you on the phone for an hour. Family rates still apply.
Click New mission and describe the job the way you would to a colleague.
Coop, a planning Claude, asks in plain language. It is told not to use jargon, so it won’t say “SMTP” at you.
The plan sits on one side and Coop on the other. Answer, watch the plan rewrite, then press Start the mission.
It starts in a throwaway workspace, kept apart from your other work.
The handover document, the draft email, the checklist: saved to your Documents folder.
Turn the job into a recipe, so the next fire starts from what you learned, not from zero.
Fair question. For a quick chat, do. For a job you have to finish, hand over and probably do again:
Coop asks, then shows you what is about to happen. A chat just starts talking.
The handover, the draft email and the checklist are saved to your Documents folder, ready to send.
Save the job as a recipe and the next fire starts from what you learned, not from a blank chat.
Missions live on the same board as your client sessions, so the IT job and the code job are in one place.
New mission is on the Missions tab, top right. It is free to use, with no account. If saving the files fails, nothing is deleted. Recipes are free to make and run.
The Freelancer plan adds Draft, Tried and Proven badges on recipes, and a house standard: rules Coop checks every plan against. Firms can share reviewed recipes with their staff, once an owner or admin has looked them over.
// the details that matter
Full-width strips on portrait monitors, a grid on landscape — and a per-project “perch” so each session lands where you expect it, every time.
The per-project command defaults to claude but runs anything — aider, npm run dev, or a plain shell. One roster for everything you keep open.
The roster is a hand-editable JSON file on your machine, and your sessions and code stay there. No account needed. Roost checks for updates, and that is all it sends until you sign in. The table below lists everything else.

Here is everything that leaves it, and when.
One thing leaves your computer: a check for a newer version. That's it.
The work log and the recent messages of each session go through DiscoverWorthy's cloud, so your phone can show them and send your answers back. Your project files never do.
Off unless you turn it on. If you do, we see token counts and scrambled project names, never message text.
// installing
npm install -g @anthropic-ai/claude-code). Both installed? You’re ready.// and the rest of your stack
SaaS products, client integrations, plain repos: Roost is a dev cockpit for all of it.
Every tile wears its state: uncommitted files, unpushed commits, the branch you left it on, CI and open PRs, even a ▲/▼ health ping for your own SaaS. Friday’s loose ends are visible Monday, before you open a thing.
One click hatches the whole working set — Claude, dev server, log tail — tiled together. Built-in focused sessions (Catch-up, Housekeeping, Release) plus your own recipes per project: name a prompt, get a button.

// running work for a dozen clients?
Roost is the tool we built for our own freelance bench — people delivering for several clients at once, each with its own repo, its own context, its own half-open conversation with Claude. Group projects by client, give each one a perch on your monitors, and treat your mornings like a muster instead of a scavenger hunt.
// the licensed half
Everything above stays free. The Freelancer plan adds Roost Mobile, the phone half you saw earlier, and the work clients pay you for: their sites, their apps and the hours you bill them.
// DIS to 100
Every site carries a Digital Identity Score. The DIS session pulls the latest score and findings through Rigg, fixes the highest-impact SEO and AEO items, redeploys and re-scores — and keeps going while the number climbs.
Freelancer plan

// wired into DiscoverWorthy
Roost knows which client each project belongs to and what their WatchTower is reporting, so the support work arrives already scoped: the hours to log, the tickets to clear.
Freelancer plan

A project added to WatchTower shows its client’s open requests and incidents right on its page. Tick a pile, pick a folder, and they all go there in one step. A ticket that is really about one of the apps under a platform goes to that app’s own session.
When nobody has looked at a client’s WatchTower today, the project wears a chip. One click works through that client’s open incidents and requests, and the chip goes once it has run, from any machine.
One Argusbot per client folder fixes the tickets, asks “Ship it?” once and resolves them. Big batches go to workers first. It never writes to your client on its own: you see the exact words and choose Send it or Don’t send.

// the hours you bill
Choose a project’s DiscoverWorthy client once and its private work log is filed under them. At month end the Ledger rolls it up, and the Invoice session turns it into a draft at your rate.
Freelancer plan


// the part you can’t download from anyone else
Anyone can ask an AI to build a website. What they can’t ask it for is the order, the gates and the failure modes — years of client builds distilled into five moves that turn a business into a site that is unmistakably, findably theirs. The method comes down from DiscoverWorthy to Roost the moment you sign in, written into each client’s project folder for that exact job, and it is published nowhere.
A real visual identity pulled from the brand’s own artifacts, pages written from the actual business, a homepage hero that gets its own pass — and a design crit that fails anything merely correct.
Live, deploying on every push, and crawled — so the platform knows what the site is about and the rest of the method has something real to work on.
The topics DiscoverWorthy detects become pillar pages, clusters and a genuinely connected internal structure. This is where a redesign earns its fee.
Digital Identity Score past 95 for Google and answer engines alike, conversions tracked first-party, a lead magnet that captures, and the print-to-QR bridge.
A site the client edits themselves, handed over clean, with nothing left quietly rotting behind it.
Every letter ends at a gate: the build stops, reports what shipped, and waits for you to say go. That pacing is half of why the output is good — and it is the part a “build me a website” prompt never does.
What the method is, letter by letter
The app is free · the method comes with the Freelancer plan
Roost itself stays free, with no account needed.
// the licensed half
// start here
Free to download, free to run — quietly setting up your whole day’s work from the moment you sign in to your computer.
Free · Signed by Discover Worthy Pty Ltd · Windows 10 / 11 (auto-updates) and Mac