Interface Tour

The Project Launcher remains the local index, and every opened repository gets its own project window. This keeps project state and navigation scoped to one repository while letting you work across several repositories at once.

Application settings apply across Desktop. Project settings are stored with or derived from the current repository and only affect that project.

The top of the sidebar identifies the project and launcher group. Shared environments appear next, followed by the primary project surfaces:

• Activity shows signed project events.
• Validation shows global and environment-specific rules and diagnostics.
• Review scans source and configuration hygiene.
• Access manages devices, requests, grants, and automation credentials.
• Settings controls the repository path, environment types, file generation, cleanup, review, and activity.

Use the sidebar control at the top to collapse or expand it when you need more workspace.

Select an environment to show its variables. The table displays the key, a visible or masked value, version, and last-updated time. A missing-keys banner appears when validation requires keys that the environment does not contain.

Select a row to open its detail panel. From there you can edit the value and note, change enabled or commented state, inspect metadata, configure dynamic behavior, and manage validation or annotations supported by the engine.

The magnifying-glass control searches the current surface. Variable filters narrow rows by state or metadata, while Activity and Review expose controls relevant to their own results. Search never changes encrypted project state.

The environment search beside Shared environments helps when a project has many targets. The plus controls beside environments and in the variable toolbar create new records.

Use context menus for variable operations and the environment actions menu for Compare Environments, Pull Local File, Push Local File, and Sync Local File. Preview destructive file operations before confirming them.

Desktop invokes explicit CLI operations behind these controls. A failed action reports the command error without silently switching to a different repository or environment.