# AI use cases for Open Keylet (omaekumiko2-create/OpenKeylet)

Repo: [omaekumiko2-create/OpenKeylet](https://github.com/omaekumiko2-create/OpenKeylet) | Use cases: 4 | Page: https://dedupedai.com/use-cases/omaekumiko2-create-openkeylet/

OpenKeylet is a free, local password and credential manager that gives AI agents MCP access to saved logins, API keys, SSH keys and TOTP codes without exposing hidden plaintext.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Deploy to a server over SSH without pasting the password: https://dedupedai.com/use-cases/omaekumiko2-create-openkeylet/deploy-to-server-over-ssh/
- Call a provider API with a stored key the agent never sees: https://dedupedai.com/use-cases/omaekumiko2-create-openkeylet/authenticated-api-calls/
- Sign in to a web admin console with a saved login and TOTP: https://dedupedai.com/use-cases/omaekumiko2-create-openkeylet/browser-sign-in-with-totp/
- Back up the vault to your own private GitHub repository: https://dedupedai.com/use-cases/omaekumiko2-create-openkeylet/encrypted-backup-to-private-github/

## How to deploy to a server over SSH without pasting the password with Open Keylet

Repo: [omaekumiko2-create/OpenKeylet](https://github.com/omaekumiko2-create/OpenKeylet) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Let an agent run SSH commands and upload files using a saved host item.

**Who it is for:** A developer or ops engineer whose agent must deploy a build to a server that needs a password or private key.

**The problem:** Agents stall on SSH prompts, and pasting server passwords or keys into chat exposes them.

**The outcome:** The agent deploys the build and verifies the service while the password or key stays hidden from the model.

### Steps

1. Download the portable build for your platform and open Open Keylet.
2. Open Settings, then Agent connection, connect your detected client, and start a new agent session.
3. Save an item with a unique name such as Production Server and add the SSH host, port, username, and password or private key modules.
4. Ask the agent to use that item name in Open Keylet MCP for the deploy task.
5. Review the local activity records to confirm which client requested which action.

### Prompt to paste into your agent

```text
Using the OpenKeylet MCP server from omaekumiko2-create/OpenKeylet, use the item "<item name>" to upload the current build to <remote path> over SFTP and run <deploy command> over SSH. Report the command output and confirm the service responds. Verify that no password or key appears in your response.
```

### Caveat

Open Keylet does not pin or compare SSH host fingerprints, so you must verify the server identity yourself.

Risk, credentials: The agent can run commands on a live server with the saved item, so save only hosts the agent should reach.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/omaekumiko2-create-openkeylet/deploy-to-server-over-ssh/

## How to call a provider API with a stored key the agent never sees with Open Keylet

Repo: [omaekumiko2-create/OpenKeylet](https://github.com/omaekumiko2-create/OpenKeylet) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Have an agent send authenticated HTTP requests using a stored API credential.

**Who it is for:** A developer or account admin whose agent must list or change resources in a provider such as a DNS host.

**The problem:** Agents need API keys to work with a provider, but keys pasted into chat leak into logs and context.

**The outcome:** The agent completes the API task and reports results while the credential stays local to Open Keylet.

### Steps

1. Download the portable build for your platform and open Open Keylet.
2. Open Settings, then Agent connection, connect your detected client, and start a new agent session.
3. Save an item such as DNS Provider with an API credential module and the service URL, which is saved as a default.
4. Ask the agent to use that item name in Open Keylet MCP to run the API task.
5. Check the agent output to confirm the request succeeded.

### Prompt to paste into your agent

```text
Using the OpenKeylet MCP server from omaekumiko2-create/OpenKeylet, use the item "<item name>" to list the domains in this account through the provider API. Return the list and the HTTP status. Verify that the API key does not appear in your response.
```

### Caveat

A saved service URL is a default and relative-path base, not an Origin restriction, so the agent may call other destinations.

Risk, credentials: The stored credential can reach any HTTP or HTTPS destination the agent chooses, so review the task scope before you run it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/omaekumiko2-create-openkeylet/authenticated-api-calls/

## How to sign in to a web admin console with a saved login and TOTP with Open Keylet

Repo: [omaekumiko2-create/OpenKeylet](https://github.com/omaekumiko2-create/OpenKeylet) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Let an agent fill a login field and a current TOTP code in the browser.

**Who it is for:** An admin whose agent must reach a web console that asks for a password and a six-digit authenticator code.

**The problem:** Agents get stuck on login pages, and reading one-time codes aloud or pasting them is slow and risky.

**The outcome:** The agent signs in to the admin console using the saved item, with the password and seed kept local.

### Steps

1. Download the portable build for your platform and open Open Keylet.
2. Install the bundled Chromium extension in Chrome, Edge or Brave with its one manual load on first use.
3. Pair the Browser Bridge from Settings.
4. Save an item such as Admin Account with username, password and TOTP modules.
5. Ask the agent to open the admin console and use that item name in Open Keylet MCP when credentials are required.

### Prompt to paste into your agent

```text
Using the OpenKeylet MCP server from omaekumiko2-create/OpenKeylet, open <admin console URL> and use the item "<item name>" to fill the username, password and current TOTP code, submitting the form once. Report whether sign-in succeeded. Verify that no password or TOTP seed appears in your response.
```

### Caveat

Open Keylet writes one selected field into the focused control and does not inspect the page, so the agent must focus the correct field first.

Risk, credentials: The agent can sign in to a live account with the saved item, so confirm the target URL before the agent submits the form.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/omaekumiko2-create-openkeylet/browser-sign-in-with-totp/

## How to back up the vault to your own private GitHub repository with Open Keylet

Repo: [omaekumiko2-create/OpenKeylet](https://github.com/omaekumiko2-create/OpenKeylet) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Store encrypted snapshots in a private repo you own and restore on another device.

**Who it is for:** A developer who moves between machines and needs a recoverable copy of saved credentials.

**The problem:** A single device holds all saved credentials, so losing it can lock you out of servers and accounts.

**The outcome:** You hold encrypted snapshots in your own private repository and can merge-restore them on a new device.

### Steps

1. Create a dedicated private repository such as openkeylet-vault.
2. Create a fine-grained GitHub token and select only that repository with Contents: Read and write.
3. In Settings, open GitHub backup, enter owner/repository and the token, and choose Create a new backup.
4. Save the generated recovery key outside the repository.
5. Select Back up now and confirm that openkeylet.vault.json appears in the repository.

### Prompt to paste into your agent

```text
For the OpenKeylet project at omaekumiko2-create/OpenKeylet, ask the user to open Settings, GitHub backup, and select Back up now for <owner/repository>. Then confirm that openkeylet.vault.json exists in that repository. Verify that the file contains no unlock key or recovery key.
```

### Caveat

This version uses manual snapshots and merge restore, not automatic two-way synchronization.

Risk, credentials: Git history keeps older encrypted snapshots, including deleted credentials, and a lost recovery key makes the backup unrecoverable.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/omaekumiko2-create-openkeylet/encrypted-backup-to-private-github/