- Gateway: preserve stack diagnostics when `chat.send` or agent attachment parsing/staging fails, improving image-send failure triage. Refs #63432. (#75135) Thanks @keen0206.

- Agents/idle-timeout: add a cost-runaway breaker to the outer embedded-run retry loop that halts further attempts after 5 consecutive idle timeouts without completed model progress, so a wedged provider can no longer fan paid model calls out across the same run; completed text or tool-call progress resets the breaker, but partial tool-argument token dribbles do not. Fixes #76293. Thanks @ThePuma312.

- Heartbeats/Codex: stop sending the legacy `HEARTBEAT_OK` prompt instruction when heartbeat turns have the structured `heartbeat_respond` tool, while keeping the text sentinel for legacy automatic heartbeat replies. Thanks @pashpashpash.

- Heartbeats/Codex: keep structured heartbeat prompts aligned with actual `heartbeat_respond` tool availability and keep tool-disabled commitment check-ins on the legacy ack path. Thanks @pashpashpash and @vincentkoc.

- Agent runtimes: fail explicit plugin runtime selections honestly when the requested harness is unavailable instead of silently falling back to the embedded PI runtime. Thanks @pashpashpash.

- Maintainer workflow: push prepared PR heads through GitHub's verified commit API by default and require an explicit override before git-protocol pushes can publish unsigned commits. Thanks @BunsDev.

- Feishu: resolve setup/status probes through the selected/default account so multi-account configs with account-scoped app credentials show as configured and probeable. Fixes #72930. Thanks @brokemac79.

const codexLeakConfig = readQaScenarioExecutionConfig("codex-harness-no-meta-leak") as

| {

harnessRuntime?: string;

harnessFallback?: string;

expectedReply?: string;

forbiddenReplySubstrings?: string[];

}

);

expect(codexLeak.title).toBe("Codex harness no meta leak");

expect(codexLeakConfig?.harnessRuntime).toBe("codex");

expect(codexLeakConfig?.harnessFallback).toBe("none");

expect(JSON.stringify(codexLeak.execution.flow)).toContain("agentRuntime");

expect(JSON.stringify(codexLeak.execution.flow)).not.toContain("embeddedHarness");

expect(codexLeakConfig?.expectedReply).toBe("QA_LEAK_OK");

- runtime.no-meta-leak

objective: Verify the Codex app-server harness keeps coordination/meta chatter out of the visible reply.

successCriteria:

- The scenario forces the Codex embedded harness and disables PI fallback.

- The scenario forces the Codex embedded harness.

- The final visible reply includes the requested confirmation token.

- The visible reply does not include internal coordination or progress chatter.

docsRefs:

requiredProvider: codex

requiredModel: gpt-5.5

harnessRuntime: codex

harnessFallback: none

expectedReply: QA_LEAK_OK

prompt: |-

Think through your answer privately, but do not expose any internal planning, thread-context checks, or progress narration.

agentRuntime:

id:

expr: config.harnessRuntime

fallback:

expr: config.harnessFallback

- call: waitForGatewayHealthy

args:

- ref: env

expr: "snapshot.config.agents?.defaults?.agentRuntime?.id === config.harnessRuntime"

message:

expr: "`expected agentRuntime.id=${config.harnessRuntime}, got ${JSON.stringify(snapshot.config.agents?.defaults?.agentRuntime)}`"

- assert:

expr: "snapshot.config.agents?.defaults?.agentRuntime?.fallback === config.harnessFallback"

message:

expr: "`expected agentRuntime.fallback=${config.harnessFallback}, got ${JSON.stringify(snapshot.config.agents?.defaults?.agentRuntime)}`"

detailsExpr: "env.providerMode === 'live-frontier' ? `provider=${selected?.provider} model=${selected?.model} runtime=${snapshot.config.agents?.defaults?.agentRuntime?.id} fallback=${snapshot.config.agents?.defaults?.agentRuntime?.fallback}` : `mock mode: parsed ${scenario.id}`"

detailsExpr: "env.providerMode === 'live-frontier' ? `provider=${selected?.provider} model=${selected?.model} runtime=${snapshot.config.agents?.defaults?.agentRuntime?.id}` : `mock mode: parsed ${scenario.id}`"

- name: keeps codex coordination chatter out of the visible reply

actions:

- if:

objective: Verify the Codex app-server harness can plan and build a medium-complex self-contained browser game.

successCriteria:

- A live-frontier run fails fast unless the selected primary model is openai/gpt-5.5 with the Codex harness forced.

