← Releases

id 20260721-1 · 2026-07-21 · Kernel v0.18.0 · TUI/Portal v0.11.5

Kernel v0.18.0 · TUI/Portal v0.11.5

LingTai 0.18.0 / 0.11.5: a more resilient runtime and a verified Windows install path

This coordinated release focuses on runtime resilience and a verifiable Windows distribution path: native Windows kernel adapters and process lifecycle support, native multi-account Codex quota/epoch handling, Outlook OAuth2 IMAP, lossless Telegram inbound updates with task-card self-healing, and a PowerShell-validated Windows AMD64 install path that sits alongside the existing source and Homebrew builds.

Upgrade / runtime

Source builds and Homebrew remain supported install paths for TUI/Portal v0.11.5. This release additionally adds one bounded, verifiable Windows path: a native lingtai-<tag>-windows-amd64.zip with a .sha256 sidecar and lingtai-bundle-manifest.json, installed via install.ps1 after it validates the exact tag, archive, checksum, bundle pin, and pinned kernel wheel. This exception is scoped to that one verified release asset and is not a claim of general Windows binary support. Kernel v0.18.0 remains the runtime package source used by LingTai-managed environments; existing projects should follow their normal TUI-managed refresh or setup path.

New features and improvements

  1. 01

    Native Windows kernel adapters and process lifecycle

    The kernel now wires native Windows adapters and lifecycle/process support behind contracts and platform selectors, closing a capability gap without leaking platform mechanisms into core contracts.

    • Windows kernel runtime adapters and process handling land across the reviewed capability DAG (src/lingtai/adapters/windows/, src/lingtai/tools/daemon/windows_process.py, PR #988).
    • A dedicated Windows PR workflow (.github/workflows/kernel-windows-pr.yml) checks the platform surface on every change.

    Why it matters:Windows support is now testable and enforced per change, not a manual afterthought.

  2. 02

    Native multi-account Codex pooling and quota handling

    Codex account pooling moves to native multi-account selection with quota visibility, zero-quota exclusion, context-scoped epochs, and service-tier propagation.

    • Accounts with zero quota are skipped automatically instead of being retried (src/lingtai/auth/codex_pool.py, #990).
    • Multi-account selection, epoch binding, and epoch scoping are native and context-aware (src/lingtai/auth/codex_account_source.py, #1003–#1005).
    • Native quota-auth materialization closes out the pooling work (src/lingtai/llm/openai/codex_quota.py, #1006).

    Why it matters:Fewer wasted retries and clearer per-context quota boundaries make multi-account Codex usage more predictable.

  3. 03

    Outlook OAuth2 IMAP and more resilient Telegram updates

    Mail and messaging integrations gain a new OAuth2 IMAP provider and preserve inbound Telegram data through lossless updates and task-card self-healing.

    • Personal Outlook accounts can connect over OAuth2 IMAP, kept minimal and scoped (src/lingtai/mcp_servers/imap/, #991–#992).
    • Telegram inbound Bot API updates are preserved losslessly, and non-deletable task cards recover automatically (src/lingtai/mcp_servers/telegram/updates.py, task_card/, #984, #1000).
    • The daemon completion MCP now survives external-CLI config rehydration (#985), and compact-countdown recovery is enforced (#1007).

    Why it matters:Messaging and mail integrations stay correct and recoverable under real-world failure and reconnection.

  4. 04

    A supported, verifiable Windows install path for TUI/Portal

    TUI/Portal keeps source release and Homebrew source-build support, and adds one bounded native Windows path with an explicit verification contract.

    • The tag workflow publishes lingtai-<tag>-windows-amd64.zip, its .sha256 sidecar, and lingtai-bundle-manifest.json (.github/workflows/release.yml, PR #699).
    • install.ps1 validates the exact tag, AMD64 archive, checksum, bundle pin, and pinned kernel wheel before installing (install.ps1, kernel-release.json).
    • PowerShell 5.1 and 7+ contract coverage is recorded in scripts/test-install-ps1.ps1 and windows-installer-smoke.yml.

    Why it matters:Windows users get a verifiable path without weakening the guarantees the source and Homebrew paths already provide.

Contributors

Thanks to everyone whose commits, co-authored changes, PRs, reviews, assignments, or reported/closed issues are represented in this release window.

Validation

Final release validation was run from a clean release worktree at commit Kernel 761d9.