Cloud

Login required

CLOUD COMPONENT SHARING:

Cloud (previously called Hub) is a GitHub-like cloud storage for TD components and networks. Upload your OPs, patches and templates once — access them from any machine at any time. Supports file versioning and optional automatic collection of external assets (movies, images, etc.). Requires a twozero.ai account.

NAVIGATION:

Cloud has three levels — navigate with [ENTER]/[→]/[←]: repos — list of your repos (folders). Entry point. files — components inside a repo. [ENTER] or [→] on a repo to open. versions — version history of a file. [→] on a file to open. [←] goes back one level.

OPEN BY LINK:

Paste a twozero.ai link in the input field — works from any tool, not just Cloud. twozero detects the link, switches to Cloud and resolves it. Patterns: https://twozero.ai/hub/repo_<id> opens that repo; /hub/file_<id> opens the file; /hub/ver_<id> opens that specific version. Rudiment links (twozero.ai/hub/product_<slug>) resolve through Cloud too — that is what GET LINK copies on a rudiment page. Inside Cloud, bare IDs (repo_<id>, file_<id>, ver_<id>, product_<slug>) work.

FIRST TIME SETUP:

Open Cloud — a login dialog will appear automatically. Use Continue in browser for the device-code flow, or enter your twozero.ai email → receive a 6-digit code → enter it → done. The user chip shows account state and balance after login.

CREATE A REPO (FOLDER):

Files can only be uploaded inside a repo — create one first. Type '/new_repo $reponame' → [ENTER].

UPLOAD:

1. Open a repo ([ENTER] on it).
2. Select OP(s) in Network Editor.
3. Type '+name'.
4. [ENTER] → packages and uploads. Cloud captures a preview image, packages the .tox, and asks whether to collect external assets.

During upload the progress indicator stops short of full completion until cloud storage confirms the file. Finalizing upload... means the local file has been sent and Cloud is waiting for the storage acknowledgement; after that Cloud confirms the upload, refreshes the list, and returns to the upload location.

While a transfer is running the dialog offers two answers: Ok sends it to the background and gives the tool back to you, Cancel actually aborts the transfer. This works for uploads and downloads alike.

STORAGE LIMIT:

Free accounts get 100 MB of Cloud storage, PRO accounts get 10 GB. The figure counts the components you uploaded, all of their versions together; generated images and videos live in a separate archive and do not count against it.

You are warned at 80% of the limit. At 100% Cloud goes read-only: everything already there stays available and can be downloaded, but new uploads and new versions are refused with a message saying so. Deleting a component frees the space back.

DOWNLOAD:

1. Open a repo, select a file.
2. [ENTER] or LMB → downloads and places the latest version into the current network.

To download a specific version: open versions ([→] on file) → [ENTER] on the version.

VERSION HISTORY:

Every upload creates a new version of the file. All versions are kept. [→] on a file → opens the versions list (date, size, uploader, description). [ENTER] on a version → downloads that specific version. [CMD/CTRL]+[Delete/Backspace] → delete selected version only. In files scope → [CMD/CTRL]+[Delete/Backspace] → delete file and all its versions.

RMB CONTEXT MENU:

Right-click on any item opens a context menu. Available actions depend on what you click:

Every row that carries an id also offers Get id — copies the repo / file / version id to the clipboard. Handy when you want to hand a component to an AI agent (MCP).

SHARING & ACCESS:

Sharing is done via RMB → Share to... on a repo or file. In the dialog, pick a user and a permission level — repos support read / write / root. Shared repos appear in the other user's repos list after they accept the invite from notifications. For public access, RMB → Make public; then RMB → Get public link copies the URL anyone can open.

NOTIFICATIONS:

Incoming shares, transfers, and other Cloud events show up under /notifications. A badge on the Cloud icon shows the unread count. Open via the icon, or type /notifications inside Cloud. RMB on each item to Add to my Cloud, Download, Decline, or Delete.

OTHER COMMANDS (type / to see all):

/new_repo $name — create a new repo. /latest_repos — all repos sorted by recent activity. /latest_files — all files sorted by recent activity. /notifications — incoming shares/transfers (see above). /logout — sign out and clear the local Cloud/user cache.

NOTES:

External assets (movie files, images, etc.) are optionally collected and bundled with the component. VST plugins are handled separately and relinked on load. When a downloaded component would collide with operators already in your network, it is renamed automatically — and the references inside the downloaded set are rewritten to match, so expressions and parameter links keep working.

An AI agent connected over MCP can use the same Cloud: list repos and files, download a component and place it into the current network.