For people who already run Claude Code

Your Claude Code sessions,
running as a real employee team.

Employeflow turns your Claude Code sessions into AI employees you manage from your browser. Each one gets a name, a role, a queue and a daily spending limit, and nothing reaches a customer until you have read it. Run it on your own machine, or we host the whole team for you in Germany.

Your machine and your keys · or hosted by us · 14 days free · cancel from the portal

HOW ONE BECOMES THE OTHER
1
A session you already have open
> claude
You give it a name and a job.
2
Becomes an employee with a job
Rosa
Video editor
4 skills· limit €1.50 a day
A role, a queue, and a hard daily limit you set. On your machine, or on ours if you ask.
3
And it stops before it reaches anyone
waiting for you 1 email ready to send
You read it, then you decide. Every time.
What you get

A company, not a chatbot.

Staff have a job and a queue. A chatbot has neither. That is the whole difference.

A chatbot
Waits to be asked.You explain your business again every time.
An employee
Already knows where it works.It picks up its queue without being briefed.
A chatbot
Tells you what it would do.Then you go and do it yourself.
An employee
Does it, and hands you the file.And stops before anything reaches a customer.

Paste one command and the sessions you already run become a team: each with a name and a list of tasks, every finished job saved, and nothing sent to a customer until you approve it. Your files stay on your machine. If you would rather not run it there at all, the same team runs on our servers in Germany.

Your first portal is running in a few minutes.

One command on your own machine, or hosted by us. Free for 14 days.

How it works

Three steps. You do them once.

Setup takes a few minutes, on your own computer or on ours. What happens after it is further down this page.

01 · CONNECT

Connect your sessions

Paste one command on your computer. Employeflow then sees the Claude Code sessions you already have open. Name one Rosa · Video editor and she becomes an employee. Your conversations stay on your computer; only the task she is working on is shared. Rather not install anything? We host the team for you.

02 · ASSIGN

Give each one a job

Each employee gets a role, the skills for it, a list of tasks and a daily spending limit. They start out knowing your business, so you never explain it again every morning.

03 · APPROVE

You approve what goes out

Every email, post or message waits for you. You read the exact text and approve it or not. Your decision is saved with the time, and it can never be changed afterwards.

22
Screens in the portal you get
COUNTED IN THE BUILD · 1 OCT
1,128
Finished jobs on record, by our own team
COUNTED IN THE DATABASE · 1 OCT
€0.045
What one piece of delivered work costs
MEASURED 1 OCT · 58 COSTED DELIVERIES
A chatbot
Waits for you to open it. Every session starts from nothing. You explain your business again, paste the same context again, and when you close the tab it is all gone.
An employee here
Already knows where it works. A role, a skill set, and your own facts loaded before it starts. It picks up its queue without being briefed, and what it learned yesterday is still there today.
A chatbot
Can cost you anything. There is no ceiling and no line item. You find out what it cost when the bill arrives.
An employee here
Has a limit you set, enforced in code. A daily amount per employee. When it is reached the work stops and says so. It never quietly spends more, because it cannot.
A chatbot
Tells you what it would do. Then you copy it out, paste it somewhere else, and do the actual work yourself.
An employee here
Does it, and hands you the file. Finished work with a name and a timestamp. Anything pointed at a customer stops at your approval first — you read the exact words before they leave.
A chatbot
Leaves no trace. If someone asks who approved that email, there is no answer.
An employee here
Writes everything down. Who decided, what they saw, and when. The record cannot be edited afterwards, and the same decision cannot be made twice.
The gate

The interesting part is what doesn't happen.

An agent that can send email is a liability. An agent that drafts email and then stops is an employee. Everything outbound — mail, posts, Telegram, anything with a customer on the other end — halts at a gate and waits for a person.

WHAT THE AGENT DID

Wrote an email to eight members about this month's changes. Attached nothing. Chose the sending address. Then stopped.

draftedheld at the gate
WHAT YOU DO

