UI, CLI & Terraform

UI

Use the workspace UI for guided configuration, task assignment, progress inspection, approvals, and review. Create model and tool connections, assign their owners, configure an agent, then create a task with an outcome and acceptance criteria.

1. Choose the workspace and confirm your role.
2. Add the model and tool connections your agent needs.
3. Assign owners and configure policies and access scope.
4. Create the agent and give it a task.
5. Review session evidence and accept or return the result.

CLI

Use the Entergenie CLI for terminal-based task operations and scripts. Install the CLI distributed for your workspace, authenticate as an authorized Principal, and select the workspace before running commands. Use a separate scoped automation identity for CI rather than a personal credential.

Create the task with an explicit owner and acceptance criteria, retain its identifier, inspect status across sessions, and fetch the result for review. Keep machine-readable output separate from diagnostic logs and check command exit codes in automation.

Reuse a task identifier when inspecting or reconnecting to work. Retrying a command that creates a task can create duplicate work; use an idempotency mechanism where the command supports it.

Terraform

Use Terraform for platform configuration managed as code. Start from your team’s Entergenie provider configuration with the provider source and version pinned. Authenticate the provider through the approved process, keeping raw credentials out of configuration files and version control.

Run the following script from that Terraform project. It checks formatting, installs providers, validates configuration, and saves a plan for review. It does not apply changes automatically.

#!/usr/bin/env bash
set -euo pipefail
# Run inside your configured Entergenie Terraform project.
# Authenticate the provider using your organization's approved process.
# Keep provider credentials outside .tf files and version control.
terraform fmt -check -recursive
terraform init -input=false
terraform validate
terraform plan -input=false -out=entergenie.tfplan
terraform show -no-color entergenie.tfplan
# After reviewing the exact saved plan, apply it explicitly:
# terraform apply entergenie.tfplan

After review, apply that exact saved plan withterraform apply entergenie.tfplan. Commit the provider lockfile; protect state and saved plans as sensitive data. Use secret references rather than raw provider or model keys in managed configuration.

Assign an owner to Terraform-managed resources and route their changes through version control. Review drift with a new plan after out-of-band changes. Keep task execution and human approvals in the UI or CLI rather than using infrastructure changes to simulate an agent session.

See the Terraform plan reference.

Same authority in every interface

Changing interfaces never expands authority. UI actions, CLI commands, and Terraform operations must respect the Principal’s permissions and the policies that apply to the resource. Delegation grants, session isolation, and approvals remain explicit.