the rust side is Tauri 2, and a few parts were fun to build:

speech runs on transcribe.cpp in its own worker process, so a GPU driver crash or a GGML assert kills the worker instead of the app. if the GPU worker dies it retries once on a CPU-only worker.

voice commands go to a small router model as one forced tool call. every tool (open an app, play media, write an email, press keys) goes through a single Effects trait, so a dry run just records what would have happened.

the phone app reaches the PC through a tiny relay server, and the live window view is WebRTC with webrtc-rs, Windows.Graphics.Capture and Media Foundation H.264.

the video is a real screen recording.

https://github.com/ishangautam7/Talvio

[Sorry for the re-post the video was not showing]

Favnyr is a lightweight file browser (Rust+Slint) for Windows and Linux. At its core are workspaces: separate environments that keep their own views, tabs, folders, layouts, and display settings. You could have one workspace for work, another for games, and another for learning a new subject, then switch between them in just two clicks. Favorites remain shared and persistent across all workspaces.

Each workspace can contain multiple split views and movable tabs. Tabs can be dragged between views, detached, or dropped onto another view to create a new split layout.

Favnyr also includes shortcuts, local and network drives, configurable keyboard shortcuts, and custom commands.
It is not intended to compete with or replace the native file browsers provided by Windows and Linux, but to complement them with a different way of organizing and navigating files.

Because of the project’s complexity, AI has been used as a development assistant. However, every feature is reviewed and hand tested extensively before being considered complete.

Link here (include a video demo) => https://github.com/GlitchAwakened/Favnyr

Hi everyone,

Last week I published a shared build cache manager that handles compiled dependencies and Cargo’s artifacts inside a shared directory. The idea is simple: why recompile the same dependencies every time? epicenter takes advantage of the “freshness” rules Cargo uses when compiling a project and lets you reuse what’s already built. No wrapper, no RUSTC_WRAPPER like kache or sccache.

These are some benchmarks on 5 test projects with 37 dependencies (best case: a monorepo with a shared platform crate): five cold builds went from 71.3 s to 15.3 s, and disk usage dropped from 3.65 GiB to 0.91 GiB.

epicenter is a state layer for Cargo builds. It uses features of Cargo that for some reason are not enabled by default, like a shared build directory, and rust-lld instead of the default linker (unfortunately this can’t be used on macOS, because ld64.lld is not a drop-in replacement for Apple’s linker). It manages everything as three tiers: a durable vault (store) of compiled units that survives cargo clean, the shared build dir that every project compiles into, and disposable per-job work dirs seeded from the vault.

How is this different from sccache or kache? They are rustc wrappers: they cache compiler outputs keyed by their inputs, but Cargo still invokes rustc (through the wrapper) for every unit, and each project’s target/ gets its own copy of the artifacts. epicenter works one level above, on the state Cargo itself uses to decide that a unit is Fresh. Restored units never reach rustc at all, and files are hard-linked rather than copied. It’s a different approach to the same problem, and the two can even be combined if you want.

I also developed it to help everyone writing Rust with agents who need different workdirs without creating a worktree for every feature. epicenter lets you create per-job build dirs seeded from the vault, without Cargo locking them and without duplicated dependencies. It also manages the dependencies for you: you can see what’s in the cache, prune old stuff by age, or evict a specific crate or a stale toolchain generation, with a dry run first so nothing gets deleted by surprise.

It’s built to be plug and play: run epicenter setup (or epicenter setup --fast) once, then keep building like always. It works with both stable and nightly toolchains. Linux/WSL and Windows are verified, while macOS is only compile-verified for now, so if you’re on a Mac I’d really appreciate it if you tried it and told me what breaks.

Requires Rust 1.91+.

https://crates.io/crates/epicenter-cli