Best possible solution:

Land a narrow typing cleanup fix after restoring the pinned Copilot SDK contract and deciding or validating the shared typing-helper duplicate-stop behavior.

Do we have a high-confidence way to reproduce the issue?

Yes, by source inspection. Current main starts typing in the background while Feishu records removable typingState only after addTypingIndicator resolves, so cleanup can call stop before there is state to remove.

Is this the best way to solve the issue?

No for the current head. The typing-layer fix is plausible, but the branch must drop unrelated Copilot SDK contract drift before maintainers judge the shared cleanup semantics and Feishu proof gap.

Full review comments:

• [P1] Restore Copilot home to baseDirectory — extensions/copilot/src/runtime.ts:368
  The pinned @github/[email protected] option is baseDirectory, and the SDK sets COPILOT_HOME only from that field. Passing copilotHome here leaves OpenClaw's normalized per-agent Copilot home unused, so SDK auth and session state can fall back to the default location.
  Confidence: 0.96
• [P1] Use suppressResumeEvent for resumed SDK sessions — extensions/copilot/harness.ts:271
resumeSession takes suppressResumeEvent, not disableResume, in the pinned SDK. Leaving this field renamed means history compaction resumes can emit the resume event again and reintroduce the side effects this option was suppressing.
  Confidence: 0.94
• [P2] Keep hook fixtures on Date timestamps — extensions/copilot/src/hooks-bridge.test.ts:8
  The SDK hook input contract has timestamp: Date, but this fixture now passes 0. That makes the hook test fixture drift from the SDK-derived handlers and can fail type-checking instead of proving the real hook shape.
  Confidence: 0.9

Overall correctness: patch is incorrect
Overall confidence: 0.96

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 24dba4b44a5b.

Label justifications:

• P2: This is a bounded user-visible channel cleanup regression fix with limited blast radius, not an emergency runtime outage.
• merge-risk: 🚨 compatibility: The PR changes an SDK-exposed typing helper contract and rewrites Copilot SDK option names without updating the pinned dependency.
• merge-risk: 🚨 auth-provider: Passing an unrecognized Copilot home option can make SDK credential state use the default global location instead of OpenClaw's per-agent home.
• merge-risk: 🚨 session-state: The Copilot home and resume flag drift can mis-associate or unexpectedly resume SDK-backed session state during history compaction.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🌊 off-meta tidepool and patch quality is 🧂 unranked krab.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This is a ClawSweeper-authored replacement PR, so the external contributor proof gate does not apply; maintainers still need live Feishu proof or an explicit override before merge.

PR surface:

Source +50, Tests +90. Total +140 across 7 files.

Security concerns:

• [medium] Copilot home may fall back to global state — extensions/copilot/src/runtime.ts:368
  Using copilotHome instead of the pinned SDK's baseDirectory can leave the runtime without OpenClaw's normalized per-agent Copilot home, so credentials and sessions may use the SDK default location.
  Confidence: 0.9

Acceptance criteria:

• [P1] node scripts/run-vitest.mjs src/channels/typing.test.ts extensions/copilot/src/runtime.test.ts extensions/copilot/harness.test.ts extensions/copilot/src/hooks-bridge.test.ts.
• [P1] pnpm check:test-types.
• [P1] pnpm lint:extensions:bundled.
• [P1] pnpm check:changed.

What I checked:

• Repository policy read: Root AGENTS.md plus the scoped src/channels and extensions guides were read; the dependency-contract and shared channel SDK boundary guidance affected this review. (AGENTS.md:1, 24dba4b44a5b)
• Current main still backgrounds typing start: onReplyStart starts fireStart in the background and returns after one microtask, while fireStop can close and send stop before that start settles. (src/channels/typing.ts:97, 24dba4b44a5b)
• Feishu persistent state is assigned after async start: Feishu assigns typingState only after addTypingIndicator resolves, and stop returns when typingState is still unset, so a fast cleanup can miss the later persistent reaction. (extensions/feishu/src/reply-dispatcher.ts:219, 24dba4b44a5b)
• Feishu reaction add/remove contract: addTypingIndicator creates the persistent reaction and removeTypingIndicator is a no-op without a reaction id, matching the reported stale-reaction failure mode. (extensions/feishu/src/typing.ts:123, 24dba4b44a5b)
• Typing helper is SDK-exposed: createTypingCallbacks is re-exported through the plugin SDK channel outbound surface, so changed duplicate-stop behavior can affect third-party channel users, not only Feishu internals. (src/plugin-sdk/channel-outbound.ts:30, 24dba4b44a5b)
• PR head changes shared cleanup semantics: The PR head tracks pending starts and allows sendStop(true) after a raced successful start settles, which addresses the Feishu race but changes the shared helper contract. (src/channels/typing.ts:66, cdcce22c1f29)

Likely related people:

• obviyus: Authored the merged change that kept typing indicators off the reply critical path, which made the cleanup-before-start-settles race possible. (role: introduced behavior under review; confidence: high; commits: 45b86450795d; files: src/channels/typing.ts, src/channels/typing.test.ts, src/auto-reply/reply/typing.ts)
• ramrajprabu: Authored the merged Copilot runtime PR that introduced the runtime, harness, hooks bridge, and pinned SDK integration whose option contracts this PR changes. (role: Copilot runtime feature contributor; confidence: high; commits: f3cfd752d330; files: extensions/copilot/src/runtime.ts, extensions/copilot/harness.ts, extensions/copilot/src/hooks-bridge.ts)
• arkyu2077: Authored the merged Feishu typing keepalive change documenting that Feishu reactions persist until explicitly removed, directly adjacent to this cleanup race. (role: Feishu typing lifecycle contributor; confidence: medium; commits: 46df7e242138; files: extensions/feishu/src/reply-dispatcher.ts, extensions/feishu/src/typing.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.