# One venue, one agent session

Keep one agent session pointed at one trading venue (or one broker account) so fills, cancels, and kill-switches stay unambiguous — do not let the same chat juggle two brokers or mix paper + live without a hard wall. Pair with separate-browser-profile-for-agent, one-strategy-one-sleeve, separate-funding-from-trading-wallet, never-skip-review-before-place, confirm-fills-in-broker-not-chat. Agent Lane does not place trades, hold wallets, or invent broker UI.

Canonical HTML: https://agentlane.net/guides/one-venue-one-agent-session/

## Answer first

Before you connect or place: name the single venue (broker/exchange/account) and mode (paper or live) this agent session may touch. Do not attach a second live broker to the same chat. Do not promote a paper session to live without a new named wall. Confirm fills and cancels in that venue’s official UI — not chat.

## Venue and session in plain terms

1. **Venue** — broker, exchange, or wallet rail this session may place on (one account you named).
2. **Agent session** — this chat / run with live or paper connectors attached.
3. **Hard wall** — paper and live are separate sessions (preferably separate connectors/profiles); two live brokers do not share one chat.
4. **Not the wall** — “I’ll remember which is which,” juggling two brokers in one thread, or reusing a paper chat for live places.

## Why juggling venues in one chat is the failure mode

- **Fills blur across brokers** — [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md).
- **Cancels hit the wrong rail** — [confirm-cancel-in-broker-not-chat.md](./confirm-cancel-in-broker-not-chat.md).
- **Paper habits go live** — [paper-before-live.md](./paper-before-live.md), [never-skip-review-before-place.md](./never-skip-review-before-place.md).
- **Kill-switch covers the wrong surface** — [revoke-connectors-when-idle.md](./revoke-connectors-when-idle.md), [kill-switch-before-travel.md](./kill-switch-before-travel.md).

## Shield stack

1. [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md) — plan + which venue/mode.
2. [separate-browser-profile-for-agent.md](./separate-browser-profile-for-agent.md).
3. [one-strategy-one-sleeve.md](./one-strategy-one-sleeve.md).
4. [separate-funding-from-trading-wallet.md](./separate-funding-from-trading-wallet.md).
5. One venue, one agent session (this page) — one chat → one venue/mode; hard wall paper vs live.
6. [never-skip-review-before-place.md](./never-skip-review-before-place.md).
7. [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md).

## How to run one venue, one agent session

1. Name the venue for this session — [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md); no invented UI.
2. Open one session pointed at that venue — [separate-browser-profile-for-agent.md](./separate-browser-profile-for-agent.md), [one-connector-at-a-time.md](./one-connector-at-a-time.md).
3. Hard-wall paper from live — [paper-before-live.md](./paper-before-live.md), [dry-run-before-first-live-place.md](./dry-run-before-first-live-place.md).
4. Keep review and fills on that venue only — [never-skip-review-before-place.md](./never-skip-review-before-place.md), [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md), [confirm-cancel-in-broker-not-chat.md](./confirm-cancel-in-broker-not-chat.md).
5. Kill-switch maps to one rail — [revoke-connectors-when-idle.md](./revoke-connectors-when-idle.md), [kill-switch-before-travel.md](./kill-switch-before-travel.md), [log-session-end-checklist.md](./log-session-end-checklist.md).
6. Journal if you switch venues — [journal-every-override.md](./journal-every-override.md); do not juggle mid-chat.

## Practical checklist

- Venue + mode written (one broker/account; paper or live).
- One session → one venue — no second live broker in the same chat.
- Paper and live hard-walled — separate sessions/connectors.
- Browser wall on; sleeve + funding split on.
- Review on; fills/cancels in that venue UI — not chat.
- Kill/revoke maps to this rail; venue switch = new session (journaled).
- Official paths only — no invented broker UI.

Related: [Confirm symbol before place](./confirm-symbol-before-place.md), [paper-before-live-same-rules.md](./paper-before-live-same-rules.md), [separate-browser-profile-for-agent.md](./separate-browser-profile-for-agent.md), [one-strategy-one-sleeve.md](./one-strategy-one-sleeve.md), [separate-funding-from-trading-wallet.md](./separate-funding-from-trading-wallet.md), [never-skip-review-before-place.md](./never-skip-review-before-place.md), [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md), [confirm-cancel-in-broker-not-chat.md](./confirm-cancel-in-broker-not-chat.md), [paper-before-live.md](./paper-before-live.md), [one-connector-at-a-time.md](./one-connector-at-a-time.md), [kill-switch-before-travel.md](./kill-switch-before-travel.md), [journal-every-override.md](./journal-every-override.md).

## FAQ

**What does one venue, one agent session mean?**
Keep one agent chat pointed at one trading venue or broker account so fills, cancels, and kill-switches stay unambiguous. Do not juggle two brokers in one chat or mix paper + live without a hard wall. Pair with separate-browser-profile, one-strategy-one-sleeve, separate-funding, never-skip-review, confirm-fills.

**Do I invent a broker multi-venue UI?**
No. Official venue screens and your written session map. Agent Lane does not invent UI.

**Does this replace one strategy one sleeve or separate browser profile?**
No. Sleeve isolation, browser wall, and session/venue wall are different brakes. You need the stack.

## Sources

- Canonical HTML: https://agentlane.net/guides/one-venue-one-agent-session/
- Related shelf: https://agentlane.net/resources/
- Site index: https://agentlane.net/llms.txt

Agent Lane publishes checklists. We do not place trades, hold wallets, invent broker UI, or enforce your venue map.