Office
The work on your Mac, in your pocket.
Every Claude and Codex session running on your machine, in one list. See what is still working, what has stopped and is waiting on you, and answer it without going back to the desk.
It stopped an hour ago and you were not at the desk
An agent works for twenty minutes, reaches a question only you can answer, and waits. If you have stepped out it waits all afternoon. Nothing is broken and the work was nearly done, but nothing is moving either.
Knowing is the other half of it. Sessions end up spread across terminal windows, more than one login, and two different tools, and there is no single place that says what is still going and what has quietly stopped.
Everything your machine is doing, on one screen.
The list groups itself by what needs you first. Tap a session to read it as a conversation, and reply to it from where you are standing.
Everything running on your Mac, in one place.
One list, however many logins
It reads the machine rather than an account, so sessions signed in under different logins sit in the same list. Claude and Codex both appear, each labelled, newest first.
See what is waiting on you
Anything stopped and waiting for an answer is grouped at the top, with the question it is stuck on. What is still working carries on below it.
Answer it from your phone
Type a reply and it lands in the running session on your Mac, exactly as if you had typed it at the keyboard. The work picks up where it left off.
Reads like a conversation
Not terminal output. Files, changes, commands and images are each shown as what they are, so you can follow what happened on a phone screen.
Keep the important ones to hand
Pin the two or three you keep coming back to, or file sessions onto named shelves you can rename. Both stay put between visits.
Nothing passes through us
Your phone talks to your Mac directly over your own private network. The sessions, the code and the conversations never reach our servers.
It reads the machine, not the account.
Most tools show you the sessions belonging to the login you are signed into. That is the wrong unit when you switch logins during the day, or run two tools side by side. The machine is the one place where all of it exists at once.
Grouped by what needs you
Waiting first, then working, then everything earlier. The order answers the only question you have when you pick up your phone.
Filtered when the list is long
Narrow to what is waiting, what is still open, what has stopped, or one tool at a time. A filter with nothing behind it is not offered.
Named by what it is doing
Each session carries a plain-English title and the branch it is working on, so two sessions in the same project are still telling you apart.
Unblock it without going back to the desk.
A session waiting on a one-line answer is the most expensive kind of idle, because everything before it is already done. Answering from your phone turns an afternoon of waiting into a few seconds.
It lands in the real session
Your reply goes into the session already running on your Mac, keeping everything it has already worked out. Nothing restarts.
Honest about what it cannot do
A session started before Office was set up has nothing listening for a reply. It says so and hides the box, rather than letting you type into nothing.
Nothing typed is silently lost
Anything you sent while a session was busy is shown back to you, so an instruction that was never picked up cannot quietly disappear.
Your machine, your network.
Office is not a service that holds your work. It is a small program on your own Mac that your own phone can reach, and nothing about it is hosted by us.
Listens only to itself
The program accepts connections from your own machine and nowhere else. It is not reachable from the internet at any point.
Reached over your private network
Your phone and your Mac join the same private network, encrypted end to end, with a real certificate. Only your own devices can route to it.
One key, held by you
An access key is generated on your machine and pasted once into your phone. We never see it, and we never see a single session.
Three steps, once.
Put Tailscale on both
Install it on your Mac and your phone and sign in to the same account, then switch on HTTPS for your network. This is what lets the two talk privately without anything being exposed.
Run one command on your Mac
It sets everything up, starts the program when you log in, and prints an address and an access key.
Paste them into the app
Open Office on your phone, paste both, and your sessions appear. You never do this again.
Before you try it.
Who is this actually for?
People who run AI coding agents on a Mac. If you use Claude Code or Codex during the day, Office is the list of what they are all doing. If you do not, you can safely ignore it, and nothing else in Omniops depends on it.
Does my Mac need to be awake?
Yes. Office reads a machine that is running, so a sleeping or shut-down Mac has nothing to report. The app says it cannot reach your Mac rather than showing you a stale list as though it were live.
Can you see my code or my sessions?
No. Your phone connects straight to your own Mac over your own private network. The sessions never reach our servers, so there is nothing for us to see, store or lose.
What happens to sessions I started before setting this up?
They are still listed and still readable, but they cannot be replied to, because nothing was listening for input when they started. Starting them again makes them repliable.
Does it work on more than one Mac?
One at a time. The app points at one machine's address, and you can change which one in settings.
Office
Stop losing the afternoon to a session that is waiting.
Set it up once and the work on your Mac is with you wherever you are, including whatever is sitting there waiting on an answer.