Skip to main content
This guide covers setup end to end: creating your workspace, inviting your team, connecting GitHub and Slack, and sending telemetry. It takes a few minutes, plus a short wait while your workspace is provisioned. After setup, you work in chat.

​
1. Create your workspace

Sign up at app.onepatch.dev and create an organization — name it and confirm your domain. This starts provisioning your workspace: a private OnePatch instance with its own agent. Provisioning usually takes a few minutes; the setup screen shows progress, and the onboarding chat tells you when the workspace is ready.
Your telemetry, repositories, and the agent’s work are private to your organization.

​
2. Invite your team

Add teammates by email — anyone who may get paged, or anyone who wants to explore your telemetry. You can add members later under Workspace settings → members.

​
3. Connect GitHub

The agent reads your repositories to understand your services, and opens pull requests when it has a fix.
1

Authorize OnePatch

Click Connect GitHub and complete the OAuth flow.
2

Install the GitHub App

Install the OnePatch GitHub App on the account that owns the repositories you want to use.
3

Pair at least one repository

Select the repositories to make available to your workspace. You can change the selection later from the integrations screen.

​
4. Connect Slack

Click Connect Slack and authorize the workspace your team watches. OnePatch creates an #onepatch-alerts channel where incident notifications land.

​
5. Send telemetry

OnePatch reads OpenTelemetry. The onboarding chat hands you a block to paste into your coding agent — Claude Code, Cursor, or similar — which installs a setup skill and wires up the OpenTelemetry SDK. With your own endpoint and token filled in, it looks like this:
The token is write-only — it can send telemetry but cannot read anything back — so it is safe to commit, like a Sentry DSN. The endpoint and token stay available on the integrations screen. OnePatch accepts standard OTLP over HTTP, both http/protobuf and http/json; the setup skill configures your exporter. The skill is open source at github.com/1patch/skills. Commit and push the changes. Telemetry starts the next time your app runs. That covers your services. To see what people actually do in your web app — pages, clicks, failed requests and JS errors, joined to the backend traces they caused — see Browser monitoring.

​
6. Your first dashboard

When the first telemetry arrives, the agent reads the TELEMETRY.md file the setup skill wrote at your repository root — a short description of what your service emits — and drafts a first dashboard. It appears in the side pane next to the chat and refreshes as data lands. To change it, ask:

​
Next

  • Chats — ask the agent to build dashboards and monitors, investigate your data, explore your code, or open a pull request.
  • Dashboards — the dashboards the agent has saved, updating live.
  • Monitors — every monitor, its schedule, and its current state.
  • Workspace settings → integrations — connected repositories, Slack, and your telemetry endpoint and token.
For the model behind all of this, read How OnePatch works.