Guide

Cap daily loss before session

Before an agent money session starts, set a hard daily (or session) loss cap and stop rules — so a losing streak cannot keep placing after the budget for the day is gone. Pair it with fund the session ceiling, session time-box, name the strategy before connect, never skip review before place, and two-person rule for large places.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

Do not start a live agent money session until a hard daily or session loss limit and stop rules exist — written where you can enforce them. A funded sleeve and an open clock still let a losing streak place until the cash is gone. The loss cap is the stop that ends place/pay/sign when the budget for the day (or session) is spent. Agent Lane publishes the checklist. We do not place trades, hold wallets, invent broker UI, or run your agents.

What this page is

A short operator guide for the loss-budget gate on the shield — cap daily loss before session — so live connectors start with a written stop, not hope that size caps alone will save a streak. Pair it with fund the session ceiling, session time-box, name the strategy before connect, never skip review before place, two-person rule for large places, agent spend caps, log session end checklist, and the shared-box checklist.

We are a publisher, not a trading desk. Product screens change; write the number and stops in your notes or the settings your product already shows. We do not invent risk dashboards or Agentic click-paths. You set and enforce the cap.

Why no loss stop is the failure mode

• Ceiling + clock without a loss stop. Cash and time still allow place after place while the sleeve has funds — fund the session ceiling, session time-box.
• Streak chasing burns the day. Without a hard stop, “one more to get flat” becomes the whole ceiling — never skip review before place.
• Size caps ≠ cumulative loss. Per-place and session funding bound how much can move once; they do not stop cumulative realized loss from stacking — agent spend caps.

What “cap daily loss before session” means

• Loss number written first. Daily or session max loss (dollars or %) you will honor — before any live connector.
• What counts. Realized fills and fees at minimum; note if mark-to-market counts too.
• Stop rules. On hit: stop place/pay/sign; disable live connectors for this run; empty or park leftover; write the receipt/log. No “one more try.”
• Paired with cash and clock. Fund only the ceiling; set a session time-box.
• Paired with plan and gates. Name the strategy; keep never skip review; large size → two-person rule.

Where it sits in the shield stack

1. Name the strategy before connect — written plan (includes kill conditions; loss cap is one of them).
2. Cap daily loss before session — hard loss budget + stop rules before the live window opens.
3. Fund the session ceiling — cash in the sleeve matches the run, not tomorrow’s refill.
4. Session time-box — hard end time for the live window.
5. Never skip review before place + two-person rule for large places — human gates on each place.
6. Log session end checklist — close matches the plan (fills, receipts, connectors, sleeve).

Healthy flow: name strategy → write loss cap + stops → fund only the ceiling → set time-box → review on → place only while under the loss budget → hard-stop on hit → log the close. Skip the loss stop and a streak can burn the whole ceiling inside the clock.

How to cap daily loss before session

1. Write the loss number first. Daily or session max loss (dollars or %) before connect — same discipline as agent spend caps.
2. Define what counts. Realized fills and fees at minimum; say whether mark-to-market counts. Confirm fills in the broker UI, not chat.
3. Write stop rules. On hit: stop place/pay/sign; disable live connectors; empty or park leftover (empty the sleeve overnight habit); write receipt/log. No “one more try.”
4. Pair with ceiling and time-box. Fund only the session ceiling. Set a session time-box. Loss, cash, and clock all bound the run.
5. Name the strategy; keep review on. Name the strategy before connect. Never skip review before place. Large places: two-person rule. No invented UI.
6. Track during the session; hard-stop on hit. Update realized loss from the broker UI. When the cap hits, execute the stop rules — then log session end checklist. Travel/offline: kill switch before travel.

Practical checklist

• Loss number written. Daily or session max before connect.
• What counts written. Realized (+ fees); mark optional but explicit.
• Stop rules written. Disable connectors, park sleeve, log — no “one more.”
• Ceiling funded only. No surplus beside live tools.
• Time-box set. Hard end for the live window.
• Strategy named; review on. Plan + human gate before place.
• Track from broker UI. Not from chat summaries.
• No invented UI. Official venue screens and your notes only; you set and enforce the cap.
• Shared-box pass. Who can raise or ignore the loss stop on a shared computer — see shared-box.

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

What Agent Lane does not do here

• We do not place trades, preview your orders, or babysit your agents.
• We do not hold your funds, run a hot wallet, or settle payments.
• We do not invent risk dashboards, daily-loss product menus, or Agentic click-paths.
• We do not set your loss number for you or claim a product “daily loss” feature.

Related guides

• Write max loss before entry
• Flatten before news you cannot size
• One risk unit per idea
• No new risk after session end
• Stop adding size after a loss day
• Fund the session ceiling
• Session time-box
• Name the strategy before connect
• One strategy, one sleeve
• Read-only quote before trade connector
• Never skip review before place
• No averaging down without a new thesis
• Journal every override
• Max open positions per sleeve
• Confirm cancel in the broker, not chat
• No overnight margin without GO
• Two-person rule for large places
• Agent spend caps
• Confirm fills in the broker, not chat
• Log session end checklist
• Empty the sleeve overnight
• No overnight margin without GO
• Kill switch before travel
• Separate funding from trading wallet
• Review before place
• Revoke before you debug
• 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
• Shield brokerage spend
• Shield crypto spend
• More on Resources
• Size from sleeve not from hope

FAQ

What does cap daily loss before session mean?

It means: before a live agent money session starts, write a hard daily (or session) loss limit and the stop rules that fire when it is hit — so a losing streak cannot keep placing after the budget for the day is gone. Pair with fund the session ceiling, session time-box, name the strategy before connect, never skip review before place, and two-person rule for large places.

How is this different from fund-session-ceiling or session-time-box?

Fund the session ceiling is the cash you put in the sleeve for this run. Session time-box is the clock that ends the live window. Cap daily loss is the loss budget — realized (and any marked) loss you will not exceed today or this session — plus the stop that ends place/pay/sign when it is hit. Use all three.

What belongs in the written loss cap?

At minimum: the dollar (or %) loss limit for the day or session; what counts (realized fills, fees, optional mark-to-market); and stop rules (disable connectors, empty or park sleeve, write the receipt/log, no “one more try”). You write and enforce it; Agent Lane does not invent broker risk UI.

Why is no loss stop the failure mode?

A funded ceiling and a time-box still allow place after place while the sleeve has cash and the clock is open. Without a loss stop, a streak can burn the whole ceiling chasing recovery. Caps on size do not replace a hard stop on cumulative loss.

Do I invent a broker daily-loss UI?

No. Write the number and stop rules in your notes, checklist, code, or product settings your venue already shows. Agent Lane does not invent risk dashboards, Agentic menus, or product click-paths.

Does this replace review, strategy naming, or two-person rule?

No. Cap daily loss is the loss-budget gate before and during the session. Name the strategy sets the plan. Never skip review and two-person rule gate each place. Fund ceiling and time-box bound cash and clock. You need the stack.

Where do I apply this next?

Cash: fund the session ceiling. Clock: session time-box. Plan: name the strategy before connect. Gate: never skip review before place. Large size: two-person rule for large places. Close: log session end checklist. Agent Lane publishes the checklist; we do not place trades or invent broker UI.

Next steps

Before an agent touches real money, review every order before it is placed, shield your brokerage account, and map the trading-agent options. Or browse all Agent Lane guides.