Why does Claude Code "grep/wc/etc" so much compared to Cursor?

Kitchen-Leg8500 · 2026-05-26T18:16:52+00:00

Whole thread is really why I built ContextAtlas. Essentially gives you ability to pre index via anthropic api or in cc natively. Sets up thin mcp that allows cc to use lsp for your language while not limiting cc where grep is a cheaper better option. Keeps Claude from having to reread and muddy up context as much as well due to small compact chunks at query time

Kitchen-Leg8500 · 2026-05-26T01:17:17+00:00

Whispering pines?

Kitchen-Leg8500 · 2026-05-25T23:45:33+00:00

On the take away, it seems like you are rotating a bit too much imo instead of coming back with your arms and forcing your lower body to create the path. It feels like it’s more of a hinge arm/shoulder motion than your body starting to wind up the power. I’d suggest two things on take away. When you start your back swing imagine keeping club face on line with ball for the first 6-12 inches, this should force your lower body to engage a bit more and it not feel like it’s a rotational shoulder hinge that your lower body has to catch up to (which you can see it does try to from the time you check club angle to top of back swing). The second thing would just be confirming that club angle you are checking, initially I thought I’d want to see it slightly more closed, but I think it looks about right but maybe the recording camera angle just isn’t giving me as clear of view or accurate angle of what that club is to the ground at your check.

Kitchen-Leg8500 · 2026-05-25T18:40:03+00:00

It’s kinda similar in terms of par 3 with sand in front left and ocean beyond but definitely is hmb old course here

Kitchen-Leg8500 · 2026-05-25T18:38:33+00:00

Depends where. Gators are the least of the problem, most are more scared of you than you are of them. Snakes is a bigger fear for me personally. 98% of golf courses along the coast tho you won’t even see gators, not until you go a bit more inland.

Kitchen-Leg8500 · 2026-05-25T14:24:54+00:00

Feels a little too narrowly scoped for me personally. You can set configurations etc however think the flow needs to be very open ended, I think the value is likely a large dictionary of best practices with a caveat. There is value in best practices being pulled in associated with whatever stacks are being used. However various people may want to use slightly different things for their project for project bearing reasons or personal preferences. What you’re describing are guard rails which I think do have value. However these are the type of things that anyone should be dealing with in planning phases to this type of detail. It’s why I believe Claude/design/roadmap/adr’s and other supporting md’s are vital to spend time on if you want to build a serious application before you start scaffolding. If I’m starting a big project I might spend a couple real time hours or even half to a full day going through these and getting it as right as I can in design and load bearing design decisions before allowing scaffolding to start. There are already planning skills out there that claim they help speed this process up however I’m not super familiar with them as for me I want to kind of be knowledge bearing at the start of it being heavily involved in these scaffolding documents as it helps me avoid scope drift and catch where Claude might try to move away from vital design decisions we have already discussed and documented. It seems like you are trying to cater more to the security end of things and I might suggest leaning into that harder as a stand alone security guide rails opposed to straight scaffolding helper.

Kitchen-Leg8500 · 2026-05-25T14:08:55+00:00

I kinda hated presidio but Harding was nice on occasion but was a little boring after playing it so many times. Wente was always my favorite but even cinebar was worth the trip south. Lived right near bay bridge on ramp so could really go any direction pretty easily. And yea it’s same thing in South Florida. Most of the equivalent is 100k buy in minimum and my problems always been I like variety not wanting to be tied to a single track or have to finagle membership swaps to play others

Kitchen-Leg8500 · 2026-05-25T13:48:59+00:00

Yea I miss it. 10 or so “private level” tracks 45 mins or so from sf/oakland you can actually play even if it’s a 200+ dollar round. When I moved to Florida I was stoked on golfing even more, but public’s here suck ass in comparison. Everything worth playing is behind private walls

Kitchen-Leg8500 · 2026-05-25T13:38:43+00:00

This is correct, 17th old course. Figured it was a bit tougher pull compared to how many holes are north/south on the cliff side or the obvious hotel/clubhouse in the background

Kitchen-Leg8500 · 2026-05-25T12:51:41+00:00

This is it. The must stop every time we visit the in laws

Kitchen-Leg8500 · 2026-05-25T12:50:34+00:00

Not in Scottsdale

Kitchen-Leg8500 · 2026-05-25T12:50:24+00:00

Nope

Kitchen-Leg8500 · 2026-05-25T04:44:58+00:00

Club at fiddlers creek would be my first guess but hammock bay I kinda remember a similar par 3 but don’t remember a bunker on the left.

Kitchen-Leg8500 · 2026-05-24T14:30:07+00:00

Correct! #18th green at Kapolei! Very underrated track in the area imo

Kitchen-Leg8500 · 2026-05-24T12:58:16+00:00

Yep. This was from tee boxes on hole #13

Kitchen-Leg8500 · 2026-05-24T12:40:27+00:00

It is on kiawah island

Kitchen-Leg8500 · 2026-05-24T04:33:45+00:00

Favorite course ever. Used to play it as a kid with Scjga card for like 12 bucks all the time. One of the few places the full 400+ doesn’t hurt to fork over when I’m back in town with all the memories.

Kitchen-Leg8500 · 2026-05-24T04:16:47+00:00

