add-on for robOS
The whole agency works on one brain
robOS remembers for one person. robOS Team puts two or more operators on the same clients: the same brand voice, the same notes, the same working memory. Each from their own laptop, with no files flying around on WhatsApp.
where the work leaks
What happens today when there are several of you
Every operator has their own robOS, and it remembers flawlessly. The problem shows up between operators.
- xEveryone has their own brain.What one person learns on Monday reaches the others by accident, or never.
- xThe same client sounds different.Voice and brand rules live on each laptop, so the work goes out in two or three styles.
- xA new hire starts from zero.The client's history sits in someone's head and in a few old chats, impossible to hand over.
- xWhen someone leaves, what they knew leaves too.Decisions, mistakes avoided, client preferences: all of it walks out with the laptop.
the first question
"Can't we just put everything on Drive or GitHub?"
For files, yes. Both hold files very well. The difference shows up when you want each colleague's assistant to know what is inside them.
With a shared folder
- The file sits in Drive while your colleague's Claude works off their laptop. What is in the folder stays in the folder until someone opens it.
- You search by file name, and by whatever you remember calling things.
- Two people's daily notes land in the same file, so one covers the other.
- Access is granted on folders. Covering a whole client means you remember which folders belong to it.
- When you remove someone from the folder, you know you removed them. What they took stays guesswork.
With robOS Team
- Whatever lands on the client goes straight into each colleague's working memory, so their assistant already knows it when they sit down.
- You search by whatever comes to mind about the client, and you get your colleagues' notes in the same answer.
- Daily memory is kept per author, so two people can write on the same day without touching each other's work.
- Access is granted per client. One right covers voice, notes, memory and deliverables.
- Revoking access cuts what comes next immediately, and it stays in the log with author and timestamp.
As for GitHub: it is excellent and we use it too. It does ask every person on the team to know how to resolve a sync conflict, which makes it a good fit for developers and a hard one for a copywriter. Team was built for the second case, with a browser panel over the same files.
what robOS Team does
One brain per client
Team connects your robOS installations through a server that belongs to the agency. What one person knows about a client, everyone working on that client knows.
01
Shared clients
Brand voice, notes, working memory and deliverables for a client sit in one place, reachable by whoever has the right.
02
Daily memory, per author
Two people can write on the same day, on the same client, without overwriting each other. Each also sees the other's work.
03
Search across the whole team's brain
When you look something up about the client, you get your notes together with your colleagues', in the same answer.
04
One person's correction reaches everyone
When someone fixes a mistake, the rule is written on the client. The team stops repeating the same mistake four times.
05
You decide who sees what
Access is granted per client, read or write, and revoked the moment the collaboration ends.
06
A full log
Every change carries an author and a timestamp. When something looks different than you left it, you see who changed it and when.
the team panel
Who is on the team and who is allowed where, on one screen
The panel opens in the browser, on your own server. From here you add clients, invite people, grant and revoke access. No terminal, no commands to learn.
Clients
| Slug | Name |
|---|---|
| agency | The agency (shared workspace) |
Members
| Role | Status | Client access | |
|---|---|---|---|
| adrian@agency.com | owner | active | agency (write)revoke |
| maria@agency.com | admin | active | agency (write)revoke |
| radu@agency.com | member | active | agency (write)revoke |
| ioana@agency.com | member | active | agency (read)revoke |
Document editor
Edit a client's brand and shared documents straight from the browser. Only the clients you have access to show up, and you can write only with write access. If a colleague saved in the meantime, you are warned before you cover their work.
| File | Version | Last save | Author |
|---|---|---|---|
| brand/voice.md | v7 | today, 11:24 | maria@agency.com |
| context/learnings.md | v23 | yesterday, 18:02 | radu@agency.com |
The real panel, with a four-person agency on the shared workspace.
the best news
Deletions stop being scary
The fear of working together is called "someone deleted something and I no longer know what it was". The panel has a screen just for that.
Deleted files
What was deleted and can still be brought back. Restoring writes the old content as a new version, so it does not rewrite history and even a wrong restore can be undone. The recovery window is 30 days.
| File | Deleted at | Versions | |
|---|---|---|---|
| brand/tone-of-voice.md | 29 Jul, 14:12 | 6 | Bring it back |
| context/notes/client-preferences.md | 28 Jul, 09:41 | 3 | Bring it back |
| projects/standard-offer/offer.md | 26 Jul, 16:55 | 11 | Bring it back |
Nothing vanishes quietly
Every deleted file stays on the list, with the date and how many versions are left behind it. One button brings it back.
Restoring breaks nothing either
When you bring a file back, the old content is written as a new version. What was there before stays in the history, so you can go back from there too.
Deletions reach everyone
When you delete and confirm, your colleagues are not left with a ghost copy that reappears at the next sync.
Who and when, on the record
Every deletion and every restore goes into the log with author and timestamp. "Who deleted this" has an answer.
the boundary
What goes to the team and what stays with you
Goes to the team
- ✓Shared client folders: brand voice, notes, working memory, deliverables
- ✓The rules learned on that client
- ✓The project files you work on together
Stays with you
- -Everything outside the shared clients, personal projects included
- -Your own keys and tool accounts, which stay on your laptop
- -Your personality and your way of working
setup
Three steps, and the first one is on me
Before the steps, here is what it looks like in practice: the team panel, creating a client, inviting a colleague, then working on a shared client from Claude Code. A real, unedited recording.
7 minutes 46. Feel free to skip ahead.
A tailored setup on your agency server
I set it up myself, security certificate included, right next to whatever you already run there. You touch nothing technical. If you have no server, I keep it on mine.
Connecting everyone on the team
One command on each operator's laptop, following the step-by-step instructions in the guide. Their robOS stays exactly as it was, with everything already in it.
Access per client, granted by you
From the web panel: add members, send invitations, give read or write rights on each client. This part stays your day-to-day work.
the model that works
Treat the agency itself as a shared client
The simplest way to run Team: alongside the real clients, create a workspace for the agency. Each person keeps their private space for personal work. When they work for the company, they switch to the agency workspace and start from the same voice, the same rules and the same history as everyone else.
The team rule that makes the difference, and it is easy to remember: "I am working for the company" means "I have switched to the company workspace".
honesty
What robOS Team does NOT do
- xIt does NOT replace robOS.Every operator still needs robOS on their laptop. Team sits on top and connects them.
- xIt does NOT pool your tool accounts.Everyone's keys stay their own. For an account used in common, buy seats in that application.
- xIt does NOT wipe what a colleague already pulled.Revoking access cuts new access immediately and leaves a record. What they already downloaded stays on their machine, same as with any tool that works on files.
- xIt is NOT a service you simply subscribe to.Activation is paid once, not monthly. The server is yours, so its upkeep is too. I can run it for you for a monthly fee, if you prefer that.
what it costs
One price per team, not per head
Two people or twelve, activation costs the same. Every person on the team needs their own robOS licence.
Activation and setup
199 USD
one-time
- ✓Team rights on your email address
- ✓I set it up on your server myself
- ✓The first client and the first people, configured together
- ✓Any number of people on the team
The server is yours, at the provider you choose. You touch nothing technical.
Buy nowNo server? I keep it for you, at 50 USD a month. Running, updated and backed up, and you administer nothing. Even then, the files still live on your laptops: the server only keeps them together. Tell me when you buy and I take care of it.
Your robOS keeps working exactly as it does today. Team replaces nothing and asks you to reinstall nothing. It sits on top and adds working as a team on the same clients. If you drop Team tomorrow, everyone's robOS stays whole, with everything in it.
After payment, on the email address you bought with a new tab called Team opens in your download area: the server program and the web panel. Access is switched on within 24 hours of payment.
questions
What people ask me
Do we have to be a technical team?
Where does the data live?
What exactly gets synced?
How many people does it take to be worth it?
Does it work with the robOS I already have?
How much does it cost?
Still have questions?
Message me on WhatsAppLooking for robOS just for yourself? The base product page
Want it working while you sleep? robOS AlwaysOn