8rney Desk
The agent, runningon your own machine.
Point Desk at a folder of papers on your own machine. It reads them, drafts, and marks up in place, on the model you connect.
8rney Desk is the desktop application. A folder on your machine becomes the workspace, the agent works on the papers inside it, and tracked changes land in the real Word file. It exists for the work that cannot be uploaded: the bundle held under an undertaking, the data room copy, the matter your engagement letter says stays on your own infrastructure.
Everything the web application can do, Desk does against papers it never has to move.
Where the line actually sits.
Most tools ask you to accept a boundary you cannot see. This is the whole of it.
Stays on your machine
The papers, and everything done to them.
- The folder, and every file in it
- The agent engine and its working state
- Drafts, mark-ups, and the output it writes back
- The record of what it read and what it changed
Leaves, once
The text you put to the model you chose.
- The passage the question is about, and your instruction
- To Bedrock, Azure OpenAI, or your own provider endpoint
- Under your contract with that provider, not ours
- Nowhere else, and never to 8rney
What you get on the desktop
- A folder is the workspaceChoose a directory. The agent reads the papers inside it, works on them, and writes its output back to the same place. There is no import step and no second copy of the file.
- Word, Excel, PowerPointThe Office add-in puts 8rney inside the applications you already draft in. Tracked changes in the document itself, not a note about it.
- Your modelConnect AWS Bedrock, Azure OpenAI, or your own provider key. Privileged material reaches the model you chose and nothing else.
- Skills, commands, and MCPYou decide which tools it may use. Add the firm precedent bank as a skill, wire an internal system through MCP, and the same set follows every workspace.
- Remote workersWhen a job outgrows the laptop, connect a shared worker and move the run onto it. The same interface, more capacity.
- Computer useFor the practice management systems that have no API, Desk can drive the interface itself, under supervision.
Some papers cannot leave the building.
A great deal of legal work sits under an undertaking, a confidentiality club, or a client policy that makes uploading it the wrong answer whatever the tool is worth. Desk is the version of 8rney that does not ask you to make that trade.
- Local by defaultThe engine runs on your device. A remote worker is a decision you take, not the default.
- Your provider, your keysPrivileged material reaches the model you connected and nothing else. There is no second hop.
- In the documentThe mark-up is tracked changes in the original file, so the deliverable is the file you send.
- Yours to extendSkills, commands, and MCP connectors are configured by you and shared across workspaces.
Questions
About Desk
- Do my documents leave the machine?
- Only what the agent sends to the model you connected. The papers stay in the folder you chose, and Desk runs locally by default. If you attach a remote worker you are choosing to move that work elsewhere, and Desk tells you so.
- Which model does it use?
- The one you connect. Bedrock, Azure OpenAI, or another provider key. Free models are available to try the app, and those should not be used with privileged or client material because free-tier usage is logged.
- Does it work offline?
- The app runs locally, but the model it talks to needs a connection unless you are pointing it at something you host yourself.
- How does it relate to the web app?
- Same account, same agent, different ground. Open a matter on the web and continue it in Desk, or work entirely locally. Desk is the right answer when the papers cannot leave the building.
- What platforms are supported?
- macOS on Apple silicon and Intel, Windows, and Linux on x64 and arm64.
- Can I extend it?
- Yes. Skills, commands, and MCP connectors are managed in Settings and shared across every workspace, so a firm can standardise how its agent works.