OpenCode (Beta)

The Raindrop OpenCode plugin (@raindrop-ai/opencode-plugin) instruments OpenCode so that every LLM response and tool call is sent to Raindrop. You don’t need to add any per-call instrumentation.

Installation

Add the plugin to your OpenCode config. Config file locations: opencode.json in your project, or ~/.config/opencode/opencode.json for a global config. Add this to the config file:

{
  "plugin": ["@raindrop-ai/opencode-plugin"]
}

Quick Start

Add the plugin to your OpenCode config (see above).
Set your write key in the environment where OpenCode runs:
export RAINDROP_WRITE_KEY="your-write-key"
Start OpenCode. Sessions are automatically traced to Raindrop.

After that, each session appears in your Raindrop dashboard with turn-by-turn input/output, tool spans, and LLM metadata.

Configuration

Required: set your Raindrop write key in the environment where OpenCode runs:

export RAINDROP_WRITE_KEY="your-write-key"

Optional: provide additional metadata to be included with every event

export RAINDROP_EVENT_METADATA='{"userId":"user_456","eventName":"support-chat","properties":{"source":"web"}}'                                                         

System Prompt Capture

To include the system prompt in trace spans (visible in the Trace tab when you click an LLM span), enable the captureSystemPrompt option:

export RAINDROP_CAPTURE_SYSTEM_PROMPT="true"

Or via config file (~/.config/opencode/raindrop.json or .opencode/raindrop.json):

{
  "capture_system_prompt": true
}

When enabled, the assembled system prompt is stored as a gen_ai.prompt.0.* span attribute and rendered as a “system” labeled section in the span detail view. This is useful for tracking which system prompt version was used in a given conversation. Defaults to false — no system prompt data is captured unless explicitly enabled. System prompts longer than 32KB are automatically truncated.

Projects

If your org has multiple projects, route this plugin’s events to a specific one by setting its slug via RAINDROP_PROJECT_ID or the project_id config-file key:

export RAINDROP_PROJECT_ID="support-prod"

Or via config file (~/.config/opencode/raindrop.json or .opencode/raindrop.json):

{
  "project_id": "support-prod"
}

This sets the X-Raindrop-Project-Id header on every event. Omit it (or pass default) to use your org’s default Production project, which is the existing behavior. Single-project orgs need nothing new.

Context & Metadata

Per-Call Context Override

You can override the environment-set metadata on a per-prompt basis by passing a metadata field on any text part when calling session.prompt():

await client.session.prompt({
  path: { id: sessionID },
  body: {
    parts: [
      {
        type: "text",
        text: userMessage,
        metadata: {
          userId: "user_456",
          eventName: "support-chat",
          properties: { source: "web" },
        },
      },
    ],
  },
});

Supported fields:

Field	Type	Description
`userId`	`string`	User to attribute this turn’s event to
`eventName`	`string`	Event name for this turn
`properties`	`object`	Additional properties for this turn’s event

Merge behavior:

Prompt-level values override RAINDROP_EVENT_METADATA for that turn
properties are shallow-merged (prompt-level wins on conflicts)
convoId is always the OpenCode session ID

Identifying Users

To associate traits with a user, use our TypeScript SDK:

import { Raindrop } from "raindrop-ai";

const raindrop = new Raindrop({ writeKey: RAINDROP_API_KEY });

raindrop.setUserDetails({
  userId: "user_456",
  traits: {
    name: "Jane",
    email: "jane@example.com",
    plan: "paid", // we recommend 'free', 'paid', 'trial'
    os: "macOS",
  },
});

Tool catalog capture (`ai.prompt.tools`)

OpenCode’s step events carry no tool list, so the plugin cannot see the exact tools each model request was given. Instead it records the host’s tool catalog for the step’s model: the v1 plugin calls client.tool.list({ query: { provider, model } }) once per session and model (2s timeout, cached, never surfaces errors); the v2 plugin reads the registered tool list (ctx.tool.list()). Because this is OpenCode’s catalog rather than the exact per-request set, those spans also carry ai.prompt.tools.source = "opencode.tool.list". A tools array in raindrop.json (user- or project-level) replaces the catalog entirely, skips the lookup and carries no source; tools: [] records an empty catalog. See Tool catalog capture for the attribute format, the absent / [] semantics and the override shapes accepted.

Troubleshooting

Events not appearing in the dashboard

Check your write key — Make sure RAINDROP_WRITE_KEY is set in the environment where OpenCode runs. Use the Raindrop dashboard to confirm events and traces after your first session.

Application Git identity

OpenCode does not use the edited project or plugin process as the application-under-test revision. In ~/.config/opencode/raindrop.json or .opencode/raindrop.json, set app_git to an object with commit_sha, commit_dirty, optional branch, or a source_directory that explicitly identifies the AUT checkout; set it to false to opt out. See the TypeScript Git reference.

Getting Started

SDK

Integrations

Platform

Organization

Cookbooks

Workshop

Query API

MCP

Security

Support

Installation

Quick Start

Configuration

System Prompt Capture

Projects

Context & Metadata

Per-Call Context Override

Identifying Users

Tool catalog capture (`ai.prompt.tools`)

Troubleshooting

Events not appearing in the dashboard

Application Git identity

​Installation

​Quick Start

​Configuration

​System Prompt Capture

​Projects

​Context & Metadata

​Per-Call Context Override

​Identifying Users

​Tool catalog capture (ai.prompt.tools)

​Troubleshooting

​Events not appearing in the dashboard

​Application Git identity

Installation

Quick Start

Configuration

System Prompt Capture

Projects

Context & Metadata

Per-Call Context Override

Identifying Users

Tool catalog capture (`ai.prompt.tools`)

Troubleshooting

Events not appearing in the dashboard

Application Git identity