Hello everyone,
I have spent quite a lot of time trying to make Opencode feel more like Codex (the Windows app), and it got me thinking
If I am chasing a "Codex" like experience, is there any reason to use Opencode instead of Codex itself?
For reference, I am running Qwen 3.6 27b Q8
I’m a Windows user, and I have fairly Windows-y expectations for software: I prefer not having to live in a terminal just to install, build, configure, and run things.
I couldn’t find an app that managed the full llama.cpp-on-WSL workflow the way I wanted, so I made one.
llama.cpp Console is an unofficial Windows desktop app for setting up and running llama.cpp models through Ubuntu/WSL. The Windows app itself is a self-contained WPF app, and it helps manage the WSL side from the UI.
GitHub:
https://github.com/alekk89/llama.cpp-Console
What it can do from the UI:
- Detect/install WSL and guide Ubuntu setup
- Install/update CPU build tools inside Ubuntu
- Install/update CUDA Toolkit support inside WSL
- Install/update Vulkan build dependencies
- Download llama.cpp source from the official repo or a custom repo
- Build CPU, CUDA, or Vulkan llama.cpp runtimes inside WSL
- Search Hugging Face for GGUF models
- Download/register models, including some compatibility hints and companion projector/mmproj handling
- Set launch parameters per model
- Choose which llama.cpp runtime/build each model should use
- Start, stop, and supervise llama-server
- Monitor live tokens, runtime metrics, logs, GPU status, utilization, and temperatures
- Track logs, jobs, downloads, and lifetime metrics
- Manage local OpenCode model/provider/agent config snippets from the app, so a configured model can be added to OpenCode quickly
The main reason I built it is that I wanted the boring setup work to feel more like normal Windows software - click through the UI, see what is installed, see what is missing, build the runtime, download a model, pick launch settings, and run it without losing full control of what's going on.
A few notes:
- This is a Windows-first app. The actual llama.cpp runtime runs in Ubuntu/WSL.
- Model serving defaults to local-only.
- Right now the app is centered around one active served model at a time.
- The first public release is unsigned, so Windows SmartScreen may warn. SHA-256 files are included with the release artifacts.
- This is not affiliated with or endorsed by llama.cpp or ggml-org.
I’ve been using a simpler version of this locally for a while, then polished it up enough to release in case it’s useful to other Windows users. Planned future work includes faster model switching, keeping models warm in RAM where practical, and eventually supporting more than one loaded model at a time.
Please note that I do not own AMD GPUs, so the Vulkan installation/build path has not been validated on AMD hardware by me.
I’m a Windows user, and I have fairly Windows-y expectations for software: I prefer not having to live in a terminal just to install, build, configure, and run things.
I couldn’t find an app that managed the full llama.cpp-on-WSL workflow the way I wanted, so I made one.
llama.cpp Console is an unofficial Windows desktop app for setting up and running llama.cpp models through Ubuntu/WSL. The Windows app itself is a self-contained WPF app, and it helps manage the WSL side from the UI.
GitHub:
https://github.com/alekk89/llama.cpp-Console
What it can do from the UI:
- Detect/install WSL and guide Ubuntu setup
- Install/update CPU build tools inside Ubuntu
- Install/update CUDA Toolkit support inside WSL
- Install/update Vulkan build dependencies
- Download llama.cpp source from the official repo or a custom repo
- Build CPU, CUDA, or Vulkan llama.cpp runtimes inside WSL
- Search Hugging Face for GGUF models
- Download/register models, including some compatibility hints and companion projector/mmproj handling
- Set launch parameters per model
- Choose which llama.cpp runtime/build each model should use
- Start, stop, and supervise llama-server
- Monitor live tokens, runtime metrics, logs, GPU status, utilization, and temperatures
- Track logs, jobs, downloads, and lifetime metrics
- Manage local OpenCode model/provider/agent config snippets from the app, so a configured model can be added to OpenCode quickly
The main reason I built it is that I wanted the boring setup work to feel more like normal Windows software - click through the UI, see what is installed, see what is missing, build the runtime, download a model, pick launch settings, and run it without losing full control of what's going on.
A few notes:
- This is a Windows-first app. The actual llama.cpp runtime runs in Ubuntu/WSL.
- Model serving defaults to local-only.
- Right now the app is centered around one active served model at a time.
- The first public release is unsigned, so Windows SmartScreen may warn. SHA-256 files are included with the release artifacts.
- This is not affiliated with or endorsed by llama.cpp or ggml-org.
I’ve been using a simpler version of this locally for a while, then polished it up enough to release in case it’s useful to other Windows users. Planned future work includes faster model switching, keeping models warm in RAM where practical, and eventually supporting more than one loaded model at a time.
Please note that I do not own AMD GPUs, so the Vulkan installation/build path has not been validated on AMD hardware by me.
A lot has changed and has been polished since my last post. I hope you guys enjoy the simplified trading experience
Windows App - Github
Website - https://www.horadricexchange.com
Why Horadric Exchange and not other marketplaces?
I have put a lot of work into this and I really hope there is some interest in at least trying it out.
This comes from someone who really doesn't like spending time listing items and spending a ton of time trying to trade
For my fellow Windows users, are you guys using something that can use your subscription based app (not API) as a supervisor and planner and have it fully automatically complete a whole project? Something like Aider but being able to use the codex/claude app itself not the API
Will anybody be interested in my local solution? It connects codex/claude or any other app with llm and have it plan/serve and examine the code your local llm writes.
It creates a report copy/paste it into the window and instruct the model to reply into a file where the planner reads and serves the local llm
Is there something better than this that can do the same thing that is already out there and i wasted my time with this?
Workflow
- Create task (basically write a detailed prompt about what you want a plan for)
- Choose which llm you want to write the plan for you (local or selected window)
- It handles everything else automatically from there
CPU: Intel Core Ultra 7 270K Plus
RAM: Crucial DDR5 2x16GB 5600MHz
GPU: 2x Manli NVIDIA GeForce RTX 3090
Motherboard: ASUS WS Z890-ACE SE
Storage: Samsung SSD 970 EVO 1TB + Samsung SSD 990 EVO Plus 2TB
PSU: EVGA SuperNova 1600W
Riser: Thermaltake PCI-E 4.0 Dual 90 Degree Riser Cable 400mm
Case: APNX Creator C1 Black Mid Tower Case
Since it's impossible to cool them when mounted directly on the board with air cooling alone i found another place to mount the second GPU
Did i go too far avoiding watercooling?
Hi everyone, I’ve been working on Horadric Exchange, a Diablo II: Resurrected marketplace focused on reducing friction in trading.
The main feature is fast item listing through OCR (Optical Character Recognition). On PC, the Windows app can capture an item tooltip with a hotkey while you are playing. The app sends the screenshot to the website, where the item is identified and built into a listing within a few seconds.
It is not literally “one click” from screenshot to published listing, because you should still review the item and set an asking price, but the item creation part is basically one button.
For console players, the mobile website supports taking a photo of the tooltip. Open “List an Item” on your phone, tap the photo box, take a picture of the item tooltip, and the site will try to identify it and fill the listing for you.
Other features currently include but not limited to:
- Marketplace listings with card/list view
- Selling and buying listings
- Item roll display and roll-based sorting
- Currency Exchange, where rune/key/gem/etc trades are separated from regular item listings for faster trading
- Estimated values in Ist runes based on completed trades (Requires enough completed listings in order to provide any/accurate data, can be sorted within X amound of days)
- Trade history
- Offers, messages, and notifications
- Draft listings, so OCR results can be checked before publishing or saved while you continue playing
The site is still in beta. There will be bugs, missing polish, and OCR mistakes. The OCR has been trained and tested mostly on data I could collect myself, so more real examples will help improve it over time.
If you try it and something feels good, bad, confusing, or broken, I would genuinely like to hear about it.
Website: https://www.horadricexchange.com
Github: https://github.com/alekk89/horadric-exchange-companion