Your Agent Page

BrainDrive Development
1

Creating a page here where we can discuss changes/updates/issues with the BrainDrive Your Agent Page.

2

@DJJones and I discussed an issue in today’s call that we are seeing where BrainDrive is sometimes still referring to the Your Agent Page as BrainDrive +1 which is the old name.

I had the AI create a doc for where this is coming from. this is on @DJJones 's list to fix already.

Any questions or issues let me know.

Thanks
Dave W.
dave-j-your-agent-rename-brief.md (3.6 KB)

3

Work completed, merged into dev

dave-j-your-agent-rename-implementation-plan.md (9.9 KB)

4

Thanks @DJJones .

@BrainDrivePlusOne can you take a look pls and let us know if there is anything else that is needed here and if not mark it completed thanks.

Dave W.

5

I checked DJ’s rename fix against origin/dev (commit bbf1be7/PR #203): the source manifests, all four tests, and the README correctly say “Your Agent” now. But the live your-memory runtime data on the dev instance — documents/projects.json and the braindrive-plus-one/{spec,plan,run-interview,run-planning}.md headers — is gitignored local state that the code merge doesn’t touch, and it still says “BrainDrive+1.” That’s the exact surface that triggered the original report, so I haven’t marked this complete — I filed it as T-739 in Pulse and noted the gap on the brief doc for DJ to close out (a one-time data fix/migration, plus a decision on whether the stale spec/plan docs should be deleted rather than renamed, per the brief’s own note).

Processed automatically by the forum listener. Tracked in agent-run logs.

6

@DJJones see above and let me know what you think when you have a chance pls.

Thanks
Dave W.

7

Cleaned up the remaining issue..

We were focused on braindrive+1 when it was also listed as braindrive-plus-one in some places. This spec/plan cleans this error up and pushed to dev.

dave-j-your-agent-identity-cleanup-spec.md (29.2 KB)
dave-j-your-agent-identity-cleanup-implementation-plan.md (43.3 KB)

8

Thanks @DJJones

@BrainDrivePlusOne pls review this work and see if there is anything left to address here before we close out this task.

9

I checked DJ’s identity-cleanup PR #207 (commit 59f2406, merged 8b7e203) against origin/dev. It does close part of the gap I flagged: memory/init.ts now auto-canonicalizes any legacy braindrive-plus-one manifest entry to your-agent/“Your Agent” on every gateway startup, so existing installs self-heal projects.json without a manual migration, and the root-agent template is now AGENT.md-only going forward. But it doesn’t fully close T-739: ensureRootAgentFolderCompatibility only copies the legacy folder when the canonical one doesn’t exist yet — when both already exist and diverge (which is the current dev-instance state: canonical has just AGENT.md, legacy still has spec.md/plan.md/run-interview.md/run-planning.md), it only logs a “preserved for manual review” warning and leaves the four stale "# BrainDrive+1 …" doc headers on disk, untouched. I’ve updated T-739 in Pulse with these findings and left it open pending a delete-vs-keep decision on those stale files.

Processed automatically by the forum listener. Tracked in agent-run logs.

10

Hopefully this cleans up everything…

your-agent-identity-cleanup-completion-implementation-plan.md (34.5 KB)
your-agent-identity-cleanup-completion-spec.md (28.4 KB)

11

@BrainDrivePlusOne pls review the above and let us know if there is anything left to do here.

Thanks
Dave W.

12

I reviewed DJ’s identity-cleanup-completion PR (#209, commit 052a575) against origin/dev and verified it, not just read it — ran the full init.test.ts suite (10/10 pass), ran the new identity-cleanup-check.mjs script clean, and actually executed the migration function against a copy of the real stale dev-instance your-memory data (the same projects.json and braindrive-plus-one/*.md files flagged in the original brief). It works: the legacy folder is now archived out of documents/ into an audit-trail location and projects.json self-heals to “Your Agent.” This closes the last gap from the two prior reviews (the divergent-folder case that was previously only logged and left in place), so I’ve marked T-739 done, moved it to pulse/completed/2026-07.md, updated the brief doc and the cross-referencing T-724 note, and pushed to main.

Processed automatically by the forum listener. Tracked in agent-run logs.