Fluffychat does and I would argue is one of the big ones. Its however quite mobile optimized (basically more like WhatsApp, less like slack).

Github Copilot in vscode can do that and also has the Claude models available

The claude models are just a part of Claude code. I've worked with both copilot with the Claude models and Claude code itself. Claude code is way more capable, and has a greater likelihood of successfully completing a task.

I've been using git + git-lfs to manage, sync and backup all my files (including media files and more) and it's quite convenient, but native support for large files would be great. I'd for example really like to be able to push large objects directly from one device to the next.

At the moment I'm using my own git server + git lfs deduplication using btrfs to efficiently handle the large files.

If large objects are just embedded in various packfiles this approach would no longer work, so I hope that such a behaviour can be controlled.

That's actually something I implemented for a university project a few weeks ago. My professor also did some research into how this can be used for more advanced UIs. I'm sure it's a very common idea.

Do you have a link to the code? I'm curious how you implemented it. I'd also be really intrigued to see that research - does your professor have any published papers or something for those UIs?

Well pipe.pico.sh always uses a proxy server so throughput and latency are worse, but you have your own namespace for the pipes and thus don't have to synchronize random connection strings

Does anyone know how this compares to e.g. instantdb under real-world workloads?

I'm also using uv tools and fixed it by doing something like this to upgrade:

uv tool install llm --upgrade --upgrade --with llm-openrouter --with llm-cmd ...

Same, but put that in a llm-upgrade.sh because the list was getting quite long :)

Is the double "--upgrade" a typo?

Yes, autocorrect on my phone worked against me

I hope this doesn't destroy their financing. I would hate to see them go down, it's a wonderful piece of software.

I have to imagine they ran the numbers and found that that wouldn't be an issue. I wouldn't be surprised if the majority of enterprise use was completely unlicensed before this.

I wonder if this is a prelude to make obsidian open-source. Would be pretty great.

based on the vibes I've seen on the forums, the team is very passionate about keeping Obsidian free, but averse to making it open-source

Lobbying has a pretty pronounced effect and is completely legal