I've seen people set up crons to run every 15 minutes and accidentally spend a ton because the agent runs every time, even when there's nothing to do. Do you have a way to run a cheap check first and only wake the agent when something actually needs its attention?
I think there are a lot of people using AI who aren't as familiar with these tools as us. We stop noticing a lot of the complexity when we pick it up gradually. There are so many powerful capabilities built into codex/ claude code that have little or no UI affordance.
it's tons of small things like choosing the right effort level for a task. or knowing when to ask for subagents. oh, you can have two threads working at the same time and communicating with each other? you can do /side to parallel path and fold that back into the main thread?
which of these things happens automatically, and which do you need to ask for? and does any of this still work the way it did a few months ago?
the list goes on forever. many users of AI are only just now getting comfortable with skills (and probably still writing bad skills unfortunately hah).
A lot of the specific things you learned may have become obsolete. But there's still a gap between what these tools can do and what most people know how to get them to do. Keeping up with that is a skill too, but perhaps not forever.
> and does any of this still work the way it did a few months ago?
For me this is why it's not worth it investing much time and effort learning any specific AI workflow. Remember "prompt engineering"? Remember "Ralph loops"?
I'll play with various harnesses but until things settle down in a few years I'm not going to learn Claude Code the way I learned SQL.
"In a few years" is eons. I have absolutely no idea how these things will look in a few years and I'm not at all confident that it will settle, rather than accelerate until it's basically not even recognizable as a software "tool" that you have to "learn" for a "job".
Codex /side allows you to toggle to a different pane and maintain an ephemeral or persistent side conversation at the context point which it was launched. It can't natively communicate back to the main thread though. It also allows you to fork the side chat into a new chat. I don't believe it can edit files in side chat mode so the only way to paste context back is fork and do that or just copy and paste. So similar to /btw but with other features.
Claude allows the teams feature and easily spawning co agents or subagents in tmux panes you can interact with (or send to the background). These can communicate with each other. Sometimes you can't interact with one of the tmux agents agents though if it was spawned as some specific type I can't remember.
Here's a certified human written post from the one and only Yvon Chouinard about tumplines. Patagonia actually used to sell a tumpline compatible with some of their packs briefly in the 2010s!
I've been a trackpad proponent for years, but with Steermouse I've been able to dial in my MX Master so perfectly that I find myself missing it when I travel.
What really took it to the next level for me were adding chord mappings. For example I can hold right mouse button + scroll the thumb wheel to adjust volume. So convenient!
Your point on the harness is interesting. How do you distinguish characteristics of the model from characteristics of the harness?
In the early days I feel it was more apparent. You would frequently see the model making failed tool calls etc.. but now that feels so rare. I'm not confident I can perceive whatever shortcomings of the harness remain.
I'm not talking about model performance. I just mean the UX of Claude Code. I'm trying to use pi but there are so many paper cuts. Of course you can configure everything but that's a ton of work. Claude Code has pretty good defaults.
Bit of a tangent but at work we have GitHub Copilot and the VSCode harness is somehow night and day better than whatever happens in the IntelliJ plugin. Aside from having better features, for some reason prompts seem to be cheaper as well.