Team projects
A team project is one your whole team works on. Each teammate works in their own checkout. Once your team enables hosting, what anyone's agents learn about the project is there for everyone.
What a team project is#
A team project is known by its repository and the folder within it. So every teammate's clone of that repository lands on the same team project, wherever it sits on their disk.
Some projects always stay yours. A project with no git remote stays on your machine. So does a parent project that groups other projects.
What a teammate's agents save about a team project, their memories and library documents, belongs to the team. Until your team enables hosting, it is kept on the machine that saved it, and members do not share saved project knowledge. Once hosting is enabled, it is kept in one place, and every member's agents read it. See Where your team's knowledge lives. Your global knowledge stays your own.
Work in a connected checkout as you always do. toryo commands and agent sessions started there use your team's project and its knowledge. There is no extra flag to pass.
Share a project with your team#
You need a seat on a team. See Joining a team. A trial or personal license has no team to share into.
The project needs a git remote. It cannot have child projects.
In board, open Projects while it shows your own projects. On the project's row, choose Make team project. If your team already has that repository, the row offers Sync to team instead. The panel counts what will move before anything is written. Confirm to share.
From a terminal, name your team the way toryo license list prints it:
toryo project share web --to <team>
Add --dry-run to see what would move without moving anything. Add
--slug <slug> when your team already uses the project's short name.
- What moves: the project's memories, documents and run history.
- What stays: your global knowledge.
- What is rebuilt: the code index. Your team's shared refresh builds it again.
Any member can sync their copy into a team project that already exists. Only an owner or admin can make a new one.
If a share stops part-way, run it again. The second run finishes the job.
Join a project a teammate shared#
Clone the repository as usual.
In board, switch to your team's projects. The badge beside the Projects heading shows your team's name, or Personal when you are looking at your own. A team project with no checkout on this machine shows Not bound here. Click it, enter the checkout folder, and press Bind. Board checks that the folder's origin is the project's repository.
From a terminal, run this inside the checkout:
toryo project bind --auto --root "$PWD"
It connects every team project that lives in that repository. A project that is already connected is left as it is. If it cannot decide for a project, for example because another project already uses that folder, it connects nothing for that project and says why.
Then work there as usual. What your agents save there is your team's.
Who can change a shared project#
| Role | What they can do with a team project |
|---|---|
| Owner | Make a project a team project. Change its name and settings: verification, install command, sensitive paths. Remove it. |
| Admin | The same as an owner. |
| Member | See the team's projects. Connect a checkout. Save knowledge. Sync their own copy into an existing team project. Read settings. |
An admin differs from an owner only outside projects. An admin manages people, never billing. See What a seat covers.
A role change reaches your machine at its next check-in. Run
toryo license refresh to pick it up at once.
Sharing is one way#
There is no command to turn a team project back into one of your own. What moved belongs to the team. Your global knowledge never moves.
When a shared project is removed#
Only an owner or admin removes a team project. Do it from board's Projects
screen or with toryo project remove <project>.
It disappears from every teammate's list at once. Each machine lets go of its
checkout the next time that checkout is connected, by bind --auto or board's
Bind.
Its knowledge is kept for 30 days, so a teammate who was offline can see that it was removed. Then it is deleted.
The same repository can be shared again straight away.
Removing one of your own projects is different. It deletes the project at once. Lasting memories and documents about it move to your global knowledge, and the rest is cleaned up. See Removing a project.
Full command surface: CLI & contract reference.