workshop  by raindrop-ai

Local debugger and eval framework for AI coding agents

Created 2 weeks ago

New!

566 stars

Top 56.5% on SourcePulse

GitHubView on GitHub
Project Summary

Summary

Raindrop Workshop addresses the challenge of debugging and evaluating complex coding agents by providing a local, real-time trace debugger. It empowers developers to observe every decision, token, and tool call their agent makes, enabling the creation of automated evaluation and self-healing loops, significantly improving agent development workflows.

How It Works

The system captures and streams agent execution traces—including tokens, tool calls, and spans—directly to a local Vite UI without polling. It integrates with coding agents, allowing them to read these traces, write evaluations against the codebase, and automatically fix identified issues through a self-healing loop. A local replay feature also scaffolds endpoints to reproduce production traces against live agent code.

Quick Start & Requirements

Installation is via curl -fsSL https://raindrop.sh/install | bash. Building from source requires git and bun (bun install, bun run dev). The system relies on a local SQLite database (~/.raindrop/raindrop_workshop.db).

Highlighted Details

  • Extensive compatibility across languages (TypeScript, Python, Go, Rust), SDKs (Vercel AI SDK, LangChain, LangGraph, CrewAI, etc.), and providers (AWS Bedrock, Azure OpenAI).
  • Supports numerous coding agents including Claude Code, Devin, and Cursor.
  • Features a self-healing eval loop where agents write, run, and fix evaluations autonomously.
  • Enables local replay of production traces against agent code.

Maintenance & Community

The provided README does not contain specific details regarding maintainers, community channels (e.g., Discord, Slack), or a public roadmap.

Licensing & Compatibility

The project is licensed under the MIT license, which generally permits commercial use and modification with attribution.

Limitations & Caveats

The "Compatible with everything" claim should be verified against specific agent/SDK versions. Integration requires running the /instrument-agent command within the user's agent codebase. Information on project health signals like active development or community engagement is not detailed in the README.

Health Check
Last Commit

3 days ago

Responsiveness

Inactive

Pull Requests (30d)
8
Issues (30d)
3
Star History
568 stars in the last 17 days

Explore Similar Projects

Feedback? Help us improve.