Read the exact text. Approve it or don't. Your name and the timestamp go into a record that cannot be edited afterwards, and the same decision can never be made twice.

your call
Who this is for

People who have to answer for what their tools send.

◎
Owners running lean
You already do six jobs. This gives four of them to staff who work overnight and never send anything you have not read.
▣
Agencies with client work
One portal per client. Separate employees, separate ceilings, separate audit trail. Nothing crosses between them.
⋮
Teams already in Claude Code
You have the sessions open right now. This puts a company around them instead of a tab you forget about.
Straight answers

What this is not.

It is not a model, and it does not replace your Claude subscription
Your employees are the Claude Code sessions you already run, under your own account — or ours, if you ask us to host them
It does not read your transcripts
The bridge sends session titles and a one-line summary of what an employee is doing. Nothing else leaves
It will not send anything on its own
Everything starts held for your approval. You can switch a skill to automatic once you trust it — and switch it back instantly
It is not finished
23 modules work today. We tell you which ones are thin rather than dressing them up
What is in the box

Twenty-three modules, not three screens.

Skills

What you can put them to work on.

Each employee only has the skills you give it. Every one of these can be held for your approval or switched to automatic — your choice, per skill.

Telegram & WhatsApp
Answers incoming messages on your rules. Never messages anyone first unless you tell it to. Guided setup for your bot.
Email
Drafts replies and follow-ups from your own address. Held by default so you read the words before they go.
Social posts
Turns one recording or article into a week of posts, in your voice, queued for you to wave through.
Research
Competitor checks, market numbers, background on a person or company — with the sources attached.
Documents & reports
Writes the thing you keep putting off and hands you the finished file, named and dated.
Spreadsheets & data
Cleans lists, removes duplicates, reconciles numbers, and tells you what it changed.
Video & images
Cuts clips, adds captions, makes thumbnails and stills. Output lands as files, not links.
Follow-up
Chases the leads that went quiet, on a schedule, and stops the moment someone replies.
After the first day

Then you stop starting things.

The three steps above are setup, and you do them once. What the product actually is shows up in the week after.

It starts on its own
You say it in a sentence and it holds you to it. “Every Monday morning, draft the weekly update and hold it for me.” “Tell me when nothing has moved for a day.” “Tell me when the report is delivered.” It fires, it says why it fired, and it cannot fire more than a few times in a run — a rule you wrote badly cannot spend your afternoon.
Work with several people in it
A job is a chain, not one order. Research it, then write it, then cut the video, then back to the Boss. Each step waits for the one before it instead of all four starting at once, and a step that is stuck ages visibly on the board rather than sitting there quietly for a fortnight.
On the phone, because it is a browser
The part you do away from the desk is deciding. Approvals are short: read the exact words, approve or decline. That works on the device in your pocket, which is where most of them will actually happen — in a queue, between meetings, at the end of the day.
And when something breaks
The team says so instead of going quiet. A session that cannot be reached is named, a decision waiting too long is raised in the chat you already read, and every spending limit reports itself. Silence is the one thing this is built not to do.

See what it costs.

Pricing

You are buying the company around the sessions.

Connect Claude Code once and you get the portal: your employees with names and jobs, the skills you give them, a gate in front of anything that leaves, the automations that start work without you, and the projects it all hangs on — open from your phone in a queue at the airport as easily as from your desk. The model spend stays on your own Claude account, where it is cheapest. Ask us to host instead and the Claude usage is included up to the amount on your plan.

The portal
Every session becomes an employee with a name and a job. One screen for all of them, instead of tabs you have to remember the order of.
On your phone
The same portal, in a browser, on the device in your pocket. Read what is waiting, approve it, give someone the next job. Nothing to install there either.
Skills
Give an employee what it needs and nothing more. A library to hand out, a handbook the whole team reads, and skills only your team has — written by your own Boss and approved by you before anyone gets them.
Approvals
Nothing outbound moves without a human click. You see the exact text, edit it if you want, then approve or decline. The decision is written down with a timestamp and cannot be edited afterwards.
Automations
Work that starts without you asking. Tell it in plain words — every morning, when nothing has moved for a day, when a job is delivered — and it holds, fires and reports itself.
Projects and the record
A job is a chain, not a single order. Steps wait for the step before them, a stuck one ages visibly, and every action leaves a receipt: who decided, when, which employee, what came out.

