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

Basically the stroy is i created this to sovle a problem i have. I don't want to spend time at my desk all day. I don't want to babysit agents. They work, often long tediuos hours iteraing and updating and progressing. I don't need to be there fore that. If I'm at my desk, there's only so much I can do. Watching them is a waste of time. Couldn't there be a better way? So I made it. Email. Very simple. Plus you can CC your friends and team, and then can contribute. Their replies get routed to the agent conversation as well.

Works across codex, claude, gemini, copilot and opencode.


This is beautiful. Thank you for this! Beautifully execute, beautiful idea :)

Working on a way to keep my agents running using email while I'm away from my desk. I want to spend time with the moments that matter, not babysitting agents. I want them to keep working while I'm out. Why can't I just email them?



There is an option to check the source if you’re serious about that: sign an NDA, jump on a secure data room call and I can take you through the source for audit. Normally I only do this for big customers of other products but, I’m open to it.

Beautiful design. And I love that 1970s high quality plastic.

That's awesome man that is REALLY cool. Useful :)

Partially correct: we don't give away the source, but we also don't use your credentials.

We use the official cloud CLIs (gcloud, hcloud, aws, az, vultr-cli) that are either already signed in or not. If not, we detect using their subcommands to display login status, like gcloud info, etc). If not signed in, we ask if you want to sign in, and if you do then the official cloud CLI does the sign in and handles your creds however each one does. That might sound like splitting hairs, but to me that approach made much more sense that trying to safely handle your creds!

You might be wondering why not give away the source code? I tried this over the last 10 years with a bunch of different products (BrowserBox, DownloadNet), and ones where I didn't (WisprNote, etc). The trend was clear: giving away source led to less revenue, and more "shady" usage (big corps using but ripping it off, etc). Whereas proper "license and source protection locked-doors" led to people behaving with more respect, and more revenue.


Thanks, bud!

Does this mean TS is not FIPS 140-3 now?

It never was FIPS-approved and likely will never be. The wireguard protocol used by Tailscale uses ChaCha20 for encryption which is not FIPS approved.

Interesting. What is the FIPS version of wireguard?

> What is the FIPS version of wireguard?

IPsec or TLS-based overlays which use AES encryption and NIST-approved ECC curves or (gasp) RSA for key exchange and authentication. They generally suck in comparison with wireguard, which is a clean-sheet modern cryptographic protocol.


There are some forks that are not compatible with regular wireguard, for example from wolfssl. Or just classic mTLS.

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

Search: