Environment profile

The environment profile selects which terminal image variant Buddy uses when it investigates through the terminal. Variants differ by which infrastructure and cloud tooling is pre-installed, so that Buddy starts an investigation with the right command-line tools already available.

How the profile is chosen

Today the environment profile is fully automatic — Organizations cannot set it manually.

• Default: a new Organization starts on simple.
• Self-learning: the profile is detected automatically from your environment — the services your alerts reference and, over time, the infrastructure Buddy observes — and is adjusted for you as evidence accumulates. Until there is enough signal, it stays on simple.

Planned capability: a future release may add an explicit override (for example, per Team). When that ships, an explicitly set value will take priority over auto-detection, and this document will be updated. The section below describes the trade-offs of that planned override so you can decide whether to use it when it becomes available — it does not describe anything you can do today.

Choosing to override (planned capability — not available today)

When the explicit override ships, setting the profile will be a trade-off between a known starting premise and staying in sync with reality.

Reasons to set it (useful early, before there is learning data):

• Before auto-detection has accumulated any signal, there is nothing for it to infer from. If you already know your environment, setting the correct variant lets Buddy begin every investigation on the right premise — the right tooling is present and Buddy can assume the correct environment from the first turn, instead of spending an investigation working it out. A correct explicit value makes early investigations more efficient. (This is about correctness of the starting premise, not about picking a lighter variant.)

Reasons to leave it on auto (often better once learning data exists):

• Once enough signal has accumulated, auto-detection usually tracks reality more faithfully than a fixed choice.
• Because an explicit value would take priority, it keeps winning even when it no longer matches reality. This matters most when you use more than one cloud provider: a fixed value cannot represent a mixed environment, and a stale setting overrides the up-to-date picture that auto-detection would otherwise follow. Auto-detection adapts to change; a pinned value does not.

Guidance: once the override is available, set an explicit variant early if you already know your environment and want a correct starting premise; prefer leaving it on auto once there is enough history, and especially if your environment spans multiple providers.

Related

• Organization settings — Organization-wide defaults and AI feature controls.
• Team — Teams live inside an Organization; investigation context (including the environment a Team operates) is Team-scoped.