Crush's agent, TUI, LSP and MCP support, with the phone-home taken out. No telemetry, no catalog fetches, and the only update check is a GitHub release lookup you can turn off. Web tools stay off until you say so, cloned repos stay inert until you trust them, and your OpenCode setup comes along.
Free, open source, FSL-1.1-MIT. Version —, released .
Upstream Crush is excellent. This build changes what it does without asking, not how it codes. Every change is listed in the changelog.
PostHog telemetry, Charm's update check, the Catwalk and Hyper catalog fetches, the Hyper vendor service and the forced Termux DNS resolvers are removed, not just disabled. The provider catalog is a local file you refresh on purpose with tada update-providers.
fetch, agentic_fetch, download and sourcegraph are hidden from the model until you run option web-tools true. Even then, every request asks first. Downloads are capped and headers are redacted in logs.
A cloned repo's tada.json, tadarc and OpenCode config are ignored until you run tada trust. No MCP servers or LSPs start from a project you have not vouched for. .env files are no longer auto-loaded.
Only a single, parsed, read-only command runs without a prompt. Wrappers such as env and timeout, redirections, pipes into writes and multi-line commands always ask.
MCP servers, providers, model choices, the models.dev cache, rules, skills, custom commands, tool toggles and file-edit permissions come from your OpenCode install. Read from disk only. How it works.
Every tag builds six archives and two Windows installers in a public GitHub Actions run with pinned actions, ships a SHA256SUMS.txt, and lands as a draft release that is reviewed before it is published.
tada update fetches the newest release, checks it against SHA256SUMS.txt and swaps the binary in place. Ta-Da mentions a new version once; it never downloads on its own, and the check can be turned off.
A warm "cetla" theme, a Ta-Da wordmark and a short startup flourish (any key skips it; TADA_NO_INTRO=1 turns it off). Charm's themes are still in the picker.
Ta-Da reads ~/.config/opencode at startup and brings the useful parts across. Nothing is copied or rewritten, and nothing of OpenCode's runs. Plugins in particular are never executed: they are listed in the report so you know what is being skipped.
Ta-DaAGENTS.md, skills and custom commands (as opencode:<name>)edit: allow as a no-prompt list inside the projectnetwork: note for MCP commands like npx -y that reach the registry on every startEach part has an on/off switch under options.opencode, and TADA_DISABLE_OPENCODE=1 turns the whole thing off. Run tada opencode to see exactly what was read and what was skipped.
Config files read
~/.config/opencode/opencode.jsonc
project-level config: skipped (not trusted; see `tada trust`)
MCP servers (on)
bench local bench-mcp --project bench imported
playwright local npx -y @playwright/mcp@latest imported
network: playwright: npx contacts the npm registry
every time it starts; add --prefer-offline
Model choice (on)
large pc/bonsai-27b (agent build) selected
small pc/bonsai-27b-quick (small_model) selected
Models catalog (on)
cached 232 providers, 9056 models; 219 usable by Ta-Da
Credentials (off) set options.opencode.credentials to use
API keys from `opencode auth login`
Commands (on)
opencode:commit, opencode:review, opencode:simplify
Notes
plugins are never run: media-models.js, notify.jsVerified with a process-tree connection watcher during the fork's audit, and again on a Windows PC against a local llama-server. If a line isn't here, Ta-Da doesn't do it.
GET /models discovery call against the same base URL.tada login.tada update-providers.api.github.com for this repo's latest release; downloads only when you run tada update. Off with options.update_check: false, option update-check false or TADA_NO_UPDATE_CHECK=1.always, to hosts you chose opt-in or can be turned off
Latest: v, . No release is published yet; check the releases page or build from source below. All releases
tada_<version>_Windows_x86_64_Setup.exe
tada_<version>_Windows_arm64_Setup.exe
The installer needs no admin rights. It puts Ta-Da in %LOCALAPPDATA%\Programs\Ta-Da, adds tada to your PATH and the Start menu, and uninstalls from Settings → Apps. Open a new terminal afterwards and run tada in a project folder. Not code-signed: if SmartScreen appears, choose More info → Run anyway.
tada_<version>_Darwin_arm64.tar.gz
tada_<version>_Darwin_x86_64.tar.gz
Not notarized. If macOS refuses a binary you downloaded with a browser, run xattr -d com.apple.quarantine ./tada.
tada_<version>_Linux_x86_64.tar.gz
tada_<version>_Linux_arm64.tar.gz
A static binary; works on any glibc or musl distro, Raspberry Pi 4/5, Graviton and Ampere.
Package managers (Homebrew, npm, AUR, Nix) install Charm's upstream Crush, not Ta-Da. Get it from the downloads above or build from source.
Every release includes SHA256SUMS.txt. Put it next to the archive and compare.
# macOS / Linux
shasum -a 256 -c SHA256SUMS.txt --ignore-missing
# Windows (PowerShell)
Get-FileHash tada_<version>_Windows_x86_64_Setup.exe
Select-String Windows_x86_64_Setup SHA256SUMS.txtGo 1.27 or newer, nothing else. Same command on every platform.
git clone https://github.com/ItsCetla/tada.git
cd tada
go build -o tada .
./tada --versionNo. It is an independent fork of charmbracelet/crush. Charm is not involved and does not support it. Bugs in code that isn't fork-specific belong upstream.
Yes. Any OpenAI- or Anthropic-compatible endpoint works, including llama-server, LM Studio, Ollama and vLLM. Set a provider with a base_url and an API key (or a {file:…} reference in OpenCode config) and pick the model. Timeouts are long enough for a cold 30k-token prompt on a 27B model.
tada trust actually gate?Project-level config, project OpenCode files, project MCP servers and LSPs, and the no-prompt list for edits inside the project. Until a project is trusted, Ta-Da still works in it but uses only your global config. TADA_TRUST_PROJECT=1 trusts the current directory for one run, which is handy for scripts.
Signing and notarizing cost money and tie a release to a person's certificate. Instead, every build runs in a public GitHub Actions workflow with pinned actions, and the checksums file lets you verify what you got. If you'd rather not trust that, go build takes about a minute.
Yes: option web-tools true inside Ta-Da, options.enable_web_tools: true in config, or TADA_ENABLE_WEB_TOOLS=1. Each fetch still asks for permission, and downloads are size-capped.
Run tada update (add --check to only look, or -y to skip the prompt). It downloads the release for your platform, verifies it against SHA256SUMS.txt and replaces the binary. On Windows with the installer, quit Ta-Da first, or just run the new Setup.exe; it upgrades in place.
On first run Ta-Da copies ~/.config/crush and ~/.local/share/crush into its own folders and still reads CRUSH_* variables, .crush/skills and .crushignore. Per-project session history in .crush/ isn't moved. The 0.2.0 Windows installer replaces the old crush.exe and its shortcuts.
FSL-1.1-MIT, the same Functional Source License as upstream Crush. You may use, copy, modify and redistribute it for anything except a competing product; each version becomes MIT two years after its release.