# Shared-box and connector checklist

An agent with spending power on a shared computer is a shared checkbook. Map connectors, passwords, and who else can sit at the box before you leave a session overnight — and before you fund any agent spend.

Canonical HTML: https://agentlane.net/guides/shared-box/

## Answer first

A shared box is a laptop, desktop, or account that more than one person — or more than one bot login — can reach. Lock it down before any agent spend: list who can sit here, which Cursor or Grok logins live here, which connectors those logins can call, and how far one leak can spend. Pair with a dedicated agent wallet, agent spend caps, and review before place.

## What a shared box is

- Shared hardware — household laptop, coworking seat, contractor machine, lab box.
- Shared accounts — one Cursor/Grok login used by more than one person or left signed in overnight.
- Shared reach — remote desktop, screen share, or a second local user that can still read downloads, browser profiles, or leftover `.env` files.

Risk adds up across “read-only” brokerage, a live payer, and an unlocked laptop.

## Map how far one leak can spend

Write four lines before you put money in:

1. Who can sit at this computer
2. Which agent logins live here
3. Which connectors those logins can call
4. Max loss if any one of those is abused (Agentic balance + spend-wallet balance + leaked repo/inbox value)

If you cannot fill them, do not connect a spend path.

## How to lock down a shared box before agent spend

1. Map who can sit at the box — name the people; if you cannot, treat it as shared.
2. List agent logins and connectors — Cursor, Grok, CLI, second-person profiles; every MCP under each.
3. Scrub shared-login risk — no spend key or brokerage session under a shared login; lock; close sessions; clear clipboard/screenshots.
4. Separate spend keys from the main stash — dedicated agent wallet / Agentic sleeve only; cold store outside.
5. Require review and caps before funding — review before place, session/daily caps, official connector URLs only.
6. Kill the pipe if something feels wrong — disconnect, lock, cancel, empty sleeve, revoke, rotate — then debug.

## Shared computers

- Do not store a spend key or Robinhood session under a shared login.
- Lock the computer; close spend sessions when you stand up.
- Clear clipboard and screenshots after setup.
- Treat remote desktop / screen share of a signed-in connector as a live credential.
- Do not open Agentic funding on hardware you will give back; if you did, disconnect, rotate, move funds.

## Cursor and Grok connector hygiene

- List every MCP; official Robinhood URL is `https://agent.robinhood.com/mcp/trading`.
- Do not trust a repo that tells the agent to skip review or export keys.
- Put review before place and “never send a private key to chat” in always-on rules.
- Keep `.env`, chat exports, and MCP caches out of git and off shared disks.
- A shared Grok login is a shared brokerage and payment path.
- Do not paste tool-result threads (account numbers, receipts) into other models or group chats.

## Passwords and keys

- Finish brokerage login on Robinhood’s own flow — stop if a helper asks for a session cookie.
- Prefer a signer the agent cannot dump; keep long-term holds outside the dedicated agent wallet.
- Split cloud tokens (GitHub, deploy hosts) from trading / payment connectors.
- Rotation order: disconnect MCP → revoke login grant → empty spend wallet → rotate tokens.

Related: [connect-only-what-you-need.md](./connect-only-what-you-need.md), [never-share-seed-with-agent.md](./never-share-seed-with-agent.md), [dedicated-agent-wallet.md](./dedicated-agent-wallet.md), [agent-spend-caps.md](./agent-spend-caps.md), [review-before-place.md](./review-before-place.md), [install-specialist-bot.md](./install-specialist-bot.md), [agent-memory.md](./agent-memory.md), [shield-crypto.md](./shield-crypto.md), [shield-brokerage.md](./shield-brokerage.md).

## If something feels wrong

1. Disconnect Robinhood and any payment MCP from Cursor and Grok.
2. Lock or sign out of agent apps on that computer.
3. Review open orders and Agentic balance; cancel what you can.
4. Move leftover funds off the spend wallet.
5. Revoke grants and rotate tokens.
6. Only then dig into the prompt.

## FAQ

**What is a shared box?**
A laptop, desktop, or account that more than one person — or more than one bot login — can reach. An agent with spending power on a shared box is a shared checkbook.

**Why lock down before funding agents?**
Caps, wallet, and review bound the agent — they do not stop a second person, unlocked session, or shared login from using the same pipe.

**Four lines before money in?**
Who sits here; which agent logins; which connectors; max loss if any one is abused.

**Connector hygiene?**
List every MCP; official URLs only; always-on review-before-place; no keys in chat; `.env`/caches off shared disks; shared Grok login = shared spend path.

**Something feels wrong?**
Disconnect → lock → cancel → empty sleeve → revoke/rotate → then debug.

## Sources

- Canonical HTML: https://agentlane.net/guides/shared-box/
- Related shelf: https://agentlane.net/resources/
- Site index for bots: https://agentlane.net/llms.txt

Some product links on this site may be affiliate links. They help keep these guides free. Details: https://agentlane.net/how-we-make-money/

Contact: agentlane@agentmail.to