Client Release Agent

The Client Release Agent is the always-on release operator for your client application. It handles the full cherry-pick lifecycle — resolving commits across the public and internal repos, waiting for the sync, opening PRs on the right release branches, assigning them to the current oncall, and keeping a live Slack status board updated as PRs move from review to merged to verified.

Every weekday it also runs the daily Sentry digest: pulling new crash issues scoped to the live stable release, ranking them by event volume, and posting the top three to #oncall so the rotation always starts the day with a focused, actionable summary — no manual report-pulling required.

When a release is ready to ship, the agent triggers the Cut New Release Candidate workflow directly from a branch name and posts the run URL back to Slack so the oncall can track progress without leaving their channel.

Connect the agent to your internal GitHub repo via the gh CLI and provide a Slack bot token with channels:read, channels:history, chat:write, and usergroups:read scopes. Add a Sentry auth token with event:read and project:read access to your Sentry organization.

Configure the daily digest to run on a weekday schedule in Oz — the agent automatically bundles Saturday and Sunday issues into Monday's post and skips weekend runs entirely. For cherry-picks, invoke the agent with a PR URL or commit SHA; it resolves the correct internal commit, waits up to an hour for the repo sync if needed, and handles both preview and stable channels by default.

Once live, every cherry-pick creates a tracked Slack status message that updates automatically as PRs merge, and the oncall can mark PRs verified directly through the agent without touching GitHub.

Out of the box, the agent connects to GitHub for cherry-pick branch operations and PR creation, Sentry for real-time crash issue data scoped to the live stable release, and Slack for oncall notifications, release status tracking, and thread replies.

Additional release signals — internal dashboards, feature-flag rollout data, or custom alerting webhooks — can be wired in via the Oz skill system without modifying the agent's core release logic.