crewrota

Run Claude Code as any of your crew members

npm install -g crewrota v0.2.0

Then the plugin, in your main Claude Code:
claude plugin marketplace add pasindu-premachandra/crewrota
claude plugin install crewrota@crewrota

View on GitHub
PowerShell

PS C:\Users\you> crew

crewrota  pick a crew member

     member   5h                       week
  ›  main     ▖▖▖▖▖▖▖▖▖▖▖▖▖▖   42%     ▖▖▖▖▖▖▖▖▖▖▖▖▖▖   31%  
     side     ▖▖▖▖▖▖▖▖▖▖▖▖▖▖   71%     ▖▖▖▖▖▖▖▖▖▖▖▖▖▖   55%
     team     ▖▖▖▖▖▖▖▖▖▖▖▖▖▖   92%     ▖▖▖▖▖▖▖▖▖▖▖▖▖▖   83%
     + Add a crew member

     ship     ‹ home ›
     model    ‹ opus ›
     effort   ‹ high ›

  ↑↓ move   ←→ ship, model, effort   enter start   esc quit
The crew menu, drawn by crewrota itself with a demo crew. Ship, model and effort are remembered per member.

How it works

Crew members

Each member is one Claude login in its own config folder, signed in with Claude Code's own sign-in. Start one with crew <member>, or pick it in the menu.

Ships

Members on a ship share conversation history, memory, session folders and the ship's own MCP servers, and every member gets your main setup's skills, agents, commands and plugins. Join with crew ship join, step off with crew ship leave.

Quota at a glance

Each member's 5-hour and weekly usage sits next to its name in the menu, checked as it opens, so you can start on the one with room left.

Your crew moves with you

One command packs every ship into a single zip: conversation history, memory, session folders, MCP servers and your crew settings. One command unpacks it on the next machine and points every project at its new path. Each member signs in again, and that is all there is to redo.

  • Logins never leave the machine: crewrota never copies a credential.
  • Transcripts and MCP keys are plain text inside, so --password encrypts the zip with AES-256.
  • Projects on another drive now? Add --map E:\Projects=D:\Projects to the restore.
PowerShell

PS C:\Users\you> crew backup --to D:\backups --password

[OK] Backup written: D:\backups\crewrota-backup-20261026-2244.zip
[i] 1.1 GB, 1 ship, 3 members, encrypted
[i] No login is in it: after a restore, each member signs in again with crew login <member>.

PS C:\Users\me> crew restore D:\backups\crewrota-backup-20261026-2244.zip --password

[i] Project folders C--Users-you renamed to C--Users-me: 12
[OK] Ship home (new): 1418 copied, 0 brought up to date, 0 already there, 0 kept beside a changed copy

[OK] Restored 1 ship and 3 members from D:\backups\crewrota-backup-20261026-2244.zip
[i] Logins are never in a backup. Sign each new member in:
  crew login main
  crew login side
  crew login team

Example output from crewrota 0.2.0; --password asks for the password first

Who has room left

For every member, a 5-hour bar and a week bar: the percent used and when each one resets. crew quota prints them in the terminal; crew widget keeps them on your desktop, and crew widget startup on opens it at login.

  • under 60%
  • 60 to 79%
  • 80% and up
crewrotaread 09:53

main

5h42%resets 12:10

week31%resets Thu 09:00

side

5h71%resets 10:40

week55%resets Sat 21:30

team

5h92%resets 13:00

week67%resets Mon 06:00

Example values

Commands

crw and crewrota are the same command as crew.

crew
Open the menu. Pick a member, its ship, the model and the effort, and the session starts.
crew use <member>
Make that member the current one. If it does not exist yet, crew offers to create it.
crew add <member>
Add a member: a new config folder, signed in with Claude Code's own sign-in.
crew <member>
Start a session as that member, with its ship and its remembered model and effort. crew run does the same for the current member.
crew ls
List your crew members with their ship, usage, email and organisation.
crew quota
Every member's 5-hour and week use as bars.
crew warmup
Send every member one short Haiku message, which starts its 5-hour window if none is running, then show the bars.
crew widget
The same bars in a small window on your desktop; crew widget startup on opens it at login.
crew ship create|join|leave
Create a ship, put a member on it, or take a member off it.
crew ship mcp add|list|remove
The MCP servers a ship gives its members, keys included, kept with the ship.
crew drop <member>
Drop a member. Its folder moves to removed/; its ship keeps the history.
crew setup
Install the default tools from upstream: one list with each command and where it lands, one yes. Anything already installed is skipped.
crew init
Write the project's root .claude/ folder into the current folder. It never overwrites a file.
crew backup|restore
Pack every ship, the member list and your settings into one zip, and bring it back on another machine. Logins are never in it; --password encrypts it.
crew doctor
Check the setup and report anything that needs fixing.

Windows first, macOS beta

Windows is the first platform. macOS is in beta.

Windowssupported

The primary platform.

macOSbeta

In beta.

Who it's for

For one person running their own Claude subscriptions, each logged in through Claude's own sign-in. crewrota never reads or stores your login.

See the Anthropic Consumer Terms and Claude Code legal and compliance.