Repository navigation
Releases
Terminux 0.1.1
Terminux 0.1.1
English
A documentation release: English versions of the README and of the bundle's install guide. This page can be read on its own; the full user documentation site is not online yet.
License
Terminux is released under the PolyForm Shield License 1.0.0. It is source-available software and not open source as defined by the OSI.
Any organization may use it free of charge, including for internal business and customer projects, but may not use it to provide a product or service that competes with Terminux.
See LICENSE.md for the terms and THIRD_PARTY_NOTICES.md for third-party licenses. The license texts and sources of the Python and the dependencies inside the portable bundle are in its third_party/ directory (including the Sleepycat License of Berkeley DB, used by CPython's _dbm module; Terminux itself does not use it).
What changed in this version
README.mdand the bundle'sREADME-INSTALL.mdare now bilingual: English first, Traditional Chinese second, with language links at the top. The English text is a section-by-section translation; no claim was added.README-INSTALL.md(English section) states explicitly that~/.local/binonly receivesterminuxandterminux-qt-check, and that the other commands live in~/.local/opt/terminux/current/venv/bin/.- Version string 0.1.1. No change to the Python package other than the version; no change to the GUI or DQE Viewer sources.
Release contents
| Item | Value |
|---|---|
| Source commit | e6e41705f8fc5578092e21f7e4200f7ba88540b4 |
| Public file inventory (634 files) sha256 | 68a22d9d87a4c184a7d15c83ebf26042b011f2e3bb7b12a290b74035222a0695 |
| Python wheel | terminux_engine-0.1.1-py3-none-any.whl |
| Wheel sha256 | fd8c28da2fc673baf478f1b12c4a21d1287f8b27f6a679ca77f02f82558d801e |
| Linux x86_64 portable bundle | terminux-0.1.1-linux-x86_64.tar.gz (116,595,642 bytes) |
| Bundle sha256 | 2170775b8158d9b995361bbce5a1294f5439ed3bad12a7a7312eb5c5a3a434f7 |
Two ways to install: build from source (wheel plus CMake), or use the portable bundle. The bundle contains Python 3.12.14 (python-build-standalone), the same wheel as above with its dependencies, the prebuilt GUI and DQE Viewer, and the third-party license texts (third_party/); Qt is not included. SHA256SUMS lists both the wheel and the bundle.
Installation
Requirements:
- Python 3.12 or later and
uv; - for the GUI: CMake 3.16 or later, a C++17 compiler, and the Desktop gcc 64-bit default components of Qt 6.7 or later (no additional modules).
uv venv --python 3.12 .venv
source .venv/bin/activate
uv pip install terminux_engine-0.1.1-py3-none-any.whl # or from source: uv pip install './engine'
cmake -S . -B build -DCMAKE_PREFIX_PATH=/path/to/Qt/6.7.3/gcc_64 -DTERMINUX_BUILD_TESTS=OFF
cmake --build build
cmake --install build --prefix "$VIRTUAL_ENV" # GUI and Python share one prefix- After installation you have
$VIRTUAL_ENV/bin/terminux(GUI) and$VIRTUAL_ENV/bin/dqe_viewer(DQE Viewer) with the Qt runtime they need. - The DQE Viewer is started locally by the GUI or CLI; the GUI defaults to the
dqe_viewernext to its own executable, andTERMINUX_DQE_VIEWER_BINoverrides it.
Portable bundle (Linux x86_64):
- Requirements: x86_64; glibc 2.34 or later and a system libstdc++ providing
GLIBCXX_3.4.29(Ubuntu 24.04, RHEL/Rocky/AlmaLinux 9, CentOS Stream 9); a Qt 6.7+ Desktop gcc 64-bit SDK you installed yourself; no root; no network during installation.
sha256sum -c --ignore-missing SHA256SUMS
tar -xzf terminux-0.1.1-linux-x86_64.tar.gz
cd terminux-0.1.1
./install.sh --qt-dir /path/to/Qt/6.7.3/gcc_64- Installs into
~/.local/opt/terminux/0.1.1and pointscurrentat it after the Qt check passes.~/.local/binonly receives two entries:terminux(starts the GUI) andterminux-qt-check. - The other commands (
terminux-orfs-run,terminux-orfs-report,terminux-launch,terminux-daemon, …) live in~/.local/opt/terminux/current/venv/bin/; the installer does not add that directory toPATH. To type them directly in a terminal — including Terminux's built-in terminal — add the directory toPATHyourself. - Required system libraries, removal and first launch are described in the bundle's
README-INSTALL.md.
Configuration
Credentials:
~/.terminux/credentials.jsonwith mode0600, otherwise the whole file is ignored;TERMINUX_CREDENTIALS_FILEselects another location.- Supported names:
TERMINUX_GEMINI_API_KEY,TERMINUX_OPENAI_API_KEY,TERMINUX_OPENAI_BASE_URL. - Environment variables of the same names also work, but the credentials file wins.
LLM backend: selected with TERMINUX_LLM_BACKEND; there is no default, and without it no data is sent to any LLM provider.
| backend | Notes |
|---|---|
openai_compatible |
DeepSeek and other OpenAI-compatible services; the Agent (@@) is available. Verified in this release with DeepSeek's default model deepseek-chat |
gemini |
Agent available (not verified with the public artifacts of this release) |
llama_cpp |
Local GGUF; basic Q&A only, no Agent capability (not verified with the public artifacts of this release) |
- When the credentials file also contains
TERMINUX_GEMINI_API_KEY, search-index embeddings go to Gemini;TERMINUX_EMBEDDING_BACKEND=noopturns that off. - What each feature sends is listed in
README.md, section "Data sent to the LLM provider".
Running ORFS (terminux-orfs-run)
ORFS runs directly on the host under your own account — no Docker, container, sudo or root. The host needs OpenROAD-flow-scripts, OpenROAD, Yosys and KLayout.
terminux-orfs-run --orfs-repo-root /path/to/OpenROAD-flow-scripts \
--work-home ~/orfs-runs/my-run --design gcd --platform nangate45 --variant my-run \
--design-config ./designs/nangate45/gcd/config.mk \
--ledger-db ~/orfs-runs/my-run-ledger.sqlite --receipt-out ~/orfs-runs/my-run-receipt.json-
The tool environment comes from
--env-script(default<orfs-repo-root>/env.sh); apart fromHOME,LANGandPATH, your shell environment is not inherited.--make-executable,--openroad-exeand--yosys-exeaccept absolute paths when needed. -
klayoutmust be onPATH, or be added toPATHby--env-script; otherwise the flow stops at the last step with exit code 1, keeping the outputs and DQE records of the earlier stages. -
--design-configmust be a path relative to the ORFSflow/directory. Without write access to the ORFS installation, bring your own--env-script:sourcethe originalenv.sh, thenexportthe variables the config defines with?=(for exampleCORE_UTILIZATION). -
--ledger-dbmust be a path dedicated to this run. -
The receipt is written to the current user's EventStore by default, so the daemon and
@@can find the run;--no-receiptskips it,--receipt-storewrites to the given EventStore. -
Exit codes:
exit code Meaning 0 Succeeded and the receipt was written 1 Failed 2 Argument or environment error (including running as root, or --work-homenot owned by you)3 Succeeded but the receipt was not written 130/143 Ctrl-C/SIGTERM received -
Report:
terminux-orfs-report --receipt <receipt.json> --run-id <run_id> --attempt 1prints the finish report verified against the receipt and the artifact manifest.
Using AI (@@)
In the terminal of the Terminux window, type @@ followed by your question; the answer appears in the Notification Bar. You can also select text in the terminal and right-click → Ask AI about this.
- The AI can only query recorded execution evidence (receipts, artifact manifests, DQE results); it cannot read your files or run shell commands, and never approves or performs any action on your behalf.
- To ask about one ORFS run: bind it with
@@/bind-run <absolute path of the receipt>, then ask; afterwards verify with@@open DQE Viewerandterminux-orfs-report./bind-runrequires the administrator to enable Profile mode (Profile file, outbound policy file and audit setting); steps and examples are inREADME.md, section "Using AI (@@)". - Without a bound run and without text attached to the question, the AI states that it has no evidence to query and gives only general information or asks you to bind a run first.
Capabilities verified with the public artifacts
Verification below was carried out on 0.1.0 (2026-11-10) and is carried over: the only differences from 0.1.0 are the two documents and the version string. For 0.1.1 the export gates, the wheel audit, the clean install, the ABI check and the isolated installation of the bundle were run again; the GUI-driven Tutorial 02 walkthrough and the full test suites were not repeated.
The Tutorial 02 (S01–S07) operator flow was completed in an isolated environment with the public artifacts, plus one earlier RPC-level verification. Environment: Ubuntu 24.04 x86_64, Python 3.12, Qt 6.7.3; ORFS commit be0dca0b1fd41df54792b3012350cd52bccd99bb, OpenROAD 26Q3-1510-g6cb3f2b704, Yosys 0.68+post, KLayout 0.28.16; LLM: DeepSeek deepseek-chat (Profile mode, outbound policy structural_c2). The package contents of the wheel above are identical, file by file, to the packages installed during those verifications; the GUI and DQE Viewer were built from the same source.
| Capability | What was verified |
|---|---|
| Installation (source) | Offline installation of the wheel and its dependencies; CMake build and installation of the GUI and DQE Viewer; the installed executables use only the Qt inside the installation prefix |
| Installation (portable bundle) | In an isolated HOME, following README-INSTALL.md: sha256 check, extraction, ./install.sh --qt-dir … --yes succeeds and switches current; terminux-qt-check passes; terminux --version, ... |
Terminux 0.1.0
Terminux 0.1.0
English
The first public release of Terminux. This page can be read on its own; the full user documentation site is not online yet.
License
Terminux is released under the PolyForm Shield License 1.0.0. It is source-available software and not open source as defined by the OSI.
Any organization may use it free of charge, including for internal business and customer projects, but may not use it to provide a product or service that competes with Terminux.
See LICENSE.md for the terms and THIRD_PARTY_NOTICES.md for third-party licenses. The license texts and sources of the Python and the dependencies inside the portable bundle are in its third_party/ directory (including the Sleepycat License of Berkeley DB, used by CPython's _dbm module; Terminux itself does not use it).
Release contents
| Item | Value |
|---|---|
| Source commit | 7f8cc1d5956b2d56d7259fa53bcebdcf400d0908 |
| Public file inventory (634 files) sha256 | 38ec0f57005c867cb48453622e7e16dcb3bf7b94024050bf06a7241b98bb0e3f |
| Python wheel | terminux_engine-0.1.0-py3-none-any.whl |
| Wheel sha256 | 74446fc692d6ed72aef39d31ed07e6f7e449c3f49a381962ad2b9fee3a3e4390 |
| Linux x86_64 portable bundle | terminux-0.1.0-linux-x86_64.tar.gz (116,592,476 bytes) |
| Bundle sha256 | fddce8d6c854a69d96b73c0cc7a19ce7365b42e6ba487d229df1c1a20edc9ac6 |
Two ways to install: build from source (wheel plus CMake), or use the portable bundle. The bundle contains Python 3.12.14 (python-build-standalone), the same wheel as above with its dependencies, the prebuilt GUI and DQE Viewer, and the third-party license texts (third_party/); Qt is not included. SHA256SUMS lists both the wheel and the bundle.
Installation
Requirements:
- Python 3.12 or later and
uv; - for the GUI: CMake 3.16 or later, a C++17 compiler, and the Desktop gcc 64-bit default components of Qt 6.7 or later (no additional modules).
uv venv --python 3.12 .venv
source .venv/bin/activate
uv pip install terminux_engine-0.1.0-py3-none-any.whl # or from source: uv pip install './engine'
cmake -S . -B build -DCMAKE_PREFIX_PATH=/path/to/Qt/6.7.3/gcc_64 -DTERMINUX_BUILD_TESTS=OFF
cmake --build build
cmake --install build --prefix "$VIRTUAL_ENV" # GUI and Python share one prefix- After installation you have
$VIRTUAL_ENV/bin/terminux(GUI) and$VIRTUAL_ENV/bin/dqe_viewer(DQE Viewer) with the Qt runtime they need. - The DQE Viewer is started locally by the GUI or CLI; the GUI defaults to the
dqe_viewernext to its own executable, andTERMINUX_DQE_VIEWER_BINoverrides it.
Portable bundle (Linux x86_64):
- Requirements: x86_64; glibc 2.34 or later and a system libstdc++ providing
GLIBCXX_3.4.29(Ubuntu 24.04, RHEL/Rocky/AlmaLinux 9, CentOS Stream 9); a Qt 6.7+ Desktop gcc 64-bit SDK you installed yourself; no root; no network during installation.
sha256sum -c --ignore-missing SHA256SUMS
tar -xzf terminux-0.1.0-linux-x86_64.tar.gz
cd terminux-0.1.0
./install.sh --qt-dir /path/to/Qt/6.7.3/gcc_64- Installs into
~/.local/opt/terminux/0.1.0and pointscurrentat it after the Qt check passes.~/.local/binonly receives two entries:terminux(starts the GUI) andterminux-qt-check. - The other commands (
terminux-orfs-run,terminux-orfs-report,terminux-launch,terminux-daemon, …) live in~/.local/opt/terminux/current/venv/bin/; the installer does not add that directory toPATH. To type them directly in a terminal — including Terminux's built-in terminal — add the directory toPATHyourself. - Required system libraries, removal and first launch are described in the bundle's
README-INSTALL.md.
Configuration
Credentials:
~/.terminux/credentials.jsonwith mode0600, otherwise the whole file is ignored;TERMINUX_CREDENTIALS_FILEselects another location.- Supported names:
TERMINUX_GEMINI_API_KEY,TERMINUX_OPENAI_API_KEY,TERMINUX_OPENAI_BASE_URL. - Environment variables of the same names also work, but the credentials file wins.
LLM backend: selected with TERMINUX_LLM_BACKEND; there is no default, and without it no data is sent to any LLM provider.
| backend | Notes |
|---|---|
openai_compatible |
DeepSeek and other OpenAI-compatible services; the Agent (@@) is available. Verified in this release with DeepSeek's default model deepseek-chat |
gemini |
Agent available (not verified with the public artifacts of this release) |
llama_cpp |
Local GGUF; basic Q&A only, no Agent capability (not verified with the public artifacts of this release) |
- When the credentials file also contains
TERMINUX_GEMINI_API_KEY, search-index embeddings go to Gemini;TERMINUX_EMBEDDING_BACKEND=noopturns that off. - What each feature sends is listed in
README.md, section "Data sent to the LLM provider".
Running ORFS (terminux-orfs-run)
ORFS runs directly on the host under your own account — no Docker, container, sudo or root. The host needs OpenROAD-flow-scripts, OpenROAD, Yosys and KLayout.
terminux-orfs-run --orfs-repo-root /path/to/OpenROAD-flow-scripts \
--work-home ~/orfs-runs/my-run --design gcd --platform nangate45 --variant my-run \
--design-config ./designs/nangate45/gcd/config.mk \
--ledger-db ~/orfs-runs/my-run-ledger.sqlite --receipt-out ~/orfs-runs/my-run-receipt.json-
The tool environment comes from
--env-script(default<orfs-repo-root>/env.sh); apart fromHOME,LANGandPATH, your shell environment is not inherited.--make-executable,--openroad-exeand--yosys-exeaccept absolute paths when needed. -
klayoutmust be onPATH, or be added toPATHby--env-script; otherwise the flow stops at the last step with exit code 1, keeping the outputs and DQE records of the earlier stages. -
--design-configmust be a path relative to the ORFSflow/directory. Without write access to the ORFS installation, bring your own--env-script:sourcethe originalenv.sh, thenexportthe variables the config defines with?=(for exampleCORE_UTILIZATION). -
--ledger-dbmust be a path dedicated to this run. -
The receipt is written to the current user's EventStore by default, so the daemon and
@@can find the run;--no-receiptskips it,--receipt-storewrites to the given EventStore. -
Exit codes:
exit code Meaning 0 Succeeded and the receipt was written 1 Failed 2 Argument or environment error (including running as root, or --work-homenot owned by you)3 Succeeded but the receipt was not written 130/143 Ctrl-C/SIGTERM received -
Report:
terminux-orfs-report --receipt <receipt.json> --run-id <run_id> --attempt 1prints the finish report verified against the receipt and the artifact manifest.
Using AI (@@)
In the terminal of the Terminux window, type @@ followed by your question; the answer appears in the Notification Bar. You can also select text in the terminal and right-click → Ask AI about this.
- The AI can only query recorded execution evidence (receipts, artifact manifests, DQE results); it cannot read your files or run shell commands, and never approves or performs any action on your behalf.
- To ask about one ORFS run: bind it with
@@/bind-run <absolute path of the receipt>, then ask; afterwards verify with@@open DQE Viewerandterminux-orfs-report./bind-runrequires the administrator to enable Profile mode (Profile file, outbound policy file and audit setting); steps and examples are inREADME.md, section "Using AI (@@)". - Without a bound run and without text attached to the question, the AI states that it has no evidence to query and gives only general information or asks you to bind a run first.
Capabilities verified with the public artifacts
The Tutorial 02 (S01–S07) operator flow was completed in an isolated environment with the public artifacts, plus one earlier RPC-level verification. Environment: Ubuntu 24.04 x86_64, Python 3.12, Qt 6.7.3; ORFS commit be0dca0b1fd41df54792b3012350cd52bccd99bb, OpenROAD 26Q3-1510-g6cb3f2b704, Yosys 0.68+post, KLayout 0.28.16; LLM: DeepSeek deepseek-chat (Profile mode, outbound policy structural_c2). The package contents of the wheel above are identical, file by file, to the packages installed during those verifications; the GUI and DQE Viewer were built from the same source.
| Capability | What was verified |
|---|---|
| Installation (source) | Offline installation of the wheel and its dependencies; CMake build and installation of the GUI and DQE Viewer; the installed executables use only the Qt inside the installation prefix |
| Installation (portable bundle) | In an isolated HOME, following README-INSTALL.md: sha256 check, extraction, ./install.sh --qt-dir … --yes succeeds and switches current; terminux-qt-check passes; terminux --version, dqe_viewer --version and dqe_viewer --smoke-exit (offscreen) work. The ABI requirements of every ELF file in the bundle stay within glibc 2.34 / GLIBCXX 3.4.29. The GUI and daemon were also started from the same bundle in an isolated HOME and Tutorial 02 S01–S07 was repeated; everything passed |
terminux-launch and the GUI terminal |
Started from the ORFS flow/ directory; ordinary commands run in the GUI's built-in bash |
@@ questions and select text → Ask AI about this |
Question and answer appear in the Notification Bar; without a bound run the AI states that it has no evidence to query |
| ORFS run and receipt | terminux-orfs-run executed nangate45/gcd inside the GUI terminal, exit 0, receipt and DQE summary written; two earlier runs (baseline and candidate) as well |
| Failed run | A run without KLayout ended with exit code 1; receipt, DQE and the daemon's verdict (FAILED) agree |
| Artifact manifest and DQE | The manifest hashes match the receipt; the 14 DQE items are bound to ... |