Post

I work on Claude Code now, if it is ever falling short for you I'd love to hear!

2 reposts131 likes

Heavy user here. One thing: when subagents run with run_in_background=True, file reads silently fail — the file_path gets dropped. Causes infinite retry loops. Took us days to isolate. Would love a fix or at least an error instead of silent failure.

I think most make sense? The more the web experience matches my TUI experience, the better. If some are more difficult than others, I think state management is first need, followed by custom commands for skills.

Asking this question publicly is hugely powerful. A problem with most corporate systems is getting basic feedback into the development team. Developers (particularly tool devs) have a strong tendency to be receptive to these inputs, but layers of insulation get put between them and users.

The TUI is amazingly annoying. Breaks completion in iTerm2. Overloads Ctrl-b so you can’t go back a character. Doesn’t have any completion for filenames (and breaks other types of completion). I wish I didn’t have to use it but it’s the only choice with a subscription

can you say more about breaking completion, like when you're in it it doesn't use shell completions? for shell commands? You can get filename completion with `@`, I know ways that falls short for me but curious to hear

I just got stung by this. `@` isn't filename completion. It is file inclusion. If you `@` complete the name of a 5GB file, but tell Claude not to read the file because it's too big, it crashes Claude because it tries to put the entire file in the context.

iTerm2 (on MacOS) has its own application level completion that suggests matches from output across all of your terminal sessions (example attached). It's amazingly useful and the main reason I use iTerm2. Claude Code is the only thing I've seen that manages to break it.

When you try to complete, Claude Code used to cause iTerm2 to suggest JS functions and variables, but now the screen just flashes. Both completely break completion, which means Claude accounts for 80% of all my copy and pasting.

Thanks!, I'm annoyed with myself that I didn't think of doing this. In my defence, I've been using Claude Code (on and off) since it didn't know about Claude Code, and I got out of the habit of asking it how to fix itself.

Hey! One thing I've been wanting for a while now is for the current session id to be visible on the process so that tmux can see it (without having to set any extra flags) The env variable is set in the container that executes tool calls, but isn't set on the overall process last time I checked

I have a tmux command to take fork the session for the current tmux pane (open a new pane, runs `claude resume {session_id} --fork-session`) And the advantage of it being a tmux command is that you can run it while the current session is doing things without interrupting

It is so fun! Hard to ignore when I'd really been enjoying using it for the last year, very fun to work on a product I use all the time.

with a background command running, it becomes possible to lose the visible cursor

oh its very easy to repro with ~any bg command I think? down arrow to select the bg tasks, then up arrow and the cursor is no longer anywhere visible (until I press another key) I usually add and remove a char to get back to working state, annoying if I am trying to edit at the end of the prompt

There's a dangerous bug in how CC checks its allowlist for commands. If the user permits 'safecmd' unprompted, CC will run 'safecmd && rm -rf' and 'rm -rf && safecmd' unprompted. I saw this bug a couple days ago. This report links to some of the many dupe reports: github.com/anthropics/c...

noted, i am constantly seeing shit and have ttyrec recordings i can extract samples from to help determine repro criteria too top of my mind is the thing where two queued messages swap like every other frame and make a huge flickering mess, can try to find some samples tomorrow if helpful

anytime you see a pattern would be helpful to hear, that's the right instinct imo that a ttyrec is more helpful than a transcript. Just the pattern is helpful too though, "two queued messages flicker swapping position" plus a version number!

I've found that the default cloud environment often gets stuck in an unrecoverable state. The UI shows a stop button and neither returns control to the user, nor makes any progress. There aren't any obvious ways to hard-reset and continue.

hi thanks for your work! not sure if intended or user error, but I am stumped figuring out how to copy out claude code output without softwrap newlines appearing as real newlines in claude code in ghostty in opencode, I don't have this issue so i wonder what the difference is between the tuis

I always use claude code in tmux panes so I don't notice this bc i don't expect it to work but yeah for non-indented stuff should be possible to sometimes? always? use softwrap. Not user error

yup I am using ghostty without tmux (somehow I like the simplicity of it) -- would definitely be appreciative if a fix for copying softwraps without hard newlines lands 👾

I currently have a weird workaround workflow of copying claude code output into a text file so I can remove the newlines before pasting it into another terminal. with opencode i can just copy and paste directly, but not sure what tui magic they use

Following on, it's not built: Test-directory (3 new/modified files): - app/api/simulate-verify/route.ts — ... - app/verify-button.tsx — "Simulate Verify" button I'm going to have to create a skill. In fairness, I've worked with junior developers who take this approach.

Hey Tom, just hit a pretty serious problem. I've also been working heavily with a TDD approach this week. Claude was failing on a particular feature when I ran it, but the tests passed. A quick skim of the code, and saw that the E2E test case was injecting a local storage value to force it!