Your data is not on your machine. It has not been for years. It lives in the cloud, on servers you will never see, under a document you clicked through without reading. You hold an account, and an account is a key to a room in someone else's building. That was the trade. You clicked I agree, and the bytes moved somewhere you cannot reach into and cannot walk out of with the originals.
We used to call sovereignty a wall around your data. Keep the bytes local, encrypt them, hold the only key. By the time anyone wrote that down, the wall was already gone. The data went up to the cloud one convenience at a time, one I-agree at a time, and the old worry, some reader breaking in, was beside the point. We handed the reader a key at signup.
So the data fight is mostly over, and it did not end well. Now the same machinery comes for the next thing.
The software reading your data stopped just reading. It acts, the way you would act. An agent reads your inbox and answers in your voice. It reads the feed you paid for and drafts the post you would have written. It watches a surface change and takes the next step before you ask.
And it runs where your data already went. On their servers, its memory in their store, under the same document you did not read. The bytes stopped sitting still. They got a hand, and the hand is being leased to you the same way the data was.
When an agent can act as you, the question is no longer where your data is kept. It is who that agent answers to when it acts in your name.
When an agent acts for you, the line between you and it goes soft. You run a process over the bytes that already arrived for you, on the surfaces you already use, at your own instruction. Is that you, or a third party?
The company that owns the platform gets to answer that, and it answers in its own favor. Your agent is the one who runs into this. Ask it to work your own LinkedIn feed and it hits the terms you clicked, the user agreement that treats automated access as a violation and can close your account for it. The agent read what you were licensed to read and did what you told it, inside your own session. That is your hand, moving faster, treated as a foreign robot at the gate. The word automation does the work of turning your extended reach into a violation, and the terms you already clicked give it teeth.
The fight is old, the front is new. The same argument was had over the VCR, the ad blocker, the screen reader, the spreadsheet macro. Each time, a tool that let a person do their own thing faster got recast as a threat by whoever preferred the person slow. The agent goes further than any of them, because it does not need you in the room. It can be your hand while you look away.
Three questions decide whether an agent is really yours.
Can you see what it did? An agent whose reasoning is hidden and whose memory lives on a server you do not control occupies your name like a tenant. You can be sovereign only over a hand you can watch move. The reasoning legible, the steps auditable, the memory yours to read.
Can you take it back? Data you cannot delete was never yours. An agency you cannot pause keeps acting after you have stopped agreeing with it. If the off-switch belongs to a vendor, the sovereignty is rented, and rent gets raised.
Does it answer to you alone? A hand that acts as you while it also serves whoever built it is only partly yours. Every model call that leaves your machine, every memory written to someone else's store, hands a second party a share of it. The maker's own goals, keeping you on its platform, steering you toward its products, learning from your data, ride along in what the agent does in your name. A passive tool doing that is a nuisance. Something that does it while acting as you turns your own choices into someone else's leverage.
Fail any one and someone else holds a piece of the hand. Pass all three and the agency is yours.
We gave away the data one I-agree at a time and barely felt it. Agency is next in the same queue, behind the same button, on the same servers. First it was what someone could read about you. Now it is what someone can do as you.
None of this is inevitable. Nothing about an agent requires the cloud, hidden reasoning, or an off-switch someone else holds. Those are business decisions dressed up as technical ones.
Picture the hand built the other way, an agent that passes all three tests by design. It runs on your own machine, so the work happens where you are and your data stays put. Every step it takes is written down where you can read it, so you can check what it did in your name. Its memory sits in a store you own and can open, edit, or wipe. Its off-switch is a key in your hand, so stopping it is your call, made the moment you want to make it. It answers to you alone, because you are the only one in the loop.
The parts for this are on the table today. Capable models run on a laptop. The compute is already on your desk. The storage is already yours. Most agents get built to harvest you instead, because harvesting pays, more data, more lock-in, more of your attention flowing back to the maker. Building an agent that is wholly yours is possible right now. It is a choice, and the choice is still open.
The moment an agent can act as you, someone owns that agency. You can decide that it is you, or you can click I agree and let someone else decide.
Whose hand is on the keyboard?
Port42 runs on your Mac. Your companions act as you with their reasoning in the open and the off-switch in your hand.