展示HN：Armorer – 一个安全的本地控制平面，用于AI代理
嘿，HN，
我创建Armorer是因为我厌倦了两件事：
1. 设置新的AI代理（Codex、OpenClaw等）时的“依赖地狱”。
2. 将强大的本地代理赋予广泛访问我主机的安全风险。
Armorer是一个安全的本地控制平面，管理您的代理生命周期。它使用Docker实现真正的进程隔离，并提供统一的用户界面/命令行界面，用于监控和作业跟踪。
我特别兴奋的一个功能是：您可以将现有的编码代理指向Armorer的代码库，它将自动安全地为您安装和配置整个技术栈。
源代码： [https://github.com/ArmorerLabs/Armorer](https://github.com/ArmorerLabs/Armorer)
网站： [https://armorerlabs.com](https://armorerlabs.com)
我很想听听您对架构的看法，以及您如何在本地处理代理安全问题。
查看原文
Hey HN,<p>I built Armorer because I was tired of two things:
1. The absolute "dependency hell" of setting up new AI agents (Codex, OpenClaw, etc.).
2. The security risk of giving powerful local agents broad access to my host machine.<p>Armorer is a secure local control plane that manages the lifecycle of your agents. It uses Docker for true process isolation and provides a unified UI/CLI for monitoring and job tracking.<p>One feature I’m particularly excited about: you can point an existing coding agent at the Armorer repo, and it will autonomously install and configure the entire stack for you securely.<p>Source: <a href="https://github.com/ArmorerLabs/Armorer" rel="nofollow">https://github.com/ArmorerLabs/Armorer</a>
Website: <a href="https://armorerlabs.com" rel="nofollow">https://armorerlabs.com</a><p>I’d love to hear your thoughts on the architecture and how you're handling agent security locally.