WUWuzzy·Aug 5, 2026
I think this exists: https://github.com/imbue-ai/latchkey (and there are other similar projects, too).
In Stateless MCP has recaptured my interestimbue-ai
latchkey
TypeScript2026–2026
imbue-ai / latchkey
latchkey
A command-line tool that injects credentials to curl requests to known public APIs.
2Distinct people
5Mentions
0Explicit recommenders
133GitHub stars
What to know before exploring
What it is
A command-line tool that injects credentials to curl requests to known public APIs.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week5 dated mentions
Observed mentions: 2026-02-03 20:15:40 UTC to 2026-08-05 04:38:11 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Feb 2 | 2026-02-02 00:00:00 UTC | 2026-02-09 00:00:00 UTC | 2 | 1 | 1 |
| Feb 9 | 2026-02-09 00:00:00 UTC | 2026-02-16 00:00:00 UTC | 0 | 0 | 0 |
| Feb 16 | 2026-02-16 00:00:00 UTC | 2026-02-23 00:00:00 UTC | 0 | 0 | 0 |
| Feb 23 | 2026-02-23 00:00:00 UTC | 2026-03-02 00:00:00 UTC | 1 | 0 | 1 |
| Mar 2 | 2026-03-02 00:00:00 UTC | 2026-03-09 00:00:00 UTC | 0 | 0 | 0 |
| Mar 9 | 2026-03-09 00:00:00 UTC | 2026-03-16 00:00:00 UTC | 0 | 0 | 0 |
| Mar 16 | 2026-03-16 00:00:00 UTC | 2026-03-23 00:00:00 UTC | 0 | 0 | 0 |
| Mar 23 | 2026-03-23 00:00:00 UTC | 2026-03-30 00:00:00 UTC | 0 | 0 | 0 |
| Mar 30 | 2026-03-30 00:00:00 UTC | 2026-04-06 00:00:00 UTC | 0 | 0 | 0 |
| Apr 6 | 2026-04-06 00:00:00 UTC | 2026-04-13 00:00:00 UTC | 0 | 0 | 0 |
| Apr 13 | 2026-04-13 00:00:00 UTC | 2026-04-20 00:00:00 UTC | 0 | 0 | 0 |
| Apr 20 | 2026-04-20 00:00:00 UTC | 2026-04-27 00:00:00 UTC | 1 | 0 | 1 |
| Apr 27 | 2026-04-27 00:00:00 UTC | 2026-05-04 00:00:00 UTC | 0 | 0 | 0 |
| May 4 | 2026-05-04 00:00:00 UTC | 2026-05-11 00:00:00 UTC | 0 | 0 | 0 |
| May 11 | 2026-05-11 00:00:00 UTC | 2026-05-18 00:00:00 UTC | 0 | 0 | 0 |
| May 18 | 2026-05-18 00:00:00 UTC | 2026-05-25 00:00:00 UTC | 0 | 0 | 0 |
| May 25 | 2026-05-25 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 1 | 2026-06-01 00:00:00 UTC | 2026-06-08 00:00:00 UTC | 0 | 0 | 0 |
| Jun 8 | 2026-06-08 00:00:00 UTC | 2026-06-15 00:00:00 UTC | 0 | 0 | 0 |
| Jun 15 | 2026-06-15 00:00:00 UTC | 2026-06-22 00:00:00 UTC | 0 | 0 | 0 |
| Jun 22 | 2026-06-22 00:00:00 UTC | 2026-06-29 00:00:00 UTC | 0 | 0 | 0 |
| Jun 29 | 2026-06-29 00:00:00 UTC | 2026-07-06 00:00:00 UTC | 0 | 0 | 0 |
| Jul 6 | 2026-07-06 00:00:00 UTC | 2026-07-13 00:00:00 UTC | 0 | 0 | 0 |
| Jul 13 | 2026-07-13 00:00:00 UTC | 2026-07-20 00:00:00 UTC | 0 | 0 | 0 |
| Jul 20 | 2026-07-20 00:00:00 UTC | 2026-07-27 00:00:00 UTC | 0 | 0 | 0 |
| Jul 27 | 2026-07-27 00:00:00 UTC | 2026-08-03 00:00:00 UTC | 0 | 0 | 0 |
| Aug 3 | 2026-08-03 00:00:00 UTC | 2026-08-10 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
5 sourcesI agree that there are downsides to this approach. NVIDIA OpenShell does the same thing: https://docs.nvidia.com/openshell/latest/sandboxes/manage-pr.... I had wondered how they deal with the fact that client programs sometimes come with their own CA bundles. Turns out OpenShell sets various common environment variables (like REQUESTS_CA_BUNDLE used by Python's requests) to try to convince as many clients as possible that the proxy's certificate is to be trusted :) I would assume exe.dev does something similar.
(I was interested in this because I was actually working on something similar recently: https://github.com/imbue-ai/latchkey. To avoid the certificates issue, this library uses a gateway approach instead of a proxy, i.e. clients call endpoints like "http(s)://gateway.url:port/gateway/https://api.github.com/..." which can be effect
Read the rest
ively hidden behind the "latchkey curl" invocation.)
In the vein of related work, there is https://github.com/imbue-ai/latchkey which injects secrets into cURL commands issued by your agent.
In Show HN: enveil – hide your .env secrets from prAIng eyesI believe in an MCP-less future of agent-service interactions and have recently submitted this general alternative (which also supports Slack) based on curl: https://github.com/imbue-ai/latchkey
With that said, a specialized tool like this will almost certainly work better if Slack is the only service you want your agents to interact with. I like that the auth is transparent.
In Show HN: Slack CLI for AgentsShow HN: Latchkey – inject credentials into agents' curl calls
Hi HN,
At Imbue, we’ve been following the rapid developments in the agent landscape and noticed that the way agents interact with third-party services on users’ behalf often leaves a lot to be desired. Integrations are ad hoc, complicated, context-heavy, and either unfriendly to non-technical users or tied to a lock-in of some sort.
We‘re experimenting with a command-line tool, Latchkey, that could be used by local agents targeted at non-technical users while avoiding remote intermediaries. As far as we know, this is the only existing approach at the intersection of these two goals.
Core idea: Agents access APIs of third-party services by prepending ordinary `curl` calls with the `latchkey` command, like this:
latchkey curl -X POST 'https://slack.com/api/conversations.create' \
-H 'Content-Type: application/json' \
-d '{"n
Read the rest
ame":"something-urgent"}'
Latchkey then transparently injects credentials into these calls, prompting the user to log in via a browser pop-up when needed. Browser automation is used to extract an API token from the browser session once logged in.
Benefits:
* A single skill to integrate with all services.
* Direct communication between the agent and the third-party service (no OAuth intermediary app needed).
* Agents usable by non-technical users.
* Secrets do not leak to logs or chat transcripts.
We believe this aligns with a vision of a decentralized future in which people don’t need to ask corporations for permission to use their own data. We imagine a lively ecosystem of local agents that people use freely, supported by a community helping each other keep these tools useful and functional.
We’re aware that this approach comes with some downsides, too, and would love your feedback.
P.S. Here’s also a link to Passepartout, a toy demo AI assistant app built using Latchkey: https://github.com/imbue-ai/passepartout