Live data from Hacker News

Ask HN: What are you working on? (February 2026)

news.ycombinator.com

261–270 of 1001 posts

Re: Ask HN: What are you working on? (February 2026)

#261

I'm working on lots of projects. My favorite is what I call "context bonsai" where I'm giving LLM harnesses the ability to surgically edit the context. It's available as a tool. You can say "remove that failed debugging session and write a summary of what we learned." Or you can take a more hands-on approach and say "remove messages msg_ID1 through msg_ID2". The removal leaves a summary and keywords, and the original…

I find it fascinating to give the LLMs huge stacks of reflective context. It's incredible how good they are at feeling huge amounts of csv like data. I imagine they would be good at trimming their context down.

I did some experiments by exposing the raw latent states, using hooks, of a small 1B Gemma model to a large model as it processed data. I'm curious if it is possible for the large model to nudge the smaller model latents to get the outputs it wants. I desperately want to get thinking out of tokens and into latent space. Something I've been chasing for a bit.

Re: Ask HN: What are you working on? (February 2026)

#262

https://sampler.meiji.industries/ I built a TUI sampler which cherry-picks my favourite features from modern & vintage hardware samplers, DAWs, plugins, outboard FX gear, and DJ equipment. If you know what an AKAI MPC Live, MPC 3000, SP404, SP1200, BOSS RC-202, Alesis 3630, Serato Sample, S950 filters, and stem separation does, then you'll love seeing these "greatest hits" up in a terminal interface. Last year while…

Great intro video!

Re: Ask HN: What are you working on? (February 2026)

#264
I've been thinking about this a lot after shutting down my previous startup. One problem I've identified is that tools like Claude Co-worker or Claw Bots will never truly deliver reliable agentic outcomes for people due to the fact that scaling a human-like agent is paradoxically harder than scaling a script.

- I see a lot error propagation with CUAs

- A GUI is very flakey and it produces a lot action latency

- There're hidden states behind each screen that CUAs simply can't capture

- Token consumption is absurd (but I guess this will alleviate as LLMs get cheaper)

What do you guys think? Any good ideas what'd be a good counter to this?

Re: Ask HN: What are you working on? (February 2026)

#265
Borrow This And Improve It - an app for tracking repairs to a thing (right now it's bicycles only, planning to extend to other things like leaf blowers and electronics) and giving away half broken things or repaired things to others but with the advantage of also giving away the repair history for something. So for example, I found a bicycle in the trash, fixed it up with a few new parts (less than $6) and soon I'll try to give the now repaired bicycle away to a new home, plus a QR code that links to its repair history. The idea being that knowing how something was fixed once will make it more likely that it would be fixed again.

How Home Alone My House - A fun app I'm making with my children using computer vision. The idea is I can scan the room with my camera before unwittingly walking into their traps and becoming a hapless adult who didn't pay close enough attention to tripping hazards and choke lines.

Re: Ask HN: What are you working on? (February 2026)

#266
I'm building a safer Agent system for SMBs.

The biggest problem is internal knowledge and external knowledge systems are completely different. One reason internal knowledge is different it is very specific business context and/or it's value prop for the business that allows charging clients for access.

To bridge this gap, the best approach is to train agents to your use case. Agents need to be students -> interns -> supervised -> independent before they can be useeful for your business.

https://github.com/rush86999/atom . it's still in alpha.

Re: Ask HN: What are you working on? (February 2026)

#267
I’ve been experimenting with a live win probability predictor for the 10-player arcade game Killer Queen. The goal is to predict the winner in a causal, event-by-event fashion.

Right now I’m struggling to beat a baseline LightGBM model trained on hand-engineered expert features. My attempts at using a win probability head on top of nanoGPT, treating events as tokens, have been significantly worse. I am seeing about 65% accuracy compared to the LightGBM’s 70%. That 5% gap is huge given how stochastic the early game is, and the Transformer is easily 4 OOM more expensive to train.

To bridge the gap, I’m moving to a hybrid approach. I’m feeding those expert features back in as additional tokens or auxiliary loss heads, and I am using the LightGBM model as a teacher for knowledge distillation to provide smoother gradients.

The main priority here is personalized post-game feedback. By tracking sharp swings in win probability, or $\Delta WP$, you can automatically generate high or low-light reels right after a match. It helps players see the exact moment a play was either effective or catastrophic.

There is also a clear application for automated content creation. You can use $\Delta WP$ as a heuristic to identify the actual turning points of a match for YouTube summaries without needing to manually scrub through hours of Twitch footage.

Re: Ask HN: What are you working on? (February 2026)

#268
post #11

Visually I’m working on a new landing page for phrasing. It’s almost done, just need to record a few videos: https://phrasing.app/next Behind the scenes I’m rebuilding the sync engine to properly support offline mode. Trying to get to instant opens for the app (and of course work offline). It’s probably my 5th sync engine. It’s been really fun to see how much easier, faster, better, etc each new iteration is. (And th…

This looks really interesting! Is it correct that the trial is paid? I've never seen that before :O

Re: Ask HN: What are you working on? (February 2026)

#270
Been working on a weekly newsletter [1] to stay fully informed about agentic coding with one email, once a week. I also keep the focus narrow, only on what engineers and tech leaders would find useful for shipping code and leading teams, which means I filter out all generic AI news, or what CEO said what, or any marketing fluff.

[1]: https://www.agenticcodingweekly.com/

Post reply on HN