Local-first software

#How local-first software works

The device holds the working copy. Edits happen locally first, with no round trip to a server, and changes sync later when a connection is available. The essay lists seven ideals: fast response, use on several devices, offline work, collaboration, longevity, privacy and user control.

#Why it matters for AI agents

An agent that runs on your computer can act with the data and sessions that already live there. Local-first design keeps your data and credentials with you, not with a service that holds a copy. Check each tool's design anyway, because local-first is a choice a product makes, not a guarantee.

#Wield and local-first software

Wield applies the same idea to browsing. Passwords and cookies never leave your computer. Wield never reads, copies or sends them. Recipes run in your own browser through the Wield extension, and results go from the extension to wield-mcp to your AI app. They never pass through wield.run.

Wield does not meet all seven ideals. The public recipe registry is online, so the local-first part covers your data and credentials, not the whole system.

#Related terms

• Native messaging
• Audit log
• Cookies and sessions

#FAQ

#Is local-first the same as offline-first?

No. An offline-first app works without a connection. A local-first app also keeps the primary copy of its data on the device, and the server is secondary. An offline-first app can still keep its main data on a server.

#Is Wield local-first?

Partly. Your passwords, cookies and browsing results stay on your computer, and results never pass through wield.run. The recipe registry is online, and Wield makes no claim to meet every local-first ideal.