Debugy docs

Debugy is a skill that teaches your coding agent to write and read runtime logs — it inserts debugy.log() calls into your code and reads them back from the cloud. Install the skill, set your write key, and you're ready to go.

Add the Debugy skill

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

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

 debugy.log()
Your agent adds debugy.log() calls where it needs runtime data. Each call includes the file, function, a message, and optional metadata.
debugy.log("src/api/checkout.ts", "handleCheckout", err.message, {
  level: "error",
  metadata: { status: err.status, cartTotal: cart.total }
})
Logs are structured — your agent can query by file, function, or error level instead of scanning raw output. It removes the temporary log calls when the bug is fixed.
After install, the agent also sets up a global unhandled-error hook for your runtime — so unexpected crashes are automatically captured and sent to Debugy Cloud, even in code that isn't manually instrumented.
 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 keys
  2. Set DEBUGY_WRITE_KEY in the app env
  3. Keep DEBUGY_AGENT_KEY with the agent or your local shell — not in the deployed app
How to use
During a session, tell your agent debugy — it will fetch logs from Debugy Cloud using your DEBUGY_AGENT_KEY and can filter by file, function, or error level to find exactly what it needs.
Reading logs
Your agent can filter by level, file, fn, search, limit, and offset:
curl -s "https://www.debugy.dev/api/logs?limit=100" -H "Authorization: Bearer <DEBUGY_AGENT_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 per project, 5,000 monthly calls. See plans