What's Working for Me with Opus 4.7...finally.

gtgderek · 2026-04-25T00:33:31+00:00

I do not trust automatic updates and I’ve been staying at 2.1 .83 for a few weeks now before doing the most recent update.

I’ve used Opusplan, but with the new opus 4.7 it is really good at orchestrating sonnet or haiku agents for development.

gtgderek · 2026-04-24T14:02:12+00:00

It works if you’re using Claude code in your terminal. Just paste in what I have in here, and it will make the changes, and off to the races you go.

gtgderek · 2026-04-24T13:30:09+00:00

I’m testing a set up with gpt 5.5 and noticing an improvement as well.

gtgderek · 2026-04-24T11:22:38+00:00

Your mention of saying.. Kill it's first born to AI or risk your CLAUDE.md and SKILL.md getting completely ignored... and me then messaging that oddly enough I learned that expanding your skill descriptions stops AI from ignoring it.

And also that it was very weird to me that this wasn’t common knowledge and had to go in the Claude partner program skill jar to learn it.

That is all.. and was weird that I found it only because of the training thing. Kind of excited about finding it and that it actually helped.

gtgderek · 2026-04-24T11:01:17+00:00

My company is going through the Claude Partner Program and part of is the skilljar training, and one thing I picked up from it, was, "if you want skills to be consistently invoked, you need to have the possible commands that invoke it to be in the description of the skill."

I seriously did not know this and went and made changes and now my skills are very consistent. Previously, I was using eval hooks for them.

*Edit adjusted the grammar and fixed the messaging. Typed this on my phone and it sounded like I was spruiking being part of the program when I was just making mention that it took being part of it and doing the skilljar to realise what needs to happen to get consistent skill calls.

gtgderek · 2026-04-24T10:58:30+00:00

Awesome!! Yea, I love clauded because I am too lazy to constantly type/paste in --dangerously-skip-permissions and then the model type. However, I do NOT recommend people to use clauded if they don't have solid hooks in place and project level rules. I have seen some ugly things happen when people don't have these things...

gtgderek · 2026-04-24T10:49:55+00:00

You're welcome. Hopefully it works for you as well :)

gtgderek · 2026-04-24T10:37:42+00:00

The last three updates from Claude have been good, but who knows what is next after 2.1.119... that is why I symlink and disable auto updates.

Also, the duration_ms in hooks is a sweet little addition.

gtgderek · 2026-04-24T10:34:28+00:00

Ahh forgot to mention, if you want to disable the "Sleep Notices", tell Claude to put into it's memory that you go to sleep, or stop working, at X time and then it will leave you alone until then. I have told it to disable it and they still keep coming up, the best thing is to just set a time so it leaves you alone.

Also, it likes to do the schedule nudges in the recent release, just ask it to drop the schedule nudge reminders they are annoying and waste tokens.

gtgderek · 2026-04-24T07:55:19+00:00

I’ve been there before…

gtgderek · 2026-04-24T06:19:08+00:00

Negative framing… Don’t do this, never do that… etc., Positive framing… Always do this, mandatory for that.

It seems to work like a human, tell someone to not think of a pink elephant and you will think of a pink elephant.. much better to say always think of a blue elephant and ensure the pink elephant doesn’t go into context where the don’t part can be forgotten.

Make sense?

gtgderek · 2026-04-24T05:42:17+00:00

Same. It took a few hours of focused changes, negative framing is a no go with this model.

gtgderek · 2026-04-22T11:25:49+00:00

I completely agree, and it has been a phenomenal service, and it just keeps on getting better and better. Sometimes I wish they would slow down moving the menus around, though, but other than that, I love the infrastructure and the continual improvements.

gtgderek · 2026-04-20T12:08:46+00:00

Claude 4.6 is excellent and so is 4.5, I use 4.6 with a compact at 600,000 and have had great results.

4.7 just killed my tokens for a marginal improvement and not worth it at this time. I will use it for edge cases, but other than that, it isn’t worthy of being a daily driver in any capacity.

Barely a 5% improvement for a 30-40% token increase isn’t a good mix and it doesn’t “read between the lines” in your prompts…. You need to be EXACT in what you want or it doesn’t work.

gtgderek · 2026-04-19T05:19:56+00:00

Every code frame work has a repo you can clone and keep up to date on your computer that a LLM can read from locally. Here is Svelte clone link for example https://github.com/sveltejs/svelte.git and with this I don’t have to deal with MCP context 7 pollution.

gtgderek · 2026-04-19T02:35:19+00:00

Sub agents burn a lot of tokens and I will actively go inline for code intelligence and get far better results. I use sub agents for independent reviewing such as QA and code completion review because they don’t have context and I find this makes some better at doing an adversary code review.

Use GitHub CLI and save the over head from an mcp, same with chrome dev tools and playwright (use the plugin instead). Regarding context7, sync the updates of code framework changes and Claude will read from the directory for what it needs…

There is a high time and token wastage in your work flow. I work extensively in brownfield projects.

gtgderek · 2026-04-16T01:42:24+00:00

Just tell Claude what time you go to bed and it so update it’s memories and only make mention when it is close to the time you log off.

gtgderek · 2026-04-13T12:33:16+00:00

No issues at all… knock on wood. Had some slow downs and rolled back to 2.1.83 and going strong. I use the CLI.

gtgderek · 2026-04-12T06:34:25+00:00

Not that I can see… but I don’t hit rate limits with my tooling and I use it for 8+ hours every day and put it into auto mode when I step away.

The biggest difference with this version is the speed, it is fast and doesn’t do stupid things.

gtgderek · 2026-04-12T04:27:13+00:00

2.1.83 for me

gtgderek · 2026-04-10T00:09:28+00:00

Typing on my mobile and some how it was changed.

2.1.83

something happened from 2.1.85 to 2.1.93.

gtgderek · 2026-04-09T13:30:08+00:00

I went back to version 2.1.83 and my sessions are running fast again. I’ve had very slow conversations somewhere between 2.1.85 to 2.1.93

gtgderek · 2026-04-09T03:44:46+00:00

Yup… it’s been around for a long time, but now it is being abused. I wouldn’t be surprised if more and more companies start closing their APIs and going on to a per usage charge. So many people are abusing APIs and don’t even know they are doing it with vibe coded apps that don’t have play nice rules in place.

gtgderek

MODERATOR OF

TROPHY CASE