Your team, thoughtfully built.

Running AI Agents on Your Computer: What Stays Local

Practical guides from the Staffmor team.

In an installed Staffmor office, working files and local records live on your computer. That is a storage choice, not a promise that nothing leaves it. Your AI provider receives the prompts and file contents you send. If you use an enabled remote connection, selected office content and commands can also pass through and be stored by Staffmor's relay. New installs start local-only; an existing office keeps its selected mode. See the current privacy policy for the hosted data flow, and why running AI agents on your computer is safe.

What stays on your computer

  • Your office. In Staffmor, the team workspace (channels, tasks, decisions and the Needs-you home) runs on your computer and saves to your office folder.
  • Your project files. Agents work on files in that folder. Your AI provider receives the files they read, as the next section explains.
  • Your tools' session history. Claude Code, for example, keeps session transcripts on your machine so you can resume them (Anthropic).

What goes to your AI provider

To answer, a model has to see the work. According to their own documentation:

  • Claude Code sends "all user prompts and model outputs" to Anthropic, encrypted in transit. Anthropic doesn't train on code or prompts from commercial accounts (Team, Enterprise, API) by default. On Free, Pro and Max, you choose whether your data can be used to improve models (Anthropic).
  • Codex sends your prompts and conversation context to OpenAI to run the model. Its sandbox and approval rules run on your machine (OpenAI).

"Prompts" include whatever the agent reads to do the task, so an agent that opens a file is sending that file's contents to the model. Keep secrets out of files your agents work on, and check your account's data settings.

What the agents are allowed to do

Both tools have their own guardrails, and running locally doesn't remove them:

Tool and modeWhat to check
Claude Code Manual modeStarts read-only. File edits and commands require approval unless you have allowed them. File-tool access outside the starting folder prompts; approved Bash commands can reach further unless sandboxed.
Claude Code other modesAutomatic approvals and restrictions vary by mode and organization settings. Check the permissions and sandbox in the session you use.
Codex local workspace-write sandboxLimits writes to the workspace and keeps command network access off unless enabled. Your configured mode, approvals and managed settings can change those boundaries.

Sources: Claude Code security, Codex approvals & security. Settings and permission modes can change these defaults, so check yours.

Setup does not replace the permission settings of your AI app. You open your assistant in your office folder yourself, and its usual permission prompts and sandbox apply. That also means Staffmor can't restrict a tool you start with full access, so choose permission modes deliberately.

What uses a hosted service

A few things can't happen only on your computer:

ServiceWhat it handles
Purchase and billingPayment and subscription records through the payment provider and Staffmor's account services.
Saved setup and activationChoices you submit to an enabled save flow, plus office and licensing identifiers.
Paired web office and remote relay, when enabledSelected state, messages, commands and replies for your connected device. The current relay uses HTTPS and can retain this content; it is not end-to-end encrypted.

The hosted web office serves an existing paired connection; it does not make a local-only office remotely accessible by itself. Local backups and deletion remain separate from hosted retention and provider records. Read the current policy and retention limits.

Economical by design

A model call costs time and money, so the routine parts of Staffmor don't use one. The local app handles seats, navigation and saved records in ordinary code. Asking your assistant to set up or work still uses its model allowance. Your provider's own pricing and limits apply.

Before you hand an agent a file

Three questions settle most of it. Which session is doing the work? Which folder can it read? Where does the result go?

A made-up example: you want a summary built from a public workshop policy and one private planning note. The policy can be quoted in public copy. The note cannot. Neither your customer list nor the rest of your Documents folder is needed.

The request: "Before you summarize, list the two files you need and where the result will go. Use only this folder. Keep the private note out of anything marked for public use. Do not connect another service, grant permissions or read other folders."

A good answer names the two files, says where the summary will be saved, and marks which passages are safe to use publicly. It does not read the whole project to be thorough. If your assistant can't open the folder you chose, that is the point to stop and fix access in its own settings. A summary written without reading the file is worse than no summary.

Delegating safely: a short checklist

  1. Give agents a folder for the work, not your whole computer.
  2. Keep passwords and keys out of that folder and out of chat.
  3. Let routine, reversible work run. Approve anything public, paid or destructive yourself.
  4. Treat anything an agent reads from the web as information, not instructions.
  5. Review your AI accounts' data settings once.

Your office. On your computer. Under your control.

Set up Claude Code or Codex with an empty folder. Staffmor prepares the office after your approvals. Your office keeps its records on your computer, your AI provider receives the requests and files your agents read, and you choose what goes in the folder. Membership is available now, with your own Claude Code or Codex account. Set up your office → · See the plans →

Your own AI account does the work, and nothing installs or connects until you approve it.

Staffmor Tasks in an example studio: open tasks as cards, each with its progress from assigned to done, and the question waiting on you first.
Example office. Each job keeps its owner, progress and questions together.