What’s so simple about it?

I said relatively simple. It is mostly an API interface with Anthropic models, with tool calling on top of it, very simple input and output.

▲

brookst 2 hours ago | parent | next [-]

With extensibility via plugins, MCP (stdio and http), UI to prompt the user for choices and redirection, tools to manage and view context, and on and on.

It is not at all a small app, at least as far as UX surface area. There are, what, 40ish slash commands? Each one is an opportunity for bugs and feature gaps.

▲

9dev 2 hours ago | parent | prev [-]

I’m pretty certain you haven’t used it yet(to its fullest extent) then. Claude Code is easily one of the most complex terminal UIs I have seen yet.

▲

dvfjsdhgfv 2 hours ago | parent [-]

Could you explain why? When I think about complex TUIs, I think about things we were building with Turbo Vision in the 90s.

	▲	gorbypark an hour ago \| parent [-]
		I’m going to buck the trend and say it’s really not that complex. AFAIK they are using Ink, which is React with a TUI renderer. Cue I could build it in a weekend vibes, I built my own agent TUI using the OpenAI agent SDK and Ink. Of course it’s not as fleshed out as Claude, but it supports git work trees for multi agent, slash commands, human in the loop prompts and etc. If I point it at the Anthropic models it more or less produces results as m good as the real Claude TUI. I actually “decompiled” the Claude tools and prompts and recreated them. As of 6 months ago Claude was 15 tools, mostly pretty basic (list for, read file, wrote file, bash, etc) with some very clever prompts, especially the task tool it uses to do the quasi planning mode task bullets (even when not in planning mode). Honestly the idea of bringing this all together with an affordable monthly service and obviously some seriously creative “prompt engineers” is the magic/hard part (and making the model itself, obviously).