OpenCode setup

Before setup

Tested on OpenCode 1.18.32 with a short file-read tool loop. Confirm your invited account and balance using the quickstart.

Use a synthetic or non-sensitive project during the alpha. Coding tools can send source, terminal output, tool arguments and history to an external operator. Never use private code, credentials, personal data or customer material for this check.

The setup requires Bash, curl and Python 3.10+. Optional installation uses tar on Linux or unzip on macOS. If OpenCode is missing, it offers an explicit y/N installation of OpenCode 1.18.32 in your home directory. Rerunning setup upgrades an older official user-local OpenCode binary to that tested version; update package-managed or other installations with their own package manager first. It never downgrades a newer version. No sudo or shell startup-file edits are required. OpenCode 2 uses a different plugin API and is not supported by this installer yet.

Set up with a hidden key prompt

Create a programmatic key in Console only for this trusted tool. Download the launcher, then run it and enter the key at its hidden prompt. The helper stores a new key separately with user-only mode 600. If a Tenvor provider is already configured at the same endpoint, it keeps that provider and its existing OpenCode credential. Other providers and defaults are preserved with backups.

curl -fsS https://tenvor.io/setup/opencode.sh -o tenvor-opencode.sh && bash tenvor-opencode.sh

You can review the Bash launcher and Python helper first. Launcher SHA-256: fd31f1fa51e7640c9e9d72b639b4ec28bb32930c62313577c153d8c110abd747. The launcher pins installer code, not downloaded OpenCode release assets. Rerunning it refreshes script-managed Tenvor settings and the pinned cache plugin. It backs up changed config and preserves other providers, defaults, plugins, and any tenvor-agent you edited; review that agent's model and tool permissions before use.

Use the Run command printed by the setup; no terminal restart is needed. The usual command is:

opencode --agent tenvor-agent

The setup also installs the pinned session-cache plugin. It enables private, short-lived prefix reuse for eligible streamed Tenvor sessions; the server decides whether a lease is retained and reused. It does not change the billed input-token rate. A pre-existing matching plugin is preserved.

For manual setup, merge only the provider and agent from the existing JSON example into your configuration and check its limits against the current catalog. Keep the key in a separate user-only file. Run the setup script to install the cache plugin after manual provider setup.

Keep tool approvals enabled

The tenvor-agent asks before every workspace tool call and denies direct file-tool access outside the project. Approved shell commands retain your user authority. Review each request; do not enable OpenCode's --auto mode. These approvals do not make arbitrary shell commands harmless.

Verify the chosen provider and one continuation

1. Select tenvor-agent and explicitly select a Tenvor model from the current catalog. The OpenCode provider base URL is https://orchestrator.tenvor.io/v1. Check project-local or JSONC overrides if settings differ.
2. For this routing check, disable Auto selection and automatic cloud/model provider fallback. A different provider's successful answer does not validate Tenvor. Restore your preferences afterward.
3. Send one short synthetic prompt first. For a tool check, create a small synthetic text file in the project, ask OpenCode to read it, approve only that expected read, and inspect the continuation.
4. Wait for the completed tool call and successful turn before execution. Do not execute partial streamed arguments. A tool read alone does not prove the following model request finished.

After completion, check the matching time window, model, usage and charge in Console Activity. A configured endpoint or an answer claiming to be Tenvor is not proof of a completed Tenvor request. If the account evidence is missing or still pending, record the outcome as unverified and reconcile it before submitting again.

The 1.18.32 check completed a real read-tool continuation and returned a cache lease on the next model request. One short test does not establish a latency target or smoothness guarantee. Read the streaming boundaries.

Remove setup or replace a key

bash tenvor-opencode.sh --remove

Removing local configuration does not revoke or rotate the server key. Follow the client checklist's key replacement instructions for supported revocation, replacement and verification. Do not expose either key while checking it.