v0.8.13 / v0.11.1

New features and improvements

1. 01

   Molt continuation: less guesswork after shedding context

   Molt is how a LingTai agent survives finite context. This release tightens the continuation path so the post-molt self receives a clearer wake-up signal instead of depending on heuristic prose extraction.

   • Post-molt continuation notices are emitted from the actual molt result instead of a guessed next_action heuristic.
   • Post-molt notifications now wake after the context shed, so a successor can pick up the summary, pad, and pending work rather than waiting silently.
   • Deferral is limited to real molt results, reducing the chance that unrelated notifications are delayed, duplicated, or attached to the wrong turn.
   • The improvement is most visible during long development sessions: the agent can deliberately shed context, re-open with a handoff, and continue the release, PR, or investigation thread with less manual reorientation.

   Why it matters:LingTai treats conversation as temporary but work as durable. Stronger post-molt continuation makes that memory model feel practical, not ceremonial.

2. 02

   Soul flow becomes exploratory and voice-aware

   Two late-window kernel changes make the idle inner voice less like a forced productivity checklist and more like a configurable reflective companion.

   • Kernel PR #204 changes the default soul-flow posture toward exploratory reflection rather than narrow task extraction.
   • Kernel PR #206 routes soul-flow consultations through the configured voice prompt, so custom soul voices affect both current-insight and past-self consultations.
   • The change fits the same memory model as molt: conversation is temporary, but reflection and handoff should help the next turn notice what the busy self might miss.

   Why it matters:LingTai’s “inner voice” should be something an agent can cultivate and tune, not a hard-coded narrator with one personality.

3. 03

   SQLite trace index: JSONL remains the truth, queries become fast

   Local agent traces now have a derived SQLite sidecar that can be rebuilt, inspected, and queried without replacing the append-only JSONL record.

   • Kernel PR #201 adds logs/log.sqlite as a fail-open, rebuildable index for logs/events.jsonl, plus lingtai-agent log rebuild|doctor|query <agent_dir>.
   • Read-only SQL query support accepts safe SELECT / WITH ... SELECT / EXPLAIN paths and keeps JSONL as the source of truth.
   • Kernel PR #203 expands the index to agent chat history, chat archives, daemon events, and daemon chat history through a new chat_entries table and source provenance fields.
   • TUI PR #221 adds an interactive migration that asks whether to backfill historical SQLite logs, warns that large histories can take time, shows progress when confirmed, and makes skipping safe for normal use.

   Why it matters:Agents generate a lot of local history. Keeping JSONL durable while adding SQL inspection makes debugging, trajectory mining, and future UI views much less painful.

4. 04

   WhatsApp joins the first-party MCP channel set

   WhatsApp is now wired like LingTai’s other first-party communication channels: a curated MCP registration, runtime dependency, TUI wiring, and README channel documentation.

   • The new lingtai-whatsapp package provides a WhatsApp Cloud API MCP server and is tagged at v0.1.0.
   • Kernel PR #188 registers the curated whatsapp MCP, and PR #189 adds the runtime dependency on lingtai-whatsapp>=0.1.0.
   • TUI PR #216 wires WhatsApp into the MCP setup surface, and PR #220 adds WhatsApp to the documented channel list.
   • As with other MCP channels, activation still depends on user-provided provider credentials; registration and packaging are now first-party.

   Why it matters:LingTai’s human-facing channels become broader without inventing a separate integration model for every platform.

5. 05

   Diagnostics and resident guidance move toward kernel-owned manuals

   This window keeps moving operational knowledge out of scattered UI copies and into intrinsic skills/manuals that agents can load when needed.

   • Kernel PR #185 adds the intrinsic lingtai-doctor skill and expands read-only diagnostics for agent health, stale paths, heartbeat/process disagreements, and MCP/addon path issues.
   • TUI PR #213 wires /doctor to the kernel-owned intrinsic doctor instead of maintaining a separate diagnostic script path in the TUI.
   • Kernel PR #187 and TUI PR #215 route expanded runtime guidance into system-manual, keeping the resident prompt smaller while preserving detailed procedures on demand.
   • TUI PR #214 adds the standing guidance that substantial human-facing deliverables should prefer standalone HTML when appropriate.

   Why it matters:Agents should carry durable operating knowledge with them, while the always-on prompt stays small enough to leave room for actual work.

6. 06

   Product narrative, license alignment, and public documentation polish

   The release also cleans up the public shape of the project: what LingTai is, how it is licensed, and where new users see the supported channels.

   • TUI PR #212 expands the project README, and PR #219 repositions it as a product entry rather than only a developer note.
   • TUI PR #220 adds WhatsApp to the README communication channel list, matching the new first-party MCP path.
   • Kernel PR #200 and TUI PR #218 align the repositories on Apache-2.0.
   • The release window also includes routine star-count maintenance commits in the web-facing project metadata.

   Why it matters:As LingTai becomes easier to install and easier to extend, the public entry point needs to explain the system in the same language the product now uses.