kits: one Harness per workspace, and a database connection's configuration on the graph - #240
Merged
Merged
Conversation
…ation on the graph A launched kit's Harness belongs to the workspace it was launched in, but launch and the catalog looked the org over: a second workspace was handed the first workspace's Harness, which its members could not see, and its card said Running for a kit that workspace never launched. Both now keep to the caller's workspace, with the Default Workspace's leniency for a Harness made before workspaces were stamped. What a harness is connected to is configuration, and configuration is listed and managed; a vault record is neither. The database attach now writes a HarnessConnection vertex (engine, host, database, sampling, the vault key) beside the vault record that alone holds the credential, and a removed entry drops it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
richard-epsilla
approved these changes
Sep 22, 2026
richard-epsilla
left a comment
richard-epsilla
left a comment
Collaborator
There was a problem hiding this comment.
Per-workspace launch and the connection vertex match the hosted change; checks green.
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
1 participant
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.
A launched kit's Harness belongs to the workspace it was launched in, but launch and the catalog looked the whole org over: a second workspace was handed the first workspace's Harness, which its members could not see, and its card said Running for a kit that workspace never launched. Both now keep to the caller's workspace, with the Default Workspace's leniency for a Harness made before workspaces were stamped.
What a harness is connected to is configuration, and configuration is listed and managed; a vault record is neither. The database attach now writes a
HarnessConnectionvertex (engine, host, database, sampling, the vault key) beside the vault record that alone holds the credential, and a removed entry drops it.Tests:
gateway/tests/test_kits_workspace.py. Gateway suite green locally (618 passed). The same change is on the hosted service.Patch release: v0.23.4.
🤖 Generated with Claude Code