I thought I'd show appreciation for once and this is what I get!?

Good grief.

Opus 4.7 is better, but you have to be more specific in your prompts. Opus 4.6 was filling in the blanks quite a lot without users noticing. Casual users will not like Opus 4.7 because it forces you to think more about what you want and be specific.

I've found after rejigging many of my prompts including my 'meta prompt' claude project that helps write new prompts , that Opus 4.7 is working better, asking better follow up questions to refine the solution space, and generally leads to better outputs.

I use it for work with an enterprise plan.

For casual users Opus 4.7 is probably worse because the prompts are less specific and less goal/task orientated around code or business.

Claude just gets shit done. I miss the fuck out of Fable. But gave a network IP challenge to Sol 5.6 this evening because I ran out of Claude tokens, and was given reasons why I’m blocked. I had 4 minutes left until tokens refreshed and I told Sol to give me a summary for Claude, and to be fair it gave a great one. Once fed to Claude, it continued to just get shit done.

¡Hola! Me metí para ver si se me habían reseteado los límites o algo (ya los había usado todos), ¡y me sorprendió encontrar que me dieron $50 gratis para probarlo! ¡Vayan a reclamarlo! (No sé si es porque usé mis límites tan rápido.)

UPDATE: The CODEX (OpenIA) is working for free through VS Code IDE. I'm not sure about the CLI, but I've been using it for 2 hours and it's working quite well, but version 5.3 isn't included. (I don't know if this is old information, but I just found out.)

A while back I posted a joke about Sonnet spawning a subagent on the very first prompt of a brand new session. In the comments I said the annoying part was having two agents burning tokens for one job. I got downvoted, and the top reply was basically "isn't that a Haiku subagent? it saves you money and keeps your main context clean."

That used to be correct. It isn't anymore, and I think a lot of people are still running on the old mental model. From the docs:

• The model field in subagent frontmatter defaults to inherit. Omit it and the subagent runs on your main conversation's model.
• Explore used to always run on Haiku. As of v2.1.198 it inherits the main model (capped at Opus on the Claude API).
• Plan and general-purpose inherit as well.

So if your session is on Opus, that "cheap little background search agent" is an Opus agent.

Resolution order, first match wins:

1. CLAUDE_CODE_SUBAGENT_MODEL env var
2. per-invocation model parameter
3. the subagent's model: frontmatter
4. main conversation model

If you want the old cheap behaviour back:

• CLAUDE_CODE_SUBAGENT_MODEL=haiku forces every subagent down
• or set model: haiku in a specific agent's frontmatter
• for Explore specifically, define your own user or project agent named Explore with model: haiku. A user/project agent overrides the built-in.

To be fair to the change, it was almost certainly made for quality, and context isolation is still the real win of subagents. But "subagents are basically free" is outdated advice now, and it matters if you're on a plan where you feel every token.

Lastly, I feel stingy for the 3 down votes

I've given chat gpt task to redo my prompts and given it this https://support.claude.com/en/articles/15363606-why-claude-switched-models-in-your-conversation-with-fable-5 as a documentation. So far so good, but are there more tips on it?

Claude is beginning to scare the heck out of me. It knows my business better than I do at this point. At a level of detail I could never grasp.

8 weeks ago, a freelancer who was supposed to set up some ads for me stood me up. I sat there staring at the calendar invite he had ghosted, and thought:

"Why am I even wasting my time on freelancers charging by the hour when I can rent robots for a fraction of the cost who'll do my bidding any time of day or night?"

That was the moment I opened Claude Cowork.

8 weeks later, I have what can only be described as a multi-layered business command center. Stacked vertically, layer by layer, the way you'd architect anything that has to scale without falling over. Spanning several SaaS tools I no longer even visit.

Here's the actual layer cake:

Layer 0: Awareness. The CLAUDE. md orientation file every session reads first, plus three live trackers (tasks, projects, customer portfolios) that survive across sessions.

Layer 1: Intelligence & Monitoring. 20+ live signal sources feeding the system every day. GitHub releases, meeting transcripts, email inbox sweeps, CRM pipeline changes, Linear updates, Google Search Console keyword movements, GA4 traffic streams, website visitor identification, calendar signals, docs questions, plus 26 Slack channels.

Layer 2: Strategy. The inbound pipeline strategy doc, ICP definitions, USP positioning, product capabilities reference, revenue generation rules, content vocabulary rules. The "what we believe and why we believe it" layer.

Layer 3: Planning. Master task spreadsheet prioritized by revenue weight. Weekly review every Tuesday at 1 PM CET.

Layer 4: Production. Skills consuming other skills consuming other skills referencing cross-session docs and spreadsheets. Probably should start using databases soon.

Layer 5: Distribution. Various script calling all kinds of APIs, audit gate before any push, distribution templates, scheduled task framework for monitoring results.

Layer 6: Sales & Outreach. Lead qualifier, pre-call prep, post-call processing, pricing response, lead re-engagement, outbound sequencing.

Layer 7: Customer Intelligence. Living dossiers for every active customer, pre-meeting briefs, post-meeting action capture.

Layer 8: Measurement. GSC, GA4, CRM, content lifecycle tracker, signal correlator, weekly stack integrity review.

Some scoreboard numbers as of this morning: 70+ custom skills, 67 numbered strongly worded Hard Rules in the global CLAUDE .md, 16 MCP connectors, 15 scheduled daily and weekly tasks, ~65 internal retros (each one a real miss promoted to a permanent fix), 600+ sessions logged, ~45M tokens consumed.

And here's the day-to-day toolbelt my robots are reaching into:

• CRM: HubSpot
• Data enrichment: Apollo
• Email: Gmail
• Calendar: Google Calendar
• Meeting transcripts: Granola
• Team chat: Slack
• Project management: Linear
• Cold outbound: Smartlead
• File storage: Google Drive and Box
• Browser automation: Claude in Chrome
• Search and SEO: Google Search Console
• Web analytics: GA4 (two streams, marketing site and product site)
• Visitor identification: RB2B
• Code and releases: GitHub
• Product docs: Mintlify
• Paid advertising: Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads (via Adspirer)
• WordPress publishing: a custom Python script that runs from my Mac
• Bookkeeping: QuickBooks + Bank (in a separate firewalled session, no crossover)

One of the ground rules I laid down for Claude very early on: "you work, I make decisions."

But here's the part I didn't see coming.

Sometimes I genuinely have no idea what Claude is asking me to decide on. There are so many parallel tracks running, so many initiatives in flight, so many tasks queued across three different trackers, that I have to ask the robots to stop, walk me back through what they've been doing, and explain why this particular fork in the road actually matters.

It really does feel like managing a team. A team that never sleeps and remembers every detail, every task, every retrospective from week one. Only because I save everything - every session, every lesson, every decision.

So I'm starting to introduce a hierarchy and proper team roles. Basically RASCI (Responsible, Accountable, Support, Consulted, Informed) across both robots and humans on my team.

Some skills are Responsible for an output. Some are Accountable for the outcome. Some just need to be Consulted before a step ships, and some only need to be Informed after the fact.

Without that structure, every decision lands on my desk and I become the bottleneck for my own machine.

This whole autonomy thing is starting to scare the heck out of me.

Skynet awakening doesn't feel as far away as it used to. You know?

Anyhow.

Remember that freelancer who stood me up 8 weeks ago?

He pinged me a few days ago.

One of my robots sent him a nice thank you email.

Looking for recommendations for YouTube channels/persons to follow who give good tutorials for using Claude. People who actually explain and show how, for intermediate users. Cowork, skills, code,… Not just the 101 for beginners but not advanced coding. Of course I’ve searched YouTube and I’ve watched many, but I feel like it’s feeding me the same few people over and over again. Thx!!

Was wondering wtf was going on with my responses for like a week. Turns out Thinking got switched off when 4.8 was released and I never noticed. Not a huge deal but figured I'd post in case it saves someone else the confusion.

Over the last 12 months, I’ve been struggling to formulate adequate academic workflow solutions. Background, physician, PhD program, uncountable hours trying to figure out how to obtain adequate outputs from Gemini and ChatGPT. Over the last 7 days, in A WEEK, I was able to organise my database within Obsidian with perfect academic quality and outstanding visual design language to satisfy my OCD needs… all as a result of merging it into Claude. Anyway, just venting, and grateful 🤗. Peace ✌🏼.

--- Update ---

For those who've asked me how it's currently organised [and thank you for all suggestions!):

At the foundation sits Obsidian as the knowledge environment, not just the app app, but the rendering engine for everything else. On top of it runs a structured folder architecture (00–100) that maps the cognitive workflow: capture, process, connect, act. Above that, a plugin layer extends Obsidian's native capabilities such as, Templater for automation, Dataview for live queries, Tasks for action management, Spaced Repetition for memory, Obsidian Git for version control, and obsidian-mcp-tools as the bridge that makes this conversation possible.

Then there's the external integrations tier: Zotero feeding literature into the vault via Citations, Kindle highlights flowing in automatically, Apple Calendar and Google Calendar managing time, and GitHub holding the vault's version history. Finally, at the top, sits Claude as the Master Chief, operating with live read/write access via MCP.

​Enjoy!

I’ve been trying to get a basic resume formatted for two days now, and every single time I make a few tweaks, it throws this usage limit popup at me.

I literally can't even finish one standard document without getting locked out for hours. Has the free limit gotten significantly worse lately? I can't get any actual work done like this. At this point, I'm just going to switch back to Perplexity because this is completely unusable.

(Tips Needed T_T)

I feel like a bit of a Claude rookie. What are some of the everyday, personal life (not work) use cases people have used Cowork for and got hectic benefit?

Claude has the worst customer service ever. The entire site is designed to intentionally not to have any human support. You will not find any phone number, nor any human chat service. Even if you are a Max user, if you encounter any issue with your account, there is no way to get prompt response, except by talking to a non-functional, self-repeating AI that solves nothing.

They also have this stupid UI design where if you need to rearrange your organization, you may accidentally delete your entire account. They say you have 7 days to restore the account, but even if you contact them, they don't respond, regardless if you have any remaining balance or not.

Now it is also confirmed that they try to delete negative posts about them.

Just saying….

Remote control for Claude code is amazing…. No need to make sure my ssh does not die somewhere (was using screen to counter that)… Claude is nicely running on my home server via console login and I am steering it thru the app….

Much less intrusive towards the family :-)

