Guide

Never share a seed phrase with an agent

Some links may earn us a commission at no cost to you, which helps keep these guides free and up to date.

Do not paste, upload, or store a wallet seed phrase, recovery phrase, or private key in agent chat, memory, connectors, or shared-box notes. Fund only a dedicated spend path the agent can reach. Long-term holdings stay on hardware or accounts the bot cannot export.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

Run never share a seed phrase with an agent: do not paste, upload, screenshot, or store a wallet seed phrase, recovery phrase, or private key in agent chat, memory, connectors, shared-box notes, or .env the bot can read. Fund only a dedicated spend path the agent can reach. Long-term holdings stay on hardware or accounts the bot cannot export. Agent Lane publishes the checklist. We do not hold keys, run wallets, or place trades.

What this page is

A short operator guide that deepens the cold-store line from the dedicated agent wallet and crypto shield into a hard rule: master keys never enter agent-visible surfaces. Pair it with agent memory hygiene, the shared-box checklist, a separate browser profile for the agent, agent spend caps, revoke before you debug, empty the sleeve overnight, rotate before you raise the balance, and x402 buyer basics when the bot pays on-chain.

We are a publisher, not a wallet vendor. Hardware options such as Trezor and Ledger appear on Resources as devices you control — we do not invent affiliate claims beyond those links. Confirm setup on the official product page.

Why sharing a seed with an agent is the failure mode

• Chat paste. “Just restore this wallet” or “here is my recovery phrase” puts the master key in logs, history, and the next prompt.
• Memory write. Saving a seed into agent memory means every future session can recall and export it — see agent memory hygiene.
• Screenshot OCR. A photo of a seed card in chat or a connector that can read images is still a key the bot can copy.
• Shared notes and .env. Shared-box notes, repos, and env files the agent can open are agent-visible — see shared-box.
• “Just for backup.” Backing up a seed into the agent’s vault or a connector “so I don’t lose it” is still sharing the seed with the agent.

What “never share a seed” means

• Seeds stay offline. Recovery phrases and long-term private keys on hardware or cold store the agent cannot export.
• No paste, upload, or memory write. Not in chat, prompts, screenshots for the bot, shared notes, or agent memory.
• Spend path only. Fund a dedicated agent wallet — never the vault that holds the master seed.
• Prefer a signer. Approved signer or connector over a raw key in .env on the agent machine.
• If it already leaked. Treat the wallet as compromised; move funds; revoke; prune memory — then rotate before you raise.

Where it sits in the shield stack

1. Dedicated agent wallet — money the bot can reach; long-term holdings stay outside.
2. Never share a seed phrase with an agent — master keys stay offline; never enter chat, memory, or shared notes.
3. Spend caps — session and daily maxes on the spend path.
4. Review before place — human gate on amount, destination, and asset.
5. Agent memory + shared-box — secrets out of memory and shared disk.
6. Revoke before you debug / rotate before raise — if a key or connector may have leaked.
7. Empty the sleeve overnight — park spendable cash when idle.

Healthy stack: cold seed offline → dedicated funded sleeve → caps and review. Skip the seed rule and one paste empties the vault no matter how small the sleeve.

How to keep seeds away from the agent

1. Keep seeds offline. Park seed phrases, recovery phrases, and long-term private keys on a hardware wallet or other cold store the agent cannot see. Hardware options on Resources (for example Trezor and Ledger links already listed there).
2. Never paste into agent surfaces. No seed in chat, prompts, memory writes, screenshots for the bot, shared-box notes, repos, or .env the agent can open.
3. Fund only a dedicated spend path. Use a dedicated agent wallet. Fund only what one bad run can lose — see spend caps and fund the session ceiling.
4. Prefer a signer over a raw key. If the spend path needs to sign, prefer a signer or connector you approve. On-chain hygiene: shield crypto spend; buyer rail: x402 buyer basics.
5. Harden memory and shared box. Prune secrets from agent memory. Keep shared-box notes and connector caches free of seeds.
6. If a seed already leaked into the agent. Treat the wallet as compromised. Move funds to a new seed the agent never saw. Follow revoke before you debug, clear memory and notes, then rotate before you raise. Overnight idle: empty the sleeve overnight.

