Comment by embedding-shape

> All of the models that can do tool calls are typically good enough to use Git.

But again, it's the "user message > llm reason > llm tool call > tool response > llm reason > llm response" flow I think is inefficient and not good enough. It's a lazy solution built on top of the chat flow.

What I imagined would exist by now would be something smarter, where you don't say "Ok, now please commit this" or whatever.

I already have a tool for myself that launch Codex, Claude Code, Qwen Code(r?) and Gemini for each change I do, and automatically manage them into git branches, and lets me diff between what they do and so on.

Yet I still think we haven't really figured out a good UX for this.