prefix.dev

We just made it really easy to switch from conda to pixi. You can now use the pixi init - - import environment.yml to quickly port a conda project. You automatically get a pixi.toml, lockfiles and a powerful task system.

Ever want to just quickly send some files? sendme by iroh is a very simple clean tool to get it done. No ssh or networking required, just a simple send-receive command. Quickly install it with Pixi 🚀

Pixi is gaining traction fast in robotics, so we built a dedicated landing page to help roboticists get up and running quickly. pixi.prefix.dev/latest/robotic… #ROS #robotics

Pixi now supports relative `exclude-newer` definitions. This allows users to set a cooldown period before using packages from the internet. This helps avoid pulling in vulnerabilities discovered shortly after release.

Database update completed! ✅ We feel that our website is now even snappier - thanks to the latest @PostgreSQL & @TimescaleDB updates.

This work was generously funded by @Anaconda for a workshop we held recently. You can find the book here: prefix-dev.github.io/rattler-book/

Our @tldejager wrote a "rattler book" that teaches the reader on how to write their own package manager, on top of our composable Rust libraries and the Conda ecosystem. Read all about it here prefix.dev/blog/the-rattl…

We're thrilled to announce our second non-prefix core maintainer of Pixi! Welcome Lucas Colley! He's been an ESOC 2025 student and since then kept being active, both in the Pixi repo, our Discord community and by adding Pixi to Open-source projects like CPython, SciPy & Numpy!

However, we need to have an open source CVE mapping for @condaforge packages. To achieve this, we hope to start a conda-forge security special interest group. Read more in our blog post: prefix.dev/blog/securing-…

Supply Chain Security is a hot topic! Pixi already has a "exclude-newer" feature to use a dependency cooldown for an extra layer of security. But we need to go further. As a first step, prefix will start quarantining packages on our mirror immediately when vulnerabilities occur.

If you are missing a plan or would like to require some extra services or support, don't hesitate to contact us prefix.dev/contact-us or schedule a meeting with our CEO, Wolf meet.pixi.run

Existing channels are automatically moved to a "Free Legacy Plan", which has more generous limits when compared to the new "Free Plan".

Over the past years, our platform has grown from just a few small channels to over 600 Conda channels storing more than 20TB of data. To help scale it further, today we are launching a fair pricing model based on your usage and needs. prefix.dev/blog/welcome-c…

Do you want to control your Spot robot dog from a Pixi environment? You can now easily install the spot-cpp-sdk from @condaforge! github.com/boston-dynamic…

More on conda-mirror in the incubator project github.com/conda-incubato…

conda-mirror has a config file that let's you select what subset you want to mirror by familiar matchspecs. Did you know that conda-mirror was rewritten in Rust and uses the rattler libraries?

I've migrated the old Mast3r-SLAM example I had made last year to the latest version of @rerundotio and made a bunch of improvements! I wanted to spend some time with agents to modernize it. Here's an example of me walking around with my iPhone and getting a dense reconstruction at about 10FPS on a 5090. Heres the following improvements I made. Brought it into the monorepo with proper packaging: • Using @prefix_dev pixi-build to get rid of all the mast3r/asmk/lietorch vendored code with just a few small patches. This let me remove so 60k lines of code from the repo! • Don't have to build the lietorch code on my machine anymore, which was taking ~10 minutes to compile (and also made it work on blackwell when it previously did not) Rebuilt the @Gradio interface: • Fixed incremental updates, .MOV uploads, and stop behavior • Made the CLI + Gradio interface share the same entry point so updates automatically propagate Upgraded the @rerundotio integration: • Switched to a multiprocessing async logging strategy • Added video/pointmap/confidence logging • Improved blueprint layout and hid noisy entities from 3D view • Biggest perf win was the async background logger - documented about a ~2.5x speedup from decoupling logging from tracking The newest and most interesting part was my attempt to replace the CUDA kernels for Gauss-Newton ray matching with a @Modular Mojo backend. As a Python dev, every time I look at CUDA code I basically shy away as it's pretty difficult for me to understand. Mojo let me rewrite the matching logic in a syntax I'm more comfortable with while still getting near-CUDA performance. Mojo is now the default matching backend with CUDA fallback. One major piece that's missing is the custom PyTorch op path, but I'll eventually do that as well. I heavily leaned on Claude Code to do the CUDA → Mojo migration, and I have no doubt it's not the cleanest or most idiomatic, BUT it's way more readable for me and helps me better understand the underlying algorithm. This was a ton of work, and a large part of why I'm doing it is how the monorepo compounds. This becomes an artifact for the next example I want to build with Claude that I can point to, which will make it even faster to implement. The compounding nature of this is really interesting and part of why I'm spending so much time trying to make things nice and readable.

You can now register Pixi workspaces globally and access them through their name from anywhere in your shell! From all our conda CLI lovers this was a big request! Thank you Sophia Castellarin for the implementation! #pixi #conda #condaforge