Disagreements & proposals

The harness never silently rewrites your user profile. When it thinks something should change, it submits a proposal , visible in the Memory view → Proposals tab, and waits for you to act on it. When a proposal would conflict with something you've explicitly stated, it's escalated to a disagreement and queued under the Disagreements tab. How proposals get created After a run, the harness may notice something proposal-worthy: You've corrected the same kind of output three times: maybe your preference is different from what your profile says. You're consistently asking for shorter outputs than the role's defaults produce. You're consistently asking for citations the writer didn't include. The harness emits a proposal: Proposed change : under "Communication preferences" , add "Always include inline source citations in long-form content." Reason : corrected this 3 times in the last week . The Proposals tab Each pending proposal shows: The target memory file (usually user/profile.md ). The proposed change (diff format: what to add, change, or remove). The harness's reason. The runs/observations that triggered it. Actions: Accept : applies the change immediately. Edit then accept : adjust the proposed text before applying. Reject : discards the proposal. Adds a note to corrections so the harness doesn't re-propose the same thing. Defer : keeps it in the queue for later. Disagreements If a proposal would change something you've already stated explicitly, it becomes a disagreement. Example: your profile says "prefer concise summaries." The harness wants to propose "always include detailed step-by-step explanations" based on recent corrections. That's a disagreement. It's queued in the Disagreements tab with both sides shown: The existing preference, with its origin (e.g. "user-stated on 2026-03-10"). The proposed change, with its evidence. Actions: Keep existing : rejects the proposal and notes the conflict. Replace with proposal : accepts the proposal, overwriting the existing preference. Reconcile : opens an editor where you can write something that satisfies both intents. Resolved disagreements move to memory/disagreements/resolved/ for your reference. When to engage Don't feel obligated to action every proposal immediately. They queue. You can review the queue weekly, monthly, whenever. If the queue grows large (50+ items), the harness throttles proposal generation; it interprets your silence as low interest in profile evolution and stops being noisy. Manual proposal You don't need to write proposals manually. If you want to update your profile, just edit it directly in the User tab. The proposal system exists for the harness's side of the loop, not yours. Auditability Every accepted, rejected, or deferred proposal is logged in memory/profile-proposals/audit.ndjson (append-only). You can read the audit log to see what proposals were ever surfaced and what you did with them.

Back to docs