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
Ours is one `CLAUDE.md` in the repo and `AGENTS.md` just points to it, so every agent reads the same file and a change goes through a commit like any other code. When I approve a memory in Beacon, can it land as a file in the repo so a teammate sees it in the PR?
@julien_zammit using those markdown files is definitely a useful baseline for sharing memories and context across agents! With Beacon, you get all that cross-harness compatibility out of the box too. And yeah, when you approve a memory or skill in Beacon it lands as a file that can be checked in via a PR.
We actually also just shipped a Beacon Team plan so you can share agent sessions, memories, skills + findings across your team! Let me know what you think, happy to personally onboard you: https://beacon.sh/pricing
@julien_zammit appreciate the thoughtful comment, Julien! absolute fan of what you're building at @CybeDefend, curious to see what you could build with @beacon.sh 👀
Love the idea of carrying lessons across coding agents. How does Beacon handle it when two agents learn conflicting things about the same codebase?
@ankit_pandit_dev thanks Ankit! Beacon has a configurable human-in-the-loop step for approving memory + skill candidates. If they're both approved but later become conflicting, we also leverage agent session traces as a feedback loop to continuously eval whether those memories + skills become stale!
@ankit_pandit_dev thanks, Ankit! make sure to upvote the launch and spread the word on LinkedIn, repost this
Love that memory travels across agents like Claude Code and Cursor, so every session makes the next one smarter instead of starting from zero.
@ilko_kacharov 100% Ilko! Glad that our approach with Beacon resonates with you. If you get a chance, please upvote our launch and I'd love your feedback on the project as well: https://github.com/Asymptote-Labs/agent-beacon
@ilko_kacharov exactly! help us spread the word on X, repost this