SendOptions

Routing identity for ChatUiChannel requests. Replaces the need to understand io.agentscope.harness.agent.gateway.channel.DmScope by letting the caller express routing intent through simple business identifiers.

• userId — identifies the user. Maps to io.agentscope.harness.agent.gateway.MsgContext#userId() for HarnessAgent namespace isolation, and is used as the default session key when sessionId is null.

• sessionId — optional explicit conversation identifier. When provided, different sessions for the same user are kept separate. When null, one session per user is the default.

• agentId — optional target agent override for multi-agent setups. When null, the channel's default agent is used.

• runtimeContext — optional per-call RuntimeContext merged into the agent turn (attributes, typed values, force-sync flags, …). Gateway-owned identity fields still win on conflict.

Usage

`// One session per user (most common)
chat.send(SendOptions.userId("user-1"), "hello");

// Same user, different sessions
chat.send(SendOptions.of("user-1", "session-a"), "hello");
chat.send(SendOptions.of("user-1", "session-b"), "hello");

// Target a specific agent in multi-agent setups
chat.send(SendOptions.userId("user-1").withAgentId("support"), "help me");

// Pass application context into the agent turn
chat.send(
SendOptions.userId("user-1")
.withAttribute("tenant", "acme")
.withRuntimeContext(
RuntimeContext.builder()
.put(AgentSpawnTool.CTX_FORCE_SYNC, true)
.build()),
"hello");
`