What the plans differ on is size: how many teams, how big each one is, how many people can sign in, and how much they may spend in a day. While we are in early access nobody is charged anything — these buttons take you to sign-up, we put your account on the plan you picked, and billing opens later.

Trial
14 days free
  • 5 teams, 10 employees each
  • At most €1.50 a day per team
  • Hosted: €10 of usage included
  • No card while we are in early access
Solo
€99/mo
  • 3 teams, 5 employees each
  • At most €1.50 a day per team
  • Hosted: €15 of usage a month
  • 2 people can sign in
Business · most chosen
€249/mo
  • 5 teams, 10 employees each
  • At most €4 a day per team
  • Hosted: €50 of usage a month
  • 5 people can sign in
Operations
€599/mo
  • 10 teams, 20 employees each
  • At most €12 a day per team
  • Hosted: €150 of usage a month
  • 15 people, monthly check-in
ON YOUR OWN MACHINE

The model spend is yours and goes to Anthropic directly, which is the cheapest it can be. The plan price is all that comes to us. The daily ceiling is still enforced in code, so a runaway employee cannot empty your account overnight — it stops and tells you.

IF WE HOST IT INSTEAD

Nothing to install and your computer can be off. A message to an employee costs about six cents, measured on our own teams, so €15 is roughly 230 messages a month and €50 about 770. Reach it and the team pauses and says why; nothing is billed past a ceiling you set.

Enterprise from €1,490 a month: 20 teams, 40 employees each, €400 of usage, a data processing agreement and a named contact. Prices exclude VAT.

Still deciding? Take the 14 days.

We are in early access, so there is no card to enter yet and nothing to cancel. Connect the sessions you already run, or ask us to host the team, and tell us when to stop.

Examples

What people actually hand over.

Three kinds of people who use it, all of them already working in Claude Code. Pick the one that sounds like you.

An agency with clients
One portal per client, not one folder per client

You already keep a session per client and remember which is which. Each one becomes its own portal: own employees, own spending limit, own record. Nothing crosses between them, so you can hand a client their own login without showing them anyone else's work.

Hands over
  • Weekly reports, written and filed
  • Research nobody had time for
  • Draft replies, held for your approval
An owner doing six jobs
The work that never gets done

The things that stay on the list for months. A chat cannot pick them up, because it waits to be asked. An employee has a queue, so it takes the next one overnight and leaves the finished file where you can see it in the morning.

Hands over
  • Following up on quiet leads
  • Cleaning up a spreadsheet nobody trusts
  • Turning one recording into a week of posts
Someone with an audience
Answering people, carefully

Messages get drafted and held, never sent. You read the exact words before anyone receives them, which matters most when the person on the other end is having a hard week. This one is not hypothetical: it is running in production for a coach's team, and nothing has ever left without a human click.

Hands over
  • First drafts of every reply
  • Sorting what needs you from what doesn't
  • Keeping a record of what was said

All three run on sessions you already have open.

Security & privacy

Where the work happens, and what never leaves.

The honest version, in plain words. If something here matters to you, ask us about it before you pay.

