3 ms·

I wasn't even aware that was possible. I will IMMEDIATELY do this. The mere fact this is necessary to stop their data-fiending is disgusting. You prepend it ev

I wasn't even aware that was possible. I will IMMEDIATELY do this. The mere fact this is necessary to stop their data-fiending is disgusting. You prepend it everytime you run Claude or do you slap that into an .env file?

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 ago
  Oh, shame, I use claude across 4-5 devices, but thanks anyways.
  - wrsh07 9mo ago
    I 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 ago
    Arent you going to be banned by using it on too many devices ?
    - godzillabrennus 9mo ago
      I think they charge based on consumption, not devices.
    - onesandofgrain 9mo ago
      They charge based on consumption as the comment below me stated.
      - ttoinou 9mo ago
        Ah sorry, I was thinking about the Pro / Max plan, not API token usage
        Wowfunhappy 9mo ago
        The Pro and Max plans don't have a device limit either. I frequently use Claude code in disposable virtual machines.
- hexbin010 9mo ago
  More 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
yearolinuxdsktp 9mo ago
You can also put these into settings.json.
mmh0000 9mo ago
> I wasn't even aware that was possible. That's why you should always read the manual! These aren't hidden and secret settings: https://code.claude.com/docs/en/settings https://code.claude.com/docs/en/settings And, if you really hate manuals, you can just ask Claude to write the settings for you =D
immibis 9mo ago
> to stop their data-fiending Every time you run it, it uploads most of your project's code to Anthropic's server. That's just how this category of product works. If you're disgusted by a survey...

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 ago
Oh, shame, I use claude across 4-5 devices, but thanks anyways.
- wrsh07 9mo ago
  I 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 ago
  Arent you going to be banned by using it on too many devices ?
  - godzillabrennus 9mo ago
    I think they charge based on consumption, not devices.
  - onesandofgrain 9mo ago
    They charge based on consumption as the comment below me stated.
    - ttoinou 9mo ago
      Ah sorry, I was thinking about the Pro / Max plan, not API token usage
      - Wowfunhappy 9mo ago
        The Pro and Max plans don't have a device limit either. I frequently use Claude code in disposable virtual machines.
hexbin010 9mo ago
More 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

yearolinuxdsktp 9mo ago

You can also put these into settings.json.

mmh0000 9mo ago

> I wasn't even aware that was possible. That's why you should always read the manual! These aren't hidden and secret settings: https://code.claude.com/docs/en/settings https://code.claude.com/docs/en/settings And, if you really hate manuals, you can just ask Claude to write the settings for you =D

immibis 9mo ago

> to stop their data-fiending Every time you run it, it uploads most of your project's code to Anthropic's server. That's just how this category of product works. If you're disgusted by a survey...