[FEATURE] binding a default cloud environment per repository

Resolved 💬 2 comments Opened Feb 9, 2026 by AmirGatt Closed Mar 10, 2026

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

When working with multiple repositories (e.g., MICB_FAST and MOCB_SW), each repo may need a different cloud environment with its own environment variables, secrets, and configuration.

Currently, the cloud environment is selected manually per session. There's no way to set a default environment for a specific repository, so I have to remember to pick the right one each time I start a task.

Proposed Solution

Allow configuring a default cloud environment per repository, for example in .claude/settings.json:

{
"remote_environment": "MICB_FAST"
}

This way, when starting a web session for that repo, the correct environment would be selected automatically — while still allowing manual override when needed.

Alternative Solutions

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

I have two repos that share a similar codebase but require different environment variables and configuration. Having to manually select the environment each time is error-prone and easy to forget.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