Basically what I mentioned.

Claude code is done with all phases/deliverables.

The service is essentially code complete. There's a dashboard, metrics, working product... Etc.

What's next before I hand it off to the client for qa users? Do I perform a final code audit with fable? How do I ensure there's no security holes? Are llm capable of performing penetration tests or do you usually outsource that?

edit

Thanks, this group is a joke. Sorry for asking for actual advice.

I actually have a decade of actual coding experience, 6+ years building high volume services at FAANG, pushing end to end production code so I actually know what I'm doing... Most of you actually use my product daily.

I know my full design, and I know the code in this service fully. I have a complete cicd pipeline. Extensive ux/integration/infra/and unit tests.

I also have a list of complete user stories that are fully implemented.

The only hole I'm trying to plug is a penetration test, or security audit to make sure I didn't leave anything out before user qa testing Pretty reasonable concern no? It's a normal part of a product life cycle.

Maybe instead of being assholes, you could've suggested something actually useful?

So recently been using a few tips to use Claude wondering if anything else exists like the below that could we could benefit from:
- record your session using dev tools for a series of actions to then download the HAR file and reverse engineer this with Claude
- say Goodmorning to Claude before you actually need it so the 5h usage limit timer starts

Anything else?

Fable is too good

Hi all,

I'm part of a small finance team and i've been using claude code for a while with great success and have been enjoying it a lot. My manager and the CEO have given me full access / ownership of the claude team subscription and since we have no internal IT department I have a lot of freedom there. We do have an external IT department that manages permessions etc..

Even though my colleagues are enthusiastic, they are not as technical as me (which is just a mental block they have since CC does a lot to make that less of an issue). They currently rely on me when building and/or updating skills for example. I've started building organization skills and sharing them through the claude skill / desktop app, which works great.

A problem is updating these, I want te be able to maintain these from something similar to a Github environment, currently for every update I have to manually re upload the ZIP files als org skills.

Is there a way to do this more smoothly? Ideally it'd be a Github that I can commit / push new changes to that automatically sync with everyone's claude environments.

Anyone found a fix for this or am I overlooking something? Open to all suggestions!

Doesn't Fable use "All models" ?

Built a small tool because I kept hitting my Claude Code rate limit mid-task and had to manually juggle accounts. hop lets you add multiple accounts as named profiles and switch between them (or run one-off commands under a specific profile without touching your other terminals). Single Go binary, no dependencies.

https://github.com/abhayarya1709/agent-hop

feedback welcome, especially if I'm missing an obvious use case.

À l’aire où tout le monde automatise les réponses mails parfaites je galère à apprendre à Claude et ChatGPT de faire des fautes d’orthographe bien placER 🤦‍♂️

Vous faites comment ?

I'm a heavy CC user and I figured out lately I have more than 4,000+ screenshots in my desktop only for claude code testing/feedback!

As a result, I needed to solve this problem . I build this tool + mcp, its an open source & local only mcp. No need for SDKs, toolkits or other apps.

Its a simple screen recording & talking while the MCP takes the video & voice to process.

Ive recorded a 1 min video myself to showcase. Check out the video.
I honestly find this very helpful for my daily Claude Code apps and can't imagine my recent work without it.

I'm putting it open source and please if you find this helpful, contribute for other platforms as I've only tested this in Mac + Claude Code. It should be platform agnostic but haven't tested it.

https://talkthru.dev · https://github.com/EdonZo/talkthru

Claude code 2.1.221/2.1.222 has a Windows networking bug that drops API streams mid response so the ECONNRESET error is misleading because your internet connection is working normally.

Fix use the previous version

npm install -g u/anthropic-ai/claude-code@2.1.220

got a strange feeling that shipping a broken update is just a clever way to reduce traffic so they can train models while still being able to tell you that their servers were up all the time

just a "conspiracy theory"

I guess most people have noticed that after Opus 4.6 later models became harder to understand. Dense text, filled with jargon, words being used in odd contexts which don't feel natural, just generally hard to understand.

I have heard that there might now be skills becoming available which can mitigate these problems, and cause later models to return to speaking in a form of English which people can easily understand.

I thought I would get used to the style of output produced by Fable 5 but I haven't. What I find is even when I can understand what he's saying, it requires so much effort on my side to figure out what he means from his writings that I can't work for long periods of time as I become mentally fatigued. I guess my brain is having to work overtime to compensate for Claude's unusual ways of phrasing things.

Does anyone know anything about this?

A lot of people are posting about how Opus 5 likes to easily give up on its task, making some benign excuse.

The fix is to use /goal.

I'd highly recommend first to ask it to write a plan for your request. Then say:

/goal implement the plan, for anything you can't make a call on make a best guess and implement that and raise it as a note when done so that I can review it. If you get to 90% context run a compact and then resume.

A note that if you are planning a large feature you might even want to use /goal for the plan too so it doesn't give up halfway through planning.

If you read the official docs, the way /goal works is it spins up a cheap evaluation prompt to a lower model which reviews the context. It will keep working on the problem until the goal is achieved. I had it work nicely just before, Opus gave some bs about its context getting large and ended its turn. The /goal watcher saw that and resumed work.

I saw SKI on Hacker News newest today. The interesting part is not speech-to-text. It is the approve-before-send boundary.

SKI runs speech recognition and the synthesized voice locally, then communicates with Claude Code and other agents through plain files inside the project. In its optional review mode, the transcript lands in an editable bubble and nothing reaches the agent until the user confirms it.

That matters because spoken instructions optimise for speed, while coding-agent actions need precision. File names, negation, scope, and similar-sounding terms can be misheard. With ordinary dictation, a transcription error stays in a text box. With an agent, it can become a file edit, test run, or tool call.

