Imbue
We build AI that works for humans
309 followers
We build AI that works for humans
309 followers
Imbue develops tools that help people think, create, and build. We believe technology should be loyal to the user and aligned with human goals.
We share many of our tools openly because we believe progress in AI should be collaborative and developer-driven.
This is the 5th launch from Imbue. View more
Latchkey
Launching today
Getting your agent authenticated with third-party services shouldn't require a custom connector for each one.
Add Latchkey once and agents prepend latchkey to standard curl calls. Credentials are detected and injected automatically. They're stored encrypted on your machine, and never show up in logs or chat transcripts.
25+ services supported out of the box. Register any HTTP API at runtime. Works with Claude Code, OpenCode, Codex, and more. Open source software by Imbue.
Free
Launch Team
Imbue
@mrtibbets Congrats on getting this out! How Latchkey handles rate limiting when multiple agents are hitting the same service with shared auth?
Imbue
@rohanrecommends Latchkey is a transparent credentials layer; as such, it passes raw responses back to the requester without attempting to handle app-specific errors. Depending on the situation, it may sometimes make sense to share auth across many agents, while other times you may want to use isolated Latchkey instances to keep auth separate. There's an environment variable (LATCHKEY_DIRECTORY) that can be overridden to completely isolate Latchkey instances if desired (thus letting you use different tokens with different agents).
The credentials never showing up in logs or chat transcripts detail is the actually important thing here. I've seen agent setups where the auth storage is secure but the credential ends up in tool call output anyway - solved the wrong problem. Does token rotation work automatically? If a service refreshes the token mid-session does latchkey pick that up, or does the agent need to restart?
Imbue
@mykola_kondratiuk Really glad that resonates :) The credentials lifecycle is not connected to the agent lifecycle so you wouldn't need to restart agents. Supported services that work with the standard access token + refresh token pair should "just work".
@hynek_urban That's the key detail - decoupled credential lifecycle means the agent can keep running across token refreshes. Makes Latchkey much more practical for long-running workflows.