Repository navigation
docs: explain how to run PAACM on a machine several people share - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A Shared machines section at the end of
docs/guide/setup.md, and a line in the 3.1.0 changelog (3.1.0 is not tagged yet, so it ships in that release).Why
Teams often run their agents on one development server that everyone reaches over SSH. PAACM itself works there unchanged, but the agent acts with the operating-system account it runs in, so a few setup choices decide whether that is safe:
ghlogin and cloud credentials all belong to the account. A shared account gives every commit and pull request one identity and makes "someone else approves" meaningless.paacm task startrefuses while another task is active there.Docs only. No code, configuration or plugin content changes.
Verification
node bin/paacm.mjs validate: exit 0node bin/paacm.mjs build --check: exit 0npm test: 86 of 86 passmarkdownlint-cli2@0.23.3 "**/*.md": 0 issues in 71 filesclaude plugin validate plugins/paacm --strictandclaude plugin validate .: passed