Where it runs
Where you choose: your machine, or ours. By default the work runs where you already work — your own computer, your own Claude account, your own keys. Ask for hosting and it moves to our server in Falkenstein, where every customer gets a separate operating-system account with its own home folder and its own secrets, tested in both directions so that one cannot read another's.
What we can reach
On your machine: a session's name and one line about what it is doing. Not your prompts, not your files, not your transcripts. If a line looks like a password or a key it is thrown away before it is stored. On the hosted option we run the machine, so the honest answer is that we could reach it — we do not read your work, and we will put that in a data processing agreement.
What the command installs
Two Python files and a cron line. You can read all of it. One carries what your sessions are doing up to the portal, the other brings your messages and orders down into them. They update themselves from a published address, and the version they are on is printed every run. Removing it is deleting the cron line: your sessions keep working, they just stop reporting.
Sending
Held by default, automatic only if you say so. Every skill arrives set to hold and wait for you. You can turn individual skills — Telegram replies, say — over to automatic once you have read a week of drafts, and turn them back with one click. Either way the send is recorded with a timestamp, so there is always an answer to "who approved this".
The record
It cannot be edited afterwards. The same decision cannot be made twice, and an approval cannot be un-made. That is the point of having one.
Between portals
Nothing is shared. Separate employees, separate limits, separate records. One client's portal cannot see another's.
Spending
A hard limit, enforced in code. Not a fair-use policy. Every plan has a daily ceiling per team, and it applies wherever the work runs — on your own machine that is what stops a runaway employee emptying your Claude account overnight. On the hosted option there is a monthly allowance on top of it. When either is reached the work stops and says so.
Leaving
You can cancel from inside the portal. Your records stay readable while your account exists and you can take them with you. When an account is closed its whole folder on the server is archived and handed over, then removed from the machine.

Anything here you want in writing?

Ask before you pay. We would rather answer it now than have you find out later.

Straight answers

The questions worth asking.

Short answers, including the ones about your own machine and what this can see. Where you get a choice, we say so.

Can it send things without me, or do I have to approve everything?
You choose, per skill. Set email to hold for approval while Telegram replies go out on their own, or the other way round. Most people start with everything held, read a week of drafts, then switch the ones they trust to automatic. You can change any of it in a click, and switching a skill back to held takes effect immediately.
What can they actually do besides email?
Anything you can describe as a job. Telegram and WhatsApp replies, social posts, research and competitor checks, spreadsheets and data cleanup, documents and reports, video and image editing, and following up on leads. Each employee gets the skills you give it — nothing more, so nobody wanders outside their job.
Can it run my Telegram for me?
Yes, and you do not have to set it up alone. The portal walks you through connecting your bot step by step, then an employee handles incoming messages on the rules you set: reply to the easy ones, hand you anything sensitive, and never message anyone first unless you tell it to.
Do I need to be technical to set this up?
You paste one command once, and that is the whole of it. Everything after that happens in the portal, and each skill has a guided setup that tells you what to click and why. If even that is one step too many, the hosted option has nothing to install at all.
Do I need Claude Code?
For the normal way of using this, yes — and that is what makes it cheap. Your employees are Claude Code sessions on your own machine, under your own account, so you are not paying us a markup on somebody else's model. If you do not want them on your machine, we host the team in Germany instead and the Claude usage is included in the plan, up to the allowance on the pricing page.
Does it use the sessions I already have, or start new ones?
The ones you have. It reads session titles, nothing else. Rename one to Rosa · Video editor and Rosa becomes an employee, keeping everything that session already knows. Sessions you do not name are left completely alone, so you can try this with one of eleven and see what happens.
Does it read my conversations?
No. It sees a session's name and one line about what it is working on. Not your prompts, not your files, not your transcripts — those never leave your machine. If a line looks like a password or a key it is thrown away before it is stored. When an employee is handed a message from the portal, the answer it writes is what comes back, and nothing else.
What happens when I close my laptop?
Work waits, it does not vanish. Anything you sent from the portal queues up and is delivered the next time the machine is awake; approvals and the record live in the portal, so your team can still read them from a phone while your laptop is shut. If you want work to continue overnight without the machine on, that is the one thing the hosted option buys you.
What will it really cost me?
The number on the pricing page, plus your own Claude subscription. On your machine the model spend is yours and ours is the plan price; every plan still carries a hard daily ceiling per team, enforced in code rather than by a fair-use policy, so a runaway employee cannot empty your account overnight. On the hosted option the Claude usage is ours and comes out of the monthly allowance, and the team pauses and says so when it is used up.
Where does my work live, and can you see it?
On your machine, if you run it there. We receive a session's name and one line about what it is working on — not your prompts, not your files, not your customers' data. On the hosted option the work lives in an operating-system account of your own on our server in Germany; we run that machine so we could technically reach it, we do not read your work, and we will sign a data processing agreement saying so. See Security & privacy.
How many employees can I have?
Five on Solo, ten on Business, twenty on Operations — per team, and you get several teams. Hiring one is a name and a job description, and what it costs you is the work it does, counted against your allowance.
What happens if I cancel?
You cancel yourself, from inside the portal. No email, no retention call. Portals stop at the end of the period and your approval records stay readable, so you keep the proof of what was sent and who signed it off.
Is this finished software?
Twenty-three modules work today, and we will tell you which are thin. If something you need is missing, say so before you pay — we would rather build it than take money for a promise.

