Claudable: a Lovable-style web builder that borrows the CLI agents you have

The builder shape: describe, preview, deploy

Claudable is a Next.js-based web app builder combining Claude Code's or Cursor CLI's agent capabilities with Lovable's app building experience, and the workflow it names is the product, describe your app idea, such as a task management app with dark mode, and watch as Claudable generates the code and shows a live preview of the working app. Deployment targets Vercel with one click and no configuration, and database integration goes to Supabase for production PostgreSQL with authentication ready to use. The builder itself charges nothing, there is no additional subscription cost for the app builder, the economics resting entirely on the agent accounts underneath. Generation targets production-ready Next.js code styled with Tailwind CSS and shadcn/ui. The hot-reload preview is the loop's heartbeat, changes appear immediately as the AI builds, so the describe-and-watch cycle stays interactive rather than batch, and the generated project is a real Next.js codebase on disk that the developer can take over and edit directly at any point.

Five agents, each with its own economics

The supported agent list doubles as a pricing comparison. Claude Code, marked recommended, runs on Claude Opus 4.6 with native 200k token context, included with Claude Pro, Max, Team and Enterprise plans or an Anthropic API key, installed with npm install -g @anthropic-ai/claude-code and a login. Codex CLI brings GPT-5 support with interactive, auto-edit and full-auto modes, included with ChatGPT Plus and up from 20 dollars a month. Cursor CLI offers multi-model access with AGENTS.md support and a free tier before its 20 dollar Pro. Qwen Code is Alibaba's Apache-2.0 CLI for Qwen3-Coder with 256K native context, 1M extrapolated, completely free. And Z.AI GLM-4.6 from Zhipu runs 3 to 30 dollars monthly, with 200K context. One builder, five backends, swappable by which account is logged in.

Zero setup as a design goal

The zero setup claim is specific, no complex sandboxes, no API key, no database headaches, just start building immediately. The mechanics behind it are visible in the setup section, npm install detects available ports and creates .env files, installs all Node.js packages, and the SQLite database auto-creates at data/cc.db on first run, so the builder's own state needs no external service. A check-cli script verifies the agent installation separately, and the postinstall hook runs the environment setup automatically. The application serves at localhost:3000 with automatic port fallback when the default is taken, the detail that makes the first run survive a busy development machine. The first run is three commands from the README:

# Clone the repository
git clone https://github.com/opactorai/Claudable.git
cd Claudable

# Install all dependencies
npm install

# Start development server
npm run dev

with prerequisites of Node.js 18 or later, a logged-in Claude Code or Cursor CLI, and Git. For the desktop form, dev:desktop runs it in development and the package scripts produce platform builds:

# Development mode
npm run dev:desktop

# Build desktop app
npm run build:desktop

# Package for specific platforms
npm run package:mac      # macOS
npm run package:win      # Windows
npm run package:linux    # Linux

The migration trap, documented

The troubleshooting section names the failure mode of upgrading a tool that owns a database, database migration conflicts happen when upgrading from a previous Claudable version, and the remedy is resetting the Prisma database so it matches the latest schema with npm run prisma:reset. The warning attached is explicit, the command drops and recreates the local database, so back up any data you need before running it. The db:backup command creates data/backups/cc_backup files with timestamps, and db:reset restores initial state, the three database commands forming the maintenance surface of the builder's own history, prompts, generated projects and settings, which matters because losing it loses the context for every app you have described.

Electron on three desktops

Beyond the browser app, Claudable ships as an Electron desktop application for Mac, Windows and Linux, with parallel scripts for each platform, package:mac, package:win and package:linux, all building the Next app then running electron-builder. Development mode runs through dev:desktop, and the repository's electron directory sits beside the Next.js app, pages, components and prisma directories. The desktop form fits the tool's shape, it drives local CLI agents as child processes and watches their output, a natural desktop workload, while the web form keeps the zero-install path. The package.json marks the project private at version 2.0.0, the internal version running ahead of the v1.0.0 release tag.

The stack underneath

The technology choices are current-generation. Next.js 15 with React 19 forms the app, the Anthropic claude-agent-sdk at 0.2.68 provides the agent bridge, Prisma 6 with its client handles the builder's own persistence, ws carries the websocket traffic for live previews, and zod validates the configuration surface. The UI stack is framer-motion, lucide-react, react-icons, react-markdown and highlight.js, the rendering side of showing agents' code and conversation. Prerequisites are three, Node.js 18 or later, a logged-in Claude Code or Cursor CLI, and Git, with GitHub integration providing automatic version control and continuous deployment setup for the generated projects. The agent SDK dependency means Claudable speaks the agent protocol natively rather than shelling out and parsing terminal output, so structured progress, tool calls and file edits arrive as events the UI can render, which is what makes the live preview keep pace with the build.

One release, a fork, and a move

The repository carries one release tag, v1.0.0, titled a fully CLI-powered multi-agent web builder, dated 2025-08-30, with the repository's own version counter at 2.0.0 and the last push on 2026-04-11. The badge links tell an origin story, the project began under the opactorai organization and now lives in anymorph-ai, with links to both repositories standing side by side, and an awesome-claude-code listing beside the author's Twitter and a Discord community. The demo examples name Codex CLI and Qwen Code runs, showing the multi-agent story in practice rather than only in the feature list, and the claude_code_zai_env.sh script at the repository root wires the Z.AI environment specifically. For evaluators, the single release tag and the internal 2.0.0 version imply the master branch is the real distribution, and the Discord community beside the author's feed carries the announcements between tags.

Editorial conclusion

Use Claudable when you already pay for or run a coding CLI agent and want a Lovable-style builder interface over it without another subscription, since the app generates Next.js code, hot-reloads previews and wires Vercel and Supabase around the agent's output. It requires Node.js 18 or later and a logged-in agent, so it is not a standalone AI service. Before adopting, verify your agent is among the five supported CLIs and logged in, expect database migration resets when upgrading across versions since the Prisma schema changes, and prefer the SQLite backup command before major changes, since prisma:reset drops the local database.

Frequently asked questions

Official sources

1. anymorph-ai/Claudable on GitHub
2. Issues
3. License: MIT
4. README
5. Releases