An OpenCode user faced harassment after reporting a free AI usage loophole, drawing a bitter backlash in a GitHub thread that has since been deleted.
- Sarah Gooding
An OpenCode user who reported a loophole in its free AI usage limits became the target of harassment, including comments encouraging suicide, from people who blamed the disclosure for cutting off their supply of free AI. The GitHub thread has since been deleted, although an earlier version remains available through the Wayback Machine.
OpenCode is an open source AI coding agent that helps developers write, edit, and run code from a terminal, IDE, or desktop app. The MIT-licensed software can connect to commercial AI providers or locally hosted models. Its developer, Anomaly, also offers hosted model access, including free models with usage limits, and paid enterprise features such as centralized configuration and SSO integration. The reported bypass concerned the allowances on the free hosted models.
The report drew a flood of hostility in the project’s public issue tracker, with warm pillow wishes among the mildest responses. Other participants unleashed the kind of abuse that would ordinarily get someone banned from an open source project, openly encouraging suicide and pressing the reporter for identifying information.
A Call for a Fix Turned Into a Pitch for the Bypass# #
The report, opened on June 28, described limits tied to an IP address. Switching to a different address through a VPN allegedly restored access while preserving the coding session. The author claimed to have automated the process and kept DeepSeek V4 Flash and MiMo V2.5 running for weeks. They proposed tying limits to accounts and detecting rapid IP changes. The account was created 13 days before the report and has no public repositories, a sparse history consistent with a throwaway account.
In an odd reversal, the author inexplicably closed the issue as completed on July 31, then reopened it on August 24 to promote the very workaround they had originally proposed fixing. They complained about the available free models and said they wanted people who could not afford subscriptions to build more with them.
Three days later, the reporter claimed to have run 130 agents across concurrent sessions, hitting usage limits six times in four to five hours and continuing by changing IP addresses. By then, the author was advertising the same behavior they had initially proposed preventing.
The same technique was being discussed elsewhere. A September 5 Hacker News commenter described OpenCode’s per-IP limits and told readers that “if you get some high-quality proxies you can get basically unlimited agent compute.” The comment did not reference the GitHub issue, but it shows the workaround had circulated beyond that thread before the late-October backlash.
On October 1, OpenCode collaborator rekram1-node responded that enforcing limits without authentication was difficult and that abuse undermined the effort to let anyone try a coding agent at no cost.
“Broadcasting this isn't very helpful, it only serves to harm,” the collaborator wrote before closing the issue. The response did not announce a fix.
Commenters Attacked the Reporter and Kept Trading Workarounds# #
In late October, users traded conflicting accounts of whether changing IP addresses still restored access. Some said it had stopped working, while others offered additional workarounds. The attacks on the reporter escalated alongside those exchanges.
One GitHub commenter accused the author of gaining nothing from the disclosure, adding, “thanks for ruining it for us.” Other commenters wished suffering on the reporter, and at least two encouraged suicide.
The pile-on also included a supposed million-dollar reward. A commenter claiming to represent OpenCode offered the money if the reporter supplied their address. Replies joined in requesting identifying information, including the reporter’s “government name.” There is no evidence that the offer came from OpenCode.
Later replies quoted a participant telling others to stop harassing the reporter, only to accuse that person of being the author posting from another account. Other commenters challenged the reporter’s reversal, pointing out that they had first recommended closing the loophole, then reopened the issue and described using it extensively.
The discussion became a mix of personal attacks, arguments over the reporter’s motives, and requests for help keeping the bypass working. Some blamed the disclosure for losing access even as others continued to claim success. It’s unclear whether OpenCode changed its enforcement in response to the report.
The blame also spread to Reddit. In a post titled “The End of Long Free OpenCode Sessions”, the author complained that sessions had shrunk from hours to one or two prompts and claimed IP-switching workarounds no longer worked. “I didn't even know about this VPN bypass stuff, people like you ruined it for us,” one commenter told the Reddit poster. A reply redirected the blame with a link to the aforementioned deleted GitHub issue.
Others welcomed the prospect of tighter restrictions. “Well, if this helps my paid subscription to work much better, then it’s more than welcome,” another participant wrote.
The thread offered no settled explanation for the restrictions. Its author asserted that OpenCode now tracked hardware IDs and account metrics, without supplying evidence, while another commenter said changing a cellular IP still worked.
VPN Users Reported Access Problems# #
Reports of disrupted access predated the October 27 release. In an October 22 Reddit thread, users said free models were blocked after little activity, including users who said they were not using a VPN. An October 23 post described changing IP addresses successfully for two months before the workaround recently stopped helping.
In another Reddit discussion, a user said a longstanding VPN setup now produced a daily-limit message immediately upon opening OpenCode.
“I think the IP detection may be a bit over zealous?” the user wrote. After another participant attributed the restrictions to VPN-based abuse, the original poster asked why the offering was described as a free tier when it appeared available only to people without VPNs. Another commenter said changing servers still worked.
OpenCode contributor Tarquinen addressed network-level blocking in a separate GitHub issue, explaining that the restriction applied to the connecting network address.
“Shared VPN addresses are often flagged, and we can't make exceptions for individual users,” the contributor wrote.
The experiences remained inconsistent. In an October 27 Reddit discussion, one commenter reported usable access through a dedicated-IP VPN, while another described very low limits without using a VPN.
The Fix Status Remains Unclear# #
OpenCode made several infrastructure changes in October, including routing free-model requests through a newer inference service and tightening how it handles client IP information. An October 13 change addressed spoofed IP headers, but that is different from switching to a genuinely different IP address through a VPN. Whether those changes closed the reported loophole remains unclear.
The October 27 v2.2.0 release added visibility into usage and budgets but did not announce a fix for the reported bypass. Enforcement could also have changed on the hosted service independently of an application release.
The final comments preserved before the thread’s deletion still offered conflicting accounts of whether the workaround functioned. The thread remained accessible on October 28, after the release, and was subsequently deleted without a public explanation.
Socket contacted OpenCode for comment on the reported bypass and the thread’s removal but had not received a response at publication time.
Demand for AI Compute Accelerates# #
The rush to code with AI has reached a fever pitch, with developers chasing more capable models, longer sessions, and enough compute to keep fleets of agents running. AI demand is squeezing memory supplies and driving prices higher. At the high end of the local hardware market, Apple’s newly available 512GB Mac Studio configuration reached an eye-watering $29,799 with 16TB of storage.
In the OpenCode thread, that hunger for compute curdled into a pile-on. The reporter went from proposing a fix to boasting about running 130 agents through the loophole. Other users blamed them for spoiling the arrangement, hurled abuse, and kept asking how to get the free models working again. The thread captures the AI coding gold rush at its most frantic, with users scrambling to keep their agents running and searching for the next route around the limits.