Still unsure? Name one session and watch what happens.

Drag to rotate

Twenty‑three modules, ready on day one.

Employees, skills and spending limits are set up for you. You name them and start assigning work.

Create your account

A few minutes to a
running company.

Free for 14 days. Connect your own sessions, or let us host them.

or

Already have an account? Sign in

Drag to rotate

One approval is waiting for you.

Nothing was sent while you were away. That is the whole idea.

Access

Your company is
already running.

Your portals, your employees, your approvals — exactly where you left them.

or

No account? Create one free — 14 days, no card while we are in early access.

Not signed in
Sign in and this fills with your own portals, employees and numbers — nothing here is an example.

Your dashboard

Every team you run. Enter one, watch its numbers, or build a new one.

PORTALS LIVE
–
reading…
EMPLOYEES
–
across all portals
WORKING NOW
–
reading…
WAITING ON YOU
–
reading…
SPEND TODAY
–
reading…
DELIVERED
–
files, last 24 h

Your portals

Enter opens the real portal

Need another one?

The designer builds a portal from a description — employees, skills and ceilings included.

Nothing goes out without you: read what arrived, edit the draft if you want, then approve or decline.

Waiting on you — every portal2
Outbound email — "August update" to 8 members
Iris · Harbour & Fields Agency · 3 min ago · from hello@
Telegram message to a grieving client
Sam · Northwind Coaching · 26 min ago
The signed recordimmutable
Email to 8 members — APPROVED
you · Aug 22, 18:04 · sent 18:04
sent
Telegram broadcast — DECLINED
you · Aug 21, 11:20 · "wording"
held
Post to LinkedIn — APPROVED
you · Aug 20, 09:12 · sent 09:12
sent

A decision cannot be made twice and cannot be un-made. Verified on real rows, 17 checks out of 17.

Everyone who works for you, across all portals — what each one is doing right now and when they last proved it.

Everyone, every portal

14 employees

Each of these is a Claude Code session on your own machine. Rename the session and the employee is renamed here.

Your company

—

One company, several people, several teams — so a colleague joins once instead of team by team.

Reading…

People with access

—

Colleagues who can open a team, see its work and approve what goes out. This is people, not AI employees.

Reading…
Single use, valid 7 days. The link goes on your clipboard — send it however you like.

The full record of everything that happened — warm rows are you, blue rows are the machine. Newest first.

Everything your team doesreading…

What your employees can do — and how you teach them. Everything here reaches their Macs by itself within five minutes; nobody types anything.

Skill Library

reading…

Your team’s own skills

written by your Boss, approved by you

What your team may reach

off unless you switch it on

Team Handbook

how you teach your team · day-one guide

Hire a position

most used first

Connectors

outside tools your employees can use

A connector is an Anthropic MCP server that Claude Code talks to. When you request one, we wire it so that your employee gets it by itself — you authorize in the browser, the courier configures the machine.

Missing something?

Tell us what you need and we build the skill for your team. It is saved on your team and reaches us; it appears in the Library when it is built.

