Save, publish, and restore agents
Choose whether a package stays on your computer, is stored privately for your account, or is submitted to the public Hub. Each choice has its own result to check.
1. Choose a destination
2. Save a private copy
- After a Desktop build, select Upload to Cloud, or open Agent Forge → Upload agents and select your registered agent or package folder.
- Choose the private Agent Cloud action. Review the package and any reported problem; keep credentials in the host's key or connection settings.
- Wait for the save result and open View in Agent Cloud when offered. Verify the package appears in your account.
Private storage is limited by your plan's agent capacity. It does not require the public routing card. If another computer has changed the Cloud copy, restore the latest version and review the differences before saving again.
3. Publish to the Hub
- Use the separate Hub (public) action. Check the name, description, licence, and the files intended for public distribution.
- Review the source-access choice. When you permit it, eligible readable files in the public package can be viewed in Agent Space.
- Resolve publication requirements reported by the app, including missing routing information. Review warnings before continuing.
- Check the returned publication state and open the Hub page when offered. A submitted candidate and a publicly usable listing are different states; confirm what the page actually shows.
Publish only a package you own and have permission to distribute. An installed copy obtained from somebody else is not automatically eligible for publication. Do not include credentials or private working documents. Publishing uses a public distribution copy; the original local build folder remains separate. Hub use follows the package's licence and the selected model provider's terms.
4. Restore on another host
- Sign in with the owning account on the destination Desktop or Terminal and select the private Cloud package.
- Restore and install the package, then check the local agent list. Complete model and tool connections on that computer.
- Run a small test with an input you can verify. For phone access, pair the phone with the Desktop that will execute the work.
Agent Cloud stores files, not a hosted LLM or an execution computer. The Web repository's Files view lets you inspect package files. Full package ZIP export belongs to Cloud packages you own; a Hub listing offers eligible individual text files only where its author permits source access.