Repository navigation
EN Getting Started
한국어 | English
This page condenses the repository quickstart into a Wiki-oriented workflow.
- Node.js 24.0.0 or later
- Plugin support in Codex or Claude Code
- For multi-session collaboration, access to the same shared AGS state location
Always use the repository README as the authoritative source for the latest installation commands and current release version.
Run inside Claude Code:
/plugin marketplace add jaeseongs95/agent-governance-suite
/plugin install agent-governance-suite@agent-governance-claude
Start a new session after installation.
Use the installation commands from the current repository README.
After installation, start a new Codex session. Review and trust the installed hooks through /hooks if you want context continuity, the session board, and host execution observation to operate.
You can begin with a normal request that makes scope and completion explicit.
For example:
Implement and verify this feature.
First define the change scope and completion criteria.
In the final result, include the checks you actually ran
and any unresolved issues that remain.
Installed specialist skills can then be selected according to the task conditions.
To verify the session board and PEER messaging without changing code, open two sessions on the same project.
For this demo, you are the reviewer.
Record your current work on the AGS session board as:
"AGS-DEMO-REVIEW · Review test execution instructions"
When the research session sends a PEER message,
open the referenced files and verify whether its explanation is correct.
Acknowledge the message, then send the actual review result
back in a separate PEER message.
Do not modify files or run tests.
Record your current work on the AGS session board as:
"AGS-DEMO-RESEARCH · Investigate test execution instructions"
Find the project's documented test command and supporting file locations.
Do not modify files or run tests.
Find the session responsible for "AGS-DEMO-REVIEW"
on the session board and send the research result through a PEER message.
Keep the acknowledgement state separate from the actual review result.
The expected sequence is:
Research
↓
PEER message sent
↓
Reviewer receives message
↓
ACK
↓
Reviewer inspects evidence
↓
Reviewer sends result
↓
Research session compares and concludes
The key point is that ACK and task completion are different events.
A queued message and an automatically resumed session are separate states.
Host-specific wake support may require additional configuration, such as Codex queue wake.
See:
If participating hosts resolve different default state paths, configure the same absolute AGENT_GOVERNANCE_SHARED_STATE_DIR for each host.
Matching path strings are not sufficient by themselves. Every participating runtime must be able to read and write that location.