We're looking to more than double our founding team at @beacon.sh, hiring aggressively across research and engineering.
We're building the visibility and control layer for AI agents, and we've got some serious momentum:
$5.5M raised in seed funding
3,200+ GitHub stars and a growing OSS community
#1 Product of the Day on Product Hunt
Our founding team brings experience from Doppel, Brex, and Trail of Bits, and we're looking for exceptional builders to join us.
We're hiring:
Founding Engineer: Build high-performance infrastructure to secure and govern AI agents at scale.
Founding Security Researcher: Break AI agents, uncover novel attack surfaces, and publish cutting-edge research.
Who we're looking for:
Deep technical curiosity and obsession with craft
High agency, relentless ownership, and bias toward shipping
Exceptional problem solvers with incredibly high standards
We want world-class engineers and researchers. We don't care about pedigree. We care about what you've built, the problems you've solved, and the quality of your work.
NYC in-person preferred, open to exceptional remote talent.
DMs open. Come build with us! Contact me at founders[at]asymptotelabs.ai
The portability angle is the part that hits home for me — I switch between Claude Code and Cursor in the same day, and right now the second tool starts from zero no matter what the first one figured out. Turning past sessions into reusable skills instead of another summary doc is the right shape for that. One thing I'm curious about: are those memories scoped per repo by default? A workaround that makes sense in one codebase could be actively wrong in another, so I'd want the compounding layer to know which project a lesson came from.
@jcbuilds The scoping is really up to you and dependent on your codebase layout :) You can choose where to persist the memories + skills that Beacon generates for you, and can either share across repos or scope per repo.
Definitely try it out and let me know what you think JC! I'd love to get your feedback on the product: https://github.com/Asymptote-Labs/agent-beacon
@jcbuilds @justindsouza also make sure to claim your @beacon.sh profile to see where you stack up on the leaderboard: beacon.sh ✌️
@jcbuilds @fmerian here's the link to our profile leaderboard btw! https://beacon.sh/leaderboard
Congrats on the launch @justindsouza! Finally I can switch between Claude Code and Codex without re-explaining the same context all over again 🙌
@peggy_rayzis thank you Peggy! And yes, exactly -- that superpower is finally here :)
fun fact: @Claude Code + Codex are the top 2 tools users are porting context + memories between
@justindsouza @peggy_rayzis it's about time haha
I love the LLM concept and dev. However the intro video although very cinematic provides no information about what you have built. Best of wishes on your launch. Cheers!!
@richatsealedvault fair point haha! ICYMI @justindsouza recorded a live demo here. hope it clarifies
@justindsouza @fmerian Yes, this should be the first video on your page.
@justindsouza @richatsealedvault thanks for your support and feedback, it means the world 🙏
one more thing: please help us spread the word on X, repost this
@richatsealedvault Thanks Richard for the kind words! Definitely check out our demo video, or even better our open-source project and let me know what you think :) I'd love your feedback: https://github.com/Asymptote-Labs/agent-beacon
@richatsealedvault @justindsouza anything else @beacon.sh should build/improve/fix from your pov?
@justindsouza @fmerian No, that was all I wanted to bring to your attention.
@fmerian @richatsealedvault gotcha, thank you Richard!
Love it. Makes tokens last longer without the friction of my agents needing to load the whole context from scratch.
@juampihernandez exactly Juampi! I'd love your feedback on the product and would be super grateful for an upvote on our launch :) https://github.com/Asymptote-Labs/agent-beacon
@juampihernandez @justindsouza yes, and follow-up question: how many different coding agents do you use in a typical week? add your input here in /p/asymptotelabs
@juampihernandez spot on! make sure to claim your @beacon.sh profile to see where you stack up on the leaderboard: beacon.sh
@juampihernandez @fmerian Leaderboard has some big time token spenders :) https://beacon.sh/leaderboard
@juampihernandez @justindsouza 400B+ tokens by @ryanyannelli 🤯
@juampihernandez @ryanyannelli @fmerian true power coder!
Losing context across chats is one of the most frustrating things I encounter.
And as such, Beacon looks like a promising tool in that direction.
All the best for the launch!
@sumitsaurabh927 totally agree! This was easily the biggest pain-point that caused us to build Beacon out in public. Would really appreciate your support with an upvote, and I'd love your feedback on the project Sumit: https://github.com/Asymptote-Labs/agent-beacon
@sumitsaurabh927 you rock! appreciate your continuous support
@sumitsaurabh927 also make sure to claim your Beacon profile on beacon.sh - curious to see where you stack up on the leaderboard
Nice! love the idea
i am always switching between Cursor and Claude so this is very helpful so they both have reusable skills and memories
@thisiskp_ Thanks KP! Portability of context + memories + skills across harnesses was one of the biggest principles behind Beacon, so I'm really glad to hear that particular feature resonated with you :)
@beacon.sh is for you!
Really cool. I jump between T3 Code, Cursor and Codex, so this is great. Also open source. 🔥
@catalinmpit We love OSS! I definitely think this would be a superpower for your cross-harness workflows Catalin. With Beacon your memories + context are instantly portable :)
oss ftw!
@catalinmpit your support means the world