CLI

The AeThex CLI documentation currently defines the intended operational contract. Treat commands not present in the installed CLI as planned rather than shipped.

Expected workflows

A stable AeThex CLI should eventually support:

• Identity and session inspection.
• Project initialization.
• Configuration validation.
• Build and deployment workflows.
• API and service health checks.
• Documentation and OpenAPI retrieval.

Verify before use

Before following a command example:

aethex --version
aethex --help

If the command is unavailable, use the documented HTTP or web workflow instead. Do not install an unverified package solely because it uses the AeThex name.

Command design requirements

• Non-interactive mode for automation.
• Structured output such as JSON.
• Explicit confirmation for destructive actions.
• No credentials in process arguments when a safer input method exists.
• Useful exit codes.
• Dry-run behavior for deployment and mutation commands.

Current alternatives

• Use API Quickstart for direct API access.
• Use OpenAPI Reference to generate a client.
• Use the appropriate public service from Service Directory.

Related documentation

• SDKs
• API Reference
• Security
• Projects