Introduce separate weave-proxy service which holds the API key #2

Open
elpoelma wants to merge 1 commits from feature/weave-proxy into master
Collaborator

This PR introduces a separate weave-proxy service which holds your WEAVE_API_KEY.
This setup ensures that the opencode service and thus your agent has no direct access to your api key.

In your compose setup, you'll need to move the WEAVE_API_KEY env var from the opencode service to the weave-proxy service.
Aside from that change, everything else should still work in the same manner.

This PR introduces a separate `weave-proxy` service which holds your `WEAVE_API_KEY`. This setup ensures that the `opencode` service and thus your agent has no direct access to your api key. In your compose setup, you'll need to move the `WEAVE_API_KEY` env var from the `opencode` service to the `weave-proxy` service. Aside from that change, everything else should still work in the same manner.
elpoelma added 1 commit 2026-10-20 12:52:44 +00:00
This prevents opencode from having access to the `WEAVE_API_KEY` enviroment variable.
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/weave-proxy:feature/weave-proxy
git checkout feature/weave-proxy
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ai-tools/app-opencode#2
No description provided.