Grok Bot 新增凭据保险库,可安全存储密钥,模型在调用时经特殊访问路径,全程不接触明文凭据。用户指令触发工具调用时,主机仅凭工具名查找对应 API key 并构造真实 HTTP 请求,凭据只在最终构造处出现。该方案简化了智能体密钥管理,被视为推动大规模采用的关键创新。
this card allows grok bot to store credentials securely in a vault! when the credential is needed, it goes through a special access path where its never exposed to the model in plain text
later when you say "file a bug that login is broken", the bot turns that into a linear call with just the title (no token). the host knows that tool call is linear's, looks up this agent's linear api key, and builds the real http request. linear creates it, and the bot gets back "sent it, we're good". the host where the final tool call is constructed is also the only place the credential shows up
here's roughly how it works
I don't see anyone pointing out this Grok Bot innovation, but I think it is actually a big deal for mass adoption. How much time have you spent trying to figure out how to securely give your keys to your agent? Most people give up before they figure out how to build and store an .env file for their agent to access and use. Grok Bot's solution is simple, and most important of all, easy!在 X 查看被引用的帖子
来源:eric zakariasson · x.com