All written in rust. The simulation engine has been solid for a while and the TUI is finally starting to expose all of the options needed to really configure a complete simulation.
Ask HN: What are you working on? (February 2026)
191–200 of 1001 posts
Re: Ask HN: What are you working on? (February 2026)
#192Re: Ask HN: What are you working on? (February 2026)
#193Re: Ask HN: What are you working on? (February 2026)
#194Designing closed loop micro-position 4-axis stage driver section v0.2.
Other stuff maybe three other people would care about =3
Re: Ask HN: What are you working on? (February 2026)
#195A Jellyfin music client for Linux written in Rust and GTK: https://github.com/Fingel/gelly I thought it would be pretty simple, but here I am almost 6 months later still adding features. The positive feedback has been nice, though! People seem to appreciate (like I do) that its fast and doesn't use Electron or some other cross platform toolkit. Learning a lot. It's not vibe coded. Sad that I have to make that qualifi…
Re: Ask HN: What are you working on? (February 2026)
#196Re: Ask HN: What are you working on? (February 2026)
#197An open-source multi-cloud governance framework powered by a YAML rule engine. We just reached a milestone by adding Database (DB) support.
The goal is to allow developers to audit configuration and compliance directly within DB instances, alongside standard cloud resources (AWS, GCP, Azure, K8s). We’re focusing on keeping the YAML rules as agnostic as possible so the same logic can apply across different environments without rewriting everything. rtk (https://github.com/rtk-ai/rtk)
This is a "scratching my own itch" project born from using Claude-code. While vibe coding, I got frustrated watching the agent spam ls -al or cat repeatedly just to "orient" itself.
It creates two main issues:
The Token Tax: It burns through tokens for info the agent already has.
Context Pollution: The context window fills up with redundant noise.
rtk acts as a CLI wrapper/filter to make LLM interactions more signal-to-noise efficient. It silences or summarizes redundant outputs so the agent only receives the necessary "delta." It’s a simple attempt to keep the context clean and make sessions last longer before the agent loses the plot.Re: Ask HN: What are you working on? (February 2026)
#198I would really like people to try it out and report bugs, failures, and successes.
https://github.com/Vibecodelicious/opencode/blob/surgical_co...
I'm currently trying to get the LLM to be more proactive about removing content that is no longer useful in order to stay ahead of autocompaction and also just to keep the context window small and focused in general.