raindrop-airaindrop-ai/workshop/AGENTS.md

workshop

AGENTS.md1.1k starsChanged 18 days agoMITView on GitHub

Read this first to decide what the user actually wants. Just run the one-liner: That installs the raindrop CLI. Then raindrop workshop starts the UI. Do not clone this repo or bun install for this. Building from source is only for developing Workshop itself. Hosted observability instead? raindrop cloud setup connects to app.raindrop.ai (no local daemon). Build from source: See .devin/blueprint.yml and .cursor/README.md for full dev-environment setup. Before creating a PR, run and confirm: For UI changes: visually verify changed…

Pipes a download into a shell

Sep 28, 2026docs: Raindrop Workshop 한국어 분석 정리 문서 추가 — bmshin94/workshop0 reactions
May 22, 2026Upstream: @raindrop-ai/opencode-plugin silently drops spans for several failure modes — josephhaaga/dotfiles0 reactions
May 19, 2026Package Raindrop CLI declaratively in the flake — sysarcher/nixos-ref0 reactions
May 19, 2026Reduce number of prompts - inspiration from raindrop — braintrustdata/spark0 reactions

On Hacker News · 2

May 19, 2026Raindrop Workshop: Local OSS agent debugger9 points · 6 comments
May 14, 2026Raindrop – Local Agent Debugger3 points · 1 comment

On Bluesky · 1

Sep 23, 2026In cloud infra we've always known: observability is foundational. AI agents fail quietly. Guardrails are a feature.… — @mikedemo.bsky.social1 likes and repost · 1 reply

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository2 other files it gives its agents.
- instrument-agentSkill
- setup-agent-replaySkill

The file

We split this AGENTS.md into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Read this first to decide what the user actually wants.
line 3
Very specific:
Do not clone this repo or bun install for this.
line 15
Distinctive:
Every changed line must trace to the user's request.
line 42
Distinctive:
Before creating a PR, run and confirm:
line 46
Distinctive:
Keep a running memory of mistakes here.
line 67

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

AGENTS.md

Agent guide

Read this first to decide what the user actually wants.

Did the user ask you to use Workshop? (the common case)

Just run the one-liner:

curl -fsSL https://raindrop.sh/install | bash

That installs the raindrop CLI. Then raindrop workshop starts the UI.

Do not clone this repo or bun install for this. Building from source is only for developing Workshop itself.

Hosted observability instead? raindrop cloud setup connects to app.raindrop.ai (no local daemon).

Did the user ask you to develop Workshop?

Build from source:

bun install
bun run dev   # daemon on :5899, Vite UI on http://localhost:5900

Commands

bun run build         # build
bun run test          # test
bun run lint          # lint
bun x tsc --noEmit    # typecheck

See .devin/blueprint.yml and .cursor/README.md for full dev-environment setup.

How to work

Touch only what the task requires. Match existing style.
Every changed line must trace to the user's request.

Verification (Definition of Done)

Before creating a PR, run and confirm:

bun run build         # MUST exit 0
bun run test          # MUST pass
bun run lint          # MUST exit 0
bun x tsc --noEmit    # MUST exit 0

For UI changes: visually verify changed pages render correctly and check neighboring pages.

Then: review your diff — no unintended changes, no debug code, changes scoped to the task.

Do not touch (without explicit permission)

.github/workflows/ — propose, don't apply
The raindrop CLI installer (https://raindrop.sh/install)
Publish/release configuration

Agent operating notes

Keep a running memory of mistakes here. Add a concrete guardrail when you make a repeatable stumble.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free