Plugins
Sazabi
Investigate production from your agent with Sazabi's logs, traces and issues, and check a deploy before you call it done
Investigate production from your agent. Ask Sazabi questions about your logs, traces and metrics in plain language, work through the issues Sazabi opened on its own, check that a deploy did what it was meant to, and get your app's and your coding agents' telemetry into Sazabi.
Skills
| Skill | What it does |
|---|---|
investigate-production | Starts from known issues and past investigations, asks the logs precise questions, and reports what fails, why, and who it hits before it changes code |
verify-a-deploy | Compares the error or behavior a change targets before and after the deploy, and checks for new errors, before it calls the task done |
triage-issues | Ranks the issues Sazabi opened by impact, finds each one's cause in the repository, and proposes one fix per issue, leaving issues open until the fix ships |
instrument-with-sazabi | Adds OpenTelemetry to an app, sends logs and traces to a Sazabi intake URL kept in configuration, and confirms the first records arrive |
send-agent-telemetry | Streams Claude Code or Codex session telemetry (tool calls, model requests, tokens, cost) to Sazabi, with prompt export off unless you opt in |
add-logging | Adds structured log lines to the code path a change touches, matching the repository's logger and leaving out secrets |
use-project-memory | Reads Sazabi project memory (runbooks, past incidents) before investigating, and writes back verified findings |
build-a-dashboard | Turns a recurring question into a saved Sazabi dashboard, validates it, and checks every panel returns data |
Skills are named sazabi-<skill>. In Claude Code they appear as superset:sazabi-<skill>.
MCP Server
Tools come from Sazabi's own MCP server at https://mcp.sazabi.com/mcp. Paradev proxies each call and adds your credentials. The server lists two tools, search and execute: the agent searches for an operation (log questions, issues, threads, project memory) and then runs it. See Sazabi's docs for what it can do.
Authentication
| Method | Details |
|---|---|
| OAuth 2.0 | You sign in to Sazabi in your browser. Paradev registers itself with Sazabi when you connect, so there is no app to set up first. |
| Secret key | Paste a key from Sazabi's Settings → Secret keys page. Use it when you cannot sign in through a browser. A key scoped to one project limits the agent to that project. Connecting another key for the same Sazabi organization replaces your existing connection; a key connected by another Paradev user is a separate connection. To reach several projects, use OAuth or an organization-wide key. |
Connect from the plugin's page in Plugins. Paradev stores the credentials on its side and adds them to each call, so they never go into your agent's configuration.