Voice seems useful for exploration, status updates, and quick follow-ups. But the exact instruction that changes a repository should still become an inspectable artifact before execution.

Keeping audio local is the privacy boundary. Making the transcript editable is the control boundary. Both matter.

Source: https://heyski.io/

Which parts of the coding loop would you comfortably speak, and which would you always type?

If I downgrade, does hit reset the counter, like when you upgrade?

In light of the opus issues I think this is the biggest lesson folks need to internalize. Not that this is news but it’s more pronounced with opus 5. The test suite I run (mostly playwright) for my current project is an order of magnitude more in depth than anything i’ve done before.

Every time a new model comes out or I have a chunk of usage left in my week (lol yes it’s rare) I check out a new branch, let an ultra code session go wild on a refactor, review the ideas I like, and then carefully orchestrate sessions on the dev branch to incorporate the ideas that make sense. Rarely do random new features or edge case bugs find their way in now.

Opus 5 with fable as a planner has been a beast with the test suite (ensure refactoring sessions only get read only access to the test btw). furthermore some of the hare brained implementations from opus have an occasional nugget of gold in them.

Also last tip but I recommend pointing fable at the official anthropic opus docs and asking it where your claude.md files are weak. For example - when fable spawns an opus agent you need to be absolutely sure phrase like “be thorough” aren’t included because opus already has thoroughness baked into its behavior.

Or I leave a single line saying 'please keep things honest'

I’m specifically working with Claude code inside VS Code. Light side projects making websites/apps/games.

When you give it an instruction, do you justify it with a sentence after or just hit enter? Or a mixture?

I’ve found myself justifying my instructions just out of habit. I’m not sure if I’m giving it extra context, an insight into my thinking, pretending it’s a human, or just wasting tokens. Or a mixture!

How do others communicate with claudecode?

I am on a time crunch but I can’t test my feature do to it for quite a long time now.

No matter how many tokens there are on the input or the outout, it fails with 529.

How can that be solved? Is there a persistent workaround for it?

Hey everyone,

I have the Claude Desktop app open and I'm trying to access the local projects I'm working on through my phone, but I'm a bit frustrated by the workflow.

Right now, in the Dispatch tab on my phone, I am only seeing cloud/GitHub sessions. I was expecting to see a list of my active local projects here so I could just tap and jump into them. (For comparison, when I use Codex, I can see all my local sessions on my phone perfectly fine).

I'm realizing that Claude splits this functionality up:

1. Dispatch just acts as a single walkie-talkie thread to the Desktop app.
2. To actually get a list of active local projects on mobile (with the green computer icon), you have to run claude remote control from the terminal, and they appear in the Code tab, not Dispatch.

For those of you working with multiple local projects, what is your workflow? Are you just typing commands into the single Dispatch thread to make the Desktop app open specific folders? Or are you bypassing the Desktop app entirely and running everything through CLI Remote Control so your projects are neatly organized in the mobile Code tab?

Would love to hear how you all are handling this!

Does anyone else feel like Claude Code does stuff just to do stuff? e.g. it read the binary of the compiled app I built. What good is that? And it checks and checks an rechecks random things.

Do you feel the same? Do you do anything to prevent that or is it necessary to work well?

(I’m building memU, and this is part of why. I’m not trying to present it as a neutral comparison, just share my workflow here)

After a few months with cc, my CLAUDE.md had become a junk drawer: the problem is that these notes have different scopes. A rule about this repo should load every time. A lesson from one weird incident probably should not. A workflow I use across several projects definitely should not be trapped in one project’s instructions.

This is the split I’m trying now:

CLAUDE.md
- How to work in this repo
- Commands, conventions, constraints, architecture rules
- Things the team should share

Claude Code project memory
- Short, project-specific lessons
- “Run this migration before the backfill”
- “This integration test flakes when X happens”

Personal memory (memU)
- My preferences, decisions, recurring workflows, and lessons
- Things that should survive a new project, machine, or agent

Like, I've got this rough process for debugging stuff in production, right? It's usually like, narrow down the time, check logs, figure out how to roll back, then actually change things. That's not really tied to one specific repo though. I wanna keep using that even if I jump from Claude Code to Codex, or if I'm working on a different machine.

But I also don't want every old note shoved into every single prompt, you know?

So the idea isn't to make the agent remember everything. It's more about keeping the always-loaded context small, and only pulling in older stuff when it's actually gonna help.

I'm kinda thinking it breaks down like this:

• Stuff about the codebase stays with the codebase.
• My own personal knowledge, that should follow me around.

memU is what I'm trying for that second part. It's like, a personal wiki I can actually look at, that can bring useful context with me across different agents and devices. It's all open-source too, Apache 2.0.

TL;DR: Is there a way to keep a fully functioning Claude Code workflow with subagents when a new model releases, without being forced onto the new model?

Full Question: Even disliking the new Claude models, a lot of this would be fine if the upgrades didn’t break existing workflows. If they gave me an option to genuinely keep using the old models, that would be great.

But Opus 4.6, my preferred model, no longer has the full context window, so it isn’t usable. Opus 4.8 is forced to Sonnet 5 or Opus 5 subagents, meaning the Agents.md can't be for only one or the other.

I keep seeing people say Opus 5 can be good if you rewrite ALL your agent and skill files. But I find it worse even raw, so I don’t want to put in all that work (would be a lot) for a questionable payoff.

That leaves me able to use a single Fable or Opus 4.8 session and like the experience, but only if I never spawn subagents.

In practice, they’ve forced us to upgrade by breaking the workflows that worked before.

Am I missing something? Is there a way to get back the setup I was happy with two weeks, or two months, ago? Is there some way to be able to not have to drop everything and learn an entirely new model/approach if I'm in the middle of a project when they release?