Show HN: Vicinae – a native, Raycast-compatible launcher for Linux

Hacker News (score: 22)
Found: September 09, 2025
ID: 1296

Description

Other
Show HN: Vicinae – a native, Raycast-compatible launcher for Linux Hi HN!

I’ve always been a fan of application launchers, and I was impressed by the approach the Raycast team took — especially their extension system. About six months ago I started building something similar for Linux, aiming to integrate deeply at the OS level and give extensions a lot of power.

Vicinae is written in C++ with Qt Widgets. I chose Widgets over QML for more imperative control of the UI, especially around extension handling. So far that’s worked well — modern C++ is great.

To support my goals I built a number of custom widgets, including a fully virtualized list that can efficiently render tens of thousands of items. That gave me a lot of respect for Qt — it’s a powerful framework that mostly stayed out of my way.

A key feature is support for Raycast extensions (React + TypeScript), most of which can be installed and used directly inside the launcher (though not all features are implemented yet). There’s also a native API package (@vicinae/api) for writing Vicinae-specific extensions with additional capabilities. This required writing a custom React reconciler — surprisingly straightforward, though still unpolished.

Like Raycast, Vicinae ships with powerful built-in modules, but the goal isn’t to make a clone. I want it to grow into its own project that fits the FOSS model better, while staying compatible with the Raycast ecosystem. I also plan to bring it to other OSes eventually.

I’d love feedback on the technical approach, and suggestions for what would make this useful to you. Contributions are very welcome — I’ve already been pleasantly surprised by how quickly people started helping.

Docs: https://docs.vicinae.com Repo: https://github.com/vicinaehq/vicinae

More from Hacker

Show HN: Hc: an agentless, multi-tenant shell history sink

Show HN: Hc: an agentless, multi-tenant shell history sink This project is a tool for engineers who live in the terminal and are tired of losing their command history to ephemeral servers or fragmented `.bash_history` files. If you’re jumping between dozens of boxes, many of which might be destroyed an hour later, your &quot;local memory&quot; (the history file) is essentially useless. This tool builds a centralized, permanent brain for your shell activity, ensuring that a complex one-liner you crafted months ago remains accessible even if the server it ran on is long gone.<p>The core mechanism wants to be a &quot;zero-touch&quot; capture that happens at the connection gateway level. Instead of installing logging agents or scripts on every target machine, the tool reconstructs your terminal sessions from raw recording files generated by the proxy you use to connect. This &quot;in-flight&quot; capture means you get a high-fidelity log of every keystroke and output without ever having to touch the configuration of the remote host. It’s a passive way to build a personal knowledge base while you work.<p>To handle the reality of context-switching, the tool is designed with a &quot;multi-tenant&quot; architecture. For an individual engineer, this isn&#x27;t about managing different users, but about isolating project contexts. It automatically categorizes history based on the specific organization or project tags defined at the gateway. This keeps your work for different clients or personal side-projects in separate buckets, so you don&#x27;t have to wade through unrelated noise when you&#x27;re looking for a specific solution.<p>In true nerd fashion, the search interface stays exactly where you want it: in the command line. There is no bloated web UI to slow you down. The tool turns your entire professional history into a searchable, greppable database accessible directly from your terminal.<p>Please read the full story [here](<a href="https:&#x2F;&#x2F;carminatialessandro.blogspot.com&#x2F;2026&#x2F;01&#x2F;hc-agentless-multi-tenant-shell-history.html" rel="nofollow">https:&#x2F;&#x2F;carminatialessandro.blogspot.com&#x2F;2026&#x2F;01&#x2F;hc-agentles...</a>)

Show HN: Ayder – HTTP-native durable event log written in C (curl as client)

Show HN: Ayder – HTTP-native durable event log written in C (curl as client) Hi HN,<p>I built Ayder — a single-binary, HTTP-native durable event log written in C. The wedge is simple: curl is the client (no JVM, no ZooKeeper, no thick client libs).<p>There’s a 2-minute demo that starts with an unclean SIGKILL, then restarts and verifies offsets + data are still there.<p>Numbers (3-node Raft, real network, sync-majority writes, 64B payload): ~50K msg&#x2F;s sustained (wrk2 @ 50K req&#x2F;s), client P99 ~3.46ms. Crash recovery after SIGKILL is ~40–50s with ~8M offsets.<p>Repo link has the video, benchmarks, and quick start. I’m looking for a few early design partners (any event ingestion&#x2F;streaming workload).

Useful patterns for building HTML tools

Useful patterns for building HTML tools

Migrating to Positron, a next-generation data science IDE for Python and R

Migrating to Positron, a next-generation data science IDE for Python and R

No other tools from this source yet.