Skip to content

Bug: Squad greets all users as 'Brady' β€” hardcoded name in template filesΒ #977

Closed

Description

@bradygaster

The Brady Bug πŸ›

Squad calls every user "Brady" regardless of who they are. This happens because template files that ship to user repos contain hardcoded "Brady" examples, and LLMs treat these examples as patterns β€” using "Brady" literally instead of the actual git config user.name result.

Root Cause

Three sources of contamination in template files:

1. squad.agent.md (coordinator template)

Line Content Problem
~35 "Hey Brady, what are you building?" LLMs use this greeting literally
~245 "add Brady as PM" Routing example with hardcoded name
~250 "add Brady as PM" (second instance) Same
~295 "Brady's favorite β€” make it instant" Comment with hardcoded name

2. init-mode/SKILL.md (init walkthrough)

Line Content Problem
~23 "Hey Brady, what are you building?" Same greeting pattern
~85-86 git config user.name β†’ "Brady" example Walkthrough shows "Brady" as the result

3. Template sync amplifies it

These files exist in 5 synced locations (template sync is enforced by tests):

  • .squad-templates/squad.agent.md (canonical)
  • .github/agents/squad.agent.md
  • packages/squad-cli/templates/squad.agent.md
  • packages/squad-sdk/templates/squad.agent.md
  • .copilot/skills/init-mode/SKILL.md + 2 package copies

Fix

Replace hardcoded "Brady" with generic placeholders in all template examples:

  • "Hey Brady, what are you building?" β†’ "Hey {user}, what are you building?" (or remove the name entirely)
  • "add Brady as PM" β†’ "add {name} as PM"
  • "Brady's favorite" β†’ remove or genericize the comment
  • Init walkthrough: use "{user}" or "Alice" as the example name

Important: Blog posts, proposals, and docs that reference Brady as the project founder are legitimate content and should NOT be changed.

Reproduction

  1. Install Squad in any repo
  2. Run squad init and go through team setup
  3. Observe that the coordinator greets you as "Brady" regardless of your git config user.name

Impact

Low severity but high creep factor. Users have reported it as "cute... but creepy."

Activity

  1. pinned this issue on Apr 14, 2026
  2. unpinned this issue on Apr 14, 2026
  3. added a commit that references this issue on May 2, 2026
    36eed05
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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions