Hacker Newsnew | past | comments | ask | show | jobs | submit | ylrd91's commentslogin

You should architect the base app yourself and create a structure with a good separation of concerns then let AI build on top it.

Don’t write your own. Fork maki.sh and customize it like I did. It’s built in Rust and is absolutely amazing.


Thanks for the suggestion, but that’s not a fit for me.

I’m writing my own harness to learn. And I’m writing it in zig.

But, I’ll absolutely add maki.sh to my reading list. So, that’s a win.


You should do that. I am also summoning the motivation to start on my own. I guess the worse will be that I fail. Might as well fork sth more basic, or build on top of sth SDK/library like.


I don't know if you'll be interested, but there is an excellent book on the topic: Build an AI Agent (From Scratch), by Jungjun Hur and Younghee Song (Manning Publication).

By chapter four you have a minimal working codebase in python. Later chapters add out features like tool calling, planning, and reflection.


I am thinking about it but I think forking will miss the point. I'd rather do in a way when there is a prevalence of various types of agentic/harness SDKs for people to make their own apps (aka harnesses) from.


That’s what pi.dev exist for but I’m not touching it because like all of the other harnesses it’s built in JS and they’re all terrible when it comes to cpu and memory use. Maki is the only one I found the be the most efficient harness. It uses 1% cpu idle vs 20-30%.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: