Claudy

What is Claudy?

Claudy is a native macOS app that provides a dedicated “home” for Claude Code. It’s designed to help you manage multiple Claude Code sessions, projects, and accounts within a single interface, including persistent session history.

The core purpose is to make Claude Code workflows easier to organize—so you can switch between projects, track different accounts, and checkpoint work without relying on manual, ad-hoc setup.

Key Features

• Multi-session tabs per project: Run multiple sessions within a project using tabs, and switch between projects in a sidebar while keeping each session’s history persistent.
• Multi-account switching: Configure multiple Claude accounts and have Claudy automatically switch accounts as usage limits are approached, with real-time usage bars for each account.
• Compact Mode layout: Shrink the window as needed; the sidebar collapses and a quick-switch bar appears to keep navigation available without taking much screen space.
• Draft commits for mid-session checkpoints: Create checkpoint commits labeled as [Draft] git commits, restore prior checkpoints, and then squash them into a final commit.
• Built-in Marketplace for plugins: Browse and install MCP servers, skills, and slash commands from within the app, with one-tap installation into your Claude Code setup (avoiding manual config files).

How to Use Claudy

1. Install Claudy on macOS and open the app.
2. Set up your Claude accounts in Claudy so it can manage switching and show usage bars.
3. Create or select a project, then open one or more Claude Code sessions as tabs.
4. Use checkpoints during work by creating [Draft] git commits, restoring a checkpoint if you need to backtrack, and squashing to a clean final commit when ready.
5. Add plugins when needed by browsing the built-in Marketplace and installing MCP servers, skills, or slash commands with one tap.

Use Cases

• Parallel experiments in one project: Keep multiple Claude Code sessions open at once (as tabs) while you try different approaches, without losing each session’s prior context.
• Project-based workflow switching: Move between multiple repositories or project tracks using the sidebar, with separate Claude Code instances per project and persistent history.
• Managing work across multiple accounts: When you rely on more than one Claude account, use Claudy’s automatic switching as usage limits approach to avoid manual account changes.
• Checkpointing and recovery during long tasks: During iterative development, create [Draft] checkpoint commits mid-session, restore a checkpoint if direction changes, then squash changes into a final commit.
• Quick setup of MCP servers and extensions: Find and install MCP servers, skills, and slash commands from the Marketplace without editing config files.

FAQ

• Does Claudy persist history for each session? Yes. Claudy runs each session with its own Claude Code instance per project and keeps persistent history.

• How does Claudy handle multiple Claude accounts? You can configure multiple accounts, and Claudy auto-switches when an account approaches its usage limit. It also shows real-time usage bars for each account.

• What is Compact Mode? Compact Mode is a layout adaptation that collapses the sidebar and shows a quick-switch bar when the window is made smaller.

• What are [Draft] git commits in Claudy? Claudy can checkpoint work mid-session as [Draft] git commits, label them for identification, let you restore checkpoints, and then squash into a clean final commit.

• Can I install MCP servers and skills inside Claudy? Yes. Claudy includes a built-in Marketplace where you can browse and install MCP servers, skills, and slash commands with one tap, avoiding manual config file changes.

Alternatives

• Terminal-based or IDE-based Claude Code workflows: Use Claude Code directly via terminal or editor integrations. This can be flexible, but typically lacks Claudy’s single-window organization for multi-project sessions, account switching, and draft checkpoint workflow.
• General-purpose tabbed workspaces: Use tools that organize projects and processes into tabs/windows. These may help navigation, but they usually don’t provide Claudy-specific features like automatic multi-account switching, Draft checkpoint commits, or the built-in Marketplace.
• Plugin/package managers for extensions: If your focus is installing MCP servers/skills/slash commands, a package manager approach may cover installation needs. Compared with Claudy, it may require more manual configuration steps and won’t centralize session/project management in the same way.