Caddi
Sign inSign up

Inbox

Every pinpoint, every portal ticket, every email-via-form lands in one inbox at /requests. The CLI mirror is caddi requests.

What a request looks like

  • Title — the first line of the user’s note.
  • Status — open, in-progress, done.
  • URL — where the pinpoint was filed.
  • Element selector — the CSS path of the clicked element.
  • Screenshot — captured at submit.
  • Reporter — the client member, or anonymous if unauthenticated.
  • Thread — replies in either direction.

Filters

Filter by status, project, client, reporter, or date. URLs are stable so you can bookmark /requests?status=open&client=meridian.

Actions

  • Reply — posts back to the portal and emails the reporter.
  • Assign — to a teammate. Optional.
  • Implement — hands the payload to your local Caddi Auto agent, which opens a PR on dev.
  • Close — with a resolution (fixed, wontfix, duplicate). Reporters get a final email.

Webhooks

Wire the request events into Linear, Slack, or your own system at Settings → Webhooks. Events: request.created, request.replied, request.closed.

bash
caddi webhooks add \
  --url https://hooks.zapier.com/... \
  --events request.created,request.closed

Next

Forms →