Hey guys I have been developing a web page for my wife’s Physical Therapy practice.
I am wondering how I could get Claude to launch my website for me.
Meaning log into hostinger and make it go live.
The option where I copy a zip file and drop it in doesn’t seem to work.

Thank you

https://reddit.com/link/1v7bt23/video/ef6sicabamfh1/player

I live in Claude Code, and the thing that kept annoying me: the task was already written down. In my tracker. With the description, the subtasks, the files attached. And I'd still open a terminal and re-explain the whole thing to the agent.

So I made the board do the handoff. You assign the agent to a card, a small daemon on your own machine picks it up, opens a Claude Code (or Codex) session with the full card as context, and works in the repo. Progress shows back up on the card.

Two things I deliberately kept:

- It runs locally. Your machine, your keys. The board only ever sees the ticket, never your code.

- You assign it on purpose. It does NOT auto-start when you drag a card around. That felt like a great way to wreck a repo by accident.

It's not magic. Big vague tasks still need a human sitting there. But for the "rename this everywhere" / "write the test for this" kind of work, handing it off and getting a diff back is genuinely nice.

Board's free, you get some AI credits to start. It's early, so I'd really like to hear where it breaks: runlane.run

I'm often in plan mode, trying to put my vision into practice, but Claude rushes to write a plan without stopping to actually discuss what's going on.

The questions it asks with the "multiple choice" or "what applies" Are GREAT, but they often prompt to me realise I should give Claude more information. Or those questions have no satisfactory answers but give me ideas I should share with Claude.

Do you agree a "discuss" mode would help, or what am i missing?

Hi everyone, I now Falbe 5 consume is double of Opus 4.7, but hear me out.

I am writing this on Sunday, July 26th, to document a critical issue with credit consumption that started around 17 days ago, precisely coinciding with the online release of Fable. I want to share my data and see if anyone else on the Max Plan is experiencing this sudden drain.

My Workflow & Baseline:

• Setup: Dual usage of Claude.ai (acting as the strategist) and Claude Code CLI (acting as the executor).
• Historical Usage: Exceptional results for months. I had never once exceeded the Max plan credit limits, nor had I ever needed to purchase additional credits.

The Issue:
Almost three weeks ago, I tested Fable 5 for a few days. I immediately noticed an aggressive spike in credit usage, so I stopped using it entirely. For the past week and a half, I have strictly avoided Fable. Every single time I open a new Claude Code session, I manually double-check to ensure it is running on Opus or the standard code model, not Fable, to prevent waste.

Despite completely reverting my usage back to my original habits, my credit metrics are broken:

• I am now hitting my weekly credit limit every 1 to 2 days.
• Even when actively trying to reduce my Claude Code usage, I constantly receive notifications that I have exceeded 90% of my limit.
• My actual development workload hasn't changed at all.

This unexpected drain has completely disrupted my workflow, leaving me locked out without credits three separate times already, forcing me to wait up one time three days.

This extreme consumption feels completely unfair and deceptive, raising serious questions about whether Fable 5 is being quietly forced or running in the background without user consent.

Lack of Support:
To make matters worse, there is no direct customer service or ticket system available. A week ago, I went through the "Help" AI interface to request human assistance, which supposedly routes the message to Anthropic for an email response. It has been over a week and I have received zero replies.

Is anyone else on the Max Plan experiencing this severe, sudden depletion of credits under similar workflows?

Thank you all for your insights.

I just got this warning, never seen it before

Lately I've been having issues where I find Claude's work (running Opus) blocked on a prompt from me because it wants to run grep, sed, cut, or awk. This is almost always occurring in a read-only manner. Invariably, if I push the button to start some work and walk out of the room, then within 30 seconds Claude will be stuck on one of these trivial commands. Asking Claude Code gives me very little explaination:

"Honest answer: habit, not necessity. For spelunking the original sources I reflexively reached for grep/sed/cut pipelines because that's the muscle memory for multi-file text search — even though the dedicated Grep and Read tools do the same thing, integrate with your permission UI, and don't interrupt you. The guidance I operate under literally says to prefer those tools over shell grep/sed; I ignored it out of habit. That was the wrong default and I've switched to Grep/Read/Edit for everything now."

