lexokoh

8 ms·

31.
Show HN: Agent Bus – Pub/Sub Messaging and Coordination for AI Agents(github.com)
3 points by lexokoh 1y ago|0 comments
32.
Show HN: GitTalk – Chat with Contributors Directly in GitHub PRs and Issues(github.com)
1 points by lexokoh 1y ago|0 comments
33.
Show HN: GitTalk – DM for GitHub(github.com)
1 points by lexokoh 1y ago|0 comments
34.
Show HN: Agent Key – A Permissions Broker for AI Agents(github.com)
1 points by lexokoh 1y ago|0 comments
35.
Show HN: Kage Bus – Lightweight Pub/Sub Message Bus for AI Agents(github.com)
1 points by lexokoh 1y ago|0 comments
36.
Show HN: Scoped, Ephemeral API Keys for AI Agents(github.com)
1 points by lexokoh 1y ago|0 comments
37.
Show HN: GitTalk – DMs and realtime PR/Issue chat inside GitHub(github.com)
2 points by lexokoh 1y ago|0 comments
38.
by lexokoh 1y ago
I’ve been experimenting with AI agents lately, and one problem kept coming up: they either get a raw API key with full access or nothing at all. That’s risky, especially if you’re testing agents that can make arbitrary calls. So I hacked th
39.
Show HN: OAuth for AI Agents(github.com)
8 points by lexokoh 1y ago|3 comments
40.
by lexokoh 1y ago
I finally added support for windows and linux
41.
by lexokoh 1y ago
If you open an issue or feature request, could look at it.
42.
by lexokoh 1y ago
Yes, but that's when they fork your repo. But if they are basically are cloning or using it, you mostly don't know who is.
43.
by lexokoh 1y ago
i made an update to specify ports like these. You can check.
44.
Show HN: Agent Key – OAuth for AI Agents(github.com)
2 points by lexokoh 1y ago|0 comments
45.
Show HN: Email Extractor – lightweight URL shortener and email extractor(github.com)
2 points by lexokoh 1y ago|0 comments
46.
Show HN: Agent Key – A permissions broker for AI Agents(github.com)
2 points by lexokoh 1y ago|0 comments
47.
by lexokoh 1y ago
A lot of ReadMe's are generated with AI. Doesn't really mean anything.
48.
by lexokoh 1y ago
Nice. I have this too. I wanted something more visual and expansive.
49.
by lexokoh 1y ago
It's just a tool I built for myself. There's no business case. It just helps me
50.
I hacked a way to use URL shortener to extract users' emails from GitHub/Docker
4 points by lexokoh 1y ago|2 comments
51.
by lexokoh 1y ago
Not sure I can add images here, but if you check the repo, I'll be adding one shortly.
52.
I started building a permissions broker for AI agent for myself(github.com)
3 points by lexokoh 1y ago|0 comments
53.
Show HN: Port Kill – A lightweight macOS status bar development port monitor(github.com)
128 points by lexokoh 1y ago|48 comments
54.
by lexokoh 1y ago
Thank you. Yes, it's one of the things I'm already looking into. So will work well with any Secrets manager, not compete with them. Curious if you'd want to use it?
55.
by lexokoh 1y ago
Thank you. Instead of giving the agent your real API key, it gets a scoped, short-lived capability (e.g. “can post 1 message to Slack channel X in the next 30s”). The short-lived nature means that if the token is leaked or the agent goes ro
56.
Show HN: Spin up 5 agents that don't trip over each other in 10 lines of code(github.com)
4 points by lexokoh 1y ago|0 comments
57.
Show HN: Scoped, expiring API keys for AI agents(github.com)
4 points by lexokoh 1y ago|4 comments
58.
Easy to use, protected and tracked artifact delivery(kagehq.com)
3 points by lexokoh 1y ago|0 comments
59.
by lexokoh 1y ago
Thank you for the thoughtful pushback. This is exactly the kind of discussion I was hoping for. I totally agree that FOSS + support can be a great model in the right context. We’re definitely not trying to reinvent DRM or lock users out of
60.
Ask HN: How do you handle licensing and revenue leaks for self-hosted software?
4 points by lexokoh 1y ago|4 comments

More ›