osFoundry / Platform
Folders
A hierarchy of notes, files and KBs. Permissions cascade. Local + cloud per folder.
What it is
Folders is the organizing layer for everything your AI works with inside osFoundry: notes you write, files you drop in, and knowledge bases (KBs) your agents search. Instead of scattering context across separate tools, you arrange it as a tree — nest a folder inside a folder, group a project's reference docs next to its notes and its indexed KB, and keep the whole structure in one place alongside your chats, agents, code, and data.
Permissions cascade down the hierarchy. Set access on a parent folder and its children inherit it, so you grant a teammate or an agent reach into a branch of the tree once rather than reauthorizing every item underneath. That makes a folder a natural boundary for what a given agent or person can read — a useful control when the same workspace holds both shared reference material and private working notes.
Storage is decided per folder, not globally. A folder can live entirely local on your device — the local-first default that keeps sensitive material off any server — or it can sync to the cloud when you want it reachable elsewhere or shared. Because osFoundry is bring-your-own-key and desktop-first, choosing local for a folder means that content, and the context your agents pull from it, never has to leave your machine. You mix both in the same tree: a local folder of confidential drafts beside a cloud folder of team docs.
Key capabilities
- Arrange notes, files, and knowledge bases as a nested folder tree, with folders inside folders
- Permissions set on a parent folder cascade to every child, so you grant access to a whole branch at once
- Choose local or cloud storage per folder — keep sensitive material on-device, sync the rest
- Scope what agents and chats can read by pointing them at a folder rather than loose items
- Mix private local folders and shared cloud folders in the same hierarchy, one workspace
Use cases
- Solo researcher: keeps a local-only folder of confidential source files and personal notes, with a cloud folder of publishable write-ups beside it
- Small team lead: sets read access once on a shared project folder so everyone — and the project's agents — inherits reach into its docs and KBs
- Agent builder: points an assistant at one knowledge-base folder so it answers only from that branch of the tree, not the whole workspace
Frequently asked questions
Can a folder stay on my device instead of syncing to the cloud?
Yes. Storage is set per folder. A folder can remain entirely local on your device, or sync to the cloud when you need it available elsewhere or shared. You can keep local and cloud folders side by side in the same tree.
How do permissions work across nested folders?
Permissions cascade down the hierarchy. Access you set on a parent folder is inherited by its child folders and their contents, so you configure a branch once instead of item by item.
What can I actually put in a folder?
Notes you write, files you upload, and knowledge bases your agents can search — organized together in a hierarchy so a project's reference material, working notes, and indexed KB live in one place.