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

Can you also compare in the charts https://maki.sh?

Should give you some competition.


Oh very nice, can you also compare it to https://maki.sh?

Would be interesting to compare to a harness optimizing for cost reduction too.


The techniques appear to be orthogonal, so you might be able to combine them

Competition is good

It really is good. I forgot to mention that within that said sub agent, it also went into exploring top e-commerce websites (Zalaondo, Temu, Amazon, eBay) for exploring prevailing industry UX best practices and taking screenshots of their product and category pages with its own written chrome driver that I talked about and then went onto prototyping a new website in a temporary directory and then taking hundreds of screenshots to analyse what would be the best column density one each medium for each language.

And that all is 0.07 cents all included.


What harness do you use with it? Are you using v4.1flash via open router ?

I am using DeepSeek Harness[0] (switched from OpenCode) and I am using DeepSeek directly via the API. The speed is insane. Like 200 tokens/second is the norm but I have seen much higher too at times.

PS: I do not know why but opencode pushes CPU usage to very high which has NOT happened with DeepSeek harness even once.

[0]. https://github.com/deepseek-ai/deepseek-harness


That's incredible, might just switch myself. Thank you!!

> and I am using DeepSeek directly via the API.

Do you know if they retain your prompts or use it for training?


They train. Deepseek doesn't have a Zero Data Retention policy, but for many personal tasks I'm (not parent) ok with them having this data if it means better, cheaper models for everyone on the future.

Different story with $DAYJOB where ZDR matters, but the beauty of open models is that you can find a provider hosting them in your preferred terms.


Comes across as this "I'm special", and kinda cringe...


looks cool would be nice if its GUI , terminal have limitations .

Funnily enough, I feel the exact opposite! The limitations of terminal make them portable while still being more than powerful enough. But then I've used vim as my editor for going on 15 years now so I'm biased.

I do used vim for many years too , but when developing web apps , Terminal become a limitation , things cannot be preview outright in the interface is a big downer.

Huge plus for GUI base dapplicaitons : you can view total and complete render of HTML , PNG , SVG , PDF right in the IDE/Harness tools. That is no where terminal app can do with good performance .


I was really confused when reading the article that their claim is you don't know formal verification, I was expecting something way juicer.

I've made https://maki.sh for use cases such as this


Isn't using it with GitHub Copilot a violation of GitHub terms of usage, due to usage of internal API? I read that they have an official partnership with OpenCode, and I guess it is fine to use it with OpenAI Codex, but what about other coding agents like maki?


Is it really? I'll need to check it out


Do I understand correctly that in your harness models don't call tools and pass output of one to another via context, but instead code whole pipeline as small on-demand tools and see only final output?


They can do both, the model decides when to use code_execution like any other tool


Are you freaking kidding me with YC throwing money at something like this? I guess I can fund raise just by having built https://maki.sh, and months ahead of other founders too...


I'm not sure why anyone would fund "creating an agent". OpenCode is competing with Codex and Claude already.

"The bullets" are not any different than other new agent projects. New agent projects pop up and die constantly and it's not from a lack of funding.


I think that if there are many players in the space, it's a problem worth working on! Like I said in the post, our main problem is speed and that's what we're trying to fix. It's been a problem, and it still is a problem. We have tried tools like OpenCode, Pi, etc. but for our speed issue, it did not fix it. If we go down dying on this boat, so be it, at least we went down dying on a problem we care about!


Meanwhile, Cerebras running Sol at 750 tokens per second, the harness "speed" becomes irrelevant compared to making better use of results from insta-Sol.


Yes, we saw this and it's really exciting, can’t wait to try it in Bullet. But faster inference only speeds up generation. In our own experience, testing, building, searching, and other tool work still dominate plenty of real tasks. We’ll have to test it in practice, but it’s a great development for everyone building agents.


YCombinator's investments are unfortunately very questionable nowadays.


People were saying that about YC in 2009, when Airbnb and Stripe were funded. YC’s philosophy has always been to invest in a great many companies, accepting that you can’t know in advance which will succeed, most will fail, but the ones that succeed will be successful enough to pay for all the losses.


That's not just YC's philosophy. That's how seed level funding works in the industry. Spray and Pray.


“Spray and pray” is a deliberately belittling term for an approach that YC largely pioneered and has delivered outsized returns over two decades. There’s no “pray” about it. YC partners work incredibly hard to attract and select the most promising founders and support them through their most nascent and fragile stages. They keep turning out huge successes, whilst also giving off the appearance that most funded companies are unimpressive. That’s always been true; it’s the easy thing to focus on for people who are motivated to be critical, but it’s a valueless observation.


All the harness tools have been re-implemented as plugins in Lua: https://github.com/tontinton/maki/tree/main/plugins

Here is the full API reference: https://maki.sh/docs/lua-api/


Mine sends even less - https://maki.sh


Nice!

> When context gets too long, maki compacts history automatically: strips images, thinking blocks, and summarizes older turns.

Don’t the summaries of older turns effectively invalidate the context cache, such that you consume less tokens but more expensive tokens?


Only once per compaction


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

Search: