The agent investigates incidents and pages the on-call responder when it needs a human decision or action, explaining what’s needed and linking to the relevant fix or evidence. Your team’s rules determine what warrants an interruption, and pages follow your on-call rotation through Slack DMs or SMS. See Set up paging.
The agent can follow your team’s procedures across conversations. Save a procedure as a skill and run it from chat with a slash command.
The agent shows why it reached a diagnosis and whether a fix is working, with production charts and traces alongside its findings.
Admins can set workspace-wide instructions under Settings → Agent — your team’s conventions, production context, and rules for taking action.
The Services page brings together the agent’s map of your system: each service’s health, monitors, dashboards, and dependencies. See what calls what, including the external services your system relies on.
Collect product analytics, crash logs, and other telemetry from native apps built with React Native and Expo. The agent investigates mobile issues alongside your backend telemetry.
Claude Code, Codex, and Cursor can investigate production issues with your telemetry and hand work to the OnePatch agent from inside the editor.
onepatch onboard connects your repository and coding agents to a OnePatch workspace; see Coding agents.Connect Linear from the Integrations page and the agent reads your issues for
context while it investigates, and can create and update them in your workspace.
It works under its own Linear identity, so everything it writes is attributed
to OnePatch.
⌘K finds anything in the workspace — chats, incidents, monitors, and dashboards. The agent searches the same index, so a new incident starts with a look through past ones.
The agent can use the internet while it investigates, scoped to a domain allowlist you control. See Network allowlist.
After a pull request merges, the agent watches the change in production and reports on the PR whether it held up. A review comment before merge says what it will watch, and a regression opens an incident. See Verify PRs in prod.
Point the agent at a Slack channel and it reads every new message there, opening a thread on the ones that need attention. Turn it on from the integrations screen or with
@onepatch watch in the channel. See Watched channels.When something breaks for a user, the agent can see what that user actually did — the pages, clicks, failed requests, and JS errors of their session, each joined to the backend trace it caused. Setup is adding
@onepatch/rum to the frontend. See Browser monitoring.When a new incident turns out to be part of one already open, the agent merges them into a single episode. You follow one thread instead of a row of separate chats.
Connect an IAM role from the Integrations page and the agent can describe resources, read logs, and take whatever actions the role’s policies allow while it investigates. Permissions stay on your side, and every action lands in your CloudTrail named for the chat that made it. See AWS.
One workspace-wide memory that carries across chats, so the agent doesn’t start cold every time.
Every workspace gets an ingest address. Forward alert email from any vendor and it becomes telemetry a monitor can act on.
Scripts and unattended agents can query production telemetry and ask OnePatch to investigate issues using an API key scoped to your workspace. See API keys.
Chat, dashboards, monitors, the command palette, and onboarding are navigable by keyboard and announced to screen readers.
Dashboards show how your services behaved during an incident, with filters and a shared time window across charts. Individual charts have links you can share with your team.
Connect any OAuth-protected MCP server from the Integrations screen and the agent can use its tools. See How OnePatch works.
DM the OnePatch bot, or @-mention it in a channel and it replies in a thread. Each conversation is a real chat that also shows up in the app, with the sender’s name. See Incidents and Slack.
Fixes arrive as a PR against your connected repo rather than a suggestion in chat.