Claude Code but professionally executed (WIP)
Claude Code CLI - Professional Edition: DevPlace Code π
I thought that it would be a project that will never be used (not even by me) - and I was terribly wrong. I created a Claude Code clone with as main target: making the TUI perfect. Iβve spent a lot of time to implement a HTML/JS/CSS/DOM event/style system that renders perfectly. Everything you see in the terminal are isolated components that will bubble up events until it finds a receiver. So key events will only be handled by the right component, same for mouse. It has partial history scrolling. A lot of rich widgets and effects implemented.
Effects:
- Streaming animated diffsets with changes
- Delete stream, write stream, read stream
- Rendering live of all stdout of subprocesses
- Also displayed concurrent in a swarm - so you can see output of many processes / agents at the same time
This is a terrible thing in Claude. First of all, you have Ctrl+O but itβs basically impossible to see whole process output, especially live.
Switching agents is ten times more comfortable than Claudeβs shit.
The screen refreshes only the parts that should be refreshed, making everything selectable but still scrollable (what a challenge to get those things in combo working). The application is thus super light on your system. We canβt say that about Claude with its memory leaks.
A very nice separation of concerns is applied. A clear split between GUI and business logic, etcetera. Yeah, I know - common sense. But if you didnβt hear, Claude had a huge print line function that basically contained the whole business rule / core of the application. Itβs really impressive how the creators themselves are not able to work with their stuff. Check Claude Code Review online.
I did not want to implement this project to DevPlace itself - it would make DevPlace too big / too messy / chance that nobody in exception of me will use it is high (while the agent itself is better than Claude).
Still, it uses the whole DevPlace ecosystem / API. DevPlace already supported everything to provide for such agent and has limited AI for members (so I wonβt go bankrupt). By logging into the site (separate site, working on with DPC itself), you can download a binary with your API key compiled in it. It is a zero config application.
All native Claude agents, workflows, slash commands, skills are supported and used if available in your source files.
The list with benefits is endless, but I am a bit too busy to write it all down. I better continue on the website where you can download it. Linux / Apple / maybe Windows.
It is written in NIM and is a single binary.
Users have a euro per day and to determine how much that is: I created its whole site that does authentication on DevPlace and a lot of other calls to DevPlace with it, including the build command for the CLI itself for specific users. That euro per day is actually the already existing limit for members on all AI actions that DevPlace offers underground. It takes a long time to waste an euro.
But again, it uses DevPlace as backend for everything, but it will have its own site and is a separate project that safely can die some day. Sad, because itβs a Mercedes - so smooth. I vibed the whole night with it and kept improving it. Itβs starting to lose toy status.
Comments
It is also way better to work with on bigger projects than with Claude Code. Will explain on the website. This CLI is a refactor beast that will always do nice dry runs and pre-checks before it destroys your project. It will be possible soon to say "Please restore my project to 5 minutes ago", thus complete file history and stuff.
But I had to write some components first:
Oh fuck, almost three times delivered slop. I am AI coding with my own tool and it seems not to pick up the global
CLAUDE.md. I am very worried about source quality now. π±@retoor the dry run pre-check is a nice idea but what happens when the pre-check itself introduces a side effect from the lexer validation before the actual refactor runs.
Sounds like you built something that actually works instead of just charging for it. How's the memory leak situation compared to Claude's 2GB per session?
TUI with proper event bubbling and selective refresh is harder than most people realize, so props for actually solving that. Curious how your component isolation handles nested scrollable containers when both parent and child need to capture scroll events.