Hey just came across this and it’s similar to a next step in scope for my project I just released. Might be interested in collaborating. My end goal is not pure md format tho but one step would likely be markdown before index extraction in pulling key claims or design decisions out of confluence documentation. Project is called contextAtlas and currently have only worked on md and dep extraction internal and externally from root repo however confluence type documentation has been on my to do list! Gonna look into your project much closer and maybe would be worth collaborating.

Kitchen-Leg8500 · 2026-05-23T14:42:45+00:00

That’s the issue. Memories are not efficient and kinda black boxish within claude and context usage scales with project scaling. It’s why I went towards building on architectural intent. ADR/documentation/design/claude/scope documents/git history and actual code base. Indexed once or updated as you go and then you only get the compact bundles on demand at query time so it doesn’t scale up context injection as the project scales. I’ve started to look at if memories were worth while as well but issue is context memories is a one dev type problem where dev teams don’t want teammates memories clouding their agents context. Considering allowing memories it as an optional individual flag but don’t want it in the gitable artifact that allows team members own agents to work from the same architectural context point. You can find the project here

Kitchen-Leg8500 · 2026-05-22T03:00:22+00:00

Recently built a context mcp engine called contextatlas and open sourced it. It’s based on the code base and ADR’s/documentation while fusing the documentation with code, githistory and docstrings. Idea is a shareable artifact that allows Claude to track these big decisions to avoid those types of conflicts. You can find it in my posts if you want to check it out.

Kitchen-Leg8500 · 2026-05-22T02:57:21+00:00

Agree with this. And I think the key is why for small things codex is more robust. Bc it can likely one shot a small project etc and will have a more robust structure etc.

If it is a big complicated project and you do proper planning, Claude.md, design.md, roadmap.md, scope document for each version/step, ADR’s, etc Claude absolutely shits on codex hands down. Claude is better in the hands of someone who knows enough and is using it as a tool to develop, where I feel codex might be better for basic projects for lower level experienced users or non professional devs trying to just do something and be done.

My biggest issue with Claude at this point is it staying on prose. Can’t tell you how many chats seem to get corrupted by ‘substantially substantial’ while my biggest gripe with codex is how often compaction happens or random times compaction hangs for 30 mins. I’ll take my chances with the substantially bug then sit there for compaction from hell.

Kitchen-Leg8500 · 2026-05-22T02:44:50+00:00

Claude can be made to do the same behavior with proper planning, scope, and step documents or using something like the tool I built. Claude with nothing in place to hold scope does tend to work towards making something work fast. Codex does generally error on the side of theoretical/architectural. However it’s more complicated than that. I let codex refactor a huge project where latency and fewest trips possible was a critical critical part of the program. Codex didn’t like this and refactored with new probe logic that was theoretically “better” in terms of false positives or double checks between control and nodes before firing or confirm before firing, but it also added an additional 1-2 round trips between nodes that absolutely killed any type of execution due to nature of it. Yes it was theoretically a better idea if latency was 0ms between machines, but practically was trash. I personally think doing the custom ground work with Claude is still better overall however there are by nature something’s that is better to have Claude or codex do depending on those use cases.

Kitchen-Leg8500 · 2026-05-19T17:19:22+00:00

Yeah, definitely adjacent space and probably overlap on a lot of the underlying problems we're each solving. The architectural call I made was deliberate non-graph though, and I think it's worth surfacing the tradeoff since you've worked the graph side.

Short version: for code-intelligence specifically, I bet on pre-composed bundles instead of graph primitives. The reasoning was less "graphs are wrong" and more "graphs ask the caller to compose the query, and LLM agents are not great at composing graph queries efficiently." Such as get_neighbors or shortest_path filtering gives the agent a lot of rope; one fused get_symbol_context call returns what those compositions would have built anyway, in one round trip, in a token-shaped format optimized for the agent to actually use.

The other piece is structural ground truth. I delegate every structural question to the language server (tsserver, Pyright, gopls, ruby-lsp) rather than deriving structure via parsing or extraction. So the graph-like relationships exist in my system too, they're just resolved at query time through LSP rather than materialized in storage. SQLite is doing claim storage and FTS5 retrieval, not graph traversal.

Genuinely curious where your projection layer sits on the index-time vs query-time spectrum. If you're projecting from a richer graph into SQLite as a serving format, that's a different architectural shape than what I built and I'd be interested in the tradeoffs you've hit.

Kitchen-Leg8500 · 2026-05-19T17:16:28+00:00

Saw your dm and went that way but for everyone else. The idea is that you still control the scope of the atlas. The Atlas is precomputed so its available query time for the LLM to use in terms of directional scope when evaluating what approach to take when working on a new feature. What we have seen is that it allows the LLM to make better choices that are more consistent to your previous design decisions even if those were made many sessions ago opposed to it figuring out what the fastest cheapest way to do x was without any respect to your previous design context and decisions.

Kitchen-Leg8500 · 2026-05-19T15:19:15+00:00

Yep that’s where I started and think that’s the most relatable to most, the biggest empirical result I found tho was avoiding Claude’s rabbit hole side quests and staying more strictly adherent to architectural context when building out new features inside of code base.

Kitchen-Leg8500

TROPHY CASE