[FEATURE] Add `open-jp.larksuite.com` to outbound HTTP allowlist for cloud routines

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Code cloud routines (RemoteTrigger) cannot make outbound HTTP
requests to
Lark/Larksuite webhook endpoints. Any attempt to POST to these domains is
blocked
with the following error:

> Host not in allowlist: open-jp.larksuite.com

This makes it impossible to use cloud routines for any workflow that
delivers
results to Lark — one of the most widely adopted enterprise messaging
platforms
in Asia-Pacific organizations — without falling back to local execution.

Proposed Solution

Add the following domains to the outbound HTTP allowlist for cloud
routines:

| Domain | Description |
|--------|-------------|
| open-jp.larksuite.com | Lark Japan / APAC region |
| open.larksuite.com | Lark global |
| open.feishu.cn | Feishu (Lark's mainland China counterpart) |

Alternatively, exposing a user-configurable allowlist for trusted
outbound
domains would be a more scalable solution that also covers other popular
destinations (Slack, Microsoft Teams, Discord, custom webhooks, etc.),
without requiring case-by-case additions.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

Automated Notification & Reporting Workflows

A common pattern for Claude Code cloud routines is to:

1. Perform research or data processing on a schedule (e.g., summarizing

news, monitoring metrics)

1. Format the results
2. Deliver them to a team communication channel via webhook

Lark/Larksuite is the standard messaging platform for many organizations,
particularly across Asia-Pacific. Webhook-based integrations are the
primary method for bots and automated workflows to post messages into
channels.

The inability to reach Lark webhook endpoints from cloud routines
effectively
prevents this entire class of "research → summarize → notify" automations
from running in the cloud, forcing them back onto local machines.

Error encountered:
Host not in allowlist: open-jp.larksuite.com

Current workaround: Local execution via a scheduled task,
which introduces a dependency on a specific machine being powered on at all
times.
Cloud routines would be the natural, maintenance-free alternative.

Additional Context

_No response_