DevChime

Connect your tools

Each service takes a minute: create a token, paste it into DevChime, press Test connection, then Save. Tokens stay in a settings file on your computer; DevChime only reads from these services.

How it works

  1. Open DevChime from the tray icon and go to Settings.
  2. Under the service, press + Connect. The form says what it needs; Create a token ↗ opens the right page on that service.
  3. Paste the token, press Test connection, then Save.

You can connect several accounts of each kind (work and personal, github.com and Enterprise, two Jenkins servers): give each one a name. The free version runs three connected services or agents; Lifetime unlocks any number. Long terminal commands and alert channels don't count.

Coding agents

Claude Code

  1. In DevChime, open Setup → Claude Code and press Connect. On Windows you can connect Windows, WSL, or both: pick where you run Claude Code.
  2. Start a new Claude Code session.

You get an alert when Claude finishes a reply that took more than 20 seconds, or stops at a permission prompt. Change the 20 seconds in Settings → Notifications.

GitHub Copilot (VS Code)

  1. Open Setup → GitHub Copilot and press Connect where your VS Code windows run: Windows for local folders, WSL for WSL folders.
  2. Trust the workspace in VS Code if it asks. DevChime uses VS Code's agent hooks, which are a preview feature.

You get an alert when Copilot's agent finishes a request. Copilot has no "waiting for approval" event, so only finished requests alert.

Terminal

Commands that run longer than 30 seconds alert when they finish. Editors, ssh and other interactive tools are ignored.

Services

GitHub

  1. Create a classic personal access token at github.com → Settings → Developer settings → Tokens (classic) with the repo and notifications scopes. Fine-grained tokens can't read notifications.
  2. If your organization uses single sign-on, press Configure SSO → Authorize next to the token for that organization.
  3. In DevChime: Settings → GitHub → + Connect, paste the token. Your username is detected.

DevChime watches repos you pushed to in the last two weeks; add others under Always watch these repos. For GitHub Enterprise, set the API and web URLs under Advanced.

GitLab

  1. Create a personal access token in GitLab under Preferences → Access tokens with only the read_api scope (gitlab.com).
  2. In DevChime: Settings → GitLab → + Connect, paste the token. For self-managed GitLab, set its URL under Advanced first.

You get pipelines you start, to-dos (review requests, approvals, mentions) and your merge requests being merged or closed.

Vercel

  1. Create a token at vercel.com → Account Settings → Tokens. Give it a scope that includes the teams you want to watch.
  2. In DevChime: Settings → Vercel → + Connect, paste the token, and list team slugs (as in vercel.com/<slug>) under Teams to watch too.

Only deployments you started alert: preview ready (with the link), production live, failed or canceled.

Netlify

  1. Create a token at app.netlify.com → User settings → Applications → Personal access tokens.
  2. In DevChime: Settings → Netlify → + Connect, paste the token.
  3. Add your Git username (for example your GitHub username) under My Git usernames. Netlify can't list deploys by person, so this is how deploys from your pushes count as yours. Deploys you start in Netlify always do.

Jenkins

  1. Find your user ID at <your Jenkins>/whoAmI/: it's the Name shown there. With single sign-on it's often a long ID.
  2. Create an API token under your name → Security → API Token → Add new token.
  3. In DevChime: Settings → Jenkins → + Connect, enter the Jenkins URL, the user ID and the token.
  4. Optional: list your commit emails so builds started by your pushes count too, and the folders you care about so a large server stays fast.

Jira

  1. Create an API token at id.atlassian.com → Security → API tokens. For a read-only token, choose Create API token with scopes → Jira → read:jira-work and read:jira-user.
  2. In DevChime: Settings → Jira → + Connect, enter your site (https://yourcompany.atlassian.net), the email you sign in with, and the token.

Jira Cloud only. Under Statuses you can make moves into some statuses quiet or hidden.

Figma

  1. In Figma, open Settings → Security → Personal access tokens and create one with read scopes: comments, versions, projects (folders) and file metadata (Figma's guide).
  2. In DevChime: Settings → Figma → + Connect, paste the token.
  3. Paste the links of the projects, teams or files to watch, copied from the address bar. Recents and Drafts can't be read through Figma's API: move the file into a project or paste the file's own link.

Contentful

  1. Create a personal access token at app.contentful.com → Account settings → CMA tokens. Delivery and preview API keys won't work.
  2. In DevChime: Settings → Contentful → + Connect, paste the token, and list your space IDs (Contentful → Settings → General settings), or leave the list empty to watch every space you can see.
  3. Environments defaults to master: add others where you schedule publishes. On EU data residency, set the EU URLs under Advanced.

You get environments you create finishing their copy, your scheduled publishes going out or failing, and tasks assigned to you (tasks need a Premium space).

Alerts away from your desk

All in Settings → Notifications, each with a Send test button. Phone and chat alerts can wait until you've been away from the keyboard for a few minutes.

Phone (ntfy, free)

  1. Install the ntfy app (iOS or Android) and subscribe to a topic with a long, hard-to-guess name: ntfy topics are public.
  2. Enter the same topic under Phone · ntfy and press Send test.

Pushover

  1. Sign in at pushover.net: your user key is on the front page. Create an application there to get an app token.
  2. Enter both under Phone · Pushover.

Slack

  1. At api.slack.com/apps, create an app, turn on Incoming Webhooks, and add a webhook to a channel or your DMs.
  2. Paste the webhook URL under Slack.

Discord

  1. In the channel's settings: Integrations → Webhooks → New Webhook → Copy Webhook URL.
  2. Paste it under Discord.

Stuck?

In DevChime, Setup → About → Report a problem sends us a note, or email [email protected].