Telegram-Based TP/SL Update Messages for Existing Cornix Trades#762

Goal

Enable our system to send Telegram messages that Cornix can parse as trade update commands, allowing us to modify the Take Profit (TP) or Stop Loss (SL) of a specific trade that is already open.

Background

We already send Telegram trade signals that Cornix parses and executes. After a trade is opened, market conditions may change and we may need to adjust the trade’s TP or SL.

The requested feature is to send a follow-up Telegram message, linked to an earlier signal, that Cornix can interpret as an update to the existing open trade rather than a new trade.

Requested Behavior

The system should be able to send a Telegram message that:

1. References a previously sent trade signal or existing open trade.

2. Specifies whether to update:

   • Take Profit
   • Stop Loss
   • or both
3. Provides the new TP and/or SL values.
4. Is formatted in a way that Cornix can reliably parse.
5. Does not open a new trade.

Example Use Case

Initial signal sent to Telegram:

LONG BTC/USDT
Entry: 65000
TP: 66500
SL: 64000

Later, after the trade is already open, we want to update the SL:

Update BTC/USDT trade
Move SL to 64800

Or update TP:

Update BTC/USDT trade
Change TP to 67200

Requirements

• Support updating TP for an already-open trade.
• Support updating SL for an already-open trade.
• Support updating both TP and SL in one message.

• The update message should clearly identify the trade, ideally by:

  • trading pair,
  • direction,
  • original signal reference, or an id-number (sent before)
  • or Telegram reply/thread context.
• The message must be compatible with Cornix parsing rules.
• The update should not trigger a new trade entry.
• The system should log whether the update message was sent successfully.

Acceptance Criteria

• We can send a Telegram follow-up message that Cornix recognizes as an update to an existing trade.
• Cornix updates the TP and/or SL of the correct open trade.
• No duplicate or new trade is created.
• Failed or ambiguous updates are logged clearly.
• The message format is documented so it can be reused consistently.