Skip to content

Allow a lead name per project - #15

Merged
Atoll92 merged 3 commits into
Atoll92:mainfrom
harrisonoconnorhover:codex/per-project-lead-names
Oct 28, 2026
Merged

Atoll92 merged 3 commits into
Atoll92:mainfrom
harrisonoconnorhover:codex/per-project-lead-names

Conversation

@harrisonoconnorhover

Copy link
Copy Markdown
Contributor

The global lead name makes calls from different projects look alike. Add “Name for this project” under Characters, with the project folder shown below it. Clearing it restores the global name (or Margot); the editor's agentStandup.leadName still takes priority. Live calls, replays, forks, agent lists and transcripts all use the selected name.

Project identity comes from the session's original working directory, so Claude Code, Codex and Vibe sessions in the same folder share a name, while provider buckets and similarly dashed folder names stay distinct. Each override uses a separate preference key so two windows editing different projects retain both changes through the existing patch mechanism. Reset affects the displayed project's name, leaving other projects alone. If the first working directory arrives after a live call opens, incremental updates refresh its project identity and names before subsequent edits are saved, including updates with no new timeline event.

Refs #14.

Validation:

  • Implementation run, full repository suite after the late-project correction: 149 passed, 0 failed, 0 skipped (159.7 seconds).
  • Independent Astra review: 44 focused tests passed; the late-project regression fix was verified, including metadata-only updates. No remaining actionable defects were found within that review’s coverage.
  • Focused project-name browser suite: 7 passed, 0 failed/skipped. Astra's original late-project reproduction also passes (1 test); the new regression was confirmed failing before the fix. The updated incremental API contract test passes (1 test).
  • Browser cases cover two stale windows, reload, live/replay switching across providers, same-folder sessions, long first records, initial-cwd stability, editor precedence, clearing/reset, Unicode/sanitization, forks and name collisions, missing project metadata, and late project identity followed by editing and reload (with and without new timeline events).
  • Translation checks, JavaScript syntax, CLI build/version, and standalone landing-page name helpers pass.
  • Built package restart with a fresh browser profile passes; desktop and mobile settings views visually checked.

Tested on macOS with Node 22 and headless Chrome; no Windows/Linux or packaged Electron/VS Code GUI run. New locale strings follow the existing AI-drafted, not-native-reviewed catalogue convention.

@vercel

vercel Bot commented Oct 27, 2026

Copy link
Copy Markdown

@harrisonoconnorhover is attempting to deploy a commit to the DG_TEAM Team on Vercel.

A member of the Team first needs to authorize it.

@Atoll92
Atoll92 merged commit e7a59b2 into Atoll92:main Oct 28, 2026
1 of 2 checks passed
@Atoll92

Atoll92 commented Oct 28, 2026

Copy link
Copy Markdown
Owner

Merged, thank you! I added one follow-up commit (0c4d6dd): the project key now prefers the folder the session is filed under, so a session that started in a scratch folder, an old transcript without cwd, or a live one before its first cwd line all share their project's name, and a trailing slash no longer splits a folder in two. Your tests made this easy to check.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants