Repository navigation
Conversation
camielvs
added this pull request to stack #2930
October 22, 2026 22:34
🎩 PreviewA preview build has been created at: |
This was referenced Oct 22, 2026
camielvs
force-pushed
the
cvs/submit-as-team
branch
from
October 23, 2026 22:58
5c3a238 to
ce77b75
Compare
A run now acts as the team of the projects it's filed under. The submit button, the arguments dialog and a project's Run pipeline button all send the team header when the team resolves to one you're in, and write the run's notes and tags as that team too, since the backend only lets the run's creator annotate it. When a run would fall back to you (you're not in the team, the team can't be acted as, or the team couldn't be checked), or a secret the pipeline references isn't in the secrets the run will see, the quick submit button opens the arguments dialog instead of submitting. The dialog says who the run runs as, explains a fallback, and names the missing secrets. Missing secrets warn rather than block: the list can lag behind a secret added elsewhere. Submit waits while the team resolves and while the secrets are checked, and is refused for projects on different teams. The arguments button stays available in that case, so another project can be chosen for the run. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A run an agent submitted from a team's Tangent project was created as the user, so its secrets were looked up in the user's account and a team secret failed at launch. The Tangent editor and run view agents submit through the tool bridge, which filed the run under the project but never sent the team header. The bridge now takes the project's team from the same `useTeamForSubmission` the submit button uses: - An active team: the run acts as it, and the result says so. - The team is still resolving, or the projects are on different teams: the submission is refused with the reason, so the agent can retry or explain. - A fallback (not a member, refused, or the lookup failed): the run is submitted as the user, and the result carries a warning saying why and that it uses the user's own secrets. It's the same rule as the submit dialog, worded for the agent to pass on. Team names in the submit button and the missing-secrets warning now carry the team icon, like the rest of the team copy. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
camielvs
force-pushed
the
cvs/submit-as-team
branch
from
October 23, 2026 23:50
ce77b75 to
346ee1f
Compare
This branch has not been 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.
Description
A run now acts as the team of the projects it's filed under. The editor's Submit Run button, the arguments dialog, a project's Run pipeline button and the Tangent agents all send the team header when the team resolves to one you're in. They also write the run's notes and tags as that team, since the backend only lets a run's creator annotate it.
Runs fall back to you rather than fail, and the UI says so before you submit:
Agents in Tangent's editor and run view submit through the tool bridge, which now uses the same team. A run that falls back to the user is still submitted, and the result carries a warning saying why, for the agent to pass on. While the team is resolving, or for projects on different teams, the submission is refused with the reason.
Submit waits while the team resolves and while the secrets are checked. It's refused for projects on different teams. The arguments button stays available in that case, so another project can be chosen for the run.
Related Issue and Pull requests
Type of Change
Line Breakdown
Checklist
Screenshots (if applicable)
None yet.
Test Instructions
With the same setup as #2941:
master.Additional Comments
TangleSubmitter had no tests. It now has tests for the team cases.
🤖 Generated with Claude Code