I took a look at this repo and honestly, it looks solid. The structure is clean, easy to follow, and pretty straightforward. I was up and running much faster than I expected. Definitely worth checking out if you're looking for a local-first agent runtime.

We’re building a TypeScript server framework for backend services. The aim is to handle the parts that are easy to get subtly wrong, so teams don’t rebuild them per project:

• Tenant-scoped data with optimistic concurrency

• ABAC (attribute-based access control) policies that become database query conditions, so a caller only sees the rows they’re allowed to see. Fields a caller can’t read also can’t be filtered or sorted on. Writes are checked both before and after the change.

• Transactional outbox events, with inbox consumers, and durable jobs and workflows stored in your own database

• Rate limiting, retries, and a circuit breaker

Each capability is a separate import, so you can use one without the rest.

Our open question is which of these should be built in versus left as separate packages. We’re considering ABAC policies, transactional outbox events, and durable jobs and workflows. Which would you actually use, and what would you leave out?

one nasty data validation bug this weekend I found...felt like sharing it here.. and see how you guys usually handle integration failures..

BIGINT timestamps crossing a JS SDK boundary..

we had egress sanity checks after sending data into cleanrooms...after moving through API/SDK path, the validations started failing silently...

1/ no schema changes or errors

2/ no obvious bad row..

3/ timestamps looked almost correct..

this took like half-day for me to find even after using AI tools.....the JS had changed value by adding extra zeros at the end of the ts fields...

the exact match validation failed because the timestamps was no longer the same timestamp..

lessons i learned..

if its timestamp/id...precision matters... dont let JS tream it like a normal number... send it as string instead..

назовите ваши любимые команды

Hey everyone, I’m Memo — the founder of InstaTunnel www.instatunnel.my — and I built this tool to fix the pain points I kept hitting with ngrok and similar services:

• No more 2‑hour cutoffs — free tunnels stay live for 24 hours reddit.com+9instatunnel.my+9reddit.

• Custom subdomains included for free — no random URLs or surprise charges instatunnel.my

• Multiple tunnels — run frontend, backend, whatever, simultaneously instatunnel.my

• Password protection, auto‑HTTPS, analytics, auto‑reconnect — features that matter, without hoops to jump through youtube.com+5instatunnel.my+5youtube.com+5

I’m not here to pitch—just hoping this helps if you’ve ever been mid‑demo and your tunnel died, or paid extra just for a named URL. Check it out with:

npm install -g instatunnel
it --name myapp --password secret123

URL is auto‑detected, live for 24 h, clipboard copied—no signup or config needed.

Curious: what’s your biggest pain with tunneling tools? Session timeouts? Hidden costs? Limited tunnels? Would love to hear so I can keep improving InstaTunnel. 🚀