Claude Code Remote: add create_environment tool so environments can be provisioned without leaving Claude Code

Summary

Currently, setting up a persistent scheduled trigger (via create_trigger) requires a CCR environment — but there's no create_environment tool available in Claude Code. Users have to leave Claude Code entirely, go to claude.ai/settings, and create the environment through the UI before returning to wire up the trigger.

Expected behavior

A create_environment tool (or equivalent) that allows provisioning a CCR environment directly from within a Claude Code session, without needing to navigate to the settings UI.

Why it matters

The full scheduling workflow (create_trigger → runs on schedule → fires into a persistent environment) is a first-class Claude Code feature, but it's currently gated behind a manual out-of-band step. Users who discover create_trigger through Claude Code have no in-session path to complete the setup.

Proposed addition

A create_environment tool that accepts at minimum:

• Environment name
• Region (optional, with a sensible default)

Returns an environment_id that can be passed directly to create_trigger.