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

https://github.com/mcdirmid/cleanroom

So far I have bazel macros up that can produce tested code with a ~30GB MoE model (Jundot/Qwen3.6-35B-A3B-oQ6-mtp, I can get ~90 toks/sec on a M3 Max!) using cleanroom separate implementation and test development (and then comparing them until both are correct). Over the last month, however, I found that my bottleneck is in the specifications: as I further divided my components into separate parts (since smaller components are easier to write and test), I started hitting problems with specifications becoming badly ungrounded (code depending on knowledge they cannot access, so something is just hallucinated).

So I redid the format, e.g.

https://github.com/mcdirmid/cleanroom/blob/main/update_with_...

The spec format is designed to be declarative and very modular, and ya, an LLM is primarily writing the specs as well, so I hope to create some sort of formal reasoning framework that the specification can be translated into (by an LLM) so that ungroundness feedback can help the LLM write better specs. Also, I found that it really is much more robust to change/refactor/add features via the spec first and then align changes down to test and code, then to make changes to the code directly (even without using the system, just asking a frontier model to look at the guides and do the alignment itself directly).

I think I'll be ready to do a release over this next month, which means:

- Supporting a build system other than Bazel to express DAGs. Honestly, this could be anything, I just chose Bazel for convenience (easy to express graphs in Starlark), but it assumes a monorepo world that I don't think many developers use.

- How do I even package this? The advance of using Starlark is that I can generate python code to call into the generated python code directly. If I move away from that, I need to figure out what this really looks like as a binary.

- More demos. Right now my only project is the code for the system itself (the classic "the first program of a language is the compiler for the language"). I just can't think of many interesting things to do in Python that aren't agent related (I can support other languages, like Java, Typescript, or even C++, but I'm hitting choice paralysis).

Traditional error trackers have two failure modes:

1. False positives: They show you thousands of errors, and you can’t tell the impact on the user

2. False negatives: Many user-facing issues don’t throw exceptions, so they go unnoticed.

Opslane combines error tracking and session recording. And there is an agent that acts on both.

Opslane reduces false positives by ranking issues based on how many users are facing a particular issue. It also learns about your product by reading your code and watching your session recordings.

False negatives are harder. Opslane reviews session recordings to spot frustration. They look for rage clicks, dead clicks, and abandoned forms.

Here is a link to the repo: https://github.com/opslane/opslane

I already have a product BenkoPhone.com but the app is provided by a 3rd party and I just white label it so I have started building the replacement.

I built the account management and billing system first after implementing a proof of concept for the app then had to do a major platform change which stalled development of any other features for 3 months.

Hopefully I’ll be adding features again by the end of this month and I’ll put some screenshots in once it actually does something!