Claron
    Documentation
    Settings
    Workspace Controls    Reviewed

    Settings

    Manage identity, GitHub connection, notifications, API keys, CLI onboarding, and workspace-level outbound webhooks from one place.

    Open the setting for your task

    TaskWhere to go
    Profile and preferencesDashboard → Settings → Profile; edit and save the relevant fields.
    GitHub / GitLab / Bitbucket accessSettings → Version Control; connect the correct provider account and repository permissions.
    Personal alert deliverySettings → Notifications; follow Notifications.
    Workspace event receiverSettings → Webhooks with workspace webhook-management authority; follow Webhooks.
    CLI/build API keySettings → Developer & API; follow API Keys.
    MCP setup or OAuth accessSettings → Developer & API → MCP setup / MCP OAuth access; follow MCP.
    Extension device approval and captureSettings → Developer & API; approve the device/project and needed capture capabilities. Follow Extension setup.
    Build variables / workflow / backendProject → Settings → the relevant Build, Workflow, or Backend section.

    Review account sessions and save changes

    Open Security to review the current and other signed-in sessions. Revoke an unfamiliar session or sign out of other devices, then check that the action completed. Masked IPs and reported device details help identify a session but are not proof of a person's physical location.

    Save each section after editing. A docs demonstration uses sample values and does not configure your actual account. If a control is unavailable, check the selected workspace and role before changing another account's configuration.

    A claron:// handoff opens the CLI workflow when registered and approved by your OS/browser. It does not instantly open every editor or apply a patch without confirmation.

    SETTINGS TABS

    The settings page is organized into six tabs. Navigate between them to manage different aspects of your workspace.

    Profile & Workspace

    Update identity and contact details for your account or organization.

    VERIFYING WEBHOOK SIGNATURES

    If your workspace uses a webhook signing secret, calculate HMAC-SHA256 over the exact received body bytes before parsing JSON. Mount this route before a JSON body parser consumes the request:

    webhook receiver
    javascript
    import express from 'express'
    import { createHmac, timingSafeEqual } from 'node:crypto'
    const app = express()
    const secret = process.env.WEBHOOK_SECRET
    if (!secret) throw new Error('WEBHOOK_SECRET is required')
    app.post('/claron-webhook', express.raw({ type: 'application/json', limit: '1mb' }), async (req, res) => {
      const header = req.get('X-Claron-Signature') ?? ''
      if (!/^sha256=[a-f0-9]{64}$/i.test(header) || !Buffer.isBuffer(req.body)) {
        return res.sendStatus(401)
      }
      const actual = Buffer.from(header.slice(7), 'hex')
      const expected = createHmac('sha256', secret).update(req.body).digest()
      if (actual.length !== expected.length || !timingSafeEqual(actual, expected)) {
        return res.sendStatus(401)
      }
      let delivery
      try { delivery = JSON.parse(req.body.toString('utf8')) }
      catch { return res.sendStatus(400) }
      if (typeof delivery.event !== 'string' || typeof delivery.ts !== 'number' || !delivery.data || typeof delivery.data !== 'object' || Array.isArray(delivery.data)) {
        return res.sendStatus(400)
      }
      try {
        await enqueueDelivery(delivery) // Implement durable, idempotent queuing.
        return res.sendStatus(202)
      } catch {
        return res.sendStatus(503)
      }
    })
    app.listen(3000)