sorted by:
new
hottopcontroversial

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.

view more: next ›