Can I label or comment my alerts?

Autoview · Guide · Updated September 30, 2026

Yes, on the Chrome extension and the stand-alone runner. Autoview has a comment line, and it is the right tool when you want a human-readable label sitting next to the trades an alert fires. Start a line with two slashes and the rest of that line becomes a comment. It does not place an order, change sizing, or touch your account. It writes a note. When you later open your log and try to work out which strategy sent which order, that note is what tells you.

Comments run on the Chrome extension and the stand-alone runner. Both log the comment and skip the rest of that line before anything trades, code-verified 2026-07-29. A // line sent straight to a cloud webhook places no order either. To get the note in your log, send the alert through the extension or the stand-alone runner.

The examples on this page include e=. On a webhook, the order goes to the exchange account the webhook is linked to, and e= is ignored. e= only picks the exchange on the Chrome extension.

Here is the whole feature in one example:

// RSI oversold long, v3
e=oanda s=EUR_USD b=long q=2% & sl=-1.2%

Two lines, two commands. The first is the comment. The second is the trade. Autoview reads the comment, prints it, and moves on to the order underneath.

The rule: a line that starts with //

A comment is any command line whose first characters are //. Everything after the slashes, trimmed of surrounding spaces, is the comment text. That is the entire syntax. You don't type a label= or comment= parameter. The marker is the // at the start of the line.

So a label and a comment are the same thing. There is one mechanism, the comment line, and a label is just a short comment. If you came here looking for tags or categories, this is the thing that does that job.

What it actually does

A comment line is parsed as its own command, and Autoview treats it specially. It logs the text and then stops, on that line, before anything trades. Concretely:

• It never sends an order. A line beginning with // can't open, close, or cancel anything. That's by design.
• It doesn't merge into the trade below it. The comment and the trade are separate lines, so the comment never alters the order's exchange, side, size, or stops.
• It prints the text to your log so you can read it back later.
• It runs on the Chrome extension and the stand-alone runner, code-verified 2026-07-29. A // line sent straight to a cloud webhook places no order either.

Because it is a full line of its own, you can stack comments, put one above each command in a multi-line alert, or drop reminders to yourself between trades.

The full grammar: blank, comment, and malformed lines

Autoview's parser reads a multi-line alert one line at a time, and every line falls into one of three buckets: blank, comment, or a command. Here is what happens to each, by surface, verified against the parser code rather than assumed to be the same everywhere.

All three surfaces run the identical line-splitting and parsing code, so a blank line and a malformed line behave the same everywhere: both disappear with no trace, not even a log entry. The one place the surfaces diverge is the comment line itself. The Chrome extension and the stand-alone runner both check for the comment marker and log it before moving on. On the webhook platform, a // line is parsed into a comment internally and places no order. The logged note comes from the extension and the runner.

A malformed line is not the same thing as a comment. If you type a line that isn't a valid command and doesn't start with //, either surface, it is not logged as an error and it is not treated as a comment. It is simply not recognized as anything and disappears. If you expect to see a note in your log and don't, check that the line actually starts with two slashes.

Encoding and newlines

Autoview's line splitter reads the raw alert text character by character and treats a line feed (\n), a carriage return (\r), or a pipe (|) as the end of a line. That means a Windows-style line ending (\r\n) and a Unix-style line ending (\n) produce the same result: the same lines, in the same order, with no extra blank line inserted between them. You do not need to worry about which line ending your editor or webhook source uses.

The pipe character works as an alternative line separator, so e=oanda s=EUR_USD b=long|// note splits into the same two lines as putting the comment on its own row, unless the pipe sits inside square brackets, which are reserved for a different, unrelated multi-value syntax and are not split on. The parser itself does no character-set conversion; it works on whatever text string your platform has already decoded, so there is no separate encoding setting to configure for comments specifically.

Where you'll see the label afterward

The comment surfaces in your event log, the running record of what each alert did. In the log it shows up as its own entry, styled as a muted note rather than a trade row, so a label reads as a label and not as an order. When you scan a busy log, the comment lines are the signposts: the trade rows tell you what happened, the comment rows tell you which alert made it happen.

This is exactly why people use it. A funded account firing dozens of alerts produces a wall of near-identical order rows. Sprinkle a comment above each command and the log turns readable. You stop guessing which TradingView alert, which script, or which strategy version sent a given order.

Writing a useful label

A few habits make comments worth the keystrokes.

• Put the comment first. A comment above the trade reads in the order things happen: here's the note, here's the order it describes.
• Name the strategy and the version. // Donchian breakout v2 tells you far more in six months than // long does.
• Spaces are fine. The whole rest of the line is the comment, so you do not need quotes around a multi-word label. // momentum entry, half size works as written.

Keep it short enough to scan. The point of a label is that you can read it at a glance while the orders below it do the real work.

One thing to know about placeholders

If your alert comes from TradingView, you might reach for a placeholder like {{close}} to stamp the price into a comment. That won't fill in the way you expect. {{close}} is a TradingView placeholder, substituted by TradingView before the alert is ever sent, so whether it resolves depends on the sender, not on Autoview.

One more thing on Autoview's side. Autoview's own replacement values, the :name=value tokens you can define in an alert, are not applied inside the comment text that gets logged. A comment is logged as written. If you want a number to appear in the note, the platform sending the alert has to put a literal value there before Autoview ever sees it. For a strategy label, that rarely matters, because the useful labels are static text like a strategy name, not live prices.

What this is not

Don't confuse the comment marker with the c= parameter. They look related and aren't. c= is the cancel-or-close control: c=position closes a position, c=order cancels resting orders. That one acts on your account. The comment marker is the leading // and it acts on your log. Different jobs entirely.

Check it safely first

The rule that a comment line never places, changes, or cancels an order comes from the parser code on all three surfaces (cited in the source of this page). To see it on your own setup, add d=1 to the trade line under your comment, fire the alert once, and read your log. You should see the note, then the dry-run command, and no order on the exchange.

Putting it together

Here's a small multi-line alert with labels doing their job:

// --- ETH momentum strategy ---
// open
e=kraken s=ETHUSD b=long q=25% sl=-2%
// scale-in trigger handled separately
e=kraken s=ETHUSD b=long q=10%

Three comment lines, two trades. Nothing in the comments touches the orders. But open the log after this fires and you can read it like a sentence: ETH momentum strategy, an open, a scale-in. That is the entire value of the feature, and it costs you two slashes.

For everything the trade lines themselves can do, side, sizing, stops, order type and the rest, see the command reference or the full alert syntax page.

Read the command reference