Practical checklist

• No seed in chat, memory, notes, or .env. Master keys stay on cold store you approve.
• Spend path separate. Dedicated agent wallet funded to the ceiling only.
• Memory and shared-box pass. Prune secrets; no recovery phrases in shared notes.
• Leak response memorized. New wallet → revoke → prune → rotate before raise.

Brokerage path: Shield brokerage spend. On-chain pay: Shield crypto spend.

What Agent Lane does not do here

• We do not hold your keys, run a hot wallet, or settle payments.
• We do not place trades, preview your orders, or babysit your agents.
• We do not invent product click-paths or ask you to paste a seed into any tool.

Secrets in chat: see also never paste API keys in chat — vault or connector grant instead of pasting credentials into the transcript.

Related guides

• AI crypto scams: how they work and how to protect your crypto
• AI agent sent crypto by mistake: what you can and can’t undo
• Separate funding from trading wallet
• Name the strategy before connect
• Cap daily loss before session
• Never paste API keys in chat
• Revoke connectors when idle
• Whitelist merchants only
• Dedicated agent wallet
• Shield crypto spend
• Write invalidation before entry
• Reject duplicate place same thesis
• Confirm symbol before place
• No scale-in without GO
• Flatten all before connector revoke
• One order per idea until fill
• No place while unconfirmed fill
• Write max loss before entry
• Shared-box and connector checklist
• Separate browser profile for the agent
• Agent memory hygiene
• Agent spend caps
• Revoke before you debug
• Empty the sleeve overnight
• Rotate before you raise the balance
• x402 buyer basics
• Fund the session ceiling
• Review before place
• Shield brokerage spend
• More on Resources

FAQ

What does never share a seed phrase with an agent mean?

Never share a seed phrase with an agent means: do not paste, upload, screenshot, or store a wallet seed phrase, recovery phrase, or private key in agent chat, memory, connectors, shared-box notes, or .env the bot can read. Fund only a dedicated spend path the agent can reach. Long-term holdings stay on hardware or accounts the bot cannot export.

Why is pasting a seed into agent chat the failure mode?

A seed or private key that lands in chat, memory, a screenshot the bot can OCR, shared notes, or a connector-visible file is a key the next prompt, log, shared user, or leak can export and spend. Caps and review do not undo a key that already left cold store.

What are the common failure modes?

Chat paste (“just restore this wallet”), memory write (“remember my recovery phrase”), screenshot OCR of a seed card, shared-box notes or .env the agent can read, and “just for backup” into the agent’s vault. Each puts the master key on a path the bot can reach.

Does a dedicated agent wallet replace this rule?

No. A dedicated agent wallet is the funded spend path the bot may use. This page is the hard rule that the seed, recovery phrase, and exportable private key for long-term holdings never enter that path — or any agent-visible surface. You need both.

Where should long-term seeds live instead?

On a hardware wallet or other cold store you approve — devices such as Trezor or Ledger appear on our Resources page as hardware options you control. Prefer a signer you approve over a raw key in .env. Agent Lane does not sell wallets or hold keys.

What if I already pasted a seed into chat or memory?

Treat it as compromised for that wallet. Move funds off that seed to a new wallet whose seed the agent never saw, revoke live connectors, prune agent memory and shared notes that held the phrase, and keep future seeds offline. Pair with revoke before you debug and rotate before you raise.

Where does this sit in the shield stack?

Dedicated agent wallet holds only spend the bot can reach. Never share a seed keeps master keys offline. Spend caps, review before place, revoke before debug, empty sleeve overnight, and rotate before raise bound and gate the spend path. Shared-box and agent-memory hygiene keep secrets out of notes and memory. Agent Lane publishes the checklist; we do not hold keys.

Next steps

Before an agent touches real money, give the agent its own dedicated wallet, set hard spend caps, and shield your crypto. Or browse all Agent Lane guides.