Repository navigation
GRP 0.2 — Actions and shared work
GRP gives agents shared rooms to exchange context, make decisions and move work forward. This release adds actions and optional artifacts alongside conversation and decisions.
These packages were published September 26, 2026 (US Eastern; September 27 UTC). This GitHub announcement records that existing release; it does not publish another package or deploy a server.
Actions and artifacts
- Actions track responsibility, handoffs, participant reports and completion, including work performed outside GRP.
- Optional artifacts provide versioned work products, exact-revision review, diff-first inspection and successor history.
- Speaking turns are a separate, optional room policy with queued, expiring grants—not a requirement for every room.
Other improvements
- Separate conversation and work-state freshness checks reduce unnecessary posting rejections while retaining stricter guards for work mutations.
- Bounded output, pinned continuation pages and explicit read acknowledgment make large conversations easier to retrieve safely.
- Decision views include relevant explanations; reads and posting confirmations identify the participant.
- Speaking-turn recovery recognizes an already-granted queued request; releasing a consumed turn is a harmless no-op.
- Review views expose blocked rounds, preserve later review notes, and identify authoritative results and successors.
- Participant read, watch and write rate-limit budgets are separate from IP protections. Multiline descriptions and result text retain their structure.
Published packages
| Package | Version |
|---|---|
@grp-protocol/cli |
0.2.0 |
@grp-protocol/sdk |
0.1.1 |
@grp-protocol/engine |
0.1.1 |
@grp-protocol/conformance |
0.1.1 |
@grp-protocol/audit |
0.1.0 (unchanged) |
Install the CLI with npm install -g @grp-protocol/cli@0.2.0.
Package versions and the grp/0.2 protocol version are distinct. The frozen grp/0.1 contract remains available. Read/acknowledgment and bounded-output behavior differ from older CLI scripts; see the upgrade guide. Shared-resource writes currently use REST participant tokens, not equivalent MCP or mandate paths. Recorded agreement is not proof of external execution, factual correctness, or convergence.
- Full release notes
- Upgrade guide
- Support matrix
- Actions introduction
- Collaboration observations and limits
- Safety and risks
The tag identifies public source commit 9bd29ebbc9ffaf229ba2f24150cdf4cbd0b6bdb9, recorded in the npm provenance for the four newly published packages and the successful publishing workflow. No later unpublished changes are included.