Repository navigation
MiniCon 0.2.25
MiniCon is a standalone terminal in a single executable — no installer, no
bundled language runtime, and no Visual C++ redistributable. It uses only the
operating system's own desktop libraries.
What changed
Each release's changes are recorded once, in the repository's release history —
one document per version, naming the exact source, the workflow run ids and the
evidence:
https://github.com/partnernetsoftware/minicon/tree/main/prd/archive
What the product does today, and how to drive it, are in the
README and in
minicon --help.
Downloads
Harness/provider-pool is experimental and evolving. Complete real multi-account
and external-client acceptance is pending; availability depends on the provider
and account. See the current Harness scope.
Pick your platform and run the file — there is no installer.
| Platform | Download |
|---|---|
| Windows x64 | minicon-0.2.25-windows-x86_64.zip |
| Windows ARM64 | minicon-0.2.25-windows-arm64.zip |
| macOS (Apple Silicon + Intel) | minicon-0.2.25-macos-universal.dmg |
| Linux x64 | minicon-0.2.25-linux-x86_64.tar.gz |
| Linux ARM64 | minicon-0.2.25-linux-arm64.tar.gz |
| Advanced: one signed launcher, all platforms | minicon.com |
The macOS .dmg contains a signed, notarized, stapled MiniCon.app
(universal — Apple Silicon and Intel). A .tar.gz of the bare signed binary is
also provided for command-line-only use. Every archive has a SHA-256 beside it.
Linux archives use the distribution runtime libraries libxkbcommon0 and
libwayland-client0 (no -dev packages required) and bundle the runtime-only
X11 bridge libxkbcommon-x11.so.0, so slim X11 systems start MiniCon without
extra packages.
Windows executables and minicon.com are Authenticode-signed, and the macOS
build is Developer ID-signed and Apple-notarized, as PARTNERNET SOFTWARE PTY LTD
with an RFC 3161 timestamp. The policy, the publisher facts and the verification
commands are in
CODE_SIGNING_POLICY.md.
Verify a download before running it:
sha256sum -c minicon-0.2.25-linux-x86_64.tar.gz.sha256
If a build will not start
The in-place update keeps the copy it replaces, so an update that leaves you
with something that will not launch is undone by hand — no installer, no
uninstall step:
mv minicon.backup minicon # Linux and macOS CLI
On Windows the same file is minicon.exe.backup, next to minicon.exe. If the
backup is gone too, download the previous release's archive again: the file
inside is identical to the one you had, and there is nothing else on the machine
to clean up. A Linux binary that arrived without its executable bit is
chmod +x minicon.
Older Windows
Windows Server 2016 and Windows 10 version 1607 are supported. Those builds
have no pseudoconsole, so MiniCon hosts the shell in a hidden console instead.
See Running on old Windows.
Reporting a problem
Run minicon --status and include the output. It reports the build, the
console backend this machine selected and why, the font the system resolved to
with its measured cell width, and where MiniCon writes when something fails —
without opening a window.
MIT OR Apache-2.0.