willm

I approve of this approach.

The docs for Textual (TUI library for Python) build screenshots along with the docs. Technically not really screenshots, they are SVGs, but principle is the same. They never get out of date.

https://textual.textualize.io/widgets/markdown/#example

What TUIs are you referring to? Mouse is supported and working on just about every TUI framework.

It is possible. Terminals have supported mouse interactions for a long time.

I know for a fact that Textual can generate an entire frame in less than a 60th of a second. Any lag you see has nothing to do with the choice of language. A TUI just doesn’t require that much number crunching to use a low level language.

I’d be interesting in knowing what platform and terminal you observed the lag, when testing Toad.

Not saying there isn't room for improvement. This is the first release, and work is ongoing. But I can't predict everyone's assumptions. Everyone brings their own experiences to the table, and in 6 months of testing nobody has made assumptions you just did.

For instance, "toad run" takes a path to a directory and not a command (check the usage). You've made an incorrect assumption about how that works, based on previous assumptions on how the UI works.

I would be like to understand why you made the assumptions you did, and make changes based on your feedback. But you've chosen to be combative, for reasons known only to yourself.

For the record, I apologize for the "Mr cranky pants" quip. If you do want to improve this software, join the Discord. Let's keep it civil. Merry Xmas.

De nada.

It’s stored statically in the Codebase. In the future, I suspect there will be enough compatible agents that there might be a web service to search them.

I think they are working in the Copilot ACP layer. Doubt it will take long.

It is quite literally instantaneous on my 5 year old laptop. Whatever you are seeing isn't due to the choice of Python.

Thanks!

The ACP protocol supports MCP. That would be how the client provides additional functionality for the agent. There's no UI in Toad for that yet, but there will be in a future update.

Pretty sure you are a troll, but I'll give you the benefit of the doubt, Mr cranky pants.

Toad works the same way as a browser. Tab and shift+tab to move focus. Cursor keys move within the control. That's what is happening on the front page. If you don't like the keyboard control, you could always just use your mouse to click stuff.

The agent modal works in the same way. Tab to focus a control. The currently focused control is highlighted with a really obvious accent color. Seriously, this is how web pages work. Try it with this one.

Tiny modal? It had some padding around it, but there is plenty of space for the contents. 100x20 characters IIRC. Unless you have shrunk your terminal down to less than that.

The commands are provided by the creators of the agents. If they fail for any reason, there is probably some kind of error message you could use for tech support. You would get the same result running the command outside of Toad. But I don't think you were interested in fixing it, as you would have mentioned an error message.

> so the OBVIOUS ACTION of RUN THIS AGENT requires pressing tab, enter, down, down, down, enter, tab, enter.

Even more obvious would be to press space. Which is displayed prominently in the footer. How did you miss that? It even works from the front page. Highlight the agent, and press space. No need to open the agent modal.

> But it doesn't work for multi-word commands. And my trial with toad comes to an end.

It does work for multi-word commands. But if your command contains a space you will need to wrap it in quotes. This isn't a Toad thing, this is a CLI thing. I imagine you don't work in the terminal much?

It should be as easy as running: toad acp “command”

You may be confusing Agent Communication Protocol with Agent Client Protocol. Yeah, 2 ACP protocols. I had no hand in the naming.

If an agent can be configured to use Ollama, then you could use it from a Toad. It might be possible right now.

Pretty sure I could run Toad in Toad, but I’m scared to try.

I don’t follow your first question. Toad already displays pretty diffs. MCP works in the same way as the native CLI.

One of the advantages of Toad is that it is vendor agnostic. In the future Toad will be able to run sub agents, and allocate any agent to any job. Still to figure out the UX for that.

That’s pretty much it. You can bring your own agent. Including OpenCode by the way. I doubt they will mind as they still get paid for the tokens.

You get a nice UI that is only going to get better as time goes on.

It’s far better model to separate the agent from the UI. The current situation is like building a browser for a single website.

Hope you like it. It is still Claude Code doing the work. Toad talks to the agent, and is the agent that works with the LLM. So the results should be identical to the native CLI.

I'm very taken by your response!

I'm sure you recognise some of these? https://github.com/batrachianai/toad/blob/main/src/toad/app....

Guess you don’t like sci-fi movie quotes. You can change that to a simple pulse animation in the settings.

It literally is using Claude under the hood. Should be no different than Claude’s own CLI.

ACP is will designed. It will always be a few features behind the native CLIs as the protocol catches up. But there is very little that you can't do with ACP. A lot can be done with slash commands that are passed through to the agent verbatim.

Python is more than capable of running a TUI. It is just text manipulation after all. Toad uses Textual, which is currently the best TUI library around. I may be biased saying that as I built it...