A Pi seat can now have its own account home: an absolute PI_CODING_AGENT_DIR in its env: is used as one and needs an auth.json there. A Pi seat that already has its own login can stop at launch, so check those first. A community contribution.
A Pi seat that declares an absolute PI_CODING_AGENT_DIR in its env: now uses it as its account home and needs a readable auth.json there, or the launch stops. A Pi seat that already has its own Pi login also stops at launch when its spec declares an absolute PI_CODING_AGENT_DIR, even if that folder has an auth.json; the seat's login is kept, and the error names a missing account file rather than the existing login. This is shown by source and function-level tests, not a native run.
- Pull request
- #2630
- Contributed by
- @seanmcn
- Release
- OpenRig 0.7.11 release notes