Conversation
🎩 PreviewA preview build has been created at: |
This was referenced Sep 22, 2026
Draft
Collaborator
Author
A project holding a backend pipeline read, in Tangent, as though it held nothing: the resources window asked only for documents, so a pipeline filed under its own entity never appeared. The project page has shown these all along, which is two pages disagreeing about what one project contains. They are listed and say plainly that they cannot be opened here yet, rather than being opened into something that would fail. Nothing here can open one — the editor reads browser storage — and the fetching that would change that is being brought in separately, so this deliberately adds no API work that would be written twice and then unwound. Removing one still works: unopenable is not unremovable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
camielvs
force-pushed
the
09-21-feat_documents_on_both_pages
branch
from
September 22, 2026 01:18
5257550 to
3424b58
Compare
camielvs
force-pushed
the
09-21-feat_backend_pipelines_on_the_tangent_page
branch
from
September 22, 2026 01:18
aed2c0f to
4a1e782
Compare
This was referenced Sep 22, 2026
This was referenced Sep 22, 2026
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
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.
Fourth of the standardization PRs, and deliberately the smallest.
Why
A project holding a backend pipeline read, in Tangent, as though it held nothing. The resources window asked the API only for
documentrows, so a pipeline filed under its ownpipelineentity never appeared. The project page has shown these all along — two pages disagreeing about what one project contains.What it does, and what it deliberately does not
Those rows are now listed, and say plainly that they cannot be opened here yet:
No API work. #2706 is bringing backend pipeline support, so this adds no list endpoint, no
backend_pipelineworkarea kind and no new target type — anything built here would be written twice and then unwound. "Add a pipeline" still offers browser pipelines only; this shows what a project already holds, nothing more.An unopenable row is still removable — it can be taken out of the project like any other.
Worth knowing for whoever picks up #2706: the single-pipeline fetch already exists and is shipped —
getPipelineSpec/usePipelineSpec, which the project page's ownPipelinePreviewuses to render backend YAML. So a read-only tab here is a short change on top of a capability that is already live, whenever it is wanted.Testing
pnpm run validateandnpx vitest rungreen (3068 tests), with the row's listing, its disabled state, its removability, and the widened query all covered.Verified in a browser against a project holding one:
🤖 Generated with Claude Code