# Max open positions per sleeve

Cap how many simultaneous open positions a sleeve (or named strategy) may hold so an agent cannot stack risk across too many names at once. Pair with one-strategy-one-sleeve, fund-session-ceiling, cap-daily-loss-before-session, name-the-strategy-before-connect, never-skip-review-before-place. Agent Lane does not place trades, hold wallets, or invent broker UI.

Canonical HTML: https://agentlane.net/guides/max-open-positions-per-sleeve/

## Answer first

Write a hard max on concurrent open positions for each sleeve (or named strategy) before you connect. Cash ceilings and loss caps still matter — they do not stop stacking names while budget remains. Count open risk in the official venue UI at review; block new opens at your max. The number is yours to set.

## Why uncapped stacking is the failure mode

- **Cash left ≠ risk under control** — [fund-session-ceiling.md](./fund-session-ceiling.md), [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md).
- **Per-ticket review misses the count** — [never-skip-review-before-place.md](./never-skip-review-before-place.md).
- **Attribution and kills get noisy** — [one-strategy-one-sleeve.md](./one-strategy-one-sleeve.md), [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md).

## What it means

1. You set the number on the named plan before connect.
2. Simultaneous opens for this sleeve / strategy — not lifetime trades.
3. Separate from cash ceiling and daily loss stop.
4. Count from venue UI — [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md).
5. At max: no new open until close, or journaled override — [journal-every-override.md](./journal-every-override.md).

## Shield stack

1. [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md) — plan + write the max.
2. [one-strategy-one-sleeve.md](./one-strategy-one-sleeve.md) — isolate each plan’s cash and stops.
3. [fund-session-ceiling.md](./fund-session-ceiling.md).
4. [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md).
5. Max open positions per sleeve (this page) — concurrent-open ceiling.
6. [never-skip-review-before-place.md](./never-skip-review-before-place.md) — count before a new open.

## How to run max open positions per sleeve

1. Name the strategy and write the max — [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md).
2. Assign one sleeve per name — [one-strategy-one-sleeve.md](./one-strategy-one-sleeve.md); no invented UI.
3. Fund ceiling; attach loss stop — [fund-session-ceiling.md](./fund-session-ceiling.md), [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md), [separate-funding-from-trading-wallet.md](./separate-funding-from-trading-wallet.md).
4. At review, count opens in the venue UI — [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), [two-person-rule-for-large-places.md](./two-person-rule-for-large-places.md).
5. Block new opens at the max — or journal override: [journal-every-override.md](./journal-every-override.md); add-size: [no-averaging-down-without-new-thesis.md](./no-averaging-down-without-new-thesis.md).
6. Log and empty per sleeve — [log-session-end-checklist.md](./log-session-end-checklist.md), [empty-sleeve-overnight.md](./empty-sleeve-overnight.md); travel: [kill-switch-before-travel.md](./kill-switch-before-travel.md).

## Practical checklist

- Max written on the named plan (you set the number).
- Sleeve mapped — count applies to this sleeve / strategy.
- Cash ceiling funded; loss stop attached (separate brakes).
- Review counts opens from venue UI.
- At max: no new open unless close or journaled override.
- Official paths only — no invented broker UI.

Related: [One order per idea until fill](./one-order-per-idea-until-fill.md), [Reject duplicate place same thesis](./reject-duplicate-place-same-thesis.md), [one-risk-unit-per-idea.md](./one-risk-unit-per-idea.md), [one-strategy-one-sleeve.md](./one-strategy-one-sleeve.md), [fund-session-ceiling.md](./fund-session-ceiling.md), [cap-daily-loss-before-session.md](./cap-daily-loss-before-session.md), [name-the-strategy-before-connect.md](./name-the-strategy-before-connect.md), [never-skip-review-before-place.md](./never-skip-review-before-place.md), [journal-every-override.md](./journal-every-override.md), [no-averaging-down-without-new-thesis.md](./no-averaging-down-without-new-thesis.md), [confirm-fills-in-broker-not-chat.md](./confirm-fills-in-broker-not-chat.md).

## FAQ

**What does max open positions per sleeve mean?**
You set a hard ceiling on simultaneous open positions for one sleeve or named strategy so the agent cannot stack risk across too many names. Pair with one-strategy-one-sleeve, fund-ceiling, cap-daily-loss, name-strategy, never-skip-review.

**Do I invent a broker max-positions UI?**
No. Official venue position lists and your written max. Agent Lane does not invent UI or set your number.

**Does this replace fund-ceiling or daily loss?**
No. Cash size, loss stop, and concurrent-open max are different brakes. You need the stack.

## Sources

- Canonical HTML: https://agentlane.net/guides/max-open-positions-per-sleeve/
- 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 set your max open positions.