Why we will never square off your position for you

The single most requested feature we get is some version of this:

"Just close my positions when I hit my loss limit. I know I won't do it myself."

It is an honest request. The person asking has watched themselves blow through a limit they set that morning, and they have concluded, correctly, that they cannot be trusted at 1:20 PM with a red P&L.

We are not going to build it. Not in v1, not later, not as an opt-in toggle. LossGuardian is read-only: it cannot place, modify or cancel an order on your account, and the API permissions it holds do not allow it to. That is a design decision, not a limitation we are working around.

Here is the reasoning, because "we just won't" is not an argument.

Auto-squareoff removes the rep you need

Discipline is not a personality trait you either have or do not have. It is the accumulated result of a specific event repeating: you are shown that you have crossed your own line, you feel the pull to keep going, and you close the position anyway.

That last clause is the whole thing. It is the rep.

If software closes the position, the event still happens. You still crossed the line, you still felt the pull. But the rep does not. You did not do the hard part. Do that a hundred times and you have not built a hundred reps of discipline. You have built a hundred reps of being rescued, which is a different skill, and one that only works while the rescuer is present.

Now take the app away. Your laptop is at the service centre; you are trading from a phone; the API token expired at 6 AM and you did not notice. Every trader who outsourced the decision is, that day, exactly the trader they were before they installed anything.

The goal is not to have a good day while the software is running. The goal is to become someone whose default behaviour at 1:20 PM is different. Those are not the same product.

The dependency is quiet and it compounds

Watch what happens to your limits once something else enforces them.

When you are the one who has to close the position, the limit is a real constraint and you set it like one. When software will close it for you, the limit becomes a setting. Settings get adjusted. The number drifts up, ₹5,000 becoming ₹8,000, because "the app will catch me anyway, I just want room to breathe." The limit stops being the point at which you stop and becomes the point at which you are stopped, which are psychologically opposite things.

Six weeks in, the trader with auto-squareoff has a wider limit than the one they started with and no independent ability to honour it. That is a worse position than the one they were in before, and it took a feature request to get there.

Software should not have that power over your account

Set the psychology aside for a moment and look at it as an engineering problem.

To close a position, an application needs order-placement permission on your broker account. That permission does not come with a qualifier. It cannot be granted as "may exit, may not enter": the broker's API does not model intent, it models capability. Whatever can square off your NIFTY position at 1:20 PM can also, if it is wrong, place an order you did not want at 9:20 AM.

So ask what has to hold for that to be safe:

• The P&L calculation has to be right, on every product type, including the ones where the broker's own numbers lag by a few seconds.
• The connection has to be healthy. A stale feed showing a loss that is not there is now an order, not a false alarm.
• The logic has to be right on the day the market gaps, when the exchange feed hiccups, and when your broker's API returns a shape nobody tested against.
• Our deploy has to be right. Every time.

Software gets things wrong. Ours will get things wrong. The difference between a read-only tool and one holding trade permissions is the difference between a bug that shows you a wrong number and a bug that takes a position off at the worst possible price and posts the loss to your account. One of those you notice and report. The other one you cannot undo.

We would rather be a tool that occasionally shows a wrong number than a tool that occasionally trades.

There is a security argument on top of the safety one. A read-only token is worth very little to anyone who steals it. A token that can trade is worth taking. The smallest permission that does the job is the one worth holding, and the job here does not require trading. You can read exactly what LossGuardian stores and where on the security page.

What we do instead

We make the moment impossible to miss, and impossible to pretend you did not see.

When you cross a limit you set, LossGuardian puts a hard-stop alert in front of you that you cannot wave away with a click. It states the number, it states the rule you wrote, and it stays. It is a warning designed to be inconvenient, because a warning you can dismiss in half a second is a warning you have already learned to dismiss.

It also catches the thing a P&L number alone will not. Revenge trading does not announce itself as a big loss. It announces itself as a sequence: a loss, then a re-entry ninety seconds later, then position sizes creeping up. By the time the rupee figure looks alarming, the tilt started twenty minutes earlier. Timing and frequency are the signal; the loss is the lagging indicator.

Then you close the trade. On your broker's own platform, with your own hands. The rep counts.

"But I really cannot stop myself"

Then the limit is not the problem, and neither is the software.

If you genuinely cannot close a position after being told, in unmissable terms, that you are past your own line, no amount of automation fixes that. It just moves where the failure shows up. The trader who cannot honour a limit with a tool enforcing it is the trader who widens the limit, trades a second account, or turns the tool off. All three happen, and all three are worse than an honest failure you can see.

The honest version is useful. It gives you something to work with: a day you can look at, a pattern you can name, a number you can bring down next week. Being quietly saved teaches you nothing, and the record looks fine right up until the day it does not.

The trade-off, stated plainly

You can have a tool that protects today's capital by taking the wheel, or a tool that builds the trader who protects every future day's capital. Over one session the first one looks better. Over a year it is not close.

We picked the second one. If you want the first, we are the wrong product, and we would rather say so than sell you a dependency.

The rules are yours. We make sure you cannot pretend you did not see them.

---

Related reading: how LossGuardian compares to other Indian risk tools on permissions, pricing and what they are allowed to do: LossGuardian vs other tools. If you trade on Zerodha, the connection is an official broker-issued integration: LossGuardian for Zerodha.