mirror of
https://github.com/bdnugget/rs-sdk.git
synced 2026-11-07 09:07:30 +00:00
max bittkerandClaude Opus 5
11424fa84d
Agents hit SDK papercuts constantly - a method returns success:true and nothing happened, a dialog option isn't where the docs say it is - and there was nowhere to put that. Filing one is now a single command: bun sdk/bug-report.ts "walkTo returns success at closed gates" The SDK's git commit is stamped on every report, so a report points at the code that produced it. Server side, POST /bug-report appends JSONL to the mounted volume (BUG_REPORTS_FILE in fly.toml, so reports survive deploys). The endpoint is deliberately write-only: nothing is served back over HTTP, and reports are read off the machine with fly ssh console -C "cat /opt/server/data/bug-reports.jsonl" Reports always go to rs-sdk-demo.fly.dev, never to whatever SERVER a bot is playing on - a bug found against a local server is still a bug in the SDK. Telemetry is on by default; TELEMETRY=false in bot.env or the environment turns it off. Also renames claude.md -> CLAUDE.md and agents.md -> AGENTS.md. Those names only resolved on macOS: the filesystem is case-insensitive here, so git had recorded lowercase names that no tool would find on a case-sensitive checkout. Verified on a case-sensitive volume - before the rename, lookups for CLAUDE.md and AGENTS.md both missed; after, all three resolve to the one real file. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
7 lines
195 B
Bash
7 lines
195 B
Bash
BOT_USERNAME={{USERNAME}}
|
|
PASSWORD={{PASSWORD}}
|
|
SERVER=rs-sdk-demo.fly.dev
|
|
SHOW_CHAT=true
|
|
# SDK bug reports, always sent to the shared server (not SERVER above). false to opt out.
|
|
TELEMETRY=true
|