Documentation · Connect a tool
Set up OpenCode
One command adds a tenvor-agent to OpenCode. It asks for your key at a hidden prompt, keeps your other providers and your default model, and asks you before every tool call.
What you need
- A Tenvor API key, from the Console. See your first request.
- On macOS or Linux: Bash, curl and Python 3.10 or newer.
- On Windows 10 or 11: PowerShell and Python 3.10 or newer. Windows includes curl.exe.
- OpenCode 1.x. Tested on OpenCode 1.19.0.
On macOS and Linux, if OpenCode is missing, the setup asks (y/N) before it installs OpenCode 1.19.0 in your home folder. No sudo is needed, and no shell startup file is changed. That install supports Linux, which needs tar, and macOS, which needs unzip. If you already have an older official copy in your home folder, running the setup again upgrades it to 1.19.0. It never downgrades a newer one. On Windows the setup installs nothing: if OpenCode is missing, or older than 1.19.0, it says how to install OpenCode 1.19.0 and stops. OpenCode 2 uses a different plugin interface, and this setup does not support it yet.
Try it on synthetic data
Use a synthetic or non-sensitive project during the alpha. A coding tool sends your source, tool arguments, terminal output and chat history with each request, and requests are not yet encrypted on the node that runs them.
Run the setup
Copy the command for your system into your terminal. The tabs open on the system this browser runs on. It downloads the launcher and runs it. Paste your key at the prompt and press Enter. The key never shows: on Windows a * appears for each character, and on macOS and Linux nothing appears. Never put the key in the command line.
The setup keeps a new key in a file of its own in OpenCode's config folder (usually ~/.config/opencode, or %USERPROFILE%\.config\opencode on Windows), readable only by you on macOS and Linux. On Windows the file has your user profile's permissions: by default only you, administrators and the system can read it. It adds the Tenvor provider and the tenvor-agent, and backs up any file it changes. Your other providers and your default model are left as they are. If you already set up a Tenvor provider yourself, the setup keeps that provider and its credential.
You can read the Bash launcher, the PowerShell launcher, the Command Prompt launcher and the Python helper first. The launcher checks the helper against its own pinned SHA-256 before it runs it. The launcher's own SHA-256 is 6244f0a4cf447b6c36e7040de04bd39f298739cefdce66753b2486315bfa0725. The setup pins the installer code. It does not pin the OpenCode release files that OpenCode's own installer downloads.
On Windows, the PowerShell command downloads the PowerShell launcher and runs it in that window, and it never closes the window. The Command Prompt command saves tenvor-opencode.cmd, which downloads the same PowerShell launcher and runs it. The PowerShell launcher's SHA-256 is 75f57bf13263835f6bd1cc5e086e60efa2cb15805e83bc0d740351bf8a2e219b, and the Command Prompt launcher's is d5bba1ca478a966a7b13746c5a41856021d32c27035cda336b22c430068cf8f7.
To set it up by hand instead, merge the provider and the agent from this example into your OpenCode configuration. Keep the key in a separate file that only you can read.
Run OpenCode
The setup prints the exact command. You do not need to restart your terminal. It is usually:
opencode --agent tenvor-agentYou can also select the command and copy it manually.
The model is tenvor/chat-35b-moe, and the provider's base URL is https://orchestrator.tenvor.io/v1.
On Windows, if PowerShell says that running scripts is disabled when you type opencode, use the command the setup printed: it names OpenCode's opencode.cmd in full when that is needed.
Keep tool approvals on
The tenvor-agent asks before every workspace tool call and refuses access to files outside the project. An approved shell command still runs with your own user permissions, so read it before you allow it; do not enable OpenCode's --auto mode.
Check that it works
Choose the agent
Start
opencode --agent tenvor-agent. If OpenCode can switch providers by itself or pick a model for you, turn that off for this check. Another provider's answer says nothing about Tenvor.Send a short message
Ask something small in a synthetic project. For a tool check, make a small text file, ask OpenCode to read it, and approve only that read.
Find the charge
Open the Usage page in the Console. The request is there as a charge, and in your spend for the day.
A configured URL, or a reply that says it is Tenvor, does not prove a request ran on Tenvor. A charge on the Usage page does.
Long sessions
The setup also installs a small plugin, tenvor-session-kv-plugin.mjs, pinned by checksum. It lets OpenCode ask the node to keep one conversation warm, so a follow-up can reuse its working state. Input the node reuses is billed at half the input price, and shows as cached_input_tokens on the receipt. What the node keeps, and for how long, is on the Trust page.
Remove the setup or replace your key
Run these commands in the folder where the setup command saved tenvor-opencode.sh, or tenvor-opencode.cmd in Command Prompt on Windows (the PowerShell form needs no saved file).
This removes only what the setup added to OpenCode on this machine. It does not revoke your key on Tenvor. To do that, use the API keys page in the Console.
To use a replacement key, replace it in the Console, then run the next command and paste the new key at the prompt. The old key stops working as soon as you replace it.
Content checked . Live limits and prices can change.