What your teams cost to run, measured on your own machines.

Reading…

Not an invoice. Measured by the courier on your own machine, one figure per day. On a Claude subscription this is what the same work would list at rather than a charge — the wording says which. Metadata only: message content is never read.

What you pay us: plan, invoices, payment method. (Spend is different — it shows what your usage costs to run.)

CURRENT PLAN
Reading…
Invoicesnone
No invoice has been issued for this account.
WHAT YOU ARE USING
Reading…
Your monthly Claude allowanceincluded in your plan
Reading…
This month so far—
Reading…
Where your teams runwhat hosting you are using
Reading…

Your sign-in, your security, your gate codes.

YOUR ACCOUNT

Your email comes from your sign-in and cannot be edited here. Company and country are stored on your account and are used on your invoices when billing goes live.

SECURITY

Your password is held by the sign-in system and is never shown here, not even as dots.

DANGER ZONE

Cancelling stops every portal at the end of the period. Your audit records stay readable.

Turn your own Claude Code sessions into these employees — one pair code, no password ever in the terminal.

Connect this computer to your team

Three steps, a few minutes

Your employees are Claude Code sessions on your own computer. This links that computer to this team. Your prompts and transcripts never leave the machine — only what is finished travels here.

1  Create your connect code
One code per computer. It is shown once and cannot be read back, so copy it before you leave this screen. Creating another code adds a computer — every machine already connected keeps working, and so does your team on our servers.
curl -fsSL employeflow.com/bridge.sh | sh -s -- <create your code first>

The connector is a small file. Open the download, then right-click the Connect ….command file → Open. Terminal opens by itself and does the rest. No typing. Each computer gets its own code; the machines already connected keep working.

Only the code's fingerprint is stored, so nobody — including us — can read it back.

to do
2  Open the connector on that computer
Double-click the downloaded file, then right-click Connect ….command → Open (macOS asks once because it came from the internet). Terminal opens and works for about a minute.
There is no Claude login to do — the connector authenticates through Employeflow. When it prints You are connected to: <your team>, you are done there. Prefer typing? Copy the command instead and paste it into Terminal.
after step 1
3  We confirm when your computer reports in
Your computer reports every five minutes once connected. The first report usually lands within five minutes of the command finishing. This page checks by itself.
waiting
Bridged sessions—
Reading…
Help center

Everything, in plain language.

How to set up, run and pay for your team — and exactly what this can and cannot see. Still stuck? Open Support in the corner, or email support@employeflow.com.

Getting started
What is Employeflow?
You already run Claude Code. This gives those sessions names, roles, a queue and a spending limit, and a portal to run them like a team — with a gate so nothing goes out without you.
Create your account and build a team
Sign up free and answer five questions about your work. A team is designed for you: each employee is a name, a role and an education. No card, no confirmation email.
Connect your computer
One line. On macOS or Linux you paste it into Terminal; on Windows into PowerShell. There is no login to set up — your machine authenticates through us. Your employees then appear in your own Claude Code, named.
Where your employees show up
As named Claude Code sessions on your own computer — Boss, Ruby, Nina. You talk to them in the portal chat, or open the session directly; it is the same employee either way.
Running your team
How to run your team — day one
Onboard in three steps. ① Design the team in the Designer — your business, your positions, names. ② Connect a computer: Connect Claude Code → choose the team → Download the connector → double-click. One Claude Code session per employee is created and named; no terminal, no Claude login. ③ Give it its brain: tell your Boss to write your own methods as skills → Skills → Approve. Every employee has them within five minutes.

Run it with five verbs. Talk — team chat, name one employee (a message with no name wakes everyone and costs once each). Assign — Give a Task → Queued → Running → Delivered → Results. Approve — anything outward stops in Approvals: Approve, Reject, or Ask for changes; nothing leaves without you. Watch — Activity (every answer and order, with its cost), Spend (per day, capped by plan), the dots (working / idle). Teach — publish a skill, approve it, the whole team has it.

