Wiele keeps your work folders in the cloud with every version saved, so your team, your AI tools and you work on the same files. Files stay ordinary files. You download a folder or a single file, edit it with any app or agent, and push the change back. Each push records the whole set of changed files as one revision you can inspect or undo.
You use Wiele in three ways:
- The
wielecommand line, on macOS and Linux. Agents that can run terminal commands, such as Claude Code, Codex and Cursor, use it too. - The MCP server at
https://api.wiele.io/mcp, for AI clients that call remote tools. - The web app at app.wiele.io, to sign up, browse files and manage your organization.
New here? The quickstart gets a first folder into Wiele in a few minutes. The 1.0 launch post covers what's in this release and who it's for.
Core ideas
Organization
The team account. It holds members, workspaces and the subscription. Members have an organization role: owner, admin or member. Owners and admins manage members, billing and retention. One person can belong to several organizations.
Workspace
A versioned tree of files inside an organization, such as client-work or my-notes. Every workspace has its own history. You write paths inside it as WORKSPACE:/path, for example client-work:/acme/budget.xlsx.
Folders and files
A workspace holds folders and files like a disk. Any file type works, up to 10 GB per file. You can share a whole workspace, one folder or one file.
Checkout
A local folder linked to one remote folder or file on one branch. wiele fetch downloads a new checkout. wiele track connects a folder you already have. In a checkout you work with normal tools, then run wiele status, wiele diff, wiele push and wiele pull. Wiele keeps its own state in a hidden .wiele folder. Checkouts download only the files under their folder, not the whole workspace or its history.
Revision
Each push that changes something creates a revision: an immutable state of the whole workspace, named by a 40-character SHA. A revision records every file changed in that push together, with a message. History lists the revisions; wiele restore brings back a file as it was in any of them.
Copy and merge
A copy, also called a branch, is a separate line of work in a workspace. main is the copy everyone shares. Make a copy to try something, such as an agent's rewrite of a proposal, without touching main. When it's ready, compare it with main and merge it. If someone changed the same file on main meanwhile, Wiele shows the conflict and you choose which version to keep. A copy doesn't duplicate file bytes. See Conflicts and merging.
Retention
Wiele keeps every version of every file until you decide otherwise. Storage counts every kept version. Owners and admins can keep only the last N versions, or the last N days, per organization, workspace, folder or file, and prune old versions on demand. Current files are never removed. See Versions, history and retention.
Access
Organization membership alone gives no access to files. Access comes from the workspace's visibility (public to members, or private) and from grants. A grant gives one person read, write or admin on a workspace, folder or file; folder grants cover everything below. Readers can still make their own copies and propose changes; only writers can change main. See Sharing and access.
How a change flows
wiele fetch client-work:/acme ./acme # download one folder
cd acme
# edit files with any app or agent
wiele status # what changed
wiele push -m "Update budget" # one revision with every change
Someone else's checkout gets the change with wiele pull, or automatically with background sync.
What Wiele doesn't do
- No Windows client yet. The CLI runs on macOS and Linux.
- No mounted drive. Wiele syncs ordinary folders; it doesn't stream files on demand.
- No real-time co-editing inside a document. Two people editing the same file produce a conflict to resolve.
- No server-side content search for now. Agents fetch a folder and search it locally.
- No OAuth sign-in for MCP yet, so claude.ai and ChatGPT connectors can't connect.