Ask HN: What Are You Working On? (July 2026)

Im building an agent that interacts with health care providers on your behalf to proactively get itemized bills and other substantiation as needed. Born out of my own frustration with the paperwork for getting reimbursed from my healthcare cost sharing ministry. The app is React with a Laravel backend on EC2 where the agent runs.

Recently Ive been experimenting more with coding from my phone using Claude Code for the Web. Its basically turned Github Actions into my development environment. Its enabled me to fire off a quick prompt in planning mode, go play with my kids, review and approve the plan while Im cooking dinner, then let it go 10 rounds with the AI code reviewer while I put the kids to bed. As a busy parent I feel way more productive than if I had to carve out sit down focus time for a side project.

https://www.healthsharetech.com

Counting the beans, or by weight? (Or I suppose you could 3D scan each bean as it goes past to measure volume for extra credit)

I'm learning Rust, and a bit about audio processing: https://github.com/leocrabe225/audiodsp Just before that I was learning TypeScript, and I'll be coming back to that project as it's quite the process. I'm leaning heavy TDD and rely on the type systems a lot. The project is called "Rentier", a joke about the Monopoly board game. https://github.com/leocrabe225/rentier-rewrite I finished part 1, with a postmortem. Part 2 is React frontend. Part 3 is implement the postmortem findings in the TS engine. Part 4 is update the React frontend for the updated engine. Part 5 is make the engine in Rust from scratch. Part 6 is point the React frontend to Rust engine, and praise the pros of having a good architecture. Kind of an ode to clean code if you will (Many things to learn along the way).

Love the pseudo-tactile approach.

Very fresh and almost calming :)

Two things right now:

1. A music recommendation tool based on Last.fm scrobble history.

It's graph-based, no ML or "fancy" techniques, but I've had good results with it so far. It builds recommendations based on a listening window or just recent history. It combines several different recommendation algorithms (including an Auralist-inspired "serendipity" score for novel recommendations, meant to simulate the serendipity of being recommended something novel by a friend), scores and ranks candidates, and takes in feedback that inform subsequent recommendations.

Fun project. Found some good new music with it already. :)

2. A code exploration / indexing tool with CLI and MCP interfaces for exploring concepts and impacts of changes in a codebase.

Essentially, an overwrought "find all uses" that doesn't depend on exact symbol or string matching.

I have a codebase of non-trivial size, but thankfully it's fairly well-structured. This tool indexes the code and bundles modules into "concepts" -- these can be auto-discovered or preconfigured. Dependencies, inheritance trees, symbols and symbol usage are all also indexed.

Then you can ask, "what's the impact of extending the domain model of XYZ" or "I want to remove this property" and it shows where to start, where to look next, and fuzzy edges or dependencies that might need deeper exploration. It surfaces non-obvious connections, too, or things a junior dev (or LLM) might miss, like when a model is mapped to an API DTO, or intermediary states, etc.

It's been useful for a new dev exploring the codebase, because you can ask in terms of business concepts instead of needing to know the exact symbol name in the code. And it's been much more token efficient than grep for exploration subagents. But it's limited to dotnet only.