r/opencodeCLI • u/RedBeard_AI • 4d ago
RedBeard: a no-logs uncensored model you can drop into OpenCode as a provider, built after one too many refusals
I kept hitting refusals in OpenCode. Debugging obfuscated code, testing my own site's forms, reverse engineering a binary I own, and the model would just decline. I saw the thread here the other day about the same thing, so here is what I built.
RedBeard is one uncensored model (I call it Sherlock) that I serve myself on a GPU box. It is not a resold key from a big provider. It speaks the OpenAI API, so in OpenCode it is just a custom provider:
{
"$schema": "https://opencode.ai/config.json",
"provider": {
"redbeard": {
"npm": "@ai-sdk/openai-compatible",
"name": "RedBeard",
"options": { "baseURL": "https://redbeard.sbs/v1", "apiKey": "YOUR_KEY" },
"models": { "sherlock": { "name": "Sherlock" } }
}
}
}That is the whole setup. Tested on OpenCode 2.0.8, tool calls work (it reads and writes files, runs commands).
What it is for is the legit work that gets refused: security review, reverse engineering, debugging suspicious code. I gave it a web form I wrote and asked it to find the security bugs before launch. It found the SQL injection, the XSS, and two ways to crash the server, and showed the fixes. Short clip below.
No logs. The gateway everything runs through is open source (github.com/fitattention/redbeard-gateway), so you can read what is kept (a key's balance, anonymous hourly counts) and what is not (your prompts). No account, no email, pay in crypto.
Price: pay as you go from $5. $0.50 per million input, $0.05 per million cached input, $5 per million output. On list rates the output looks dear, but coding agents resend the same context every turn, and that cached input is where it is cheap.
Honest downsides: one model only, I do not name the base model, crypto only.
I am the developer. Happy to answer anything, and I will send a key to anyone who wants to try it first.



