
weavescope
为Elixir和BEAM的AI代理提供追踪、调试和监控的原生可观测性平台。
caudena · HN
WeaveScope – Elixir native observability for AI agents
完整作品展
技术栈
23 projects

为Elixir和BEAM的AI代理提供追踪、调试和监控的原生可观测性平台。
caudena · HN
WeaveScope – Elixir native observability for AI agents

统一代码协助、交易工具和团队协作功能的AI驱动平台。
@ThrillStack · X


监控外部攻击面、检测子域名暴露、自动映射 CVE 威胁。
@tugayakin34 · X
ThreatPort is an all-in-one Cyber Threat Intelligence & Attack Surface Management platform

AI驱动的工程团队,规划、构建、测试和发布代码,具有人类监督。
@edgex11lz · X

使用 AI 代理审计代码库,验证架构是否生产就绪。
@profericardo24 · X
Alcatraz Projects is a forensic audit layer that uses OpenClaw agents to interrogate your repo, ensuring your architecture is production-ready, not just 'vibe-coded' debt.

Lumbox为AI代理提供邮箱、登录自动化、OTP和加密凭证API。
u/kumard3 · Reddit
shipped delivered/bounced/replied webhooks, and deliberately left out open-pixel tracking an agent that sends mail needs to know what happened to it. i had delivery and bounce events sitting in the database the whole time, they just never got delivered anywhere useful, so an agent sending mail had no way to react to a bounce or know if anyone replied. shipped webhooks for the real lifecycle: delivered, bounced, complained, replied. an email.replied event fires specifically when an inbound

Etch: 追踪、重放和验证AI代理的决策,提供签名审计线索。
u/Funky_Chicken_22 · Reddit
OSS to SaaS positioning problem: when the user persona and the buyer persona are completely disjoint Founder here. Sharing a positioning problem I think a lot of OSS-to-SaaS founders hit and don't talk about publicly. Context: I have been running an OSS project (world-model-mcp) with ~2,500 monthly PyPI installs. Two weeks ago I opened up the hosted companion, Etch, at etch.systems. Launched publicly on Product Hunt at 12:00 PDT yesterday. The positioning problem: OSS user persona: in

读取 GitHub 仓库并自动提议改动、创建拉取请求的 AI 代理。
@MetriQAI · X
— Stop re-explaining yourself to every AI. One workspace. Every AI. Shared memory.

在发布前检查AI生成内容中的错误和安全问题。
u/Brief_Dust8845 · Reddit
I pivoted from my initial idea after realizing I was solving the right problem at the wrong time When I started building GaaS Guard, it was an AI governance tool for companies. The idea was to help organizations defend against prompt injection and unsafe AI interactions. It was technically interesting, and I still genuinely believe I was solving a real problem. The problem was, it just wasn’t selling—to be brutally honest. Here’s how I actually ended up pivoting. I started using a b

ClawMaven — AI 代理部署治理层,支持设计和验证
@paulrodturner · X