1. Are you using a Claude Code subscription? Or are you using the Claude API? I'm a bit scared to use the subscription in OpenCode due to Anthropic's ToS change.
2. How did you choose what models to use in the different agents? Do you believe or know they are better for certain tasks?
Frankly I didn't "build" anything. It was mostly just a case of setting up the docker scripts, make sure the volumes have proper permissions and the configuration is sane. The configuration though, I'll take all the credit in the world for wading through, haha. These are not software with opinions included.
My Main Problem is To keep the bridges up to date. I just switched my phone number in WhatsApp and Signal and that lead to a huge ton of trouble for my bridges. After a month of fiddling with it, deleting things, updating, logging in and out of accounts and puppets, I still don't get any messages from signal into element. While it was working for years just fine it gives me the most trouble now that my dad is in the hospital in another country and I have to coordinate with my siblings a lot.
Sometimes Claude Code scrolls up far away, and I struggle to scroll it down again. And I have to restart the terminal and Claude Code for it to behave well again. But I don't know if this is the flickering issue, or if it's due to a bug in Windows, Alacritty, Zsh or something else.
Thank you, that's the primary issue I have too, I'm surprised it's not being talked more here in this thread. I am on iTerm2 in macOS so not specific to your environment. It's really annoying and restarting doesn't fix it in my case, only a fresh session.
I was having this issue with Claude code, and even worse with Gemini, while using the VSCode terminal. I switched to Ghostty and I don't have any flickering or weird scrolling issues at all anymore.
In my case, Mudita Kompakt phone and Boox Go tablet for reading textbooks. Mudita has the stock launcher, Boox is full of bloatware and I installed Niagara
I know they have said that. But it feels a bit strange to me to continue to develop in C++ then, if they eventually will have to rewrite everything in Swift. Wouldn't it be better to switch language sooner rather than later in that case?
Or maybe it doesn't have to take so much time to do a rewrite if an AI does it. But then I also wonder why not do it now, rather than wait.
mise has more features - it is a super set of asdf. For example it can set your env vars when you cd into a directory (like direnv). It also has tasks (which I haven't used) - they appear to be similar to what a Makefile does. So you can potentially replace three tools (asdf, direnv, make) with one.
Mise started out using the same plugins as asdf, mostly focused on adding performance and usability improvements. Over time it added more features and security.
Most tools are now directly fetched from github releases without the need for random shell scripts (which is what asdf plugins are).
It also grew to be a task runner and environment manager. At first you might think this is scope creep but they're both opt in and very elegant additions. I don't want to ramble but let's just say they've solved real problems I've had.
I'm a fan of it, and I can't think of a reason why I would use asdf over mise. Its real competition is nix (+devbox/devenv/flox), devcontainers, and pixi.
