feat(tangent): brief the agent on naming, and on the project its runs belong to

[camielvs]

Problem

A project opened from the dashboard prompt arrived as "Project 7", with a
session called "Session 1" and a pipeline named after the entire request —
Build a pipeline that scrapes wikipedia and converts articles into a pokemon….
Every one of those is a placeholder, and the agent reading the opening message
already knows what the work is about.

What changed

The agent names all three in its first turn, from the first message.
rename_project, name_session and name_pipeline are workarea tools, and a
naming brief is seeded into the session's memory before the agent spawns, so
it is context from turn one rather than something said in the transcript.

Only a name nobody chose may be replaced. A project or pipeline someone
named deliberately is left alone and the call answers { renamed: false } —
which the brief tells the agent is a final answer, not something to retry. The
mark is dropped by whoever renames next, agent or human.

Naming a pipeline is the part with real plumbing behind it

set_pipeline_name used to rename the spec held in memory and nothing else, so
the agent reported success while the file stayed Draft and both resource lists
kept the name recorded when the pipeline was added.

The spec name is now canonical and everything follows it. The rename goes through
the file first, and the name the file actually took is what the spec is called —
a collision adjusts rather than overwriting, the rule create_pipeline already
follows, and the agent is told so:

Renamed to "Churn model 2" — "Churn model" was already taken.

The open tab retitles rather than announcing the name it resolved when it opened.

And the rename now invalidates the query behind the resource lists. Browser
storage fires no event a same-tab rename would reach, and that query is keyed on
the pointer, which a rename does not change. Without this the new name only
appeared a minute later, or on reload — which read as the rename silently
failing.

name_pipeline drives the open tab's bridge rather than the resource row,
because only the bridge moves the spec, the file and the row together. The editor
keeps a fallback rule for a pipeline still unnamed once its changes are in, and
the provisional mark lives on the spec rather than the resource because the agent
that acts on it reads the canvas and never sees the row.

Resource rows stop trusting a stale copy

Both lists ask what a pipeline is called now, which also fixes the same
staleness after a rename from the menu bar. A name-only pointer is trusted only
in the browser that wrote it — someone else's "Churn model" is not the one this
browser holds. Unknown authorship is trusted, which is every single-user backend.
useUnavailablePipelines moves to services/projects as useLocalPipelineStatus,
since both pages need it and it answers two questions rather than one.

This also meant separating a row's display label from "this row opens a
conversation elsewhere", which had been sharing one prop. A renamed pipeline is
still a row on this page; overloading the label would have made it open as a
session and lose its Remove button.

A derived name also keeps what the ask was about: trimming a dangling preposition
off the end must not amputate the subject with it.

The same seed now tells the agent which project its runs belong to

A run reaches a project's feed by carrying an annotation naming the project,
written at submit time — there is no run row to attach afterwards, and the key
cannot be added later, because the endpoint that sets a single annotation takes
the key as a path segment and rejects this one for its slashes.

A run submitted from the browser is attributed already: the scope provider puts
the annotation in the submission. An agent submitting from its own sandbox is
not, and cannot be — the remote-env handshake carries only the session id, and
the workarea tools submit no runs. So the id never reaches the agent that needs
it, and a run it starts is filed under nothing. That is what was seen on staging:
the agent fell back to building a pipeline outside the canvas, submitted it
itself, and the project reported nothing had been run.

The memory seed already briefs the agent before it spawns, so the project id goes
there, with the annotation to submit with and the two limits it would otherwise
discover by being refused: one project per run, and never this key on a saved
pipeline, whose stored annotations decide its version identity.

The key is built from the same helper the browser submits with, so the two
cannot drift.

This makes the agent aware; it does not make it certain. A brief can be
forgotten on a later turn, and a forgotten tag cannot be repaired. The guarantee
would be for the sandbox's own submit helper to add the annotation from session
context — which needs the id on the wire, and that half is not in this repo.

Note on scope

This absorbs what was PR #2796. Split apart, this PR claimed to name pipelines
while the rename only ever reached the spec in memory — they are one change.

Run attribution rides along because it is the same artifact: one memory seed,
written once before the agent spawns. A second PR would have been a second edit
to the same string.

Testing

• pnpm run validate clean; npx vitest run 320 files / 3248 tests green.
• Observed against a live agent: project and session named from the opening
  message; the pipeline rename fired and the collision message surfaced, but the
  new name only reached the lists on reload — which the query invalidation here
  fixes. The first-turn name_pipeline path has not been exercised against a
  live agent yet.

🤖 Generated with Claude Code

[github-actions]

🎩 Preview

A preview build has been created at: 09-23-feat_let_the_agent_name_the_project_and_session/d63dfbd

[camielvs]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix(runs): say why the backend refused a run instead of that it did #2794 : 2 dependent PRs (#2796 , #2798 )
• feat(tangent): brief the agent on naming, and on the project its runs belong to #2792 👈 (View in Graphite)
• feat(projects): fix cancelling, track shared projects, flag unreachable pipelines #2790
• feat(tangent): keep an agent's edits in frame on the canvas #2789
• feat(tangent): bring Tangent onto the dashboard #2787
• feat(tangent): show a project's runs on the tangent page #2786
• fix(projects): show an agent's run on the project it belongs to #2785
• fix(agent): submit a spec that came from the editor's store #2784
• chore: increase max turns in remote agent #2779
• fix(tangent): stop the tab strips scrolling up and down #2777
• feat(projects): make the agents' instructions a project document #2776
• feat(tangent): list the pipelines the backend holds #2775
• feat(projects): show a project's documents on both pages #2774
• fix(tangent): project window parity — share, new-session links, agent-created pipelines, and a folded-away project window #2773
• refactor(projects): describe a project's resources one way #2765
• feat(projects): delete and share a project from either page #2764
• feat: open a new project ready to work in #2763
• feat: let the project page and Tangent reach each other #2762
• fix: keep a long project name inside the tile it belongs to #2761
• feat: say so when Tangent cannot be reached #2760
• feat: open a project where the work happens #2759
• feat: run a pipeline inside a project #2754
• feat: add pipelines held in this browser to a project #2745
• feat: project page #2738
• feat: create a project from a tile in the grid #2735 : 2 other dependent PRs (#2736 , #2737 )
• feat: projects dashboard #2734
• chore: tangent - annotate runs submission to projectid #2758
• fix: tangent - proper debug sequence system prompt #2757
• fix: tangent - quick run button from mini content window #2744
• fix: tangent - remote agent send delta immediately #2743
• fix: tangent - mint proper authorization with tangent #2742
• feat: tangent - debug in tangent sequence #2741
• chore: add autolayout tool #2740
• feat: tangent - resource management via document entity #2733
• feat: tangent - interactive chips in tangent chat #2732
• chore: save id stack to replay ids on reloads #2731
• refactor: tangent - migrate tangetproectcontext onto mobx #2730
• feat: tangent - keep track of open tabs while switching sessions inside project #2729
• feat: tangent - remote agent for runview and editor #2728
• refactor: tangent - structured workarea target #2727
• feat: tangent - embedded pipeline run view #2726
• feat: tangent - embedded pipeline editor #2725
• feat: tangent - dynamic workarea remote tools #2724
• feat: tangent - resources management in project view #2723
• feat: tangent project view page #2722
• feat: workspaces and projects service #2720
• chore: api client for workspaces and projects #2719
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.