Launching today
Claudy
A proper home for Claude Code — multi-session, multi-account
126 followers
A proper home for Claude Code — multi-session, multi-account
126 followers
Claude Code is powerful, but juggling multiple projects in raw terminal tabs is a mess. Claudy wraps it in a native macOS app with proper multi-session management, auto account switching when you hit usage limits, Draft Commits to checkpoint and restore work mid-session, and a Marketplace to install Skills, MCPs, and Commands in one click.
Pulltodo
The Draft Commits feature is the most underrated thing here. Claude Code sessions can go off the rails 20 minutes in and there's currently no clean way to checkpoint without manually stashing or branching. AI-labeled [Draft] commits that you can restore from and then squash into a clean final commit is exactly the right mental model — it maps how you actually think about agentic coding sessions, not how git works by default. Curious whether the AI labeling is happening locally or via an API call, and whether it's labeling based on the diff or the session conversation.
Pulltodo
@abhay_agarwal5 Thanks Abhay, really glad the mental model resonates! To answer your question — the labeling happens entirely locally using git trailers. When Claudy creates a draft commit, it adds a Claudy-Draft: true trailer to the commit message. No API call, no AI classification — it's just a git convention. This means draft commits are regular git commits that you can inspect, cherry-pick, or manipulate with standard git tools. When you're ready to finalize, Claudy squashes all draft commits into one clean commit so your history stays tidy. Everything stays local and offline-capable.
the multi-account switch on rate limits is the part that would actually save me time — i currently keep two iterm windows open and swap api keys by hand. is account switching surfaced as a manual button or does it auto-fail-over when claude returns a 429?
Pulltodo
@qifengzheng you can config it on the project setting
@mark_g4 per-project threshold + ask/auto toggle is exactly the granularity i wanted — saves me from a global setting that's wrong for half the projects. what triggers the threshold — token count, request count, or actually reading a 429 from the api?
DiffSense
You know the pricing model is broken when you have to have multiple accounts to save money 😅 I guess you get away with that when you have the most successufl product in history.
Pulltodo
@conduit_design That's a fair point! The real issue is the gap between Pro and Max — Pro's limit runs out too fast for serious coding sessions, but Max is overkill (and expensive) for most solo devs. A lot of users end up with 2-3 Pro accounts instead of 1 Max because it's cheaper and gives more total usage. Claudy just makes that workflow seamless instead of logging in/out manually.
Kinda wild that having 3 Pro accounts is now a legitimate dev workflow😭