Agent Support Matrix
Overview
Keep the support matrix and memory bank accurate, and gate updates with evidence so parsing regressions are avoided.
Quick Start
- •Read
docs/agent-support/workflow.md. - •Compare upstream agent versions to
docs/agent-support/agent-support-matrix.yml. - •If gaps exist, run an impact scan, collect evidence, and update fixtures/tests before
bumping
max_verified_version.
Workflow
- •Determine the current Agent Sessions version from
AgentSessions.xcodeproj/project.pbxprojMARKETING_VERSION. - •Use
references/impact-scan.mdto inspect upstream releases for format changes. - •Follow
references/update-checklist.mdbefore updating docs or fixtures.
Guardrails
- •Do not bump
max_verified_versionwithout fixtures or sample logs plus passing parser tests. - •If an agent does not log a version, keep
max_verified_version: "unknown"and document verification scope indocs/agent-json-tracking.md.
References
- •
references/matrix-schema.mdfor matrix fields and update rules. - •
references/impact-scan.mdfor format change detection heuristics. - •
references/update-checklist.mdfor the evidence checklist.
Related Skills
- •
agent-session-format-check— detection and evidence collection for session format drift, usage/limits tracking changes, OpenCode storage backend shifts, and discovery path contract failures. Use that skill for monitoring and diagnosis; use this skill for recording and gating version bumps.