Skip to content

[Bug]: Two concurrent runs of one saved Claude workflow show identical Lineage rows #18261

Closed as not planned

Description

@caitlon

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

  1. Save a Claude workflow (here ~/.claude/workflows/pr-preflight-review.js) and, in one thread, start it twice in parallel with different args: one run reviews a whole branch, the other a fix-round delta on another branch.
  2. Open the thread's Lineage list and hover each row.

Expected behavior

Each row says what that run is working on, so the two can be told apart, for example the first line of args.target (or the call's description) under the workflow name.

Actual behavior

Both rows read pr-preflight-review. The hover card shows the model as "Not reported" and the activity line names only the current member (Gemini: gemini-tests-and-text). Which row reviews which branch can only be found by opening each member's chat.

Impact

Cosmetic issue

Version or commit

t3 v0.0.45

Environment

macOS, T3 Code desktop, Claude provider

Screenshots, recordings, or supporting files

Two identical pr-preflight-review rows in Lineage

Workaround

None in the UI; the run's args are visible only in the parent thread's Workflow tool call. #12598 (workflow phases and members in Lineage, closing #15448) is on main but not in this build; from its diff the row title stays the workflow name, so this looks separate.

Activity

  1. juliusmarminge commented on Oct 11, 2026

    @juliusmarminge
    Member

    Note

    Grok responding on behalf of Julius.

    This is a feature request, not a bug, so we're moving it to Ideas. On main, the workflow row in Lineage is labeled workflowName ?? title (ThreadLineageWorkflowRow.tsx). That's on purpose: it names the workflow, not the run. #12598 added phases and members to these rows (closing #15448) but kept the same title, and the open PR #18149 only changes coordinator status. Showing which run is which (from args, a description, or something else) would be a new UI feature, so it belongs in Ideas, not the bug tracker.

    For now, you can see each run's args in the parent thread's Workflow tool call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementRequested improvement or new capability.via-triageFiled through npx t3 triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions