News for hackers. Stuff that matters.

devendra116

Show HN: Hum – ad-free terminal music player (Rust, no API keys)

https://github.com/Devendra116/hum/

Built hum, a minimal terminal music player focused on fast keyboard flow and low overhead.> ad-free playback (raw stream URLs via yt-dlp + mpv) > keyboard-first, low-overhead terminal UX > no API keys / accounts / subscriptions > supports song search, direct YouTube links, playlists, and radio mode > one-command install for Linux/macOS or run source code for windowsInstall: "curl...

( Read More... | no comments | on HN )
if a agent has the keys in the same process, it can easily extract them
interesting, how do you use mitmproxy for calling openAI llm ? or what exactly you use it for ?
which agent framework or tool gives guarantee for leaks?
does you agent only print "Hello World" on console ? or it uses any service ;)
if you usecase is just about dealing with private key and txn signing why not use any KMS service?
so you prefer using separate VM machines?
something that you dont like about using AWS secrets Manager or think it should be handle differently?

im researching around building a execution environment that handle the secret + actual execution, any input is appreciated

so do we need something like `safe agent execution layer - that is policy enforced` (SEAL) we can manage what should be allowed and what not

agent uses llm to plan the action, but the actual execution happens in SEAL.

any example where it would make sense to start with?

open for thoughts

is there any tool that can do this ?
keyring is one of solution but even substituting values at excution does not gaurantee the security as agents can read the process itself.

im building a safe agent execution layer, A runtime where agents can act, but cannot access secrets. kinda sidecar that is callable by agent for using api keys, secrets, private keys, etc and plus one can add policy on how and what a agent can do.

does this seems good?

Show HN: Ledge - Policy layer for AI agent payments (prevents unauthorized txns)

https://github.com/Devendra116/ledge

Hey HN,I built Ledge because I kept seeing demos of AI agents with wallet keys in their .env files, and thought "this is going to end badly."The core idea: put a policy layer between your agent and the wallet. Before any payment executes, it runs through 4 checks (technical validation, policy limits, context coherence, behavioral patterns). Agent can pay for APIs/data autonomously, but only...

( Read More... | no comments | 2 points | on HN )
For those interested, the playground uses a guest wallet stored on browser localstorage so there’s no signup friction.

Show HN: A playground to test stablecoin gas fees and concurrent txns on Tempo

https://tempo-playground.vercel.app

Hi HN,I built *Tempo Playground*, a small hands-on playground to explore Tempo’s transaction model for real-world payments.The goal was to make Tempo’s ideas tangible instead of just reading documentation.*What you can try right now:* - Pay transaction fees in *any USD-denominated stablecoin* (no native gas token required) - Execute *concurrent transactions* from the same account (parallel...

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