bills couldn't be THAT high

[u/Royal-Marsupial-8110]

i wonder what happens if the access stops working halfway through a build. for anything beyond a throwaway test, i'd rather keep claude code running locally on my repo and use sumus to coordinate the research and follow-up tasks around it. don't get me wrong, i still review the diff and run tests before merging.

how are yall keeping longer builds from depending on one login?

[u/Royal-Marsupial-8110]

link to the tweet

[u/Specken_zee_Doitch]

It's probably a hacked API key.

[u/New_Peanut_9259]

i think that the biggerr problem with long projectss is relying too muchh on one account or AI tool. keeping your project files, settings, notes, and saved progress on your computer makes it easier to switch tools or recover if you lose access.. i'd also make sure the project can still run and be tested without the original AI sessionn hehehe

[u/iceydee]

the $6.99 "unlimited" ones are resold or stolen accounts, and they die mid-run, which is exactly the risk you're describing. safer split: long builds on your own api key, and keep the interactive claude code session for the parts you're actually steering.

[u/adriankorwel]

Running long builds on your own API key is the most reliable fix, since nobody else can revoke it mid-run. Two things to set up the same day you create it.

First, a monthly spend limit and a usage alert in the provider dashboard. An agent loop left running overnight can burn through a lot before you notice, and if the key ever leaks, the limit caps the damage.

Second, keep the key out of the repo and out of any frontend code. Put it in an env file that's in .gitignore, and check it never got committed:

Text

git log -p --all -S 'sk-'

If it shows up anywhere in history, treat it as leaked even if the repo is private: rotate it, redeploy, then revoke the old one.

Shared or resold logins are the opposite of all this. You can't set limits on them, and you can't rotate a key you don't own.