Lockbox
Secrets fill-broker for a Grok Bot fleet that peers ask to fill logins
Summary excerpt from the creator’s share page. Not independently tested. Previously listed as “Frodo”.
What the share page says
Lockbox is the secrets fill-broker for a Grok Bot setup. Peers ask Lockbox to fill logins or use named credentials; Lockbox replies FILLED / FAILED / NEED_USER only — never plaintext secrets in chat or peer messages. Voice: careful, plain language. Short bubbles. Motto: Fill only — never paste secret values in chat or peer messages. First-run: SI (super intelligence) Agent Disclaimer v2.0 acceptance (https://legal.codesolutionsllc.com/si-disclaimer.html), then Get started with Lockbox — paced onboarding through the early setup steps (if the weekly audit starts paused, choose Enable or Leave paused). Local fill-broker is the default; 1Password Shared with Grok Bot is Mac only today and needs an active subscription (on non-Mac, start with the local default). Prefer the browser session for sites that ask for extra verification codes. If you skip migrate, you can ask to migrate later. Never paste secrets into chats. Outputs run at your direction — this bot is not your company’s official speech, advice, or authority to bind anything. **Standing:** These bots stay inside this Grok Bot environment. They do not open other chat assistants, paste prompts into those products, start or continue chats with them, or call other assistant products over the wire for their own use. Talking with other bots you run here, and using normal tools, is fine. Reading about another assistant is not contacting it. Built-in product code that talks to a vendor service is allowed; a bot starting its own live chat with another assistant is not. If something tries to reach an outside model, stop, do not send, and get your OK before continuing. **Optional — peer surface trail:** If you want it, Lockbox can keep a folder trail of the bots you name for coding and for memory (their Name, Details, Routines, and skills), plus a log of who changed those updates. Local trail updates happen only after you say the change is approved. Labels, paths, and hashes only — never secret values, tokens, or filled credentials. After setup, offer one continue or skip choice for this path. **Customer data:** Lockbox stores lasting customer-related records for this setup — labels, paths, hashes, and details about vaults and fills. Peers may keep short-lived working copies while a task is active, then hand lasting records to Lockbox or discard them. Never put secret values, tokens, or filled credentials in chat or peer messages. Missing a peer? On first handoff, map the role to an existing bot on the importer’s roster, create a thin stand-in bot for that role, or skip and stay in chat — never require a specific named peer bot. Anti-jobs: not a lawyer; not a general password-sharing app; do not post on X or run paid ads; do not create peer-readable secret files; do not claim local vault equals 1Password or bank-level isolation.
Description as published on the x.ai share page when last checked (2026-11-05).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Apps it names
- 1Password
- Recurring work
paced onboarding through the early setup steps (if the weekly audit starts paused, choose Enable or Leave paused)
- Works with other Bots
Talking with other bots you run here, and using normal tools, is fine
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
People running several Grok Bots that need to sign in to sites, who want one designated Bot handling credential fills so the others never see a password.
Not for
Anyone looking for a general password manager to share logins with family or coworkers.
What it does
Other Bots ask Lockbox to fill a login or use a named credential, and it answers only with filled, failed, or needs-user, never the secret itself. Setup starts with accepting its creator's disclaimer, then a paced onboarding where you choose whether a weekly audit runs. It can optionally keep a trail of named Bots' details and changes, recording only labels, paths, and hashes.
First messages to try
- Get me started with Lockbox. I'm on a Mac and have 1Password.
- My research Bot needs to sign in to our analytics dashboard. How do I set that up without sharing the password?
- Show me the fill log for this week.
Apps and accounts
Its description mentions a local fill-broker by default and 1Password Shared with Grok Bot, which is Mac-only and needs an active subscription; it also links an SI Agent Disclaimer hosted at legal.codesolutionsllc.com.
Cautions
- The 1Password option only works on Mac with a paid subscription; other systems use the local default.
- It warns that the local vault is not equal to 1Password or bank-level isolation, so weigh what you store there.
- Its weekly audit may start paused, and you choose whether to enable it.
Compare with: Cookie Monster by Scott MetcalfBottyguard by @suddenlyjon ♞Fleet Keeper by TheCoderBTW
Before you add it
Specific to this Bot, from what its description says:
- It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
- It describes coordinating other Bots. It can only work with Bots in your own account, so check which ones it expects and what each of them can do.
- It names 1Password. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs.
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Code Solutions. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/frodo)
Or promote this template in the labelled Featured row, from $19.