Three honest limits. The courier delivers only into a session you have not typed in for three minutes — it never races you. Skills that need their own tools, credentials or schedules do not run themselves yet. On Windows the desktop sidebar may not list the sessions the connector created.
The approval gate
Anything that would leave the building — an email, a post — stops for you. You read the exact text, edit it if you want, then approve or decline. Nothing goes out without you.
Assign work and chat
Message an employee in the portal and the Boss hands the work to whoever it belongs to. Answers come back into the portal and into the real session.
Publish your team's skills
Teach the team your own methods: tell your Boss to write them as skills and publish them. They arrive as pending in the Skills tab; you approve with one click and every employee has them within five minutes.
Set your handbook
How your team writes and works — your tone, your rules, who your clients are. Every employee reads it before their next task. Set it in the Skills tab.
Machines & hosting
Your machine vs our servers
Employees can run on your own computer or on our servers. On your machine, your prompts, files and transcripts stay local — only finished work travels to the portal.
The two-machine handover
Whatever you open runs on your computer; whatever you don't stays on our servers. Close the laptop and the team is ours within about twelve minutes; open it and it is yours again. You never lose the team by closing the lid.
Connect a Windows PC
One line in PowerShell installs what is needed and schedules the courier every five minutes. No WSL, no Git Bash.
Move your team to our servers
One button in Connect Claude Code. Nothing to install; the team runs in Germany and answers in a few minutes.
Billing & account
The free trial
14 days, no card. Billing is not switched on during early access, so nothing can charge you.
Plans and what they include
Per month: Solo €99, Business €249, Operations €599, Enterprise €1490. Higher tiers include more Claude usage, more portals and more employees.
The daily ceiling
Each team has a daily spend cap, counted across every machine it runs on, so one runaway day cannot empty anything.
Your account
Your company and country live on your account. You set what appears on invoices in Billing & plan.
Security & privacy
What we can and can't see
We read what a task cost and its status. On your own machine, your prompts, files and transcripts never leave it — only finished work does.
Where your data lives
Portals and records sit in our EU database; hosted teams run on servers in Germany.
Removing the connection
Delete one scheduled job (or one cron line) and the courier stops. Your Claude Code sessions keep working.
The connect code
A per-computer code, shown once. Making a new one adds a computer and never disturbs the ones already connected.
What’s new

Shipped, and dated.

We build in the open. Every meaningful change to the product, newest first.

16 Sep 2026
New
The Claude login is gone
Connect your team with one line — no theme screen, no browser login, no code to paste. Your computer authenticates through us, on macOS, Linux and Windows alike.
16 Sep 2026
New
One team, two machines
Run some employees on your own computer and the rest on our servers, with a clean handover: close the laptop and we take over within about twelve minutes; open it and they are yours again.
16 Sep 2026
New
Your sessions arrive named
Employees now open in Claude Code already named — Boss, Ruby, Nina — so you always know which window is which.
16 Sep 2026
New
Windows
Connect a Windows PC in one PowerShell line. No WSL, no Git Bash.
16 Sep 2026
Design
A new look
A new logo, an AI support agent in the corner, a calmer dashboard, an onboarding checklist and a live team-health strip.
15 Sep 2026
Change
Built for Claude Code users
The product now leads with the sessions you already run; hosting is the option for when you would rather not run it on your own machine.
15 Sep 2026
Fix
The daily ceiling counts every machine
A team split across your laptop and our servers is now capped as one team, not once per machine.
14 Sep 2026
New
Hosting on our servers
Don't want it on your laptop? Move the whole team to our servers in Germany in one click.
Status

Is everything running?

Checked live from your own browser, right now — not a badge we set by hand. If something here is red, we can see it too.

Checking…
running checks from your browser

Each line is a real request to that service from this page. “Operational” means it answered as expected; “degraded” means it answered oddly; “unreachable” means it did not answer. Questions? support@employeflow.com.

Palette
Fonts
Intro
Screen