Repository navigation
fix: support Anthropic keys requiring a workspace ID - #33
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Kinfe123
marked this pull request as ready for review
October 23, 2026 03:36
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Anthropic personal/service-account keys that are not bound to a workspace reject model requests unless the host supplies
anthropic-workspace-id. Tress currently sends only the API key and API version.Add optional server-only
ANTHROPIC_WORKSPACE_IDconfiguration and reuse the resulting headers in agent execution, browser model forwarding/probes, and model health checks. Existing workspace-scoped keys continue to work without the setting, and incoming browser headers cannot override the host's workspace. Document local and Vercel configuration.Validation:
TRESS_DEPLOY_OKfrom its model endpoint before promotion.TRESS_PRODUCTION_OK. Public storage/model/Harness health checks all passed; the browser reported no console errors. The brief runtime-log stream returned no events, so it is not additional log evidence.Production: deployed this exact commit as dpl_Dr733AXdc6ymVP4qQ3678ksT5mvg and promoted it to https://tress-theta.vercel.app on October 23, 2026 UTC. The host has the validated model key and workspace setting; credentials remain server-only and are not included in this PR. The public site's low-credit error is resolved with the replacement credential.
This fix is based directly on main and does not include the larger Harness runtime or pairing UI PRs. The PR still needs merging so subsequent main-branch deployments retain the fix.