# Implementation Plan: Rename BrainDrive+1 Display Name To Your Agent **Status:** Merged to `dev`; live app verification pending **Created:** 2026-06-30 **Updated:** 2026-06-30 **Source brief:** `dave-j-your-agent-rename-brief.md` **Repo checked:** `/home/hex/Project/BrainDrive-Test-01` on `dev` **Merged PR:** BrainDriveAI/BrainDrive#203 **Merge commit:** `6f2929f2` ## Goal Ensure owner-facing and model-visible project display text uses **Your Agent** instead of **BrainDrive+1**, while preserving the internal project id `braindrive-plus-one`. The intended result is that the UI, gateway project manifests, starter memory defaults, live dev memory, tests, and public README all agree on the owner-facing name **Your Agent**. The model should not be fed `name: "BrainDrive+1"` through the project manifest or live memory context. ## Current State There is work to do. Confirmed remaining `BrainDrive+1` references that affect the requested fix: - `builds/typescript/gateway/projects.ts` still defines `ROOT_AGENT_PROJECT.name` as `BrainDrive+1`. - `builds/typescript/memory/init.ts` still defines the fallback seed name as `BrainDrive+1`. - `builds/typescript/memory/starter-pack/projects/projects.seed.json` still seeds `BrainDrive+1`. - `builds/typescript/your-memory/documents/projects.json` still has the live project name `BrainDrive+1`. - Tests still assert `name: "BrainDrive+1"` in: - `builds/typescript/memory/init.test.ts` - `builds/typescript/client_web/src/components/layout/AppShell.test.tsx` - `builds/typescript/client_web/src/hooks/useProjects.test.ts` - `builds/typescript/gateway/projects.test.ts` - `README.md` still says `Land on BrainDrive+1`. - `builds/typescript/gateway/server.ts` has one internal comment saying `behave like BD+1`. Confirmed nuance: - The live `builds/typescript/your-memory/documents/braindrive-plus-one/` files currently have `Your Agent` headers, not `BrainDrive+1` headers. - Those live files include `spec.md`, `plan.md`, `run-interview.md`, and `run-planning.md`, while the starter-pack `your-agent/AGENT.md` says Your Agent does not maintain its own `spec.md`, `plan.md`, interview procedure, or planning procedure. This is a separate cleanup decision, not required to complete the display-name rename. ## In Scope - Change only the owner-facing display name from `BrainDrive+1` to `Your Agent`. - Preserve every internal id and path using `braindrive-plus-one`. - Update default project manifests and fallback seeds used by new installs. - Update the live dev memory manifest so Dave J no longer sees the old display name in the current dev instance. - Update focused tests that assert the old display name. - Update public README owner-facing wording. - Optionally update the internal `BD+1` comment to reduce future confusion. - Run focused and broader verification checks after implementation. ## Out Of Scope - Renaming the internal id `braindrive-plus-one`. - Migrating folder paths away from `documents/braindrive-plus-one/`. - Changing aliases such as `braindrive-plus-one` -> `your-agent`. - Removing Ollama, BYOK OpenRouter, or provider choices. - Adding BrainDrive-owned provider keys to client config. - Editing historical `CHANGELOG.md` entries. - Editing `your-memory.*` backup or snapshot directories. - Broad client provider/settings regression unless a touched test reveals a direct failure. - Deleting the live Your Agent `spec.md`, `plan.md`, `run-interview.md`, or `run-planning.md` without an explicit product decision. ## User Stories 1. As Dave J, I want the app to call the landing assistant **Your Agent** so owner-facing messages do not use the retired **BrainDrive+1** name. 2. As a new BrainDrive owner, I want seeded starter projects to show **Your Agent** from first run so the sidebar, memory manifest, and model context are consistent. 3. As an existing dev-instance owner, I want the live memory manifest updated so the current running instance stops feeding `BrainDrive+1` to the model. 4. As a maintainer, I want tests updated with the intended display name while keeping the protected internal id stable. 5. As a maintainer, I want documentation and comments to avoid reintroducing the retired name in owner-facing contexts. ## Implementation Roadmap ### Phase 1: Tests First For Display Name Contract Write or update focused assertions before implementation: - Update expected project name values from `BrainDrive+1` to `Your Agent` in: - `builds/typescript/memory/init.test.ts` - `builds/typescript/client_web/src/components/layout/AppShell.test.tsx` - `builds/typescript/client_web/src/hooks/useProjects.test.ts` - `builds/typescript/gateway/projects.test.ts` - Keep assertions for `id: "braindrive-plus-one"` unchanged. - If existing tests only cover sidebar label overrides, add or adjust a direct assertion that the manifest/default project name is `Your Agent`. Verification: - `cd builds/typescript && npm run test -- --run memory/init.test.ts gateway/projects.test.ts` - `cd builds/typescript && npm run web:test -- --run src/components/layout/AppShell.test.tsx src/hooks/useProjects.test.ts` Expected result: - Tests fail before implementation only where `BrainDrive+1` is still produced. - Tests pass after Phase 2 implementation. ### Phase 2: Update Model-Visible Project Names Make the smallest rename diff: - `builds/typescript/gateway/projects.ts`: change `ROOT_AGENT_PROJECT.name` to `Your Agent`. - `builds/typescript/memory/init.ts`: change the `FALLBACK_PROJECT_SEEDS` entry name to `Your Agent`. - `builds/typescript/memory/starter-pack/projects/projects.seed.json`: change the seed name to `Your Agent`. - `builds/typescript/your-memory/documents/projects.json`: change the live dev manifest name to `Your Agent`. Guardrails: - Do not change `ROOT_AGENT_PROJECT_ID`. - Do not change the `PROJECT_TEMPLATE_ALIASES` mapping. - Do not rename folders. - Do not touch backup/snapshot directories. Verification: - Re-run the focused tests from Phase 1. - Run `rg -n '"name": "BrainDrive\\+1"|name: "BrainDrive\\+1"|Land on BrainDrive\\+1' README.md builds/typescript/gateway builds/typescript/memory builds/typescript/client_web/src builds/typescript/your-memory/documents`. Expected result: - No model-visible manifest/default project name remains as `BrainDrive+1`. - Remaining `BrainDrive+1` references, if any, are only approved historical or unrelated records. ### Phase 3: Docs And Comment Cleanup Update non-behavioral text: - `README.md`: change `Land on BrainDrive+1` to `Land on Your Agent`. - `builds/typescript/gateway/server.ts`: change the internal comment from `BD+1` to `Your Agent` or `root agent`. Verification: - `rg -n 'BrainDrive\\+1|BD\\+1' README.md builds/typescript/gateway/server.ts` Expected result: - No owner-facing README reference to `BrainDrive+1`. - No confusing internal `BD+1` comment in the touched gateway area. ### Phase 4: Live App Verification Verify the actual owner-facing behavior, not only static files: - Start the app from `builds/typescript` with the repo-standard command appropriate for the environment. - Open the dev instance and select **Your Agent**. - Send an owner-facing prompt that would normally cause the assistant to refer to the current page, such as asking what page/context it is using. - Confirm the assistant says **Your Agent** and does not say **BrainDrive+1**. Verification commands: - `cd builds/typescript && npm run build` - `cd builds/typescript && npm run web:typecheck` - `cd builds/typescript && npm run web:test` - `cd builds/typescript && npm run test` Expected result: - Build and tests pass. - The live owner-facing message refers to **Your Agent**. ## Open Items And Questions 1. Should `builds/typescript/your-memory/documents/braindrive-plus-one/spec.md`, `plan.md`, `run-interview.md`, and `run-planning.md` be deleted from the live dev memory because the starter-pack Your Agent template says those files should not exist? 2. If those files are deleted, should the deletion be limited to live dev memory, or should there also be a memory update/migration path for existing users who may have inherited those files? 3. Should tests explicitly protect against `BrainDrive+1` appearing in future project manifests, or is updating current expected values enough? 4. Should implementation happen from `dev` rather than the currently checked-out `main`, consistent with the repo instructions for normal development? ## Recommendations - Implement the display-name rename now; the brief is valid and the root cause still exists in the manifest/default seed path. - Do not rename `braindrive-plus-one`; keep it as a stable internal slug. - Treat live `spec.md`/`plan.md`/procedure deletion as a separate decision. It may be correct, but it is not required to stop the model from seeing `BrainDrive+1`. - Perform the code change on `dev` unless there is a specific release reason to use another branch. - Add a small regression assertion around the root agent project display name so future sidebar-only renames do not leave model-visible metadata stale. - Verify in the running app after tests, because the user-visible issue was triggered by live memory context, not just code defaults. ## Completion Checklist - [x] Tests updated to expect `Your Agent` while preserving `braindrive-plus-one`. - [x] Gateway root project default uses `Your Agent`. - [x] Memory fallback seed uses `Your Agent`. - [x] Starter-pack project seed uses `Your Agent`. - [x] Live dev `projects.json` uses `Your Agent`. - [x] README owner-facing wording uses `Your Agent`. - [x] Optional internal comment cleanup completed. - [x] Internal architecture-lint guard text no longer uses `BrainDrive+1`. - [x] Focused tests pass. - [x] `npm run build`, `npm run web:typecheck`, and `npm run web:test` pass. - [x] `npm run test` blocker documented: full suite currently fails in `memory/starter-pack-draft3-layout.test.ts` on Draft 3 starter-pack lint issues, including the open Your Agent artifact decision. - [ ] Live owner-facing app check confirms the assistant says `Your Agent` and not `BrainDrive+1`.