Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
SkyPuncher
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
91.
▲
by
SkyPuncher
6mo ago
And it’s working larger because the other models haven’t figured out how to provide a consistent, long running experience.
92.
▲
by
SkyPuncher
6mo ago
I’ve never been actually rate limited. Usage limits display in yellow when you’re above 90%. At the limit, you’ll get a red error message.
93.
▲
by
SkyPuncher
6mo ago
This is the problem most people are facing. Before March, I had hit the rate limit as single time. That involved security audit of our entire code base from a few different angles. As of now, I’m consistently hitting my 5 hour limit in les
94.
▲
by
SkyPuncher
6mo ago
I skimmed the issue. No wonder Anthropic closes these tickets out without much action. That’s just a wall of AI garbage. Here’s what I’ve done to mostly fix my usage issues: * Turn on max thinking on every session. It save tokens overall be
95.
▲
by
SkyPuncher
6mo ago
Yes, but the problem with these models isn't a gradual shift, it's a step function. With a gradual shift, the world has time to react and adapt.
96.
▲
by
SkyPuncher
6mo ago
Further, Opus identified most of the vulnerabilities itself already. It just couldn’t exploit them. Mythos seems much, much more creative and self directed, but I’m not yet convinced the core capabilities are significantly higher than what’
97.
▲
by
SkyPuncher
6mo ago
No, but I doubt there are more than 100. The magnitude is so small that anonymity is essential broken.
98.
▲
by
SkyPuncher
6mo ago
That part of things is what really made this entire argument all apart of me. There are ~50k psychiatrists in the US. Roughly, 1 in 10k people in the US is named Scott. Mathematically, that means knowing "Scott is a psychiatrist"
99.
▲
by
SkyPuncher
6mo ago
I've switched to max thinking mode as my default and that's helping in some capacity. It's not necessarily back to where it was, but it's not desk-flipping bad.
100.
▲
by
SkyPuncher
6mo ago
Keep in mind that Opus detected most of these vulnerabilities, it just didn’t exploit them (says so much in the article). I’m honestly not convinced this is changing the landscape significantly. It’s simple a bit better at self directing.
101.
▲
by
SkyPuncher
6mo ago
Yes, I agree. I’m about to drop Claude Code because it’s become literally unusable. Today, Opus went in circles trying to get a toggle button to work.
102.
▲
by
SkyPuncher
6mo ago
I was reading the Glasswing report and had the same thought. Most of the stuff they claim Mythos found has no mention of Opus being able to find it as well. Don’t get me wrong, this model is better - but I’m not convinced it’s going to be t
103.
▲
by
SkyPuncher
6mo ago
It just doesn't listen. Literally a conversation that I just had: * ME: "Have sonnet background agent do X" * Opus: "Agent failed, I'll do it myself" * Me: "No, have a background agent do it" * Opus:
104.
▲
by
SkyPuncher
6mo ago
My biggest frustration right now is the seeming complete loss of background agent functionality. Permissions seem completely botched for background agents right now. When that happens, the foreground agent just takes over the task despite:
105.
▲
by
SkyPuncher
6mo ago
Claude is exceptionally better at long running agentic sessions. I keep coming back to it because I can run it as a manager for the smaller tasks.
106.
▲
by
SkyPuncher
6mo ago
Those load shedding statements are infuriating. I’ve literal had sessions where we just get through planning a giant feature and I say “get started” with the response being “okay, we’ll pic up tomorrow “
107.
▲
by
SkyPuncher
6mo ago
This isn't the case. I basically did an entire business/project/product exploration before building the first feature. Even after deleting everything from the first feature and going back to the checkpoint just before initial
108.
▲
by
SkyPuncher
6mo ago
Yep. I was doing voice based vibe-coding flawlessly in Jan/Feb. I've basically stopped using it because I have to be so hands on now.
109.
▲
by
SkyPuncher
6mo ago
I'm going absolutely insane with this. Nearly all of my "agent engineering" effort is now figuring out how to keep Opus from YOLO'ing is own implementation of everything. I've lost track of the number of times it&#x
110.
▲
by
SkyPuncher
6mo ago
I've noticed this as well. I had some time off in late January/early February. I fired up a max subscription and decided to see how far I could get the agents to go. With some small nudging from me, the agents researched, designed
111.
▲
by
SkyPuncher
7mo ago
This is only an issue between 12pm and ~4pm ET. If I work at any other time of day, I never hit my usage limit.
112.
▲
by
SkyPuncher
7mo ago
Naw, it's not that. This is business-day usage for all of it.
113.
▲
by
SkyPuncher
7mo ago
That's a had sell to a finance team.
114.
▲
by
SkyPuncher
7mo ago
Professional software development. I literally have 2 to 5 terminals running all day.
115.
▲
by
SkyPuncher
7mo ago
I literally hit my 5 hour window limit in 1.5 hours every single day now. 2 weeks ago, I had only hit my limit a single time and that was when I had multiple agents doing codebase audits.
116.
▲
by
SkyPuncher
7mo ago
Just give me a subscription tier where I’m not being blocked out every afternoon. Im hitting rate limits within 1:45 during afternoons. I can’t justify extra usage since it’s a variable cost, but I can justify a higher subscription tier.
117.
▲
by
SkyPuncher
7mo ago
> If the programs you’re using refuse to let you remove those icons (or they keep re-adding them against your wishes) then those programs are bad citizens and you should probably stop using them! I always love these types of arguments. P
118.
▲
by
SkyPuncher
7mo ago
You’re seeing that primarily because it’s what people can show off easily. Side projects they do for fun. I use all of this stuff daily at work. Normally, I’m working on 2 to 4 features in parallel (so worktrees). This might not be simultan
119.
▲
by
SkyPuncher
7mo ago
But, pinning has prevented most of the recent supply chain attacks. As long as you don't update your pins during an active supply chain attack, the risk surface is rather low.
120.
▲
by
SkyPuncher
7mo ago
These tools are useful, but I can't help to feel like they're solving the wrong part of the problem. I really don't have much concern that an agent has access to one of my credentials. Outside of production, most of these cre
More ›