joshheitzman

You don't need a full browser or a full HTML implementation. You just need enough HTML support for markdown converted to HTML and wxWidgets has that level of support for HTML backed in. I've never seen an LLM generate HTML without it being explicitly told to do so, so I don't know where this notion comes from that full HTML/CSS/JS support is needed to render LLM text outputs.

> I actively use all harnesses

Several perhaps, but you definitely aren't using all coding harnesses actively.

Man-month or man-minute doesn't make any difference.

Can you add 27 more coders and cut the app build period down to 25% of what it was?

9 isn't a large number of people and its fairly well agreed on maximum limit for productive team size (the limit can be lower than 9) due to the number of possible communication channels. All that has changed is that a 9 person team can now do more with AI assistance then they could without it.

Not having to build still saves wall clock time. Also Python is a concise language (fewer tokens in context) with a monster ecosystem that avoids a lot of code having to written by agents (fewer tokens for the current task and fewer for future tasks by keeping the code base smaller).

As a counter-example, I use Deepseek v4.1 Flash to make progress on multiple projects (Python, C++, CUDA) every single day.

It is. Harnesses do not need to give LLMs such broad tools like the shell.

Let's bump that sample size to 2. I've observed the same and that observation has heavily influenced the design of my coding agent harness.

> No wonder Rust is becoming the default language for high-performance LLM-written code.

What's the evidence for this claim?

The implementation of the tools don't execute processes (i.e. the implementations aren't wrappers for shell commands).

Yeah, I don't get either. I look at source control as the first line of defense for when agents screw up to badly. I'm not going let the agent mess with the easiest way to undo its screw ups.

From the docs it seems like that would just silently not install the blocked package, so while it would protect my dev environments regular pip installs would still pick up the transitive dependency.

> specific situations in which Claude Code will embed a user's GitHub CLI OAuth token into a response body, and in situations where response bodies are logged, these tokens may appear in LiteLLM logs.

That's pretty hand wavy. What did y'all have CC doing that it had your GitHub CLI OAuth token in its context at all?

Stuff like this is why my coding agent is a coding agent not shell agent that basically own the machine. Mine has no tool for shell use narrow tools specific things like ripgrep, finding files, and deleting files that limit the paths to explicit workspace directory.

I take care of commits, push/pull, building wheels, and publishing wheels myself. It really doesn't take the much time and the coding agent frees up a lot of my time.