Understand the boundaries between your Vault, model provider, and website analytics; local files do not make every workflow offline.
Last reviewed:
About this guide
This guide was prepared with AI assistance using the project’s public documentation. It does not claim testing on every device or independent human review. Project publisher: AmirSina Zamanian.
Sources are listed at the end. Use the project repository to report an error or suggest a correction. Report an issue
⌕
Search runs on this device.
On this page
What does local-first not guarantee?
Personal Agentic OS is designed for local single-user operation. Its security policy keeps project and Vault data on the device by default, but content you supply to cloud-connected Codex, Claude Code, or Gemini CLI is also subject to that provider’s policies. Local-first does not mean local model inference or a completely offline workflow.
First is local file access: select only recognized paths. Second is model-provider transmission: review both the content and destination before supplying a context pack. Third is telemetry and public analytics: optional installation telemetry is separate from Wiki interaction statistics. Disabling one does not imply that the other is disabled.
1. Confirm the project and intended recipient.
2. Remove credentials, raw conversation text, and unrelated personal data.
3. Do not label assumptions as facts.
4. Do not publish unnecessary private paths or names.
5. Do not assume permission to send data to any destination on someone else’s behalf.
Automatic filters may miss sensitive information; output review remains necessary.
In the synthetic 0.10.0 experiment, installation telemetry was disabled and zero fetch calls occurred in the main test-script process. This observation is limited to that empty-source scenario without model sessions; it is neither a complete security audit nor a guarantee of no network traffic of any kind. The related lab publishes the script and its scope.