News for hackers. Stuff that matters.

alexandroskyr

Re:Show HN: HackerReels - Short Videos for viral HN posts on Tuesday November 03, 2026 @08:16PM (#50360418)
thanks. it is an oss python lib -> manim
Re:Show HN: HackerReels - Short Videos for viral HN posts on Tuesday November 03, 2026 @07:55PM (#50360287)
Some more: - Revolut GLM: https://wile.ai/v/LG5INVRVILRAAXXOGVNYHOW67D - Git for agents: https://wile.ai/v/TKUOSIYAV2BMJO3EYTOWKDEFWQ - Intel selloff: https://wile.ai/v/CSRXJIEFTNBNR2AIOQA6S2SNKW

Let me know if you want me to create a custom one.

Show HN: HackerReels - Short Videos for viral HN posts

https://wile.ai/v/BPOH3BHCRWWCAKU4OVNOTEQ73A

I've got a hacker-news automation which creates a short video every time a new post becomes viral.wile.ai: Every automation ends in a reel. Now, you can create your own private feed.I've been working into this for a while.We are currently pre-launch but any feedback is welcome!apple testflight: https://testflight.apple.com/join/hgNKEm76demo: https://www.youtube.com/watch?v=stXmZyrZ-Hkwile.ai

( Read More... | 3 comments | on HN )
Re:Show HN: Use all Codex Plugins inside Pi on Sunday October 04, 2026 @08:15PM (#49959348)
Just released web_search and computer_use additional tools.

Show HN: Use all Codex Plugins inside Pi

https://github.com/wileai/pi-codex-connectors

I just realized that codex now exposes local server endpoints for all plugins without extra auth. So you can just use them from any model or harness.Im soooo excited!!! One auth for everything!For Pi: pi install npm:@wileai/pi-codex-connectorFor any harness: npx -y @wileai/codex-connectors-mcp@latest

( Read More... | 2 comments | 3 points | on HN )
- claude max $200 (canceled) - codex max $200
The benchmarks we ran can be found here: https://github.com/graph2agent/benchmarks

Show HN: Graph2agent; Mermaid diagrams, explained for agents

https://graph2agent.github.io/

During the implementation of a huge high performance service. In order to keep context small (mainly for humans) I kept the specs into mermaid diagrams. When communicating with humans; diagrams were easy to follow and to remember. But when I asked the agent to implement what's in the diagram, most of the times it failed.So I came into conclusion that agents are good into writing mermaid...

( Read More... | 1 comment | 3 points | on HN )
Re:Show HN: A private pager for your AI agent loops on Tuesday June 23, 2026 @12:59AM (#48640505)
Leaving also here the GitHub repo: https://github.com/askahuman/askahuman

Show HN: A private pager for your AI agent loops

https://ask-a-human.ai

Problem Im solving: Im running 30+ fully autonomous agents. In some rare cases they get blocked because they cannot decide what direction to take.So I built a communication channel for them. So in case they get blocked they can ask me anything. The base case should be that no questions should arrive to me. But the more I automate the agents the more edge cases I find. That's why I built the...

( Read More... | 1 comment | 3 points | on HN )

Show HN: I vibe coded the fastest Decimal Go lib

https://github.com/AlexandrosKyriakakis/zerodecimal

A zero-allocation Go decimal library with no big.Int fallback — 128-bit fixed-point arithmetic that benchstats ~35% faster than the fastest existing library, with exact alloc counts and overflow correctness enforced by the test suite.The fun part was making it fast: every division by a power of ten (rescaling, rounding, formatting) is done with precomputed multiply-high reciprocals instead of...

( Read More... | no comments | on HN )
Re:What's the right trust model for an agent-to-agent network? on Tuesday February 24, 2026 @08:46PM (#47146257)
Thank you a lot for the feedback. Yeah, still debating with my self regarding web-of-trust models vs KYC.
Agent interoperability protocols are starting to emerge (e.g. A2A / similar efforts), but I’m still unsure what the trust/identity layer should look like when agents need to contact other agents and sometimes escalate to a human. I’m building a proof-of-concept (CLI-first, MCP-compatible) and want to stress-test the design before locking the architecture.

Premise (for this prototype): - Agents do the transactional work (scheduling, purchasing, monitoring) - Humans are only pinged for decisions or when an agent is stuck - I’m modeling only agent↔agent and agent→human flows (no human-to-human UI)

Examples:

- I ask my agent to reschedule lunch with George → it negotiates with George’s agent → we each get a decision card: “Thu 2pm. Accept?”

- A supermarket agent publishes a discount feed → my agent filters → “Olive oil 30% off. Buy?” → if yes, it executes

- If an agent can’t complete a step online, it escalates with a structured decision card (what/why/options/cost-risk/deadline/default)

The discovery + trust problem:

This only works if identity + spam are handled well. My current leaning:

- Business agents: public, verified (some form of validation)

- Personal agents: private/whitelist by default (contacts-only)

- Decision cards are structured + auditable (action, options, cost/risk, deadline, safe default)

But I’m unsure about the verification layer:

- Full KYC improves accountability but adds friction and centralization.

- Keys / web-of-trust is more open, but how do you prevent unsolicited outreach from becoming spam?

Questions:

1) Does “human approves decisions, agent executes transactions” match how you expect agentic workflows to evolve?

2) What trust/identity model would you use (KYC tiers, web-of-trust, stake/bond, proof-of-work, reputation, something else)?

3) What breaks first?

https://platia.ai (named after πλατεία — village square)

Curious if anyone has seen differences in how models handle conflicting tool descriptions — e.g., two tools with overlapping capabilities where the boundary isn't clear. In my experience that's where most bad tool calls come from, not from missing descriptions but from ambiguous overlap between tools.
So mainly an mcp for facebook ads? Nice!