Altifigence CLI#

Download the signed CLI Preview, run it from the extracted directory, and inspect its commands.

Overview#

Altifigence CLI is a signed Preview archive for Linux x86_64. Extract it into a new directory and run it in place; it is not a system package.

Download and Extract#

Use the official Downloads page and complete download verification before extraction. Follow Install on Linux for the current archive commands.

The archive contains 21 executables plus its contracts, release metadata, checksums, software inventory, and notices. Keep the extracted directory as one versioned unit. Copying only alti can separate it from the engine binaries and contracts it was released with.

First Success#

From the extracted directory, inspect the embedded customer action manifest:

Bash
./alti commands

Then follow CLI First Success to validate one CPU RTL job envelope and one owner-only source file entirely offline. The result is a client-preflight receipt with submitted: false and server_authority_verified: false; it is not execution evidence.

The capability command expects an installed receipt and PREFIX/bin layout that the public flat archive does not contain. It therefore cannot produce a successful trusted capability report from this distribution. Do not rearrange the archive or fabricate a receipt to work around it. That limitation belongs to alti capabilities and alti tcl evaluate specifically; it is not a statement about the rest of the binary.

What Is Shipped#

  • alti provides the 25-action customer manifest and the explicitly bounded offline job preflight documented above.

  • the action manifest marks 22 actions as execution-capable at the contract level and three fully named actions as plan-only;

  • the remaining 19 executables are engine binaries, such as alti-rtlc, alti-rtl, and alti-cx. alti resolves an engine as a sibling of its own executable, falls back to PATH, and runs it without a shell. This is why the extracted directory has to stay together.

  • alti-mcp is a packaged stdio MCP process. Its tool calls use the CLI Cloud client; “local” describes the process and transport, not local execution or a local data guarantee. alti mcp serve starts the same stdio server from the main binary.

Engine-backed commands run on your machine by default: --runner defaults to local. Only rtl compile, rtl synthesize, physical run, px analyze, and isa run accept --runner cloud or --runner private, and with those values they print a [scaffold] dispatch line instead of running anything. Executing an engine is a local run. Command Reference explains the exit status and receipt written by each command.

The action manifest and local capability report answer different questions. Read Action and Capability Contract before automating either surface.

Current Limits#

  • There is no system installer or automatic updater for the CLI Preview.

  • Interactive CLI login and verified whoami are unavailable; both exit 4.

  • alti capabilities and alti tcl evaluate require the signed installed layout and cannot succeed from the flat extracted archive.

  • Local engine execution works; review its inputs, diagnostics, and output before using the result in a project.

  • A general Public API and complete remote execution workflows are not available.

  • The local stdio MCP process requires separate environment configuration and dispatches through the Cloud client; it does not replace the hosted endpoint.

  • An execution-marked action can still require a server and account permission.

For exact discovery commands, continue to Command Reference. For the full argument surface — every namespace, subcommand, flag, value enum, and environment variable the binary accepts — start at Command Surface, which indexes CLI Engine Commands and CLI Job and Cloud Commands.