// roost · for devs running Claude Code across clients

Every client's Claude Code session, in one place. Answer them from your phone.

Roost tiles a session per project, reopens each where you left off, and starts the ones that matter when you sign in.

Get it on Google PlayAndroid: answer a waiting session from anywhere. Paid plan.

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.

The sessions you don’t open are the clients that slip.

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.

Illustration: a dark desk before dawn, a dozen glowing windows scattered in the air with gold sparks crackling between them

// how it works

From sign-in to a working fleet, hands-free.

01

Line up your clients

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.

02

One click, and you are in

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.

03

Morning muster

Projects marked for startup launch themselves when you sign in to your computer — each with an optional standing first instruction handed straight to Claude.

04

Pick any of them back up

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.

Started before you sat down. Answered from anywhere.

Roost
Roost just after sign-in, saying "Roosted 5 session(s)": the startup projects for an invented studio (Harbour Bakery, Coastal Plumbing, Willow Dental and others) back up and live
Roost opened at sign-in and roosted the morning’s startup projects itself, each back where you left it.
Roost Mobile on Android: in the Winter menu PDF session, Claude asks whether prices should include GST, the reply "Yes include GST on both pages", and Claude confirming the PDF and the site are updated
On the phone: a session asks whether prices include GST, you answer from wherever you are, and it finishes the job.
Roost's board beside a real Claude Code session on the invented Harbour Bakery project: the session lists what is left before the winter menu can go live and stops for one decision, whether prices include GST
The board beside a real Claude Code session on an invented bakery’s project: it lists what’s left and stops for the one decision only you can make.
A finished Claude Code session on an invented café app: a plain-English summary of the Pay at the counter change and its tests, and all 7 tests passing
When a session finishes: the change made, five new tests written, all seven passing, and a plain account of what it did.

// you're already the IT guy

Congratulations. You’re 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.

The 9am email outage

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.

Tax time, again

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.

Grandma’s iPhone

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.

  1. 01

    Say it in your own words

    Click New mission and describe the job the way you would to a colleague.

  2. 02

    Coop asks the boring questions

    Coop, a planning Claude, asks in plain language. It is told not to use jargon, so it won’t say “SMTP” at you.

  3. 03

    Agree the plan

    The plan sits on one side and Coop on the other. Answer, watch the plan rewrite, then press Start the mission.

  4. 04

    The work gets done

    It starts in a throwaway workspace, kept apart from your other work.

  5. 05

    Your files are saved

    The handover document, the draft email, the checklist: saved to your Documents folder.

  6. 06

    Save it as a recipe

    Turn the job into a recipe, so the next fire starts from what you learned, not from zero.

“Why not just use Claude Desktop?”

Fair question. For a quick chat, do. For a job you have to finish, hand over and probably do again:

You agree a plan first

Coop asks, then shows you what is about to happen. A chat just starts talking.

You get files, not a transcript

The handover, the draft email and the checklist are saved to your Documents folder, ready to send.

The next one is easier

Save the job as a recipe and the next fire starts from what you learned, not from a blank chat.

It sits with the rest of your work

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

A launcher that respects how you actually work.

Tiling that fits your desk

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.

Any CLI, not just Claude

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.

Local and legible

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.

The Roost board for an invented studio: 11 client projects, each tile showing startup, uncommitted and unpushed counts, test coverage, an up or down health ping, live sessions and Argus auto
Every tile wears its state: what’s uncommitted or unpushed, test coverage, whether the app is up, and which sessions are live.
Illustration: the Roost barn at night, doors shut, gold light kept inside, one thin thread of light rising from the roof

Your code stays on your machine.

Here is everything that leaves it, and when.

Free, no account

One thing leaves your computer: a check for a newer version. That's it.

With the phone

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.

Usage sharing

Off unless you turn it on. If you do, we see token counts and scrambled project names, never message text.

// installing

