Where your team's knowledge lives
A team starts with knowledge stored separately on each member's machine. Enable hosting to give everyone's agents access to a shared store. Team includes hosting by toryo; Enterprise also supports your own servers.
Start on your team's machines#
A new team starts here, with nothing to set up. What a member's agents learn about a team project, its memories and documents, is kept on that member's own machine, and their agents read it from there.
Until hosting is enabled, members do not share saved project knowledge.
Choose where it lives#
| Option | Plan | Where it is kept |
|---|---|---|
| On your team’s machines | Team, Enterprise | On each member's own machine, read only by that member's agents |
| Hosted by toryo | Team, Enterprise | On toryo's hosted service, shared by the whole team |
| Self-hosted | Enterprise | On your own servers, shared by the whole team |
To switch, an owner opens the team's Hosting card in the portal:
- On the Team plan, the two options are listed side by side. Choose one.
- On the Enterprise plan, choose Remote first, then which remote option. Hosted by toryo is selected for you; choose Self-hosted to use your own servers instead.
Then choose Save hosting. Each teammate's machine follows at its next
license refresh. A teammate who runs toryo license refresh picks it up at
once.
Self-hosting needs a server you run first. See Self-host your team's knowledge.
Moving to hosting#
When a team enables hosting, by toryo or on your own servers, what its members already saved moves with it.
Each member's machine moves the memories and documents it holds about each team project to the service, and deletes its local copy of each once the service has confirmed it. Local run history stays linked to the team projects.
An owner or admin must create each project on the service before a member's knowledge can move into it. Their machine does this automatically for projects it holds. Other members' moves wait until the project exists.
Some things do not move:
- Your own global knowledge stays on your machine. It never becomes the team's.
- Documents saved to the team as a whole, not to one project, stay on the member's machine.
- How often each memory has been used is not carried over.
- A project with no git remote becomes the member's own project, on their machine.
- The code index is not copied. The team's shared refresh builds it again from the repository.
What a member sees#
Members have nothing to run. Until their part has moved, their agents keep reading the team's knowledge from their own machine, so nothing goes missing while the move runs.
The move starts at their next license refresh, and an hourly job retries it
until it finishes. While it runs, toryo license status shows
moving from all-local: held since …. Near the end it shows
moving from all-local: routed, a last pass removes the hold. When it is
stuck, it shows moving from all-local: waiting: <reason> with the reason.
Board does not show the move.
What stays on each machine#
Embeddings are computed on each member's machine, wherever the team's knowledge lives. No model runs on the hosted service, and none runs on a self-hosted server.
Enabling team hosting does not move your personal projects or global knowledge.
Other hosting changes#
Switching back to members' machines, or between hosted services, does not transfer existing knowledge. The destination will not automatically contain what you saved on the previous service. See Known limitations.