- The scenario forces the Codex embedded harness and disables PI fallback.

- The scenario forces the Codex embedded harness.

- The prompt explicitly asks the agent to enter plan mode before editing.

- The agent writes a self-contained HTML game with a canvas loop, controls, scoring, waves, pause, and restart.

docsRefs:

requiredProvider: codex

requiredModel: gpt-5.5

harnessRuntime: codex

harnessFallback: none

artifactFile: star-garden-defenders-codex.html

gameTitle: Star Garden Defenders

minBytes: 5000

agentRuntime:

id:

expr: config.harnessRuntime

fallback:

expr: config.harnessFallback

- call: waitForGatewayHealthy

args:

- ref: env

expr: "snapshot.config.agents?.defaults?.agentRuntime?.id === config.harnessRuntime"

message:

expr: "`expected agentRuntime.id=${config.harnessRuntime}, got ${JSON.stringify(snapshot.config.agents?.defaults?.agentRuntime)}`"

- assert:

expr: "snapshot.config.agents?.defaults?.agentRuntime?.fallback === config.harnessFallback"

message:

expr: "`expected agentRuntime.fallback=${config.harnessFallback}, got ${JSON.stringify(snapshot.config.agents?.defaults?.agentRuntime)}`"

detailsExpr: "env.providerMode === 'live-frontier' ? `provider=${selected?.provider} model=${selected?.model} runtime=${snapshot.config.agents?.defaults?.agentRuntime?.id} fallback=${snapshot.config.agents?.defaults?.agentRuntime?.fallback}` : `mock mode: parsed ${scenario.id}`"

detailsExpr: "env.providerMode === 'live-frontier' ? `provider=${selected?.provider} model=${selected?.model} runtime=${snapshot.config.agents?.defaults?.agentRuntime?.id}` : `mock mode: parsed ${scenario.id}`"

- name: builds the medium game artifact

actions:

- if:

requiredProvider: openai

requiredModel: gpt-5.5

harnessRuntime: pi

harnessFallback: pi

artifactFile: star-garden-defenders-pi.html

gameTitle: Star Garden Defenders

minBytes: 5000

agentRuntime:

id:

expr: config.harnessRuntime

fallback:

expr: config.harnessFallback

- call: waitForGatewayHealthy

args:

- ref: env

defaults: {

...cfg.agents?.defaults,

model: { primary: modelRef, fallbacks: [] },

agentRuntime: { id: "codex", fallback: "none" },

agentRuntime: { id: "codex" },

workspace: path.join(state, "workspace"),

skipBootstrap: true,

timeoutSeconds: 420,

ownerOnlyToolAllowlist: params.ownerOnlyToolAllowlist,

disableMessageTool: params.disableMessageTool,

forceMessageTool: params.forceMessageTool,

enableHeartbeatTool: params.enableHeartbeatTool,

forceHeartbeatTool: params.forceHeartbeatTool,

requireExplicitMessageTarget: params.requireExplicitMessageTarget,

internalEvents: params.internalEvents,

bootstrapPromptWarningSignaturesSeen,

params.requireExplicitMessageTarget ?? isSubagentSessionKey(params.sessionKey),

disableMessageTool: params.disableMessageTool,

forceMessageTool: params.forceMessageTool,

enableHeartbeatTool: params.enableHeartbeatTool,

forceHeartbeatTool: params.forceHeartbeatTool,

authProfileStore: params.authProfileStore,

recordToolPrepStage: (name) => corePluginToolStages.mark(name),

onYield: (message) => {

promptMode?: PromptMode;

/** Keep the message tool available even when a narrow profile would omit it. */

forceMessageTool?: boolean;

/** Include the heartbeat response tool for structured heartbeat outcomes. */

enableHeartbeatTool?: boolean;

/** Keep the heartbeat response tool available even when a narrow profile would omit it. */

forceHeartbeatTool?: boolean;

/** Allow runtime plugins for this run to late-bind the gateway subagent. */

allowGatewaySubagentBinding?: boolean;

sessionFile: string;

suppressToolErrorWarnings?: boolean;

/** If true, run the model without OpenClaw tools for this turn. */

disableTools?: boolean;

/** If true, include the heartbeat response tool for structured heartbeat outcomes. */

enableHeartbeatTool?: boolean;

/** If true, keep the heartbeat response tool available even under narrow tool profiles. */

forceHeartbeatTool?: boolean;

/**

* If true, dispatch skips default tool/progress text messages and expects the

* channel to surface progress via its own streaming/edit UX.