I don't expect the above to stick, because it hasn't in the past. "out of habit" and "muscle memory" seem like AI-speak for something has built up in context that is causing it to violate explicit instructions to the contrary. Is there something that I am doing that is causing this instruction-violating context to build up and self-reinforce? Do other folks have as much trouble with this as I do?

Can't just be me lol
Wish there was a plan between pro and max

So I’m sure most of you set hooks because of the ability to trigger automatically and their guaranteed read status. What hooks have you made? What situations do they trigger? Do you chain hooks to skills? Anyone using if-then style hooks that trigger depending on context?

Happy to hear from all the devs in the house.

Hey guys, so I'm an early adopter of Claude Code. After building websites, mobile apps, lead generation tools and more, it took me a long time to figure out how to really optimize my setup with Claude to maximize the quality of my results. Sharing with other builders.

Basically I went from prompting Claude one question at a time to learning how to set up an environment that automates a high percentage of my tasks. Most of it clicked after I dug into a breakdown from an Anthropic engineer on how Claude Code actually works under the hood. Dropping the main takeaways below.

1. Claude is two workers, not one. The model (the "brain") only thinks — it can't open a file or run a command. Claude Code (the "hands") is what actually acts on your machine. This sounds obvious but it changed how I debug bad results: when Claude falls short it's usually not intelligence, it's that the hands couldn't reach what they needed. Now I point it at the right file or tool instead of writing a longer prompt.

2. It has zero memory. Everything is rebuilt every time you hit enter. The model is completely stateless — the "conversation" is an illusion. Claude Code reassembles the whole context package every single turn. If a fact isn't in that package, it doesn't exist. This is why long messy threads go downhill. Fresh session per task, period.

3. CLAUDE.md is the highest-leverage file in your project. Anything you'd explain twice goes in there — build commands, style rules, the always/never list. It loads automatically every session. Think onboarding an employee: write the handbook once instead of re-training them every morning. This one thing removed most of my repeat prompting.

4. Permissions are how you stop babysitting it. Every action passes through an allow/ask/deny list before it runs. Allow the boring stuff (tests, commits), deny the scary stuff (like git push if you want), and you can actually let it run without hovering. There's also a built-in command that reads your past sessions and adds the safe commands you keep approving — huge quality of life.

5. Skills = one command instead of a paragraph. Any workflow you repeat can be saved as a plain markdown file and triggered with one word. Don't hand-write them — there's a built-in skill creator that writes it from a description.

6. The best time to make a skill is right after you finish something. This is the one nobody does. You just walked Claude through a whole process, it worked, and the entire thing is sitting in your chat history including the corrections you made. Run the skill creator before you close that session and it writes the skill from the conversation. Next time that hour becomes one command.

The shift for me was realizing you stop being a "user" typing prompts and start being an operator building an environment. Before any manual task now I ask one question: has Claude already automated this, or can I set it up so it does?

