I’m more curious how this impacts trust than anything else.

In the span of basically a week, they accidentally leaked Mythos, and then now the entire codebase of CC. All while many people are complaining about their usage limits being consumed quickly.

Individually, each issue is manageable (Because its exciting looking through leaked code). But together, it starts to feel like a pattern.

At some point, I think the question becomes whether people are still comfortable trusting tools like this with their codebases, not just whether any single incident was a mistake.

▲

bottlepalm 4 hours ago | parent | next [-]

Not much impact, Codex is already open source. The real value is in the model itself and the ability to use it with a subscription. Something you can't do legally with a clone of this code.

The only thing I found interesting about this leak is just how much of a rats nest the code base is. Like it actually feels vibe coded without a shred of intelligent architecture behind it.

Regardless, you can't beat the subscription and model access despite the state of the code base, so I still use Claude Code daily and love it.

	▲	internet101010 3 hours ago \| parent \| next [-]
		I just hope it doesn't turn out like n8n. I built a few things, wanted to make changes, looked at the code base, opened the devcontainer, noped out after being mortified by the sheer number of warning and dependency issues, threw away all of my work, uninstalled, didn't think about it again. Two months later it was CVE after CVE.
	▲	Aperocky 3 hours ago \| parent \| prev [-]
		Exactly, we should be able to build on top of the tooling agents. They are a dime a dozen similar to the models. Power(money) lies with NVDA and people who can best harness this power.

▲

redanddead 3 hours ago | parent | prev | next [-]

Idk. This is making leaps. Idc that their tools leaked. I paid 140$ for CC the other day even after getting sometimes not 100% uptime on the lower plan. If anything this leak is most in line with Anthropic's ethical model. They're failing upwards in my opinion

▲

SequoiaHope 4 hours ago | parent | prev | next [-]

Something that has been clear to me in using it, aside from direct claims by the authors, is that Claude is itself vibe coded slop. The number of random errors I get from using various parts of the web UI or CC that should work feels high for such a popular product. But they’re so deep in the vibes that I don’t think they can tell when some path in their web UI is broken. I tried to share a public link to a chat and it asked me to login when opening it on another computer. I tried to download a conversation and it threw an error. When I download markdown output the download succeeds but the UI throws an error. I have tried to control the behavior of Claude Code in tmux using documented flags but I can’t seem to get them to work properly. Agent teams don’t clean up their tmux windows, making the view a mess after they run. Claude code is an amazing product that I love and also it is itself vibe coded slop.

	▲	jgilias 2 hours ago \| parent \| next [-]
		And there’s no reason why they couldn’t vibe fix the issues if there was a process to report the bugs. Fixing issues like that could also be something that’s fully automated. Provided there’s a good test suite (not a given).
	▲	an hour ago \| parent \| prev [-]
		[deleted]

▲

mnkyprskbd an hour ago | parent | prev [-]

No one will remember this in 4 weeks or less.