Working with Environment context

Choose where to work

An environment is where Elyxis resources and applications are managed and run. An environment owns a list of settings, each with a unique name and configuration entries. All settings contribute entries; entry keys are unique across the environment. Settings are managed within an environment and cannot be selected separately.

For the concepts and setup steps, see Environments, Settings, and Keystores. This guide focuses on using that context during an Assistant conversation.

When your request does not name an Environment, Elyxis uses the Environment already selected in your session context. You do not need to specify it again. If you explicitly name an Environment and that selection is ambiguous, the Assistant asks you to resolve it.

Inspect the current selection

Run:

/context

The CLI shows safe identifiers and display names for selected environments, apps, flows, or capabilities. Use /context --json when you need the same safe metadata in structured form.

Select context through the Assistant

You can name the desired resource in the request:

Use the Beta Testing environment for this session.

If Elyxis proposes retaining that selection as session context, the CLI asks for confirmation. Review the resource name and action before approving.

Resolve ambiguity

When two resources have similar names:

1. ask the Assistant to list the eligible resources;
2. choose the exact displayed name or identifier;
3. verify the selection with /context; and
4. retry the original task in the same session.

Do not guess a production target from a partial name.

Handle missing configuration

A capability can exist without being executable yet. The Assistant may report that a model, endpoint, catalog, credential reference, environment binding, build, or activation is still required.

Provide only information you know. Never paste passwords, access tokens, or private keys into a conversational answer. Ask the Assistant which approved Elyxis resource or key-store entry should satisfy the requirement.

Change or clear context

Ask explicitly when the selected resource should change. Use a fresh session for unrelated work. Clearing conversation memory does not mean a remote Elyxis resource was deleted or modified.