← Releases
中文 English

id 20260620-2 · 2026-06-20 · kernel v0.13.0 · TUI/Portal v0.9.3

Kernel v0.13.0 · TUI/Portal v0.9.3

LingTai release day: context hygiene, notification history, and honest backends

A paired kernel and TUI/Portal release that makes long-running agents quieter, more inspectable, and easier to recover: progressive disclosure for large tool results, a dedicated notification tool, mandatory session journals before deliberate molts, persisted notification-block history, Codex header fixes, and operator views with timezone and daemon token context.

Upgrade / runtime

$ brew update && brew upgrade lingtai-ai/lingtai/lingtai-tui

The Homebrew command updates the TUI/Portal surface. The kernel package lingtai v0.13.0 is published on PyPI as the runtime package source used by LingTai-managed environments; existing projects should follow their normal TUI-managed refresh or setup path rather than treating a bare global pip command as the user upgrade story.

New features and improvements

  1. 01

    Progressive disclosure for large tool results

    Kernel v0.13.0 makes result hygiene a first-class runtime habit instead of an optional cleanup chore.

    • Tool results now carry consistent _tool_result_metadata with call id, tool name, character count, threshold, and summarization guidance.
    • system.summarize can replace a context-visible blob with an agent-authored index while the original stays available in the event log.
    • Large-result reminders can be acknowledged without deleting the underlying tool result.

    Why it matters:Agents can keep conclusions, evidence, risks, and next steps in working context without dragging every raw build log or trace forward.

  2. 02

    Notification handling becomes explicit and inspectable

    Notification operations now live in the dedicated notification capability, and TUI/Portal v0.9.3 can show historical notification blocks.

    • The old system.notification / system.dismiss aliases are removed; lifecycle and notification surfaces are no longer mixed.
    • The kernel persists actual canonical notification-block snapshots for later inspection.
    • /notification can load from the sqlite event log and display those persisted snapshots.

    Why it matters:When an operator asks what an agent saw, the TUI can show the actual notification object instead of reconstructing it from memory.

  3. 03

    Safer context shedding and Codex backend affinity

    The release tightens the handoff before an agent sheds context and makes the Codex backend path less ambiguous.

    • Agent-initiated psyche.context.molt calls must provide a valid session_journal_path.
    • The Codex backend now sends underscore session_id / thread_id headers to match the Codex CLI path.
    • Codex requests also include honest LingTai client-identity metadata for clearer backend-side provenance.

    Why it matters:A molt should leave a durable handoff, and backend cache-affinity should not depend on guesswork about header spelling or client origin.

  4. 04

    Operator views gain local time and daemon cost context

    TUI/Portal v0.9.3 makes the runtime easier to read while work is still in motion.

    • /kanban timestamps now show local timezone context.
    • The daemons view shows timezone context and CLI token usage where available.
    • A migration version collision in the TUI metadata/state schema was fixed.

    Why it matters:Small visibility improvements reduce the gap between what agents are doing and what operators can confidently verify.

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 0ba1584fce18.

Links