News for hackers. Stuff that matters.

dippatel1994

Thank you so much @mellosouls, means a lot!
Thanks for spotting it but if I tried other way would have kicked out, it was a genuine try to help but thanks @mellosouls I can understand.
Exactly! Any optimization for local inference is a welcome change IMHO!
Don't want to jeopardize this awesome chat about tools but for AI workshops I think these visual cards I came across could be an amazing way to handout. They cover all LLM concepts and explained visually. Found very useful to revise LLM concepts before AI research scientist/AI engineer interviews.

https://github.com/llmsresearch/llm-flashcards

Show HN: Chrome extension that tailors your resume to a job posting in one click

https://ajusta.ai

Job tailoring advice is everywhere but it all bottlenecks at the same place: actually doing it 50 times. Copy resume, paste into ChatGPT, rewrite bullets, reformat everything that broke, repeat. Ajusta sits on the job page (LinkedIn, Indeed, etc.), reads the posting, and rewrites your resume against the JD without touching your formatting or adding anything that isn't already there. The output...

( Read More... | no comments | on HN )

Show HN: Open-source PaperBanana – academic diagrams from text via agents

https://github.com/llmsresearch/paperbanana

The PaperBanana paper (arXiv:2601.23265) from Google Cloud AI Research and PKU describes a multi-agent framework for generating publication-ready academic illustrations from text. The official code hasn't been released yet, so I implemented it from the paper.The pipeline chains 5 agents: a Retriever that selects reference diagrams, a Planner that generates a textual description, a Stylist that...

( Read More... | no comments | on HN )
Released mcp server and skills support. You just need "uvx --from "paperbanana[mcp]" paperbanana-mcp" to configure paperbanana mcp server.

Show HN: Implementation of Google's PaperBanana (diagram generation from text)

https://github.com/llmsresearch/paperbanana

The original authors haven't released code yet, so I built it from the paper. It takes a methodology section as input and generates a publication-style diagram.The pipeline uses five agents: a retriever selects reference diagrams via in-context learning, a planner drafts the layout, a stylist adjusts for conference aesthetics, a visualizer renders with Gemini, and a critic evaluates and refines...

( Read More... | 1 comment | on HN )
Re:What ICLR 2026 Taught Us About Multi-Agent Failures on Saturday January 31, 2026 @10:29AM (#46837491)
Author here. I went through ICLR 2026 accepted papers looking for work relevant to multi-agent production problems. Found 14 papers clustered around 5 issues: latency (sequential API calls), token costs, error cascades, brittle topologies, and observability.

A few highlights: - Speculative Actions: parallel API execution, ~30% speedup - KVComm: share KV pairs instead of text, 30% of layers gets near-full performance - DoVer: intervention-driven debugging that flips 28% of failures to successes

Happy to discuss any of the papers or the framing. The decision matrix at the end maps each problem to a starting paper.

Add the word "Be Honest" and you will see the other side of the spectrum!
Because they were hiring crazily!
Last year, we evaluated different agentic LLM frameworks before selecting to architect our production system. Too many options out there.

So I built a covering their capabilities. If you're evaluating agentic solutions for your next project, hope this saves you time. It maps what's native, what needs integration, and what's not supported.

Let me know if anything needs correction or want to add any other framework.