Summary

• Problem: LINE plugin's startAccount resolves immediately after monitorLineProvider returns, causing the channel supervisor to treat the provider as "exited" and triggering an auto-restart loop (up to 10 attempts).
• Why it matters: LINE webhook providers go into a restart storm, flooding logs and potentially missing messages.
• What changed:
  • extensions/line/src/channel.ts — after monitorLineProvider returns, await a Promise that resolves when ctx.abortSignal fires, keeping startAccount pending for the full lifecycle.
  • extensions/line/src/channel.startup.test.ts — updated existing test to handle abort lifecycle; added "stays pending until abort signal fires" and "resolves immediately when abortSignal is already aborted" tests.
• What did NOT change: Webhook registration; LINE message handling; other channel plugins.

Change Type (select all)

• Bug fix
• Feature
• Refactor
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes [Bug]: LINE plugin: provider exits immediately after startup (auto-restart loop) #26478

User-visible / Behavior Changes

• LINE webhook provider no longer exits immediately after startup; stays alive until explicitly stopped.

Security Impact (required)

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No
• Command/tool execution surface changed? No
• Data access scope changed? No

Repro + Verification

Environment

• OS: Any
• Runtime: Node.js
• Integration/channel: LINE

Steps

1. Configure LINE webhook channel
2. Start OpenClaw
3. Observe provider lifecycle

Expected

• Provider stays running after webhook registration.

Actual

• Before fix: Provider exits immediately, supervisor restarts it up to 10 times.
• After fix: Provider stays pending until abort signal.

Evidence

3 tests pass in channel.startup.test.ts including 2 new lifecycle tests.

Human Verification (required)

• Verified scenarios: Normal startup with abort; pre-aborted signal; pending until abort.
• Edge cases checked: Already-aborted signal resolves immediately.
• What I did not verify: Live LINE webhook with actual LINE API.

Compatibility / Migration

• Backward compatible? Yes
• Config/env changes? No
• Migration needed? No

Failure Recovery (if this breaks)

• How to disable/revert: Revert the commit.
• Files/config to restore: extensions/line/src/channel.ts
• Known bad symptoms: If the abort signal never fires, the provider would hang indefinitely (but abort is always fired on shutdown).

Risks and Mitigations

None — the abort signal is managed by the channel supervisor and always fires on clean shutdown.

Greptile Summary

Fixed LINE webhook provider restart loop by keeping startAccount pending until abort signal fires. Previously, startAccount resolved immediately after monitorLineProvider returned, causing the channel supervisor to treat it as exited and trigger up to 10 auto-restart attempts.

• Changed monitorLineProvider call from direct return to awaited assignment, then added Promise that waits for ctx.abortSignal
• Properly handles already-aborted signal edge case
• Added comprehensive tests covering normal lifecycle, pending-until-abort behavior, and pre-aborted signal handling

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix directly addresses a documented restart loop issue with a simple, well-tested solution. The implementation correctly handles the abort signal lifecycle including edge cases, matches the expected pattern from the channel supervisor code, and includes comprehensive test coverage. The change is isolated to the LINE plugin and cannot affect other channels.
• No files require special attention

_{Last reviewed commit: 57b3c7c}