What you actually get back.

$ xc create_cheap "a typed React useLocalStorage hook with JSON
serialization that's SSR-safe"

// useLocalStorage.ts — cheap-tier models wrote it; a synth pass merged + reviewed
import { useState, useEffect } from 'react';

const isBrowser =
  typeof window !== 'undefined' && typeof window.localStorage !== 'undefined';

function readValue<T>(key: string, initial: T | (() => T)): T {
  if (!isBrowser) return typeof initial === 'function' ? (initial as () => T)() : initial;
  try {
    const raw = window.localStorage.getItem(key);
    if (raw === null) return typeof initial === 'function' ? (initial as () => T)() : initial;
    return JSON.parse(raw) as T;
  } catch (e) {
    console.warn('localStorage read failed for ' + key, e);
    return typeof initial === 'function' ? (initial as () => T)() : initial;
  }
}

export function useLocalStorage<T>(key: string, initial: T | (() => T)) {
  const [value, setValue] = useState<T>(() => readValue(key, initial));
  // persists on change + syncs across tabs via the 'storage' event
  // …full file also writes back, guards SSR, and handles quota errors
  return [value, setValue] as const;
}

$ xc audit "security-review this Express JWT middleware:
  const t = req.headers.authorization?.split(' ')[1];
  const payload = jwt.verify(t, getKey, { algorithms: undefined });
  req.user = payload; next();"

auditor · openai/o3-mini      verdict: FAIL  (0.00 / 1.00)
────────────────────────────────────────────────
✗ auth_bypass   [high]  score 0.00
  algorithms is unrestricted → a token with alg:'none' is accepted.
  An attacker forges an unsigned token → authentication bypass.

✗ error_handling [med]  score 0.00
  jwt.verify can throw and nothing catches it → 500, not a 401.

passed: false

$ xc debate "New notifications feature: keep it in the monolith or split
a microservice? Team of 4, 3-week deadline, high reliability needed."

round 1 · all four → keep it in the monolith
early-stop · converged (0.95 agreement) → round 2 skipped

▎moderator synthesis (opus)
Keep notifications in the monolith as an isolated module with durable async
dispatch — transactional outbox + worker, retries, idempotency, a DLQ.
Reliability comes from those primitives, not from a separate service. Keep the
module boundary clean so you can extract it later if load, ownership, or
compliance ever justify it. Ship the deadline first.

$ xc pick "Charting library for a Next.js 14 dashboard"
  options: Recharts, Tremor, visx, Nivo
  criteria: developer experience (1.5), bundle size, customization, SSR

ranked · weighted across the panel
────────────────────────────────────────────────
  1. Tremor     0.789   DX 0.95 · SSR 0.93 · bundle 0.58 · custom 0.63
  2. visx       0.781   custom 0.98 · bundle 0.93 · DX 0.53
  3. Nivo       0.694
  4. Recharts   0.686

dissent · bundle size, Tremor
  opus 0.45 "wraps Recharts — not the smallest"  vs  grok 0.70

→ Tremor edges visx for a dashboard (DX + SSR); visx wins if you need
  fully custom viz and the smallest bundle.