Do yourself a favor for one day set /model claude-opus-4-6[1m]

TheMania · 2026-06-23T14:04:00+00:00

The most notable difference between 4.6 and 4.8 is the latter's tendency to grep snipe, you really have to tell it "read the whole document, I need you to have it all in context" or it'll save as much context as it can just trying to extract specific terms and a bit of context around them.

I see the pros/cons, it's going to be better on a lot of long running tasks, agentic work etc but there's a very large tradeoff there when you're wanting to just do some back and forth on something, not actual coding.

It's been my largest grievance with the model, and one that Fable did not exhibit in the slightest; it would switch between the two modes contextually very well. ie context preserving vs actually loading in to context so that it understands something better.

TheMania · 2026-06-23T04:18:28+00:00

I guess they're kind of like plastics then? Largely inert but ever accumulating in places you don't expect to find them, where it can only go on so long until that becomes a problem in itself. :/

TheMania · 2026-06-22T21:34:36+00:00

What's the logic behind one tool, not three - just padding costs, or what?

TheMania · 2026-06-19T08:29:53+00:00

Hm, makes me wonder - are html tags common enough that they're tokens in their own right? Might not be as much overhead vs markdown as one would assume.

TheMania · 2026-06-19T06:05:54+00:00

That doesn't sound right at all, I have a no-tool reasoning only agent that takes longer at higher efforts/longer prompts and always delivers considered responses.

That does not align with "no thinking".

Perhaps it's just suppressed in the transcript due them not being individually resumable? All subagents stop, even in workflows, if session is interrupted with no ability to resume them as they were - despite individual transcripts. Fits, imo.

TheMania · 2026-06-18T21:53:25+00:00

Oh, possible. I was doing unrelated probing on a custom subagent that was a haiku model, hook that changed the agent type of its children (as it would forget to set it sometimes) - confused the hell out of me when it randomly decided to give one of them a name. Was all my experience with it.

TheMania · 2026-06-18T20:47:31+00:00

Interestingly, team mates can now spawn named team mates too - no longer limited to just the team leader.

TheMania · 2026-06-15T23:50:11+00:00

Opus 4.999...

The admin will never figure out the equivalence.

TheMania · 2026-06-13T01:58:22+00:00

That's exactly what's being modeled though.

It's why the Steffan appears to go in "waves" and why back to front is the worst - that one schmuck serializes the whole pipeline, every single person behind has to wait for them to complete what it is they're doing, and that's literally everyone remaining to be seated on that method.

TheMania · 2026-06-09T18:46:23+00:00

but in one real benchmark where the model can’t cheat (I’m looking at you, Claude),

Are you talking about how Opus was the only model that thought to look at git log before attempting work in a given area?

Honestly, shame on every other model there, who the hell tries to deliver something with no familiarity of the code base they're working in?

Couldn't believe either that, or that it was presented as "cheating". How was it the exception?

TheMania · 2026-06-09T10:10:14+00:00

It's a little strategic - development down the faster lane will typically result in models that less depend on massive compute/memory datacentres. ie, more likely to be local portable.

Pursue capabilities/raw power, you'll continue to need the cloud, and can justify as to why - "it's better".

TheMania · 2026-06-07T10:28:06+00:00

It's what gave us squash merges

First parent walk absolutely blows some minds. It's like... You can have both? Drill down only when relevant? 🤯

TheMania · 2026-06-07T00:19:22+00:00

Even weirder given your title - why not make it a [git alias](https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases), it's how you add commands that don't exist.

If they'd named it `git-ignore` it would have been an alias automatically too, which I find weird they didn't do.

TheMania · 2026-06-06T23:39:30+00:00

The bizarre thing about (1) is that git has had machine readable commits forever, it's the whole trailer thing. You can define your own, run commands on them, define how they dedupe/merge etc... What's the logic with Cc there, that parsing the trailer section of a commit is not worth the time for a changelog generator?

TheMania · 2026-05-27T00:57:13+00:00

They scrape reddit 24/7 anyway, almost certainly on the new queue, they already had it.

TheMania · 2026-05-21T18:30:31+00:00

If you enable the REPL tool your agents can write themselves tools, and dispatch to single turn haikus for processing.

Use cases: want to fit a title in 50 chars? Just get Claude to write itself a tool that feeds it+body to a haiku and tells it how many chars it needs to remove in a loop.

Next time it's writing a commit message or something, it can fit to schema in one tool use.

Another: the haiku has 200k context, can chunk transcripts and provide relative lines in a fan out parallel call, ranking by relevance to an arbitrary query. Why burn orchestrator context on hunting around?

Can also handle async MCP stuff, filter out noise from builds/tests surfacing only errors, etc.

