Skip to content

Update from v0.5.4 → v0.8.18 - unknown command: doctor #188

New issue
New issue
Closed
Closed
Update from v0.5.4 → v0.8.18 - unknown command: doctor#188

Description

@KevinUK
KevinUK
opened on Mar 4, 2026

I backed up .squad

Then ran:
npm uninstall -g @bradygaster/create-squad
npm install -g @bradygaster/squad-cli@0.8.18

And deleted .squad

Then ran:
squad init

squad doctor gives
Uknown command: doctor

squad --version is 0.8.18
node -v is 22.21.1

I've tried closing the terminal window and re-opening.
I've tried with a clean .squad folder (just using squad init)

Squad Status

Active squad: repo
Path: D:\test.squad
Reason: Found .squad/ in repository tree

Repo resolution: D:\test.squad
Global path: C:\Users\KevinUK\AppData\Roaming\squad
Global squad: not initialized

Also, which files/folders exactly are safe to copy to the new .squad?

agents (exclude scribe and ralph?)
casting (don't copy as they are .json?)
decisions (all of it seems good)
log (ok to copy?)
orchestration-log (ok to copy?)
skills (all of it seems good)
decisions.md
routing.md
team.md

Thanks!

Activity

  1. jeremythake commented on Mar 4, 2026

    @jeremythake
    jeremythake
    on Mar 4, 2026

    getting the same issue too.
    I followed scenario 2.
    https://bradygaster.github.io/squad/get-started/migration.html

  2. tamirdresher
    added a commit that references this issue on Mar 4, 2026

    feat: Wave 3 — docs migration, site engine, 5 guides, mechanical upda…

    786dbb2

  3. bradygaster commented on Mar 4, 2026

    @bradygaster
    bradygaster
    on Mar 4, 2026
    Collaborator

    On it! Sorry about that, will look into it. Some folks internally have updated with success - if folks have any issues upgrading please post them here.

  4. bradygaster
    closed this as completedin 15722ceon Mar 4, 2026

  5. bradygaster commented on Mar 4, 2026

    @bradygaster
    bradygaster
    on Mar 4, 2026
    Collaborator

    Hey @KevinUK — sorry about that! The doctor command was implemented but never wired into the CLI entry point. Classic "ghost command" bug. 😅

    Fix shipped: As of the commit just pushed to main, squad doctor now works in v0.8.18+. You can pull the latest with:

    npm install -g @bradygaster/squad-cli@latest

    To answer your migration question — here's what's safe to copy from your old .squad/ to the new one:

    Directory/File Safe to copy? Notes
    agents/ ✅ Yes — all of them Including scribe and ralph — their history is valuable context
    decisions.md ✅ Yes Your team's decision ledger
    decisions/ ✅ Yes Including inbox/
    routing.md ✅ Yes Your routing rules
    team.md ✅ Yes Your roster
    skills/ ✅ Yes Learned patterns
    casting/ ❌ Skip Regenerated automatically by the casting migration check
    templates/ ❌ Skip Overwritten by squad upgrade
    log/ 🟡 Optional Diagnostic archive — no harm copying, but not required
    orchestration-log/ 🟡 Optional Same as log/

    After copying, run squad doctor to validate everything landed correctly.

    We're also updating the migration docs to include this table so future upgraders don't have to guess. Thanks for reporting! 🙏

    @jeremythake — same fix should resolve your issue too. Let us know if you hit anything else.

  6. bradygaster
    added 2 commits that reference this issue on Mar 4, 2026

    docs: add file safety table to migration guide

    fb54b82

    docs(ai-team): nap command restored, doctor command wired, migration …

    1dc3bb6

  7. jeremythake commented on Mar 4, 2026

    @jeremythake
    jeremythake
    on Mar 4, 2026

    yep that fixed it

  8. tamirdresher
    added a commit that references this issue on Mar 4, 2026

    fix: wire squad doctor command into CLI entry point

    15722ce
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions