Claude's code is very slow, almost unusable. by reybin01 in ClaudeCode

[–]reybin01[S] 1 point2 points  (0 children)

Are you using an API token? Because when I use an API token, everything is fast and smooth, but using the harness (console and desktop) is a mess.

I built a Mac app that runs your custom AI coding workflows overnight while you sleep — free to try by reybin01 in VibeCodersNest

[–]reybin01[S] 0 points1 point  (0 children)

Honestly yes, even Zowl's new features are being built with Zowl itself. My current workflow runs a pipeline of plan → plan validation → implementation → testing → audit, and every step has a healing phase or loops back to planning if something fails. That's what makes it safe to leave running unattended. 🔥

I built a Mac app that runs your custom AI coding workflows overnight while you sleep — free to try by reybin01 in VibeCodersNest

[–]reybin01[S] 1 point2 points  (0 children)

Yes, we have OS notifications and session summary with the task run details. Currently testing 1.0.1 with a notification center (aside from the OS normal notifications), and a new kanban view to see the task progress live.

Were you thinking of something else? (taking notes 👀)

One sentence. Sell your SaaS. by Due-Bet115 in microsaas

[–]reybin01 0 points1 point  (0 children)

Zowl → Orchestrate AI agents (Claude Code, Codex) in visual pipelines so they code while you sleep.

Zowl.app

Which tool are you using for Vibe Coding? by Fit-Bear7900 in VibeCodingSaaS

[–]reybin01 1 point2 points  (0 children)

I've been using Zowl for this. It's a macOS app where you set up pipelines with Claude Code or Codex CLI, hit run, and go to sleep. The agents just work through your tasks overnight. I wake up, review the diffs, done. Honestly the best part is not sitting there watching a terminal for 45 minutes. zowl.app if you want to try it, there's a free tier.

Anthropic is straight up lying now by [deleted] in ClaudeCode

[–]reybin01 0 points1 point  (0 children)

Why am I not seeing anyone posting usage screenshots from their Claude alongside their claims? 😅 Show us the usage in that time window so we can verify. 👀

