Hamed Farag

Claudeck - A browser UI for Claude Code. Zero config. 56 features.

by•
Claudeck is a browser-based UI for Claude Code. Real-time chat, autonomous agents, DAG workflows, cost tracking, persistent memory, and a plugin system — zero framework, 6 dependencies, no build step.

Add a comment

Replies

Best
Hamed Farag
Maker
šŸ“Œ

Hey Product Hunt šŸ‘‹

I'm Hamed, a frontend engineer at WakeCap. I built Claudeck because I use Claude Code every day and kept running into the same frustrations:

→ No way to see what each session was actually costing me
→ Terminal-only meant no parallel conversations
→ Claude would ask for tool approval while I was away from my desk — session just waited
→ No visual workflows, no git panel, no file explorer

On March 1st I started a weekend experiment called "shawkat-ai" — just a WebSocket bridge so I could chat without squinting at terminal output.

15 days later. 55 commits. It was a full browser UI with 56 features, competing with YC-backed tools. Cooked during late nights at WakeCap, built by one developer, for one developer (me).

What makes it different:
- Zero framework — vanilla JS, Express, SQLite, 6 npm deps
- Parallel 2Ɨ2 mode — 4 Claude sessions simultaneously
- Per-session cost tracking with 30-day charts
- 4-level agent orchestration (single → chain → DAG → orchestrator)
- Telegram bot — approve tool calls from your phone while AFK
- Plugin system — drop a file in ~/.claudeck/plugins/, hot reload
- Works as a PWA on mobile
- Everything stays local — no cloud, no telemetry, no accounts

One command to try it: npx claudeck

MIT licensed, open source. Happy to answer any questions — especially about the architecture decisions (vanilla JS with zero build step shipping 56 features is a story in itself).