You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sessions are interrupted (connectivity issues), users typically type
'continue' or 'proceed' to re-enter the agent loop. These messages pollute
context without semantic value. This feature detects the last user message
being exactly 'continue' or 'proceed' (trimmed, case-insensitive) and tags
it as NEVER_FORWARD so the proxy omits it from backend transmissions while
preserving it in the local agent context window.
Default enabled; disable via --disable-auto-continue-removal,
AUTO_CONTINUE_REMOVAL_ENABLED=false env var, or
session.auto_continue_removal_enabled: false in config.
Uses existing non-forwardable tagging + enforcement infrastructure.
Fail-open: errors during tagging are logged and the request proceeds.
| `entries[].time` | str | required | Local server time in `HH:MM` 24-hour format |
571
+
| `entries[].execute_on_weekend` | bool | `false` | Allow this entry to run on Saturday and Sunday |
572
+
573
+
### ProxyMem (Cross-Session Memory)
530
574
531
575
ProxyMem provides persistent context across sessions by capturing interactions, generating LLM summaries, and injecting relevant history into new sessions.
Automatically detect and exclude mechanical "continue" / "proceed" user messages from backend submissions after connectivity interruptions, keeping context windows clean.
4
+
5
+
## Overview
6
+
7
+
When a coding agent session is interrupted (network drop, timeout, etc.), users commonly type `continue` or `proceed` to resume. These messages serve a purely mechanical purpose of re-enabling the agent loop and provide no semantic value to the remote LLM. Without this feature, they pollute the context window and are sent to every backend on every subsequent turn.
8
+
9
+
The Auto Continue/Proceed Removal feature detects when the very last user message is exactly `continue` or `proceed` (trimmed, case-insensitive) and tags it as non-forwardable. The existing non-forwardable enforcement layer then silently excludes it from outbound payloads to remote LLMs. The message remains in the agent's local context history so the coding agent continues building a complete window; only the transmission to the remote model is affected.
10
+
11
+
## Key Features
12
+
13
+
-**Exact match only**: Only pure `continue` or `proceed` strings are matched (case-insensitive, trimmed). Phrases like `please continue` or `continue working` are **not** affected.
14
+
-**Last-message scope**: Only the final user message in the request is checked. Earlier occurrences are left untouched.
15
+
-**Non-forwardable tagging**: Uses the existing `NEVER_FORWARD` mechanism so the proxy keeps the message in local history but excludes it from all backend transmissions.
16
+
-**Default enabled**: Active by default; disable explicitly when needed.
17
+
-**Fail-open**: If the non-forwardable registry or identity service is unavailable, the feature degrades gracefully without breaking requests.
18
+
19
+
## How It Works
20
+
21
+
1. During the request transform pipeline, the proxy inspects the last message.
22
+
2. If the message role is `user` and its content (trimmed, lowercased) is exactly `continue` or `proceed`, the proxy computes a deterministic identity and tags it with `NEVER_FORWARD` and reason `auto_continue_removal`.
23
+
3. Later, just before the backend call, the non-forwardable message enforcer filters out tagged messages from the outbound payload.
24
+
4. On subsequent turns the coding agent resubmits the same context window; the tag persists for the session lifetime, so the message continues to be excluded.
25
+
26
+
## Configuration
27
+
28
+
The feature is **enabled by default**. Configuration follows precedence: CLI > Environment > Config File.
0 commit comments