llama.vim ported to Qt Creator

[cristianadam]

At https://github.com/cristianadam/llama.qtcreator/ I've pushed a Qt Creator plugin that I have hacked over the weekend.

The code was first put together by the Qwen3 Coder 30b from the vim script from https://github.com/ggml-org/llama.vim/. Then I contributed the rest of changes. The copilot plugin from Qt Creator was my inspiration when it comes to having a settings page.

I will ask a few of my colleagues for some code review in regard of the Qt Creator bits. There are some TODOs regarding the vim porting. I will address them as soon as possible.

Since you guys have done the vim script, it would be great if you could have a look. I would also want to contribute the plugin to https://github.com/ggml-org if you are willing to accept this type of work.

[ggerganov]

Nice! I don't have Qt Creator configured, so can't test it, but can review the implementation and give any insights in case something is not clear.

I would also want to contribute the plugin to https://github.com/ggml-org if you are willing to accept this type of work.

Yes, happy to accept it. If you decide to do so, I will add you as maintainer of the ggml-org plugin repo.

[cristianadam]

I've took care of the TODOs. I think it's ready for a release. 🎉

I'll have to add some translations for the ui strings and add screenshots and screencasts!

[cristianadam]

https://github.com/ggml-org/llama.qtcreator/settings/actions would have to have Read and write permissions for Workflow persmissions, at the bottom of the page.

This allows the GitHub Actions workflow to create a release, when pushing a tag as a v17.0.0 release for example.

[ggerganov]

I think it is already enabled:

Does it not work?

[cristianadam]

It's all good. I haven't tried it, it just it's not the default value, and for my repo it failed when I first tried it.

[cristianadam]

I've tried pushing a release tag at https://github.com/ggml-org/llama.qtcreator/actions/runs/17095757659/job/48479919383

It got stuck for some reason. 🤷🏻‍♂️

The same tag on my side https://github.com/cristianadam/llama.qtcreator/actions/runs/17095440263 worked just fine.

Later edit: It worked. The first release compatible with Qt Creator 17.0.0 is done! 🎉

[ggerganov]

Later edit: It worked. The first release compatible with Qt Creator 17.0.0 is done! 🎉

Congrats!

[cristianadam]

I've blogged about the whole experience at https://cristianadam.eu/20250817/from-llama-dot-vim-to-qt-creator-using-ai/

[cristianadam]

First peak at the Chat functionality in llama.qtcreator. (ggml-org/llama.qtcreator@75c0bcd is the initial chat commit)

I used it to talk to gpt-oss 20b to create me a qt c++ chat widgets application that chats with a llama.cpp server using its json api.

See how it went at ... https://youtu.be/qWrzcx6QhOA

[ExtReMLapin]

I once had to work on Qt Creator and add Lua support to it.
Working with Qt creators plugin is a pain in the butt

That was the thing that made me left this job

[cristianadam]

Things have changed in the meantime. You just ask the AI to write things for you, plug a github workflow and let GitHub build things for you.

My workflow is:

1. Install Qt Creator with the SDK libraries
2. Create a Kit that has the path to Qt Creator's SDK as part of the CMAKE_PREFIX_PATH, so that a find_package(QtCreator REQUIRED) works
3. Have run target for the plugin as the %{IDE:Executable:FilePath} and the arguments -pluginpath %{buildDir}

The latter would start Qt Creator pointing to the plugin directory and loading the freshly built plugin.

Also worth mentioning is the Lua scripting support that the newer Qt Creator has. But I don't know much about it, and I prefer to create the plugins in C++.