Dev Tooling Frustrations & TUI Build Intent

April 16, 2026 — 5:34 PM - 6:02 PM PDT
Participants: Cam (solo monologue, some YouTube audio bleed)
Solo — Afternoon Recovery

Executive Summary

A late-afternoon solo session after recovery from prior day's socializing. Frustration with the Claude Code desktop app (missing copy buttons, tab-key conflicts, unfixed bugs that "feel like a nightly build") crystallized into an intent to build a custom TUI coding tool. Broader thread: open-source quality and licensing gripes, with shout-outs to Malice (legal rewrites of restricted OSS) and a sharp critique that many popular tools aren't truly open. Expressed intent to rotate back to the Linux laptop and keep advocating for open-source alternatives.

Key Thoughts

Surfaced This Session

Build Custom TUI Coding Tool — Frustration with Claude Code desktop drove commitment to build own TUI (described as "barely usable" so far)
Pain Points Logged — No copy buttons anywhere, tab key taken by input, PR merge UX broken, right-click menu missing, hotkey handling inconsistent
Linux Rotation — Intent to go back to the Linux laptop for a stretch to evaluate workflow outside macOS
Swap Known Pain Points for OSS — "Close shop and swap out the things we know" — actively replace problem tools with open-source alternatives
OSS License Workaround — Noted Malice as a service that rewrites restricted OSS from scratch for legal use; worth filing for future reference

Topic Mind Map

mindmap
  root((Dev Tooling Session))
    Claude Code Desktop Gripes
      No copy buttons
      Tab key conflict
      Bugs unfixed for weeks
      Feels like nightly build
      PR merge flow broken
      Hotkey inconsistency
    TUI Coding Tool
      Building own replacement
      Barely usable so far
      Alternative to desktop UX
    Competitive Reference
      Routines via API or Webhook
      Plugin store model
      Better readable text
    Open Source Landscape
      Quality frustrations
      Poor maintenance
      Licensing concerns
        Redis situation
        Malice legal rewrites
      Continued advocacy
    Environment
      Rotate to Linux laptop
      Post-socializing recovery
      Sauna break
      

Action Items

Development

Cam: Continue building the custom TUI coding app (currently "barely usable")
Cam: Document Claude Code desktop pain points (copy buttons, tab key, PR merge UX, right-click, hotkeys) for eventual issue filing or as TUI feature requirements

Environment

Cam: Switch back to Linux laptop for a stretch to evaluate workflow outside macOS
Cam: Swap known-pain-point tools for open-source alternatives on next clean-up pass

Research / Follow-up

Cam: Investigate Malice (OSS license-rewrite service) for potential use cases

Transcript

Click to expand raw fragments
Cam: Continued the point where it's barely usable. I was so frustrated that I took the time to try and build my own tool. I'm building [it] into a TUI app. It fixes the first time.
Cam: 300 issues — a bunch of people filing stuff, most of which is not necessarily worth the effort. How much lower the bar does that mix?
Cam: This is the new board review. It has a bunch of new lines it doesn't need. Ways like this because the space got wrapped over. It's just bad. I think they had trouble. So no copy buttons anywhere, which is terrible. So manually select and paste, and PR will give me a button to merge.
Cam: I can't tab out because it uses the tab as an input. They said they'd been using this app for weeks. The ability to really run the code. GUIs for identity coding is cool. Work trees built the new chat view. This is the problem and the reason that I am being as loud as I am about this. Too many open source tools that I care about. The Claude Code desktop app is close to the bottom if not the bottom.
Cam: If I can right-click delete, that's cool. Far better only option where put everything in plot files. We'll have the right to recall that. This is pathetic.
Cam: Everything else kind of sucks, but I like that. I gotta test this. If you open up a terminal in one, it opens up in the one you have selected. This was two prompts. Two prompts. None of the bugs are fixed. This feels like nightly, millions of tokens will close unless it's the right way to do hotkeys.
Cam: They have routines, great template routines that can be kicked off on a schedule by API or Webhook. A whole plugin store. They picked text readable. That copy is worse.
Cam: I kind of know why this is the hottest thing ever — a shit piece of software that's maintained by people who don't seem to open source it. That's the literal only conclusion I can draw. I want to stand on that.
Cam: There are even companies now like Malice that are here to liberate open source. If you or your business wants to use something but the license prevents you from doing it, Malice will rewrite that from scratch in a way that is legal.
Cam: I'm going to continue moving forward, advocating for open source solutions. I think I need to go back to that Linux laptop for at least a little while. All of us close shop and then swap out the things that we know.
Cam: Because everything you're seeing right now was not made by Code or GPT-4. Because OpenAI, a Model 1, are really, really bad.
Audio Bleed: (Significant YouTube video audio overlapping from ~3:45–5:30 PM — car-theft documentary, true-crime, and ad content filtered out as background-noise blocks.)