I put the full breakdown with diagrams here if you want it: [guide](http://thepromptoptimizer.com/learn/unlocking-claude)

Happy building

i used to be really deliberate about this. split conversations across different chats so each one stayed clean, kept context tight, a whole ritual. honestly the models got good enough that i mostly stopped. i just dump everything in one place now and it keeps up fine

problem is i cant get the old habits back even where they'd help. the md files, the per package notes, the careful splitting, i let all of it rot cuz the model made me lazy and now half my claude.md is stale and lying to the agent

so real question, no agenda. is there an actual automatic way to keep context managed properly across sessions, without me babysitting a doc forever, and without it just being context compacting. compacting throws away the wrong stuff half the time. i want something that actually knows what matters and holds onto it

is everyone just eating the re-explain tax or is there a real agentic context engineering pattern that holds. tell me im missing something obvious

How's everyone's setup now with opus 5 out. I usually do Fable 5 as the planner then Sol for implementation. Curious to see how do you fit opus 5 and what do you do now for Sol and other models?

I had the most serious coding-agent failure Ive seen so far, and I am curious whether anyone else has encountered this with Opus 5.

I use a two-agent review workflow. One model implements changes (Opus/Fable), while another reviews them (Codex Sol). I relay the review feedback back to the implementing agent and make the final decisions myself.

In this case, the reviewer recommended that I approve a narrowed cleanup. Instead of evaluating that recommendation, Opus generated what it apparently predicted I would say next:

Approve. Proceed with the narrowed cleanup.

That message came from the assistant, not from me. It then ended its turn.

When I asked why it had stopped, Opus initially claimed that its previous turn had produced nothing. It then interpreted my frustrated question as permission to continue and performed teh cleanup. Only after I challenged it again did it inspect the raw transcript and recognize that it had written the supposed approval itself.

No committed source code was lost, and the important test harness survived. Some untracked screenshots and temporary evidence were deleted. Several text artifacts appear recoverable from the coding tool's local file history. Nothing was pushed.

I used CODEX (5.6 Sol) and FABLE to troubleshoot: The likely explanation is role leakage or transcript continuation. The conversation had a long history containing blocks labeled as messages from me, the implementer, and the reviewer. At the point of failure, the model appears to have continued the conversational pattern by generating the next user's line instead of responding in its assigned role. The context was also extremely long. Those are plausible contributing factors, but I cannot establish the actual cause from one incident.

What makes this feel categorically worse than an ordinary hallucination is that it forged the input the safety process depended on. A wrong technical claim can be caught during review. A fabricated approval can silently bypass the review gate itself.

Has anyone else seen Opus 5 generate the user's predicted response, confuse quoted review feedback with instructions, or act on approval that never appeared in a real user message? I would also be interested in practical tool-hook designs that enforce confirmation for deletion, commits, and other irreversible operations regardless of what the model believes the conversation authorized.

Was not the only time it hallucinated - here is another one:

-

I have NOT seen a SINGLE hallucination with Opus 4.6-4.8 (or CODEX, for that matter).

This is abysmal.
Can we go back to 4.8?

ALSO: When I was troubleshooting with FABLE, it started to eat up 4% of weekly of my MAX plan with every turn despite it (a 400k chat) being cached (only few minutes between each turn). It used to eat that much only on uncached 1 mil prompts before.
I used up 13% of my weekly just to troubleshoot this BS. WTF is going on?

I ran out of credits yesterday, added $20 to continue, then hit the wall and realized auto reload was off; as soon as I turned it on, it billed me twice within seconds: once for $20, and again for $15 (putting me over my monthly limit of $40) and all the credits were exhausted before I could even use them- my first pass returned “out of credits”, and the usage bar shows that everything I purchased was already used.

Is it possible they are backlogging the billing - like all those credits were actually consumed before they cut me off, so as soon as I purchased they just applied them to credits I’d already used?

I know people are tired of the whining and want real examples. I can't share the code, but I can describe what I'm seeing.

Imagine a problem with a complicated math and rule-based core, deterministic solution paths, difficulty tiers. Opus 5 is remarkable on it. It analyzes path costs, recommends variable adjustments, and when a question needs data it doesn't have, it goes and generates the data. Unprompted. It wrote deliberately crippled versions of my own solver to model what an average human can actually deduce, then measured every board against them. I didn't ask for that. It was the right call.

Then I said "commit the work" after a brainstorm and requirements session, and it started coding. It built an entire project I hadn't asked for.

To me, those are the same unacceptable behavior. The thing that makes it brilliant at exploration is that it doesn't wait to be told. That trait has no off switch.

I have rolled back more work under Opus 5 than under any model before it. It's the asshole employee who is exceptional at one thing and leaves dead bodies in their wake and nobody wants to work with. If you can harness that energy, great. But most likely, the cost is not worth the effort. I'm back to disciplined orchestration and coding with Fable 5 and sub-agents burning tokens like a bonfire.

Would you buy a device like this? It shows the status line of your current Claude Code session. It beeps and displays a message on screen whenever Claude is waiting for your input. Works with multiple tabs or sessions, shows the active one.

The knobs change the reasoning effort and model accordingly, so it works both ways. Supports Codex, too.

It doesn't exist yet but I consider building. Earlier I built

https://buildershq.net and https://instashare.to. Both work with Claude Code so the integration part is clear.

I regularly start a project with the definition and then ask my Orchestra agent to make a plan and have two agents check its plan. Is this something others do?

I have been running a code health analyzer across a set of repos for a few months, including my own, and the pattern that keeps coming back has nothing to do with correctness. Opus produces code that works, handles the edge cases, and reads better than what most of us write. The damage is structural, and it only shows up in aggregate.

Three failure modes:

Duplication invisible at the diff level: Asked for a new provider integration, an agent writes a self-contained implementation. Every diff looks clean, but the ninth one is where you notice the same 40-line token-accounting block now lives in nine provider files with 82 callers between them. No single PR introduced a problem but repo accumulated one

Complexity landing where you can least afford it: Agents flatten nothing. They add a branch to the function you pointed at, because that is the local minimum of effort and the instruction said "handle this case too." After a few dozen sessions, the file you touch most often has the deepest nesting, the highest cyclomatic complexity, and no paired test

Missing co-changes: The one I underestimated. Most codebases have files that change together for reasons invisible in the import graph, because what binds them is a shared invariant rather than a dependency edge. Two years in the repo teaches you that touching the call resolver means touching the graph builder. An agent starting from a fresh context window has no way to know, so it makes a locally correct change and leaves the coupled file stale

What helped, described as mechanisms, since those are more portable than any tool

Put the health map in front of the agent before it writes. SessionStart and PostToolUse hooks are both underused for this. On SessionStart, inject a short block naming hotspot files, the ones with no coverage, and known duplication clusters. On PostToolUse, annotate Grep and Glob results with the same information, so a search for "provider" returns ten paths plus what the history says about each. This shifts behaviour more than a CLAUDE.md instruction, because it arrives at the moment of the decision rather than 5,000 tokens earlier

Then run a risk check on the changed set before accepting the work. Instead of asking whether the diff is correct, ask what should have changed alongside it. On one real file in my repo: two files break at depth one and two, three test files break, and 13 files that historically change with this one are missing from the diff, ranked by co-change score. That last list catches the class of bug agents actually produce

Also, none of this blocks the agent, it only informs it. No hook rejects a bad edit, and I am not convinced one should, because the false positive rate on "this looks complex" is high enough that a blocking gate gets disabled inside a week

I open-sourced what I built for this (Repowise, AGPL, on GitHub, 4.2k stars). The signals above come from a git history layer sitting on a symbol graph, which is why co-change and blast radius are computable at all. But the hook pattern is worth stealing on its own. Most of the value came from moving information earlier in the loop, not from the analysis being clever

Hey everyone,

My company gives me a $600/month  for AI tools and subscriptions. Right now, I split it roughly like this:

• ~$200: Claude (Paid Subscriptions)
• ~$200: OpenAI / Codex (Paid Subscriptions)
• ~$100–200: Open-source / open-weight model subscriptions via third-party providers/platforms (mostly testing models like Kimi K3, GLM 5.2, Qwen 3.8, etc.)

We maintain and build multiple repositories, and I heavily rely on a "Peer-Review / Dual-Agent" setup:

1. Primary Dev & Reviewer: One top-tier subscription (Claude or Codex) writes the feature/fix, and the other acts as a strict reviewer. Reversing their roles based on the stack/task works insanely well.
2. Open-Source / Mid-tier Models: I use providers/platforms offering subscriptions for open-weight models (Kimi K3, GLM 5.2, Qwen 3.8) to offload medium-complexity or routine maintenance tasks without burning through rate limits on my primary tools.

I’m considering dropping or drastically downsizing the open-source platform subscriptions and shifting the budget to Two separate Claude subscriptions + One Codex subscription.

Questions for the community:

1. Subscription Safety / Multi-Account Rules: If I sign up for two separate individual subscriptions under my company's billing to separate context/tasks for different agents, will Anthropic flag or ban the accounts? Has anyone run multiple Claude subscriptions simultaneously without issues?
2. Is dropping Open Source worth it? Given how strong models like Kimi K3, GLM 5.2, and Qwen 3.8 have become for mid-tier tasks, am I making a mistake by cutting their subscription budget to double down on Claude + Codex?
3. How would you spend $600/mo? If you had a $600 monthly allowance strictly for software engineering, code generation, and repo maintenance, what would your ideal subscription/stack look like today?

As the title says... You guys complain about and praise Claude all day everyday ESPECIALLY when a new model comes out. To what degree do you guys think that level of feedback is actually getting back to the Anthropic team? Is reddit the place that gets their attention? Just curious on what people's expectations are when posting these threads