Debugy docs

Debugy is a dead-simple log API. Any service or pipeline POSTs its logs with one key; your coding agent fetches them back to see errors and runtime behavior. Install the skill, set your key, and you're ready to go.

Add the Debugy skill

Sign up free, grab your key, and copy-paste the Debugy skill into Claude Code, Cursor, or Codex.

Save to .claude/skills/debugy/SKILL.md

 Writing logs
Any service POSTs a log with one HTTP call. The only required fields are service (which pipeline it came from) and message. level and metadata are optional.
curl -X POST "https://www.debugy.dev/api/logs" \
  -H "Authorization: Bearer $DEBUGY_KEY" \
  -H "Content-Type: application/json" \
  -d '{"service":"checkout-api","level":"error","message":"payment declined","metadata":{"code":402}}'
Keep DEBUGY_KEY server-side. For browser logs, route them through a server endpoint — never ship the key to client code.
 Getting started
Logs go to Debugy Cloud so your agent can read issues from real users without reproducing locally.
  1. Create a free account and get your key
  2. Set DEBUGY_KEY where your services run
  3. Keep the same DEBUGY_KEY with the agent or your local shell so it can read logs back
How to use
During a session, tell your agent debugy — it will fetch logs from Debugy Cloud using your DEBUGY_KEY and can filter by service or error level to find exactly what it needs.
Reading logs
Your agent can filter by service, level, search, limit, and offset:
curl -s "https://www.debugy.dev/api/logs?limit=100" -H "Authorization: Bearer <DEBUGY_KEY>"
Responses may include a notice field when a limit is hit (e.g. monthly write quota exhausted). Your agent will surface it so you know logs are being dropped.
Limits
Free tier: 15 days retention, 5,000 logs, 5,000 monthly calls. See plans