4 ms·
These are good to append to your .bashrc or .zshrc (depending on your shell of choice) and they'll be picked up.
by vemv 9mo ago
These are good to append to your .bashrc or .zshrc (depending on your shell of choice) and they'll be picked up.
- onesandofgrain 9mo agoOh, shame, I use claude across 4-5 devices, but thanks anyways.
- wrsh07 9mo agoI would strongly encourage you to create a global shared bashrc for your various devices - my dotfiles repo has tremendously improved my life as an eng who needs to discard dev boxes occasionally (virtual dev boxes)
- ttoinou 9mo agoArent you going to be banned by using it on too many devices ?
- godzillabrennus 9mo agoI think they charge based on consumption, not devices.
- onesandofgrain 9mo agoThey charge based on consumption as the comment below me stated.
- ttoinou 9mo agoAh sorry, I was thinking about the Pro / Max plan, not API token usage
- Wowfunhappy 9mo agoThe Pro and Max plans don't have a device limit either. I frequently use Claude code in disposable virtual machines.
- hexbin010 9mo agoMore generically-named env vars should not be set as an "export" in a rc file like that (IS_DEMO/DISABLE_AUTOUPDATER etc). They'll get exported to every process spawned by the shell, which could have unintended consequences. You could instead eg: alias code='DISABLE_AUTOUPDATER=1 IS_DEMO=1 /usr/local/bin/code' or write a wrapper shell script (analyse/adjust $PATH if you're going to name it the same as an existing binary/script), eg #!/bin/bash export FOO=bar exec /usr/local/bin/code