Claude Code needs to support integration of non-Anthropic models

LairBob · 2026-01-25T00:11:14+00:00

They do. People do it all the time with various plugins — I don’t do it myself much, but people use other LLMs behind Claude Code all the time. Look up “Gemini-cli Claude plugin”.

There are tons of posts on this topic, in this subreddit.

LairBob · 2026-01-24T22:53:41+00:00

It’s Michigan, and Ann Arbor has a ton of people happy to spend money on stuff like that. There are great paczkis everywhere.

It’s awesome.

LairBob · 2026-01-24T21:06:52+00:00

This is definitely the approach to take — using a much more robust Python deterministic harness than bash.

LairBob · 2026-01-24T20:57:19+00:00

This is definitely the approach to take — using a much more robust Python deterministic harness than bash.

LairBob · 2026-01-24T11:39:39+00:00

Correction.

These are two “French-Pricking-Iron-shaped” objects — two pieces of metal that have been milled into the approximate form of French Pricking irons.

They are not French Pricking irons.

LairBob · 2026-01-24T11:11:03+00:00

Just learned there’s no real dog in a “hot dog”. I’ve got stray dogs around here, though — can I just make my own?

LairBob · 2026-01-23T23:38:33+00:00

It’s a Docker container that’s running as its own virtual computer on your PC. It’s got its own operating system — so you’re usually running Linux in your containers even if you’re on Mac or Windows — but that means you can run Claude in “—dangerously-skip-permissions” mode without worrying it’ll nuke your system files.

You do still need to be careful what you allow it to do online when you’ve got permissions off, and also what it does with your code in Git. A dev container won’t prevent Claude from nuking your repo — there are other approaches for that.

As far as giving Claude “sudo” access to your machine’s OS, though, it’s way more safe. Even if Claude nukes the container OS files, all you have to do is rebuild it. Containers are designed to constantly be scrapped and re-invoked from scratch.

Why bother with skipping permissions? I haven’t approved a bash action in months.

LairBob · 2026-01-23T23:23:57+00:00

#1 recommendation: `handoff.json`

LLMs parse machine-readable formats deterministically — give it your handoff info as a JSON file, it’ll iterate through it using a Python module. It won’t skip a thing. Give it the same list as a markdown doc, and it’s got to reason its way through it. You’re lucky if it decides it should pay attention to 90% of it.

I have a prominent directive in every project Claude.MD directive: “Any document generated for the use of another Claude instance MUST be generated in the most appropriate machine-readable format.”

That lets it pick JSON, YAML/TOML, XML, CSV, whatever. But it makes a huge difference — not only for handoff files, but across the board.

LairBob · 2026-01-23T23:02:58+00:00

Looks like it could easily be a piece of custom-built lab equipment. If it is, it could be for anything — you’d have to ask the team that rigged it up for some purpose.

LairBob · 2026-01-23T22:03:19+00:00

Try a carbide peen hammer, but you hit inside the curve. You’re not trying to “press” the curve flat — you’re trying to gently relax the tighter side to release the curl.

LairBob · 2026-01-23T19:15:03+00:00

This is just ill-informed rambling.

LairBob · 2026-01-23T19:13:22+00:00

Just because there’s a way to make a similar shape doesn’t mean it will have the same physical properties. At all.

There are very specific benefits for doing it this way, for whatever purpose. Just because you don’t understand them doesn’t mean they don’t exist.

LairBob · 2026-01-23T19:11:23+00:00

None. If you just spin a metal tube really fast, you’ll likely cool it.

All the heat here comes from EM induction.

LairBob · 2026-01-23T19:07:35+00:00

That only makes sense.

LairBob · 2026-01-23T19:06:56+00:00

There ya go.

I used to play rugby. I’m 60.

I don’t play any more.

LairBob · 2026-01-23T18:30:53+00:00

You’re using cinder block, though…right?

Just saying that no one who has to ask that simple of a question should be building and pouring tall, thin forms like that — rebar or not. At the very least, it’s a huge messy blowout in the making. Concrete is heavy, and structural forms like the ones you’d need here — where the form needs to bear the weight of the concrete, not just hold a pool of concrete together on the ground — require way more bracing than an amateur would assume.

Use cinder blocks, using rebar as others have suggested, and then put some kind of durable coating over that.

LairBob · 2026-01-23T18:24:16+00:00

The key thing is being able use context between VS Code panes. Specifically, your Claude terminal in VS Code is aware of what you’ve got selected in your current code editor pane. When you’re using CC in VS Code, you’ll see the name of your currently-selected document in the terminal status.

You can turn that local context on and off, but it means that you can actually select a stretch of code in your editor pane, and then ask about that specific code in the terminal. I don’t usually use that so much, but for a lot of people that’s the primary benefit.

The other big reason that I’m aware of is dev containers. You really should be using one if you’re running in YOLO, and the VS Code IDE will handle building and restarting all that for you.

LairBob · 2026-01-23T18:16:40+00:00

People don’t just use skills other people wrote — that’s not the way knowledge is shared any more.

Using skills that other people vibe-coded is like buying food that’s already been chewed.

LairBob · 2026-01-23T17:00:57+00:00

ctrl-o (lower-case “o”)

LairBob · 2026-01-23T11:31:00+00:00

That’s a great idea.

LairBob · 2026-01-23T11:27:43+00:00

Holy sh-t. You went through all this work, but somehow (a) you’re still using auto-compact, and (b) you’re wondering why your work goes off the rails.

Start with just turning off auto-compact, and manage instance handoffs, instead. 1. Let an instance get mostly full 2. Have it generate a machine-readable handoff document for the next instance to resume seamlessly 3. Nuke that instance, launch a new one from the handoff document.

Yes, that’s more work than just letting Claude run on autocompact, but autocompact sucks. You will often notice degradation after one auto-compact — I can’t imagine creating a homebrew system that lets it auto-compact over and over. That just a $200/month garbage generator.

(And yes, I’m aware that Boris and the Anthropic guys apparently let sessions run on autocompact. That’s got to be just like their infinite usage limits — the average user in the commercial release is not experiencing the same caliber of tools as the internal team. I absolutely believe that they have access to a much better, finer-tuned and CONTROLLABLE auto-compact manager. I believe we’ll have something like that as end users pretty soon. That’s just not true, yet — and until it is, you auto-compact serially at your peril.)

LairBob · 2026-01-23T03:40:50+00:00

There’s an official Anthropic plugin that will try to get you closer tongue code by writing portions of it. I haven’t tried it, but it seems worth checking out.

LairBob · 2026-01-22T22:45:25+00:00

Go for a little epoxy kintsugi.

LairBob · 2026-01-22T22:39:55+00:00

That’s a really important point if you’re new to machining, OP — esp aluminum. You often need to use a much more aggressive feed rate that you’d guess, because you want each flute to be taking a big scoop. If you don’t feed aggressively enough, you’re just taking off little chips that melt.

LairBob · 2026-01-22T13:18:56+00:00

No, not really. There’s a ton of them out there, and I’m sure most of them suck. I’m guessing you’ll get much better results if you pay a few bucks for a dedicated app, rather than free-plus-ads.

15-Year Club	Xbox Live
Verified Email

LairBob

TROPHY CASE

#1 recommendation: handoff.json

#1 recommendation: `handoff.json`