I do not want an agent workspace that becomes useless when the vendor disappears, the network drops, or the team changes models. If a folder becomes a cloud-only record, both people and agents lose the speed, resilience, and tool compatibility of local files.

That is why Folderbase starts local-first. The ordinary folder remains primary on each authorized device; synchronization and hosted services arrive as explicit capabilities rather than prerequisites for meaning.

Local files are the broadest interoperability layer

Every mature workflow already has file-native tools: editors, terminals, IDEs, office applications, media tools, Git, databases, backup systems, and operating-system search. An agent can use many of the same tools without a custom integration for every format.

Keeping files local means the workspace remains useful when a service is unavailable, an account changes, or a different agent framework is adopted.

Local-first does not mean local-only

Useful collaboration still requires identity, synchronization, sharing, history, recovery, and web access. The difference is that cloud activation is explicit and the local format does not depend on the managed service for meaning.

A Folderbase can synchronize content-addressed objects and immutable manifests while preserving a normal materialized folder. Remote services add convenience without becoming the only place the work can exist.

Offline work needs a real reconciliation model

Two devices can edit the same workspace while disconnected. A safe system must preserve competing heads, verify bytes, resume interrupted transfers, and make conflicts explainable. Last-write-wins is not enough for important human and agent work.

Local journals and immutable versions provide the evidence needed to reconcile. Clean-device recovery then becomes a testable property: restore the authorized workspace byte for byte, not merely a best-effort list of recent files.

Remote agents should receive scoped materialization

A cloud agent does not need a permanent copy of every connected folder. It needs a temporary workspace pinned to a known version and authorized scope. Exact-scope transfer tickets can materialize the required bytes without exposing storage credentials.

When the task ends, the agent returns a Change Set or merge proposal. The durable source remains the Folderbase, not the ephemeral machine.