Getting started

Open rageshake.dev/login and sign in with Clerk — use your email or a social login. Your rageshake.dev account is keyed to that identity and is created automatically on first sign-in.

A project holds your ingest key, destinations, and reports. There are three ways to create one — pick whichever fits how you work. Each produces an rs_ing_… ingest key, which is shown once and embedded in your app. Ingest keys can only submit reports, so they are safe to ship inside the binary.

# 1. Install the CLI (Go 1.22+)
go install github.com/patrickshuff/rageshake-cli/cmd/rageshake@latest

# 2. Authenticate with a management key (Dashboard -> project -> API keys)
export RAGESHAKE_API_KEY=rs_mgmt_YOUR_KEY

# 3. Create project + ingest key + Linear destination in one shot
rageshake bootstrap --name "My App" --platform ios \
  --type linear --linear-api-key lin_api_YOUR_KEY --team-id YOUR_TEAM_ID

claude mcp add rageshake \
  --transport http https://rageshake.dev/api/mcp \
  --header "Authorization: Bearer rs_mgmt_YOUR_KEY"

bootstrap_project({
  "name": "My App",
  "platform": "ios",
  "destination": {
    "type": "linear",
    "linear": { "apiKey": "lin_api_YOUR_KEY", "teamId": "YOUR_TEAM_ID" }
  }
})

In Xcode, choose File → Add Package Dependencies… and enter https://github.com/rageshake/rageshake-ios, or add it to your Package.swift directly. RageShake is iOS 15+ and has zero third-party dependencies.

dependencies: [
  .package(url: "https://github.com/rageshake/rageshake-ios", from: "1.0.0"),
],
targets: [
  .target(
    name: "MyApp",
    dependencies: [
      .product(name: "RageShake", package: "rageshake-ios"),
    ]
  ),
]

Call RageShake.configure(apiKey:) once, as early as possible — a SwiftUI Appinitializer or your app delegate's didFinishLaunchingWithOptions. That one call starts shake detection, screenshot capture, and the feedback sheet. Paste the ingest key from step 2.

import SwiftUI
import RageShake

@main
struct MyApp: App {
  init() {
    RageShake.configure(apiKey: "rs_ing_YOUR_KEY")
  }

  var body: some Scene {
    WindowGroup { ContentView() }
  }
}

That's the whole integration. The endpoint defaults to https://rageshake.dev; pass tintColor: to theme the sheet, or call RageShake.setEnabled(false) to suppress reporting in sensitive flows. Wrap any sensitive SwiftUI view in .rageShakeExcluded() to keep it out of the captured screenshot.

A report is only useful if it lands somewhere your team works. If you used bootstrap with a destination in step 2, this is already done — otherwise add one now. A project can have both a Linear destination and a webhook.

rageshake destinations create --project YOUR_PROJECT_ID --type linear \
  --linear-api-key lin_api_YOUR_KEY --team-id YOUR_TEAM_ID

# Fire a synthetic delivery to confirm the credentials work
rageshake destinations test --project YOUR_PROJECT_ID YOUR_DESTINATION_ID

rageshake destinations create --project YOUR_PROJECT_ID --type webhook \
  --url https://example.com/hooks/rageshake --secret whsec_YOUR_SECRET

Delivery is validated before saving and you can dry-run it any time with test_destination (MCP) or rageshake destinations test (CLI), which runs a real delivery against a synthetic report and reports success, retryable, or permanent.

Build and run your app. Shake the device — on the iOS Simulator use Device → Shake (⌃⌘Z). The feedback sheet rises with a preview of the screenshot and a text box; type what went wrong and hit submit.

Within moments the report is ingested, fanned out to your destination, and delivered: a new issue appears in your Linear team (or your webhook receives the signed payload). If the device is offline, the SDK queues the report on disk and drains it automatically when connectivity returns — the user's job is done the moment they tap submit.

You can confirm delivery from the dashboard's reports view, or with rageshake reports list --project YOUR_PROJECT_ID, which shows each report with its per-destination delivery status.