openclaw - 💡(How to fix) Fix [Feature]: Per-agent or per-binding session reset policy [1 participants]

Summary

Currently, session reset policies (session.reset, session.resetByType, session.resetByChannel) are global or channel-wide. There is no way to configure session reset behavior per agent or per binding.

Problem to solve

Use case:

When running multiple agents for different business workflows, each workflow has a different session lifecycle requirement:

• Some workflows (e.g., chatbots) need long-lived session continuity
• Others (e.g., one-shot task processing like health report submissions) need a fresh session for every inbound message to avoid context contamination and prevent token cost accumulation

Without per-agent/binding session reset, isolated task processing agents accumulate conversation history across unrelated requests, leading to:

• Context contamination (e.g., agent incorrectly references previous requests)
• Token cost growth over time
• Unpredictable behavior

Workaround:

Currently using cron jobs with sessionTarget: "isolated" as a workaround, but this adds unnecessary complexity for real-time inbound message handling.

Proposed solution

Allow session reset policy to be configured at the agent level (e.g., agents.list.*.session.reset) or at the binding level, so that specific agents or bindings can reset sessions on every message or after a short idle period without affecting other agents.

Alternatives considered

No response

Impact

Affected users/systems: Any OpenClaw deployment running multiple agents or bindings where different workflows coexist — particularly agents handling one-shot task processing alongside conversational agents.

Severity: Blocks workflow. Without session isolation at the agent/binding level, one-shot processing agents cannot be used reliably in production.

Frequency: Always. Every inbound message to an agent without session reset accumulates history, and context contamination occurs from the second request onward.

Consequence:

• Context contamination causes incorrect behavior immediately (e.g., agent referencing a previous unrelated request as if it were current)
• Token costs grow unbounded over time as session history accumulates
• Forces use of cron jobs with sessionTarget: "isolated" as a workaround for real-time inbound message handling — adding unnecessary architectural complexity
• Blocks adoption of OpenClaw for business workflow automation where session isolation is a baseline requirement

Evidence/examples

No response

Additional information

No response