Up and running in a minute.

  1. Check the prerequisites. Roost drives Windows Terminal on Windows (Terminal on a Mac) and, by default, Claude Code (npm install -g @anthropic-ai/claude-code). Both installed? You’re ready.
  2. Run the installer. It’s code-signed, so Windows shows Discover Worthy Pty Ltd as the verified publisher. On a brand-new release Windows may still say “Windows protected your PC” while the download builds reputation — click More info → Run anyway. On a Mac, open the downloaded disk image and drag Roost into Applications. It is signed with our Developer ID and notarised by Apple, so it opens with no warning.
  3. Add your projects. Create them one by one — Roost can scaffold the folder with a starter CLAUDE.md — or scan an existing folder and import every git repo inside. Mark your daily drivers as startup projects and tomorrow begins with the muster. No account, no sign-in: the launcher is yours from the moment it installs.
  4. Sign in whenever you want the rest. Roost Mobile, the B.R.A.N.D method and DIS to 100 come with the DiscoverWorthy Freelancer plan. Open the settings menu, enter your account email and the 6-digit code from your inbox, and the licensed half switches on — it stays on while your plan is in good standing, even through a few days offline. Skip this step and everything above keeps working.

// and the rest of your stack

Just as sharp on the projects that aren’t sites.

SaaS products, client integrations, plain repos: Roost is a dev cockpit for all of it.

The roster tells the truth

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.

Flocks & session recipes

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.

Close-up of Roost's board: client project tiles showing uncommitted and unpushed counts, test coverage, an up or down health ping and live sessions
Up close: what’s uncommitted or unpushed, test coverage, and a health ping that goes red when a client’s app is down.
Illustration: a freelancer's desk at dawn, every screen tiled neatly in steady gold light

// running work for a dozen clients?

Built for freelancers who run a portfolio, not a project.

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

Then switch on the part that does the client work.

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

Optimise your clients’ sites

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

A recorded DIS to 100 session on Wattlebrook Primary School, a demo site: Roost's site card reads 72/100 DIS while Claude Code pulls the findings through Rigg, rewrites titles and descriptions, adds structured data and a sitemap, checks and deploys, and the card ends at 100/100 DIS, Rigg 100 up 28
A real DIS to 100 run on a demo school’s site: from 72 to 100 in one round of fixes, re-scored after the deploy. Sped up: 26 minutes in 25 seconds.

// wired into DiscoverWorthy

Support their apps

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

Roost's Tickets tab: an invented studio's client requests and incidents, filtered by All, Requests and Incidents, with three ticked and Send 3 to Argusbot ready
Every client’s open requests and incidents in one list. Tick some and Argusbot takes each to that client’s folder.

Ticket triage, from WatchTower

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.

Argus auto, every day

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.

Argusbot

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.

Argusbot asking before it messages a client: the exact words to send about a fixed incident, with Send it and Don't send
Argusbot never writes to a client on its own: you see the exact words, then choose Send it or Don’t send.

// the hours you bill

Track your effort

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

Roost's Ledger for a month: every piece of work grouped by client, one line each with a size tag
An Invoice session's draft in Roost: four lines with plain descriptions, hours and a rate, totalling $1,320.00, waiting for you to add them to the client's next invoice
Month end: the Ledger rolls up every client’s work, and an Invoice session drafts the lines at your rate. Nothing is billed until you confirm.

// the part you can’t download from anyone else

Roost carries the B.R.A.N.D method.

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.

Build

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.

Release

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.

Architect

The topics DiscoverWorthy detects become pillar pages, clusters and a genuinely connected internal structure. This is where a redesign earns its fee.

Nail

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.

Deliver

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

What the plan switches on

  • Roost Mobile: answer a waiting session from your phone
  • DIS to 100 on every client site
  • WatchTower tickets, Argus auto and Argusbot
  • The work log, the Ledger and invoices at your rate
  • The B.R.A.N.D method in each client’s folder
  • Build with Rigg, site previews and shared repos
  • Up to 20% of every client’s subscription, plus leads and audits

Roost itself stays free, with no account needed.

// the licensed half

DiscoverWorthy Freelancer plan

$29/month
Get the Freelancer plan
Amount in AUD subject to applicable taxes.

// start here

Tomorrow morning, start already started.

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