Live data from Hacker News

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

news.ycombinator.com

921–930 of 1001 posts

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

#921
Is it too late to post here?

Link - https://trulytyped.com

Product : Truly typed is a document writing app which makes it extremely easy to find out how a document was created. Each document carries information such as how much of the content was actually typed, how much was pasted, how many sources were used, how many authors contributed. Each document also carries flags such as verified human, bot detected, Unverified. Unverified is for cases where humans are transcribing text looking at another tab or book. The core thesis of the product is that purely human generated thoughts will matter more and more.

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

#925
I've been working on (https://www.margarita.run) - If you could write agents as easy as writing markdown

Github: https://github.com/Banyango/margarita

I've always wanted to write a programming language, and AI made that a bit easier. So I tackled a kind of quasi-extension to markdown that lets you control coding agents easier.

Margarita provides two file formats:

.mg — A templating language that renders dynamic prompts to Markdown. Extends Markdown with variables, conditionals, loops, and includes.

.mgx — An agent scripting language that extends .mg with agentic execution: state, memory, tool calls, user input, and more.

That said I'm not sure how useful this thing is since everyone just uses claude code now, but it was a really great learning experience.

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

#930
I am working on two things in parallel. https://howareu.app/ is the first one. Of course, struggling with the making it publicly known and trusted. ;)

And the other thing I just started is a MCP server that will connect to Java remote debugging entry point. This way I will try to allow Claude to start debugging session by its own. And I hope that in pure back-end logics, it will easily trace and fix bugs. I now do it with log messages, but it is kind of annoying and dirty and error-prone to do it that way. I would like to try an approach that does not mess up the code so much. Let's see how it will go :)

Post reply on HN