Altifigence CLI#
Install the signed Linux CLI and choose native XLS, CUDA, DDS, or explicitly scoped Cloud operations.
Overview#
Altifigence CLI provides local design engines, Digital Design Studio workspace operations, and explicit connections to Cloud or a configured workspace service. The installation contract described here is for 0.1.9 on Linux x86_64. Check the official download page for release availability; this guide does not announce a release promotion.
Download and Extract#
First verify the archive and public trust material. Authenticate the Ed25519 signature and pinned public-key digest before running any downloaded executable, including its installer. Then follow Install on Linux: alti release install uses embedded release helpers to create the authenticated installation. It needs Linux root access, performs no network access or build, and requires no source checkout.
The payload contains 26 executables: alti, alti-mcp, and 24 engine runners. The installer keeps their contracts, signed catalog, and receipt together. Run the installed PREFIX/bin/alti; copying one binary or making a receipt by hand does not produce a trusted installation.
First Success#
After installation and adding PREFIX/bin to your PATH:
alti version
alti capabilities
alti xls capabilities
alti ide workspace capabilities
CLI First Success includes a small local CPU XLS evaluation and an optional offline job preflight. Neither requires Cloud credentials. Capability discovery reports availability and constraints. Use execution receipts and workload qualification results to confirm that a GPU kernel or a design job ran.
What Is Shipped#
Surface |
Use |
|---|---|
|
Bounded native DSLX/XLS IR checking, evaluation, optimization, RTL generation, and stored results |
|
Install and use a separately pinned Google XLS CPU toolchain for its broader DSLX language support |
|
Device discovery, explicit CPU/CUDA packed RTL execution, bounded Evolve activity, and result verification |
|
Local engine operations with their own input and analysis limits |
|
Project creation, saved files, durable authoring plans, settings, Git, and local search |
|
Browser PKCE login, verified identity, scoped Cloud workspace operations, saved-source search, and terminal attachment |
|
Typed operations against an explicitly configured legacy DDS HTTP service, including search and CAS replacement |
|
Bounded evaluation using the installed, signed Tcl runtime component |
|
Action-manifest discovery and offline job/source preflight |
alti-mcp and alti mcp serve provide stdio MCP. The default customer mode dispatches through the Cloud client; ALTI_MCP_MODE=local-xls selects a separate fixed XLS tool set without Cloud dispatch. Local process transport alone does not imply local execution in customer mode.
Current Limits#
Native XLS evaluates a bounded 1–64-bit subset. The Google XLS path supports imports, parametrics, aggregate types, and procs according to the selected upstream tool; optional IR/proc evaluators need a separately verified bundle. Neither path promises every DSLX design can be synthesized or run on CUDA.
CUDA is explicit for XLS and packed RTL. Evolve uses CUDA for bounded combinational activity diagnostics; candidate generation, correctness checks, and search objectives remain CPU work. Icarus is required for that workflow. No speedup or universal GPU/driver qualification is promised.
Native DDS mutations and the installer are Linux operations. A browser pane, unsaved editor buffer, Cloud workspace, and local directory are distinct contexts. Use each backend’s own identity, permissions, and conflict evidence.
ide cloud login is the supported native Cloud sign-in path. The older top-level login and whoami commands still refuse unverified identity. Account membership and service permissions remain server decisions; installing the CLI does not grant a desktop licence or Cloud entitlement.
Continue with Command Reference, Command Surface, Engine Commands, and Job and Cloud Commands.