Repository navigation
agy-crew v0.9.11
agy-crew 0.9.11 — every start uses the shared home
Background runs, account selection and cooldowns behave as in 0.9.10. This release changes agy-crew start again: the shared home from 0.9.10 is now where every interactive session runs.
What's new
start <name> runs in the shared home too. It used to run agy as that account in the account's own HOME, so its conversations were cut off from every other account's. Now <name> only chooses which account lends the credential; agy runs in ~/.agy-crew/shared/home either way, so /resume and agy --continue see the same conversations whichever account you pick. The accounts' own HOMEs are left to background runs, which need them to keep concurrent jobs apart.
start <name>checks the account as before: known, enabled, signed in, not in use. A cooldown for the model's family is printed as a note but does not refuse it.startwithout a name picks an idle account with quota for the family, as in 0.9.10.
Fixes
- A join no longer launches agy on a credential that cannot work. The shared home holds one credential at a time, so a
startwhile a shared session runs joins it. Before, astart --model <id>whose family had no quota on the running account joined anyway, printed a note and launched agy, which then failed on its first request. It is now refused before launching agy.start <name>naming a different account than the running session is refused the same way. The message gives the pids of the running sessions; exit every shared agy, then start again.start <name>naming the running account still joins, with a note if it is cooling.
Behaviour change
Conversations started with start <name> before this release live in that account's own HOME (~/.agy-crew/accounts/<name>/home), and /resume in the shared home does not list them.
Upgrading
npm install -g agy-crew@latest
agy-crew installRestart the harness. No migration is needed.