Releases: xiaotonng/pikiloom
Releases · xiaotonng/pikiloom
Release list
v0.4.72
What's Changed
- feat(kernel): surface compaction (auto/manual) as a live signal by @dijkstraplus-ux in #47
Full Changelog: v0.4.71...v0.4.72
v0.4.71
What's Changed
New Features
- Codex now defaults to GPT-5.6 —
gpt-5.6-solby default, withgpt-5.6-terraandgpt-5.6-lunaselectable (372K-token context), matching the latest Codex CLI. - Native
max/ultrareasoning efforts for GPT-5.6. The effort picker is now per-model —sol/terraexposemaxandultra,lunaexposesmax— and the chosen effort is sent to Codex verbatim instead of being silently clamped down toxhigh.
Internal
- Reworked effort dispatch so Codex effort tokens flow through as-is, while Claude keeps
ultraas its display alias formax+ workflow orchestration. Removed the stale legacy-drivermax→xhighclamp so the app-server receives the real reasoning level. - Bundled
@pikiloom/kernelbumped to 0.3.13.
Full Changelog: v0.4.70...v0.4.71
v0.4.70
v0.4.69
What's Changed
Bug Fixes
- Codex sessions no longer get stuck "running" after they finish. When a codex
app-serversubprocess died mid-turn without a finalturn/completed(crash, kill, disconnect), the driver waited forever — the turn never resolved and the session stayedrunningpermanently. The driver now settles the turn on subprocess close (mirroring the claude driver), which also un-hangs the recovery wrapper that depends on the base driver returning.
Improvements
- Startup reconciliation of orphaned sessions. A session stranded at
runningby a process that died mid-turn (crash / kill / power loss) is now repaired toincompleteat startup — but only when its owner process is provably dead, so a session store shared by multiple live processes never has a live turn clobbered. The owner pid is stamped at turn start for both new and resumed turns.
Full Changelog: v0.4.68...v0.4.69
v0.4.68
What's Changed
Improvements
- Transcript rows now label
Skilltool calls with the invoked skill's name — e.g. "Skill mirasim-design" — instead of a bare, indistinguishable "Skill". Applied in both the kernel driver (summarizeToolUse) and the legacy session summarizer (summarizeClaudeToolUse), so it shows up across every surface (dashboard, IM, and consumers of@pikiloom/kernel@0.3.10).
Full Changelog: v0.4.67...v0.4.68
v0.4.67
What's Changed
Internal
- TypeScript 7.0.2 — the whole project (main package,
@pikiloom/kernel, marketing site) now compiles on the native TS 7 toolchain; tsconfigs migrated for TS 7 (rootDirmade explicit, removedbaseUrl). - Pinned, verified dev toolchain — canonical Node 22.23.1 (
.nvmrc+devEngines) and npm 11.6.2, withnpm run verify:toolchainasserting Node/npm/TS/@types/node/Docker stay in lockstep; local Node ^25.2.0 is tolerated for day-to-day dev. - CI hardening — all workflows install the pinned toolchain via
scripts/activate-toolchain.shand runverify:toolchain; fixed setup-node's bundled-npm cache probe tripping the strict npm pin before the toolchain could activate.
Full Changelog: v0.4.65...v0.4.67
v0.4.65
What's Changed
Improvements
- Codex tool activity now exposes expandable live details for shell commands, file changes, MCP calls, dynamic tools, collaboration calls, and web searches.
- Shell activity includes the full command, working directory, streaming output, final output, and non-zero exit information while the turn is still running.
Bug Fixes
- Preserve streamed command output when Codex omits aggregated output from the completed item.
- Normalize failed and declined Codex tool states so activity rows report failures consistently.
Full Changelog: v0.4.64...v0.4.65
v0.4.64
What's Changed
- fix(kernel): stop the no-op-resume repair from re-issuing a /compact by @dijkstraplus-ux in #41
- chore(kernel): release 0.3.2 by @dijkstraplus-ux in #42
- fix(kernel): honor driver steer capability on the managed path by @dijkstraplus-ux in #43
- fix(kernel): stall watchdog no longer kills live long-thinking turns (effort-laddered window) by @dijkstraplus-ux in #44
- chore(kernel): release @pikiloom/kernel 0.3.5 by @dijkstraplus-ux in #45
New Contributors
- @dijkstraplus-ux made their first contribution in #41
Full Changelog: v0.4.62...v0.4.64
v0.4.62
v0.4.61
What's Changed
Bug Fixes
- Fixed silent "no response" when resuming an interrupted or background session. After an
ultra/background turn ended with work still running (e.g. the background hold limit was reached and its sub-agents were reclaimed), the next message could return an empty(no textual response)in ~0s — you had to re-send two or three times before it worked. The Claude agent now recognizes the CLI's synthetic "No response requested." repair no-op and automatically re-issues your prompt over the same session, so you get a real answer on the first send. Bounded and scoped to resumes, so normal turns are unaffected (tunable viaPIKILOOM_CLAUDE_RESUME_NOOP_RETRIES).
Full Changelog: v0.4.60...v0.4.61