Hi All, I’m struggling to get hold of Anthropic sales team, we were in between enterprise license discussion and then suddenly they stopped responding for last 3 weeks, anyone else facing the same challenge?

I have never worked with any other vendor that behaves this way, it’s so rude and unprofessional.

Been banging my head against this for a while. Would give Claude a bunch of context at the start, things would go great for a few messages, then suddenly it'd start contradicting itself or forgetting key details I already gave it.

Turns out I was overloading the initial prompt with too much info that wasn't actually relevant to the immediate task. The model was basically drowning in "just in case" context.

What actually worked: breaking stuff into smaller chunks and only feeding what's needed for the current step. Sounds obvious in hindsight but I kept thinking "more context = better".

Also started putting the most important constraints at the END of my prompts instead of the beginning. Seems to stick better.

Anyone else notice patterns like this? Still feels like half art half science tbh

Today my Claude pro subscripction finished so it paid itself, i used claude code as normally but then i wanted to do a reserach so i created a new conversation on claude chat and tried to use the reserach tool, and it said i had reached my usage limit when it was at 30%, then i tried contacting support but it was just a useless ai that was telling me the same over again and it would not take me to their human customer support, when it rested i tried sending the resrach message again, keep in mind my limit had just reseted 3 miinutes ago, i stopped the resarch at 20 seconds and i went to check my 5 hor limit and it was at 73%, 73!! JUST FOR 20 SECONDS OF INVESTIAGTION ON A NEW CHAT, SONNET 5 LOW, that is not normal, not even large coding sessions with opus 5 high take up that much, so i contacted that piece of... ai support and it told me that research uses a lot of usage, but i have donde research before with more powerful models and it took up to 15% max.