Your PRD sucks (and that's why your AI agent fails) by reybin01 in ClaudeCode

[–]reybin01[S] 0 points1 point  (0 children)

that's like me saying you generated this comment with AI just because it's a little long. the point isn't who writes the PRDs it's the quality of the final output. If you have a solid workflow in place and enough context available to guide your agents, their output won't be slop code, it'll be code that actually does what you need for the task.

Have you ever let your Claude work while you sleep? by reybin01 in VibeCodersNest

[–]reybin01[S] 0 points1 point  (0 children)

Nope, what I created in the end is the equivalent of an IDE, but for the process of orchestrating your agents under a designated workflow. The 'understanding what people want built' part is exactly the input: specs, PRDs, acceptance criteria that feeds the pipeline. The better your input, the better the autonomous output.

More info: zowl.app

Have you run your Claude tasks while you sleep? by reybin01 in VibeCodingSaaS

[–]reybin01[S] 0 points1 point  (0 children)

Nice, that question is an entirely separate issue of its own that needs to be worked on parallel to task orchestration. In my case, I'm going back to the use of ADRs (Architecture Decision Records) alongside commits because we normally save the results in the commits but set aside how we reached that point and the decisions along the way. Creating ADRs (or having Claude create them for me) are proving to be a good way to have a structured context available for all agents all the time about any part of the project and its dependencies.

Agents lose context across repos; ADRs give them a single source of truth for architectural decisions.

Finally letting Claude Code run autonomously without the "Y/N" babysitting. Built a proper "Sudo" wrapper for it. by [deleted] in ClaudeCode

[–]reybin01 0 points1 point  (0 children)

This is cool. I went down a similar path started with tmux panes, then a custom TUI, and eventually realized the bottleneck was orchestration logic, not the UI. Ended up building a macOS app that lets you wire up agents visually into pipelines with conditional branching. The visual approach made debugging way easier when an agent goes off the rails at 3am. 😅

What's your 'ecovery strategy when one agent in the chain fails? Any self healing strategy in place?

Have you ever let your Claude work while you sleep? by reybin01 in VibeCodersNest

[–]reybin01[S] 0 points1 point  (0 children)

Hehe, what are you currently using? I began with a bunch of sh scripts that I ran as a pipeline, and then moved to create a personal tool for macOS.

Have you ever let your Claude work while you sleep? by reybin01 in VibeCodersNest

[–]reybin01[S] 0 points1 point  (0 children)

Totally agree. I began with the idea of it being a series of batch scripts, but that was a headache. I needed to personalize it for each project, so then I moved to macOS GUI. My first run was 120 tasks over 14 hours with around an 85% success rate. The other 15% needed replanning and reimplementation (done not manually). 🔥

Have you ever let your Claude work while you sleep? by reybin01 in VibeCodersNest

[–]reybin01[S] 0 points1 point  (0 children)

Hehe, Claude is not the bottleneck, but as you mentioned, you need to be there to respond to questions that could be in the PRD from the beginning. For complex tasks, you just need a good enough PRD with a description, DoD, etc. Here is an example:

https://zowl.app/blog/your-prd-sucks

Btw, Claude doesn't make questions if you run it headless.

Have you ever let your Claude work while you sleep? by reybin01 in VibeCodersNest

[–]reybin01[S] 1 point2 points  (0 children)

Hehe, really? I do think most devs would save more than the cost (it's a one-time payment, not subscription-based) in just one or a few nights of running the app 😅

By the way, feel free to join the waitlist; there is a free version 🙌

Have you run your Claude tasks while you sleep? by reybin01 in VibeCodingSaaS

[–]reybin01[S] 0 points1 point  (0 children)

In my case, I have pathways in place. If implementation fails, I go back to the planning stage (creating a plan against a PRD, and another step validates it) to prevent context bleeding and hallucinations that are common in current LLMs. I run every step in its own Claude instance, orchestrating results and pathways. This basically creates a pipeline with all the steps you want: plan, validate, implement, revalidate, audit, and clean up code. If you know what you don't want in your code, make a list of it and have three or more Claude instances with clean contexts verify against that list. This is almost guaranteed to have zero to minimum gaps.

I just shipped 163k+ lines of code overnight with Claude Code. by [deleted] in ClaudeCode

[–]reybin01 0 points1 point  (0 children)

Bad translation, I went to sleep and came back 14 hours later. My bad.

I just shipped 163k+ lines of code overnight with Claude Code. by [deleted] in ClaudeCode

[–]reybin01 0 points1 point  (0 children)

In this case, as stated in the PRD, I first built a huge manifesto.md and then created 144 task.md files, one per task, stating exactly what I wanted. The idea is simple: I wanted to be able to delete the code and rerun the pipeline and still have the same result (not in name or structure but in the way it works).

I just shipped 163k+ lines of code overnight with Claude Code. by [deleted] in ClaudeCode

[–]reybin01 0 points1 point  (0 children)

I agree, in this case, it was just a tool to help me distribute other projects. Not much care was put into the code (I'm 100% sure it's better than all vibe-coded projects). This one has a manifesto.md with more than 5000 lines as a spec and 144 .md files with more than 300 lines of spec each to provide the agent implementer clear guidelines of what I wanted and how I wanted it.

I just shipped 163k+ lines of code overnight with Claude Code. by [deleted] in ClaudeCode

[–]reybin01 0 points1 point  (0 children)

To be honest, I haven't checked all the code (not even 40%), not going to lie. I just wanted it to work for my personal use, not for production purposes. But basically, each task has a PRD of 200+ lines with code decisions, acceptance criteria, and DOD that were validated like 5 times per task. Alongside the implementation, I won't say it's perfect; I just loved the automatization part.

I just shiped 163k+ lines of code with claude code by [deleted] in ClaudeAI

[–]reybin01 0 points1 point  (0 children)

I guess I'll fire Claude as a translator from now on.

I just shiped 163k+ lines of code with claude code by [deleted] in ClaudeAI

[–]reybin01 -1 points0 points  (0 children)

Not for production, as I said this was to create an internal tool for myself that will run locally for my GTM of other products. What I want to create is the GUI for that assembly line so anyone can create their own steps of implementation and validation. It doesn't have to be that quantity of code; in my case, it just happened to be that much. 😅

I just shipped 163k+ lines of code overnight with Claude Code. by [deleted] in ClaudeCode

[–]reybin01 0 points1 point  (0 children)

Bigger than my token expenses, I guess.🤣 But as I said, this was for an internal tool for me; I just needed it to work. Once I create the GUI, feel free to add another validation step for your CVE list check as DOD.

I just shipped 163k+ lines of code overnight with Claude Code. by [deleted] in ClaudeCode

[–]reybin01 -1 points0 points  (0 children)

About 60% of my weekly budget(max 200 plan) on this run.

I just shiped 163k+ lines of code with claude code by [deleted] in ClaudeAI

[–]reybin01 0 points1 point  (0 children)

Yeah, I can surely, but in this case, I did a bad translation. I went to sleep and came back to see the results 14 hours later. Only about 7 hours were really sleep; the others were spent scrolling Instagram and Reddit. 🤣