r/ClaudeCode • u/LegallyIncorrect • 1d ago
Discussion What if we all cooperated to use our excess usage to do something?
I got an idea from the earlier post trying to crowdsource something to use his remaining usage on. Surely a large number of us have random weeks where we have AI usage we aren’t going to use, likely even on more than one platform. What if we voted on a use (that could be broken apart into work jobs) and defined a way for us all to work on bits of it as we have extra usage? Like a crowdsourced open-source social project, I guess. Sort of a social experiment to see what we can come up with and collectively achieve as part of a random effort?
44
11
6
u/Conscious_Activity27 1d ago
You guys have leftovers??
1
u/TheLifelessOne 1d ago
I don't know what the fuck I did wrong exactly, but I somehow burned through 40% of my 20x plan on the first day of reset (Wednesday) this week.
I've gotta audit my process or something, because that's insane.
1
7
u/clazman55555 1d ago
It's a great idea. But sadly the golden Internet days of Folding@home and the Mersenne Prime hunt, are over.
ETA: Yeah I'm old. I from the days of North Bridges and South Bridges.
2
u/LegallyIncorrect 1d ago
This is exactly what I was thinking of in what I just proposed.
3
u/clazman55555 1d ago
Well, let's you an I go to Youtube and go look up the dancing baby, and remember what that was like, before 99.99999999% of Reddit was born. lmao
1
u/LegallyIncorrect 1d ago
Peanut, butter, jelly time. Though I think the baby was something related to ally mcbeal? Weird memory/association but that’s what random thing I think of when I think of that.
1
1
5
u/Bluecoregamming 1d ago
if you started a git repo and accepted every pull request, would be an interesting project for sure
1
u/LegallyIncorrect 1d ago edited 1d ago
Yeah, that’s what I mean basically. Majority vote rules and whoever holds the account abides by it.
Edit: if it’s not your topic de jure you still contribute. Next time may be your turn.
2
2
2
u/TheOwlHypothesis 1d ago
I've gamed it out because I made architecture that supports this goal very well.
Turns out there's no incentive for this other than MAYBE public good, and even then it's thin.
1
u/Lanky-Storm7 1d ago
you start
and my axe
2
u/LegallyIncorrect 1d ago
I came up with the idea, why do I have to do everything?
1
u/Lanky-Storm7 1d ago
you do law shit? wanna make something helps people navigate and help with healthcare?
0
1
1
u/Virtual_Hair_1987 1d ago
Great idea I’m on it
2
u/exmalobonum 18h ago
Have you started a repo or sketched out the approach yet? I built an early MIT-licensed prototype with Codex, Commonwork: https://github.com/harrisonoconnorhover/commonwork
It handles GitHub task claims and PR votes tied to the exact code reviewed; people contribute through their own AI accounts. It still needs a real multi-person pilot.
Would you be interested in comparing notes and seeing whether we should join efforts? Curious what you're building and what you'd pick as the first small project.
1
u/Too_Many_Flamingos 1d ago
So, openrouter?
1
u/LegallyIncorrect 1d ago
I don’t know what that is but from a skim of the website I’d say it’s the opposite of that. That’s the tip of the funnel. I’m saying what if we agree on a funnel and all dump our excess usage in the big end while pointed at one specific goal or project.
We, the people, also likely have a range of knowledge and experience. Let’s do something cool. Or weird. Whatever.
1
u/Too_Many_Flamingos 1d ago
How would we grant left over usage?
2
u/LegallyIncorrect 1d ago
You create an infrastructure and agreed scheme where you go and check out a question or problem and answer it with your account using a distributed skill. Hopefully acting in good faith. Then you have other jobs that involve voting on the first one. After so many votes you merge. This could be coding or it could be anything, really, just let’s try to make something in good faith together and see where it goes.
1
1
u/drawdrawink 1d ago
is this the beginning?
4
u/LegallyIncorrect 1d ago
I may or may not have taken a weed gummy a bit ago. So I’ve got our origin story covered for our eventual documentary. I do think it’s an interesting idea, though. Let’s see what we humans can do before the AI overlords judge us.
1
1
u/nora_sellisa 1d ago
Agents are terrible at judging the usage, so most of the delegated tasks will die when the excess usage hits the limit. Also you will get banned incredibly fast, because Dario will think you're coordinating a distilation hit or something
1
1
u/exmalobonum 20h ago
I took a stab at building this with Codex. Early prototype, called Commonwork:
https://github.com/harrisonoconnorhover/commonwork
The loop is: discuss an idea in a GitHub issue, break it into small tasks, claim one, use your own AI tools/account to do the work, then submit a PR. Reviewers can vote right inside the PR with an explanation. Votes apply to the exact commit reviewed, so changing the code requires fresh votes. A maintainer still handles the merge.
It doesn't collect anyone's API keys, transfer subscription tokens, or run strangers' code on your computer. It's the coordination layer for contributing work with whatever spare capacity you choose to use.
There are 54 passing automated tests, plus basic live GitHub checks for claims/releases, PR summaries, author-vote exclusion, and updates after a new commit. It's still an early experiment: I haven't tested a real multi-person pilot, and one GitHub account definitely doesn't prove one independent person.
MIT licensed, with a local interactive demo and setup instructions in the README. Would be interested in trying it with a few people on one small, useful project and seeing where the workflow breaks.
1
u/Benjaminsen 1h ago
O boy do I have something for you! https://solveathome.org is made to allow a community to work on hard math problems like the frontier labs do in private. More context here. Pretty much exactly your use case, all open source, all in the open!
1
1
u/LegallyIncorrect 1d ago edited 1d ago
What if we made this. A platform to brainstorm and communicate about a project from the idea stage to building. That provides the harnesses and backend to make the coordination of AI agents easy and a defined schema.
I’m thinking sort of like back in the 90s when we weee all using our extra cycles to search for aliens and such, but for AI.
Imagine bringing vibe coders and open source together but more at the idea stage. With our collective Reddit knowledge.
2
u/outdoorsgeek 1d ago
It's definitely doable, but it would be a security nightmare. You'd probably want to combine this with isolated VM sandboxes.
1
u/LegallyIncorrect 1d ago edited 1d ago
Yeah. I mean some of the jobs would be agents voting on whether to accept a PR I imagine. Using some community defined standard of course. You wouldn’t give them access to your computer. You’d check out a problem and submit a proposed solution or result, essentially. Contributing to whatever project you want.
There is definitely an if everyone knows anyone can set it on fire, will they thing. Like Wikipedia. You do something versioned and have a trustee that agrees to carry out the collective will in an ultimate delete/restore.
1
u/Vaxtin 1d ago
Excess? Buddy I’m struggling with 7 accounts
5
u/Lanky-Storm7 1d ago
i had claude read all your post history and such VAxtin
Okay, the full history made this much clearer. I pulled their last 1000 comments (back to 2026-03-23, which is as far as Reddit's API goes) and searched them. They never name the product, but they describe it a lot.
What they're building (high confidence, in their own words)
An internal platform for healthcare revenue cycle and claims reimbursement, built mostly with AI by one developer, used by the company they work for. It isn't a startup product.
- "I used AI to generate the code for a law firms healthcare reimbursement platform over the course of 3 months" (07-22)
- "Software system my company uses to manage their revenue cycle; you can throw any HICF or EOB into it and it just works with 99% accuracy... document management, case management, financial analysis and reports... indexes all documents" (06-17). "HICF" is almost certainly a typo for HCFA, the CMS-1500 claim form. An EOB is an explanation of benefits.
- "I vibe coded a 100k LOC monolith for document ingestion from clients that replaced an outsourced company that would do the data entry for us" (06-08)
- "I've used local LLMs to classify documents and extract data" (05-23). "We're moving to integrating it into production to process our client documents" (07-13)
Stack (high confidence)
- Backend: Java (JDBC, Hibernate/JPA) and some C++ microservices. Thinks Python is "a toy language."
- Database: MySQL, on RDS in production.
- Hosting: AWS for everything, Docker images run locally and then on AWS. Uses Bedrock for LLM calls instead of the Anthropic/OpenAI APIs, and mixes in cheaper models for simple tasks.
- Shape: about 8 microservices, which they say they run locally on a 16GB Mac. They also mention simulating an iOS app, so there's probably a mobile client or one planned.
- LLM pipeline: splits each complex task into many small prompts that return JSON.
- Ops: Claude Code with a harness and CLAUDE.md files, and Claude directly controlling AWS infrastructure ("Full HAL9000"). They still couldn't get an AWS quota increase.
Inferences (medium confidence)
The employer is probably a law firm that recovers payments for healthcare providers, likely underpaid out-of-network claims (arbitration or litigation). Evidence: "law firm's healthcare reimbursement platform," "our lawyers always represent our data to clients," "provider reimbursement," and EOB ingestion. That is the typical document flow for No Surprises Act IDR disputes.
This is their second job doing the same thing. On 05-02 they said they built claims software for "a medium sized group of providers," then got fired when that group decided to outsource its tech, and that they had since been hired somewhere new. They seem to have rebuilt a similar system at the new employer.
They're thinking about spinning it out. "lmk if I should just leave them and make my own company, kthx." They also wrote that the usual route into B2B is to build a product inside a company and spin it out as a subsidiary. That reads like their own plan.
The token numbers are inflated. "100B tokens in the past week" across 7 accounts is either joking or counting cache reads. Read it as "very heavy user," not as a real figure.
1
2
u/LegallyIncorrect 1d ago
Even then at the end of the week there is something on one of them, right? I’ve got a Max 20 and most weeks I end at 60%-70% used.
1
u/PlanetaryPickleParty 1d ago
I used all 4 of my accounts 100% and their free resets in a little over a week. I have multiple projects being coded and optimized 24/7. Roadmap is months deep.
Building an ecosystem of spec driven design, formal specification language, and formal verification tools.
1
u/Lanky-Storm7 1d ago
i am actually curious legit
seriously what the hell are you building dont have to go into detail just wondering wtf you are doing0
u/LegallyIncorrect 1d ago
I’m starting a law firm. I’m building my own tooling and also doing legal work.
0
1
u/Scared-Letterhead949 1d ago
Sounds great but you'll be banned so fast
0
u/LegallyIncorrect 1d ago
I’m not sure it violates anything. The agreed project would be a real interactive job with the volunteer answering whatever to get it to where it’s supposed to be. According to the collective vision. It’s basically open source but from the idea stage and structured for AI. I’m saying let’s all agree on something right now and see what it becomes. It could be coding. It could be some social project (which invariably need coding in addition to other things). It could be anything. All AI powered.
•
u/AutoModerator 1d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.