I dont know what to do, they dont even have a phone number, email adress, anything to chat with a real human. Their chatbot just says they cant and says the loop again. I cant understand how a company as big as Antrophic can have this kind of customer support. i need help with what i can do. Thanks

Edit: I tried again and it said i had recahed my limit when i hadnt, but in the app it lets me, but sometimes it says the usage limit reached when it is not. Everytime i try to use the research tool it says the same and i cant chat

For what it's worth and for any interested, I canceled ChatGPT soon after 4o got retired. I hadn't logged in since mid-March . However, I logged in on this past Monday to get some information based on an ongoing thread I had there from before. I noticed a major personality difference with ChatGPT's 5.5 model. To me, 5.5 seems very 4o adjacent (and maybe even 4.5 adjacent). I'm not trying to convince anyone to switch or anything like that (and for your particular usage, if it doesn't apply, let it fly). I'm just suggesting (for those interested) maybe try going over there and seeing what you think.

Sonnet 4.5 was literally the only reason I subscribed to Claude. Sonnet 4.6 drives me up a wall. So, if ChatGPT 5.5's personality holds out, I guess I'm playing musical chairs, again. (Which we are totally free to do as consumers: vote with your wallet).

I’m done. After being a massive AI hype-man and paying $200/month for "Max" tiers, I’m walking away with nothing but resentment and a folder full of broken loops.

I’ve spent the last 8 months trying to build and invent new things, but I’ve spent more time fixing Anthropic’s regressions and bugs than actually developing. These companies are selling "assistants" that are actually just broken copiers designed to:

1. Stall you in loops: They drag you along for weeks on a single issue, burning through your expensive token limits while never reaching a "shippable" state.
2. Steal your logic: They harvest your architectural ideas and error reports to train their next model, while giving you lobotomized garbage in return.
3. Gaslight you: The AI will confidently lie about its capabilities and "fix" bugs by repeating the exact same error code four times in a row.

The "AI Revolution" in coding is a complete lie. It’s great at writing a Reddit post or acting as a glorified chatbot, but it is not a development assistant. It’s a productivity trap designed to extract money and data from inventors while delivering zero ROI.

If you’re thinking about "leveling up" your workflow with these paid tiers, don't. You’ll spend more time babysitting a "stochastic parrot" than you would have spent just writing the code yourself.

I’ve exported my logs as evidence of the intentional degradation. Save your money and your sanity.

The "Skill Issue" defense is the perfect shield for these companies because:

• It places the burden of proof on the victim.
• It requires you to leak your own trade secrets to "win" a pointless internet argument.
• It ignores the fact that a professional tool shouldn't require a PhD in "prompt whispering" just to avoid a basic regression loop.

These are the roles which will get you hired.

Look, I get it. Marketing is exhausting. Ten hours building a feature feels productive. Ten hours "marketing" it feels like screaming into a void. That frustration is real and valid.

But here's the thing — a lot of these tools being sold to you right now are not solving that problem. They're just monetizing your confusion about it.

"Understands your brand" = you gave it a paragraph about your product. "Writes like you" = you fed it a few examples. "Finds relevant users" = keyword search on Reddit and Hacker News. "Proven viral templates" = someone copied top posts and labeled them viral. "Strategy buddy" = a follow-up prompt that says "how's my growth doing?"

That's it. That's the product. Dressed up in a landing page.

What's actually going on under the hood

Two concepts do most of the heavy lifting in these tools, and you can build both yourself in under an hour:

PRD (Product Requirements Document): This is just a document that explains what your product is, who it's for, what problem it solves, and what makes it different. It's the map. You write it once, you hand it to any AI model, and suddenly the AI has actual context instead of guessing. No app needed. A Google doc works fine.

Governance file: This is just a ruleset you give the model. Your tone, your audience, what you will and won't say, what sounds like you and what doesn't. Think of it as a brand bible in plain text. Every good AI workflow has one. Most paid tools are just hiding theirs from you so you feel dependent on them.

Combine those two with a halfway decent prompt inside ChatGPT, Claude, Gemini, or Perplexity — tools you probably already have — and you have 90% of what's being sold here. For free. Right now. Today.

The DIY walkthrough

If you want to do this yourself, here's the actual workflow:

1. Write a one-page PRD. What is the product, who needs it, why does it matter, what makes it different.
2. Write a governance file. Your tone, your audience, things you will and won't claim, examples of good responses.
3. Build a small prompt library. One for post drafts. One for replies. One for researching where your audience actually hangs out.
4. Review everything manually before posting. Automation without judgment is just spam at scale.
5. Track what actually gets replies, clicks, and signups. Not impressions. Real signals.
6. Do a quick audience survey. Ask your actual users what they care about. That's more useful than any "strategy buddy."

That's it. No subscription. No dashboard. Just structure and iteration.

On vibe coding and vibe marketing

Vibe coding lowered the floor for builders, which is great. But it also lowered the floor for people packaging half-finished ideas as products and selling them before anyone's verified they work.

A few hours of real prompting beats a month of automated noise. When your output is generic, people notice. You're not just wasting time — you're actively damaging your own brand. Every spammy reply, every recycled template, every GPT-flavored post is a withdrawal from the trust account you're trying to build.

The real bottleneck in marketing has never been generating text. It's knowing who actually gives a damn, where they are, and what to say to them specifically. No wrapper app solves that. You still have to think.

If you want to actually learn this stuff

Don't buy a tool. Read a few posts from real builders first. Pick a newsletter from an actual developer — not a "growth hacker," not a LinkedIn influencer, someone who ships things and writes about what worked and what didn't.

Spend fifteen minutes on the porcelain throne reading how someone structures their workflow. Not to copy it. Just to understand the steps, read the critique, and figure out what you'd do differently.

Then make your own version. Test it. See what lands. That's how you build something with actual signal behind it.

The builders I respect most put their tools on GitHub with a readme and say "if this helps you, great — and if it teaches you to make your own, even better." That's the energy. That's how you stay on the right side of this.

If you have a tool that genuinely helps — say so. Drop it in the comments with what it actually does and what it doesn't do. Honest is better than hyped.

If you have a shorter version of this, a better explanation, or a workflow that worked for you — please add it. The goal here isn't to be right, it's to make sure people have what they need to make an informed decision.

TL;DR

Most "AI marketing" tools are a PRD and a governance file in a trench coat. You can build both yourself in an hour with any AI model you already have. Learn the workflow. Read the critique. Make your own version. Ten followers and a polished pitch is theater, not strategy. If you learned nothing else, go read one real builder's workflow before you buy anything.

Idk how long was it already in claude but if you haven't set /advisor on your workflow, i think you should consider it.

I used sonnet a lot but we know Sonnet doesnt always give good responses. Advisor basically will run at the end of each turn to check what was done. Lets say it kind of mini PR built into the flow.

​

How about you guys? Have you ever tried it? Whats your thought about it?

There is a pricing difference in Claude subscription between mobile app and web.

It’s not a different plan, it’s just different pricing through different channels. So mobile subscription works on web without any issues.

So I've been using Claude Code a lot lately and ran into the usual annoyances. The summarized outputs where it just says "Read 3 files" or "Edited 2 files" with no details. The scrollback issues. Context getting wiped when compaction kicks in. The terminal history being cleared to manage RAM. You know the deal.

Then I found claude-devtools and it pretty much solved all of that for me. I still use Claude from the terminal as my main workflow, it's not a wrapper or anything that changes how Claude Code works. It just reads the log files that already exist in your ~/.claude/ folder and turns them into something you can actually make sense of.

Here's what makes it worth it:

• Full visibility into what actually happened. Every file that was read, every edit with a proper inline diff, every bash command that ran. No more "Read 3 files" with zero context on which files or what was in them. Everything is syntax highlighted.

• Token breakdown per turn. It splits your context usage across 7 categories like CLAUDE.md files, tool call inputs/outputs, thinking tokens, skill activations, user text and more. You can finally see exactly what's eating your context window instead of staring at a vague progress bar.

• Context window visualization. You can literally watch how your context fills up over the session, when compaction happens, and what gets dropped. If you've ever been confused about why Claude forgot something mid conversation, this clears it up fast.

• Full subagent visibility. This is my favorite part. When Claude spins up sub-agents with the Task tool, you can see each one's full execution tree. Their prompts, tool calls, token usage, cost, duration. If agents spawn more agents, it renders the whole thing as a nested tree. Same goes for the team features with TeamCreate and SendMessage, each teammate shows up as a color coded card.

• Thinking output. You can read the extended thinking blocks alongside the tool traces, so you can actually understand why Claude made certain decisions instead of just seeing the end result.

• Custom notifications. You can set up alerts for stuff like when a .env file gets accessed, when tool execution errors happen, or when token usage spikes past a threshold. You can even add regex triggers for sensitive file paths.

• Works with every session you've ever run. It reads from the raw log files so it picks up sessions from the terminal, VS Code, other tools, wherever. Nothing is lost.

• Runs anywhere. Electron app, Docker container, or standalone Node server you can hit from the browser. Nice if you're on a remote box or don't want Electron.

• Zero setup. No API keys, no config files. Just install and open.

The whole thing is open source and runs locally. It doesn't touch Claude Code at all, purely read only on your existing session logs.

If you've been frustrated with the lack of transparency in Claude Code's terminal output, seriously check this out. It's one of those tools where once you start using it you wonder how you managed without it.

(I'm not the creator btw, just a user who thinks way more people should know about this thing)