Medellis Coworker starts by watching: it reads, plans and drafts — and does nothing you haven’t approved. It runs on your own machine — we never see your files, prompts or output. Promote it when it’s earned the call, demote it the moment it hasn’t.
Version 0.1.9 · macOS 13+ on Apple silicon · Windows 10/11 x64 · Early access
Windows early access is not code-signed yet. Microsoft Defender SmartScreen may ask you to confirm before running the installer.
It’s what it did at 2am, on whose behalf, with which account — and whether you can show someone afterwards.
Most agents hand you one switch: watch every step, or let it run. That isn’t how you’d onboard a person, and it’s a strange way to onboard software that can send mail as you.
Not chat — deliverables. Real asks, and what comes back:
A sorted inbox with the replies that matter drafted — each one held for your approval.
A finished document, pulled together from your files, mail, and notes — not an outline for you to fill in.
Conflicts found, reschedules proposed — your calendar moves only after you say go.
Status pulled across GitHub, Slack, and your tracker — with the receipts, in one answer.
It searches, reads the sites, and hands back a comparison memo with its sources — not ten tabs for you to skim.
A standing task, every weekday at eight: deals that moved, mail unanswered, the digest filed. Anything outbound still waits for you.
Autonomy is earned, and it’s enforced by the engine, not the prompt. The same ask at each level — pick one:
It reads, plans, and drafts what it would do — while writes, sends and commands are blocked outright, not merely gated. You learn how it thinks before it can act on how it thinks.
It reads and gathers on its own. Anything consequential — a write, a send, a command — stops and waits for your yes, your edit, or your no. Below trusted, even actions you’ve allowed before keep asking: governance outranks convenience.
Promote a coworker once it’s proven and your normal permission rules take over — no ask-every-time ceiling. Every action still lands in the record, and demoting it is a setting, not a negotiation.
Everything here ships in the app today — and every bit of it sits under the same clearance ladder.
Built-in web search and page reading, no API key to configure — research, comparisons, and pulling sources work out of the box.
Runs commands, edits files, builds and checks its own work — and every command shows up in the ledger before it runs.
Schedules like “every weekday at eight”, or wait-until-something-changes. While you’re away, approvals queue in your inbox instead of timing out.
Durable notes and preferences, kept on your disk and carried into every session. Say it once, not every morning.
Write a routine down once — how you brief, how you file, how you ship — and it becomes a skill the coworker pulls up when the task calls for it.
@-mention it in a thread and it works the task from your desk and replies in that thread — allowed to speak there and nowhere else.
Not a transcript — a log. Which coworker acted, in which session. What ran, with secrets redacted before anything is written. What was held, what you approved, and when.
Each step lands as it happens — proposed, held, approved, ran. Not a summary written after the fact.
Every line ties to the coworker, the session, and the approval that released it — including which standing rule, if one did.
A durable log on your own disk, next to the work. Read it, query it, keep it — it leaves your machine only if you send it.
One app on your Mac or Windows PC. Signing in with Medellis Cloud is what ties your licence to you — the work itself happens locally either way.
Gmail, Google Calendar, Drive and Outlook connect in one click. Everything else takes a pasted token, and always will if that’s what you prefer.
Ask in plain English. It plans, does the work, and stops at anything that writes, sends or runs — until you say go.
Not a browser tab pointed at our datacentre. Your files are read where they live, and they stay there.
Connecting Gmail hands the token straight to your device. Our servers pass it along and keep nothing — there is no table for it.
Sign in once. After that a dropped connection means “reconnecting”, not “locked out of your own machine”.
Stop paying us and the coworker keeps working: the engine is open source and already on your machine, and the record is a file you own. What lapses is ours — branding, licence, support. We’d rather earn the renewal.
Thirty-four services today, five more on the way — mail, calendars, chat, code, CRMs, docs, files, books, analytics. Mail, calendar and Drive connect in one click; the rest take a token you paste, and always will if that’s what you prefer. Every one of them answers to the same clearance ladder and writes to the same record.
Plus anything that speaks MCP — point the app at your own tool servers and they join the same ladder.
Coworker deploys white-label through the Medellis studio: your brand, your workflows, and a licence sealed with your name — seats, term, and how far anyone may promote a coworker, enforced on every desk.
Every desk still runs local and offline — the policy travels, the data doesn’t. A fleet console, one record and one policy across the team, is next on the roadmap. Fixed implementation, then a platform fee.
Talk about a rolloutYour choice. Bring your own key for the major model providers, or run fully local. Your data goes to the provider you picked — or nowhere, if you keep it local.
Only what you approve, plus the calls to the model you chose. Connector tokens are handed straight to your device — our servers keep nothing.
Early access is free. Team rollouts are a conversation — tell us what you need.
Yes. Coworker deploys white-label through the Medellis studio — your brand, your workflows, a fixed implementation plus a platform fee.
Free to try. Nothing goes out without your say-so.