klodolph

Maybe it just reached its peak with “just according to keikaku (translator’s note: keikaku means plan)”

You can figure it out from context if don't know one or two words in a paragraph. If you are missing a word from most lines of dialogue then you are probably going to struggle.

People who can figure out words from radicals probably have >500 word vocabularies to begin with. I’d say if you started learning on some natural progression, you would start learning how to figure things out from radicals once you knew somewhere around 300 kanji (which would mean you have a vocabulary of 1,500 words, ish).

Before that point, you are probably going to have too much trouble generalizing.

It’s just a choice of which key to use. I don’t think it was some decision made with this intent, I think it is just the unexpected result of a decision.

The KHR_debug is also kind of a pain to use because it gets called asynchronously (which is what you want, yes, but the difficulty is still there).

Yeah, I've migrated away from tmux and back to using terminal windows.

Interesting. I’ve been using it heavily on macOS (ssh to Linux host) and over the web using xterm.js, and it’s been working about as reliably as tmux did. Sometimes it doesn’t resize properly, but that’s also true of tmux (when I see a big field of .).

I’m aware of “normalization of deviance”, but I think of it as a problem, and I should solve it, work around it, or decide that the status quo is fine.

Like, if I got shouted at for saying what the previous five consultants had said, I would take that as a lesson.

I've been using shpool these days (especially for things like Claude / Codex / etc). Shpool only does persistence, not multiplexing. It turns out this is exactly what I want. I want to have one keyboard shortcut, to detach the session, and that's it.

I can do terminal multiplexing better in the GUI—tabs, virtual desktops, or in the browser with xterm.js.

Yes, you can learn all these different tmux shortcuts, and I know them well enough. I like using the shortcuts in my terminal emulator better. All I really want is a way to continue my session after putting my laptop to sleep, and shpool does exactly that and no more.

Doesn’t this line of debate get kind of predictable?

I didn’t see your reply.

It should be the harness responsibility to create / destroy things like worktrees and scratch spaces, and communicate to the agent (e.g. via system prompt) where the scratch space is and its purge schedule. Harness should also set appropriate env vars to make this work in tools.

> With the same behavior showing up in multiple high-profile harnesses (Codex, Claude Code), it feels likely there must be some actual reason for doing it this way.

I think fixing it is just not high on the priority list.

Harnesses should be responsible IMO for managing lifecycle stuff, including worktrees and temp files.

It’s simple, deterministic stuff. At least most of the time.

Over eager use of /tmp is the worst. That’s RAM, my boy! Precious gold.

It was a literal factbook online. In high school, I remember using it to look up facts like the area or population of different countries.

from what I understand, there’s a high standard here, beyond “beyond reasonable doubt”, along the lines of “no appearance of impropriety”