loopandlearn · marionbarker · Apr 27, 2026 · Apr 30, 2026 · Apr 30, 2026 · Apr 30, 2026
diff --git a/docs/build/build-options.md b/docs/build/build-options.md
@@ -4,7 +4,7 @@
 
 * Browser Build: 
     * If you have never built, see [*LoopFollow* Browser Build](lf-browser-build.md)
-    * If you are updating from v5.x or older, you need follow the one-time steps to [Update to *LoopFollow* v6.x](lf-browser-build.md#update-to-loopfollow-v6x){: target="_blank" }
+    * If you are updating from v5.x or older, you need follow the one-time steps to [Update to *LoopFollow* v6.2](lf-browser-build.md#update-to-loopfollow-v62){: target="_blank" }
 * Mac-Xcode: [Build *LoopFollow* Script for Mac-Xcode](#build-loopfollow-script-for-mac-xcode)
 
 ### Build *LoopFollow* Script for Mac-Xcode

diff --git a/docs/build/lf-browser-build.md b/docs/build/lf-browser-build.md
@@ -139,7 +139,7 @@ The `Add Identifier` &nbsp;<span class=notranslate>Action</span>&nbsp; should su
 
 New builders - just continue with the instructions as provided on this page. 
 
-### Update to *LoopFollow* v6.x
+### Update to *LoopFollow* v6.2
 
 !!! important "Updating LoopFollow to version 6.0 and newer"
     This information admonition is for existing builders who need to update.

diff --git a/docs/remote/img/lf-nightscout.png b/docs/remote/img/lf-nightscout.png
diff --git a/docs/remote/img/lf-ns-remote-loop-details.png b/docs/remote/img/lf-ns-remote-loop-details.png
diff --git a/docs/remote/img/lf-ns-remote-loop.png b/docs/remote/img/lf-ns-remote-loop.png
diff --git a/docs/remote/img/lf-quick-pick-bolus.png b/docs/remote/img/lf-quick-pick-bolus.png
diff --git a/docs/remote/img/lf-quick-pick-carbs.png b/docs/remote/img/lf-quick-pick-carbs.png
diff --git a/docs/remote/img/lf-quick-pick-meal.png b/docs/remote/img/lf-quick-pick-meal.png
diff --git a/docs/remote/img/lf-remote-options-loop.png b/docs/remote/img/lf-remote-options-loop.png
diff --git a/docs/remote/img/lf-remote-options-trio.png b/docs/remote/img/lf-remote-options-trio.png
diff --git a/docs/remote/img/lf-remote-options_3.2.svg b/docs/remote/img/lf-remote-options_3.2.svg
diff --git a/docs/remote/remote-control-loop.md b/docs/remote/remote-control-loop.md
@@ -82,6 +82,49 @@ Example messages are highlighted by red rectangles in the composite below for re
     If the last update was more than 12 minutes ago, that line is not prefilled.
 
 
+### Quick-Pick Boluses and Meals
+
+!!! info "Available in *LoopFollow* 6.2 and newer"
+    <!-- TODO: confirm the exact release version before publishing -->
+
+To save a step when sending a remote command, *LoopFollow* shows **Quick-Pick**
+buttons at the top of the Bolus and Carbs screens. Each button fills in the
+amounts from one of your recent entries with a single tap.
+
+* **Quick-Pick Boluses** appear on the Bolus screen and fill in an insulin amount.
+* **Quick-Pick Meals** appear on the Carbs screen and fill in **carbs only**.
+
+| Quick-Pick Boluses | Quick-Pick Meals |
+|:--:|:--:|
+| ![Quick-Pick Boluses on the remote Bolus screen](img/lf-quick-pick-bolus.png){width="300"} | ![Quick-Pick Meals on the remote Carbs screen](img/lf-quick-pick-carbs.png){width="300"} |
+
+Tapping a button only **fills in** the fields — nothing is sent until you review
+the values and tap **Send Bolus** / **Send Carbs**, exactly as with a manual entry.
+Guardrails still apply.
+
+#### How the suggestions are chosen
+
+Every bolus or carb entry you successfully send is stored **locally on your
+phone**. When you open a remote screen, that history is scored to surface the
+most relevant options for the current moment, considering:
+
+* **Time of day** — entries sent around this time of day score higher
+* **Day of week** — weekday and weekend patterns are kept separate
+* **Recency** — older entries gradually fade out
+
+Up to five buttons are shown, and the Quick-Pick section is hidden entirely
+until you have history to draw from. So if you usually send the same breakfast
+on weekday mornings, that entry tends to appear as an option on weekday mornings.
+
+!!! note
+    The history is private to the device and stored in *LoopFollow* only.
+    *Nightscout* cannot tell remote entries apart from manual ones, so it is not
+    used as a source — a freshly installed or reset phone starts with no
+    Quick-Pick suggestions until you send a few commands.
+
+Tap the :material-information-outline: info icon next to **Quick-Pick Boluses**
+or **Quick-Pick Meals** in the app for a short in-screen explanation.
+
 ### Overrides
 
 ***More info coming soon!***

diff --git a/docs/remote/remote-control-nightscout.md b/docs/remote/remote-control-nightscout.md
diff --git a/docs/remote/remote-control-overview.md b/docs/remote/remote-control-overview.md
@@ -27,20 +27,21 @@ For a full summary of version requirements and feature history, see [Version Com
 The graphic below shows the Remote Settings screen for *LoopFollow*. You must first enter a *Nightscout* URL before any remote options are offered and then only the option suitable for that *Nightscout* site can be selected.
 
 * When following someone running Loop, the options are None or [Loop Remote Control](remote-control-loop.md){: target="_blank" }
-* When following someone running Trio, the options are None or:
-    * Trio 0.5.x and newer: [Trio Remote Control](remote-control-trio.md){: target="_blank" }
-    * Trio 0.2.x: [Nightscout Remote Control](remote-control-nightscout.md#loopfollow-careportal-with-the-trio-app){: target="_blank" }
+* When following someone running Trio 0.5.x or newer, the options are None or [Trio Remote Control](remote-control-trio.md){: target="_blank" }
 
-![LoopFollow remote options - all types](img/lf-remote-options_3.2.svg){width="600"}
-{align="center"}
+!!! note "*Nightscout* Careportal Remote Commands Removed"
+    As of *LoopFollow* 6.2, *Nightscout* remote commands are no longer supported in *LoopFollow*. Remote control is now exclusively via direct APNS to the *Loop* or *Trio* app.
 
-### Critical Configuration Information
 
-If you plan to use *LoopFollow* Remote Control with a looper using the *Loop* app version 3.x or the *Trio* app version 0.5 or newer, and you don't have your APNS key information recorded or configured, see the instructions in [*Apple* Push Notifications System (APNS)](#apple-push-notifications-system-apns).
+| **Following *Loop*** | **Following *Trio*** |
+|:--:|:--:|
+| ![Loop remote control options](img/lf-remote-options-loop.png){width="300"} | ![Loop remote control options](img/lf-remote-options-trio.png){width="300"} |
+
 
-If your looper is using *Trio* 0.2.x, use this link for configuration:
 
-* [*Nightscout* Remote Control](remote-control-nightscout.md){: target="_blank" }
+### Critical Configuration Information
+
+If you plan to use *LoopFollow* Remote Control with a looper using the *Loop* app version 3.x or the *Trio* app version 0.5 or newer, and you don't have your APNS key information recorded or configured, see the instructions in [*Apple* Push Notifications System (APNS)](#apple-push-notifications-system-apns).
 
 - - -
 
@@ -189,6 +190,5 @@ The other remote credential are entered as described in the appropriate link.
 
 * [*Loop* Remote Control](remote-control-loop.md)
 * [*Trio* Remote Control](remote-control-trio.md)
-* [*Nightscout* Remote Control](remote-control-nightscout.md) (`Trio 0.2.x only`)
 
 
diff --git a/docs/remote/remote-control-trio.md b/docs/remote/remote-control-trio.md
@@ -1,6 +1,9 @@
 ## Remote Control Overview
 
-Trio can accept remote commands from *Nightscout* or from *LoopFollow*. There are a variety of options, but the final control of whether remote commands will be enacted rests with the *Trio* user. They can enable or disable remote control.
+*Trio* accepts remote commands from *LoopFollow* via direct APNS. The final control of whether remote commands will be enacted rests with the *Trio* user — they can enable or disable remote control.
+
+!!! note "*Nightscout* Careportal Remote Commands Removed"
+    As of *LoopFollow* 6.2, *Nightscout* remote commands are no longer supported in *LoopFollow*. Use *Trio* Remote Control (TRC) below, which requires *Trio* 0.5.x or newer.
 
 !!! warning "*Nightscout* version must be 15.0.2 or newer"
     To properly display the OpenAPS pill with *Trio* 0.5.x (or newer), your *Nightscout* version must be 15.0.2 (or newer). If you do not see the expected treatments or pills in the *Nightscout* dashboard, follow the steps to [Configure Nightscout for Trio (OpenAPS)](#configure-nightscout-for-trio-openaps).
@@ -25,17 +28,6 @@ Starting with *LoopFollow* v4.0 and *Trio* v0.6, users of remote control are pro
     **Question: If I was using Trio / LoopFollow remote control do I need to change my configuration parameters?**: No, the parameters you already set up continue to work. **BUT** you need to update the *LoopFollow* Identifiers if you use Browser Build.
 
 
-??? question "How does this differ from *Trio* 0.2.x? (Click to Open/Close)"
-    *Trio* can use *Nightscout* Careportal to enter `Carb Correction`, and start and cancel `Temporary Target`.
-
-    * This was available in *Trio* 0.2.x and continues to be available in *Trio* 0.5.x (or newer).
-    * See [*Nightscout* Remote Control](remote-control-nightscout.md#loopfollow-careportal-with-the-trio-app){: target="_blank" }
-
-    *Trio* 0.2.x supported other remote options (using announcements via Careportal). 
-
-    * Those options were replaced by the more secure *Trio* Remote Control for *Trio* 0.5.x (or newer)
-    * **Using announcements to provide remote control of the *Trio* phone is no longer supported**
-
 ### Quick Access
 
 The bullets below take you to the indicated topics. The configuration steps are listed first but only need to be done once:
@@ -98,6 +90,54 @@ When entering meals and choosing to schedule the meal, any bolus included in the
 
 ***More info coming soon!***
 
+### Quick-Pick Boluses and Meals
+
+!!! info "Available in *LoopFollow* 6.2 and newer"
+    <!-- TODO: confirm the exact release version before publishing -->
+
+To save a step when sending a remote command, *LoopFollow* shows **Quick-Pick**
+buttons at the top of the Bolus and Meal screens. Each button fills in the
+amounts from one of your recent entries with a single tap.
+
+* **Quick-Pick Boluses** appear on the Bolus screen and fill in an insulin amount.
+* **Quick-Pick Meals** appear on the Meal screen and fill in carbs, and — when
+  enabled in [Meal Settings](#meal-settings) — fat, protein, and the meal bolus.
+
+| Quick-Pick Boluses | Quick-Pick Meals |
+|:--:|:--:|
+| ![Quick-Pick Boluses on the remote Bolus screen](img/lf-quick-pick-bolus.png){width="300"} | ![Quick-Pick Meals on the remote Meal screen](img/lf-quick-pick-meal.png){width="300"} |
+{align="center"}
+
+Tapping a button only **fills in** the fields — nothing is sent until you review
+the values and tap **Send Bolus** / **Send Meal**, exactly as with a manual entry.
+Guardrails still apply.
+
+#### How the suggestions are chosen
+
+Every bolus or meal you successfully send is stored **locally on your phone**.
+When you open a remote screen, that history is scored to surface the most
+relevant options for the current moment, considering:
+
+* **Time of day** — entries sent around this time of day score higher
+* **Day of week** — weekday and weekend patterns are kept separate
+* **Recency** — older entries gradually fade out
+
+Up to five buttons are shown, and the Quick-Pick section is hidden entirely
+until you have history to draw from. So if you usually send the same breakfast
+on weekday mornings, that entry tends to appear as an option on weekday mornings.
+
+A bolus that was part of a meal is stored with that meal, so it does **not**
+appear among your standalone Quick-Pick Boluses.
+
+!!! note
+    The history is private to the device and stored in *LoopFollow* only.
+    *Nightscout* cannot tell remote entries apart from manual ones, so it is not
+    used as a source — a freshly installed or reset phone starts with no
+    Quick-Pick suggestions until you send a few commands.
+
+Tap the :material-information-outline: info icon next to **Quick-Pick Boluses**
+or **Quick-Pick Meals** in the app for a short in-screen explanation.
+
 ### Temp Target
 
 ***More info coming soon!***
@@ -160,9 +200,6 @@ The Remote Settings row in the *LoopFollow* Settings screen is used to select th
 !!! question "The *Trio* Remote Control option is not available"
     The `Trio Remote Control` option is only available in *LoopFollow* if you have already entered a [*Nightscout* Site](../setup/lf-setup.md#setup-nightscout){: target="_blank" } with a default profile recognized as a *Trio* profile. Review [Troubleshooting](#troubleshooting) for possible reasons for not seeing the option.
 
-* *Nightscout* option
-    * Remote control with *LoopFollow* is limited to starting and canceling Temp Targets
-    * Available with *Trio* 0.2.x and newer
 * *Trio* Remote Control option
     * Remote control with *LoopFollow* includes adding remote carbs, enacting remote bolus, and starting and canceling Temp Targets and Overrides
     * Requires *Trio* 0.5.x (or newer) and *LoopFollow* 2.4.x (or newer)
@@ -297,7 +334,7 @@ In addition to this step, you may need to force the profile (from Trio) to uploa
 ### Update Profile
 
 !!! warning "Must on *Trio* 0.5.x (or newer)"
-    If you are on *Trio* 0.2.x, you might see the option for *Trio* Remote Control in *LoopFollow* Remote Settings, but you can't use it. See [Use *LoopFollow* *Nightscout* Remote Control](remote-control-nightscout.md#loopfollow-careportal-with-the-trio-app).
+    If you are on *Trio* 0.2.x, *LoopFollow* 6.2 can no longer remotely control *Trio* — upgrade *Trio* to 0.5.x or newer to use *Trio* Remote Control.
 
 If you were previously running the *Loop* app or the *iAPS* app, [Stop *Nightscout* upload](#stop-nightscout-uploads-from-other-apps) from those apps and then force the profile to update.
 

diff --git a/docs/setup/lf-features.md b/docs/setup/lf-features.md
@@ -38,14 +38,15 @@ Do not skip the overview page if you have not yet configured *LoopFollow* for Re
 
 * [Remote Control Overview](../remote/remote-control-overview.md)
 
-There are separate pages for the 3 different remote control options. (No page is provided if `None` is selected).
+There are separate pages for the different remote control options. (No page is provided if `None` is selected).
 Quick access is provided using these links once you have configured *LoopFollow* for Remote Control:
 
 * None
-* [*Nightscout*](../remote/remote-control-nightscout.md){: target="_blank" } (*LoopFollow* offers actions that can be done from a *Nightscout* Careportal)
-* [*Loop* Remote Control](../remote/remote-control-loop.md){: target="_blank" } 
+* [*Loop* Remote Control](../remote/remote-control-loop.md){: target="_blank" }
 * [*Trio* Remote Control](../remote/remote-control-trio.md){: target="_blank" }: requires Trio 0.5.x or newer
 
+> As of *LoopFollow* 6.2, *Nightscout* remote commands are no longer supported in *LoopFollow*.
+
 
 - - -