Clawbolt Files

Highlights

• feat(llm): per-user LLM override resolver hook (#1117). New set_user_llm_resolver extension point lets a plugin (premium) pin individual users to a different model than the global default. ClawboltAgent accepts llm_provider_override / llm_model_override; empty fields fall through to settings.llm_*. OSS-only deployments see no behavior change.
• fix(approval): clearer prompt wording + accept compound replies (#1110). The single-line "Reply yes or no (always/never to remember your choice)" prompt is now a four-line vertical menu using colons (no em dashes). Fast-path parser accepts compound forms users actually type ("yes always", "no never").
• feat(heartbeat) batch:
• (#1112) Skip the heartbeat LLM call when the user has messaged within the configurable quiet-period (HEARTBEAT_USER_QUIET_PERIOD_MINUTES, default 5). Includes integration tests against a real messages row to catch tz-aware-vs-naive regressions in the gate query.
• (#1114) HEARTBEAT_STARTUP_WARMUP_SECONDS (default 60) delays the first scheduler tick after process start so post-deploy in-flight work and queued inbound messages can drain. Cuts the deploy-induced double-execution race for side-effecting tools.
• (#1116) Phase 2 now distinguishes "real-world action followed by post-cleanup" from "HEARTBEAT.md cleanup-only" task shapes; the update_heartbeat tool is gated on the SCHEDULED_TASK_PREFIX cue so it only proactively prunes from the heartbeat path.
• (#1115) Phase 1 run decisions are scoped to actual HEARTBEAT.md items; pending user requests in conversation context are no longer eligible. Stale one-time items get routed to a removal-style run. Cleanup-only Phase 2 runs now write a HeartbeatLog so the 24-hour dedup window has a signal to dedup against; cleanup log entries do not consume the daily nudge budget.
• (#1113) Heartbeat outbound persistence serializes tool_calls via model_dump(mode="json"), matching the user-driven path. Datetimes / sets / UUIDs in tool args round-trip cleanly instead of crashing json.dumps.

Companion premium changes

The premium plugin in clawbolt-premium registers a per-user resolver against its Subscription table and exposes admin endpoints + UI for the global default and per-user override. After this OSS release lands, premium's OSS_REF is auto-bumped via oss-release-listener, and the admin LLM control PR follows on premium main.