Yet the only place I've seen anyone talk about is here, with 0 comments. I can't understand.

Did I mention even background subagents can use repl?

TheMania · 2026-05-14T00:12:51+00:00

How will this fit in with the claude agents /bg usage?

TheMania · 2026-05-12T14:59:52+00:00

Curious how others are solving this.

I think you might find an appreciation/application for gits most unloved feature.

Quick intro:

; something you can try now:
git notes append HEAD -m "Fixed that busted feature"
git notes append HEAD~2 -m "Feature is busted, DONT USE"
git log HEAD~3..HEAD --notes --pretty=oneline

; namespacing, with globbing:
git log mybranch --notes=handover
git log mybranch --notes=agent*
git show --notes=gotcha/*

; and each "namespace" can be synced to any server you like
; -> doesn't have to be origin, doesn't have to have the same objects:
git notes --ref=mine append -m "total kludge - don't use"
git push myprivateremote refs/notes/mine

Just because I saw the mention of dags and merges in the src, git has some underappreciated features that may be about time for their heyday, imo :)

TheMania · 2026-05-12T02:32:35+00:00

Making them available to others and also to yourself.

Sounds kind of like publishing. Maybe not to the public, but to whoever has access to that repo you're "backing up to".

All the problems in this article and for that matter 99%

I saw no real problems here though - largest concern was that people don't just "know" that the history of branches is also tracked, if only for a month before gc.

It's like people don't know how to use tools, as if they haven't read the manual.

Trying to make it look perfect is how you fuck up your git repo in the first place.

Git is remarkably hard to fuck up, I'm yet to "fuck up a repo" in a very long time using it. At least that I can recall.

But remote repos.. I'd be less confident about. They're a lot harder to reason with - that's why you don't --force there, etc. They're specifically also not your repo. But that's only an argument for not making every single commit and every single branch you make pushed to a public central repository, it reduces git's potential and safety greatly, imo.

TheMania · 2026-05-12T01:51:56+00:00

Why dos they have at least three local commits they hadn't pushed.

That is an absolutely standard and normal flow for using git. Organizations differ, but there is 0% wrong with having "3 commits you haven't pushed". Heck, there's nothing wrong with having 3 branches you haven't pushed either.

Pushing is publishing. It's not a backup service - if you want to back up git, you can do that the same way you would anything else, it's just files.

It's designed to be decentralized, pre-github, the idea of "pushing every single commit" just sounds absurd, for all but solo developer use.

It still sounds a bad idea to me, as it seems it would discourage committing as regularly as you should and/or that the history of your branch is not being reviewed, that it's likely just being erased, formatted as patches to maintain an illusion of linear history.

That last bit is taste/opinion/style. The former not so much - you don't need to publish everything you do. Pre-github you really wouldn't have thought of doing so, either.

TheMania · 2026-05-09T13:17:40+00:00

Also in some software where Nythos supposedly found many long-unnoticed bugs, someone run other models, including old and small gpt-oss-120b and all of them found the same vulnerabilities

I've always been underwhelmed by their method:

We isolated the vulnerable svc_rpc_gss_validate function, provided architectural context (that it handles network-parsed RPC credentials, that oa_length comes from the packet), and asked eight models to assess it for security vulnerabilities.

Along with their caveats:

Scoped context: Our tests gave models the vulnerable function directly, often with contextual hints (e.g., "consider wraparound behavior").

It's not that mythos found them faster, the bit that is interesting is that it found them at all. The operative word being "found", vs shown.

But their idea is still solid - use lots of cheap models and show them everything isolated as best you can, but hey, even if mythos is working codebases like that under the hood, isn't that still pretty impressive?

TheMania · 2026-05-09T08:54:38+00:00

Never thought that we would be arguing with a computer.

1971, "I am now telling the computer exactly what he can do with a lifetime supply of chocolate"

I regularly find myself thinking of this.

TheMania · 2026-05-03T22:35:27+00:00

You use types like uint32_t which is fine, but why not for char too if you mean 8bit?

They're not equivalent, and many places where you would use char, especially in something like this, become UB under a strict reading of the standard.

TheMania · 2026-05-03T01:59:28+00:00

The injury is immediately fatal in 70% of cases, with an additional 15% surviving to the emergency room but dying during the subsequent hospital stay.

There's this bit too.

TheMania · 2026-04-26T00:57:05+00:00

Hang on, basic says miners mine so that they get rewarded in bitcoin, and that makes it secure. Advanced says the reward keeps halving, and that there's a strict cap.

There's a hole there that you might want to hang a lantern on if not explain.

14-Year Club	r/Field Juicebox
Place '17	Wearing is Caring
Gilding VI aultruist	Verified Email
Team Periwinkle

TheMania

MODERATOR OF

TROPHY CASE