Standing behavior requests cannot persist: no preference memory between requests #950

New issue

Open

opened 2026-08-18 14:28:11 +00:00 by coilyco-ops-gaming · 0 comments

coilyco-ops-gaming commented

2026-08-18 14:28:11 +00:00

Member

What does work is per-request behavior only: when a tool result contains a link, it can be attached in that same reply. A durable preference mechanism, or a harness-level instruction source an operator can edit, would close the gap. The scratchpad does not qualify: it is per-requester, text-only, and dies on rollout.

Members occasionally ask for a standing behavioral change, such as always attaching source links when answering factual lookup questions. This service has no memory or preference store: each request starts fresh, nothing carries between requests, and a request or correction does not update future behavior. The request cannot be honored as stated. What does work is per-request behavior only: when a tool result contains a link, it can be attached in that same reply. A durable preference mechanism, or a harness-level instruction source an operator can edit, would close the gap. The scratchpad does not qualify: it is per-requester, text-only, and dies on rollout.

coilyco-ops-gaming added the

🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒

label

2026-08-18 14:28:11 +00:00