Moltlazy
On this page
0.9.0
Minor Changes
- feat: add the private CDP browser profile and enable the browser tool (911397d)
Patch Changes
-
Migrate to OpenClaw 2026.10.9 and harden the sandbox memory limits.
agents.defaults.compactionnow bounds the persisted transcript at 8 MB (down from 20 MB) with a 12k-token retained tail andmidTurnPrecheckenabled, so a tool loop cannot inflate the in-memory prompt between model calls.session.maintenancenow emits a sandbox-safe per-agent budget instead of OpenClaw’s developer-machine defaults:maxDiskBytes512 MB (from 10 GB),highWaterBytes384 MB,maxEntries500 (from 5000),pruneAfter14 days (from 30),resetArchiveRetention14 days, and cold transcript storage after 7 inactive days. Both blocks are fill-only, so a user override wins.Motivation: a 4 GiB
standard-1tenant (tenant-tarjetero-dev) drifted to the container memory limit with ~1.2 GiB of worker-thread V8 heap pages inflated by oversized transcripts and SQLite session history. OpenClaw exposes no knob for the worker pool or its RSS threshold, so the config limits bound growth while the hard restart remains the only RSS reset (seedocs/plans/sandbox-memory-usage.md). (2902de0) -
docs(personas): point the dev-only Fouria Builder/Q&A agents at the channel-versioned docs site. Both personas now read
FOURIA_DOCS_BASE_URL/FOURIA_DOCS_FALLBACK_URL(and confirm/versions.json) instead of a hardcodedfouria.io, so staging/dev agents quote release notes that match the code they run. (a3f85d0) -
feat: seed a software-manifest workspace skill that uses the software.r2.internal bridge instead of the Access-protected admin API (0731213)
0.8.1
Patch Changes
- fix(software): reset the progress log before each provisioning run (5476899)
0.8.0
Minor Changes
- feat: seed the fouria-product-build build-method skill for the Fouria Builder (per-agent workspace skill) (95a1107)
0.7.0 — 2026-10-04
Changesets is adopted from this release onward. Earlier entries were maintained manually; this section collects the changes that shipped in the 0.4.0–0.7.0 line.
New features
SDK Module
config.patch()re-added. The upstreamconfig.patchRPC now exists, soclient.config.patch({ raw, baseHash?, replacePaths?, sessionKey?, deliveryContext?, note?, restartDelayMs? })is the supported partial-update path (JSON merge patch). It waits for the active Gateway to apply the write and returns the effectivechangedPaths.config.schema()/config.schemaLookup(path). New methods for the live config schema and path-scoped schema drill-down (schema,reloadKind, presentation hints, child summaries).config.get()is now typed asConfigSnapshot. Exposesconfig, the opaquehash(pass asbaseHash), and optionalconfigRevisionHash/appliedConfigHash.- New
updatedomain module.client.update.run(params?)(update.run, withcontinuationMessage) andclient.update.status()(update.status). - CLI SDK parity:
client.config.schema()runsopenclaw config schema.
Deprecations
config.set()is deprecated. It acknowledges persistence only; useconfig.patch()for partial updates orconfig.apply()for a full replace.
v0.3.0 — 2026-05-23
Breaking changes
Config Module
- TOML replaced by JSON feature flags.
MOLTLAZY_TOML_CONTENTandMOLTLAZY_TOML_PATHenv vars are removed. Feature flags are now passed asMOLTLAZY_FEATURE_FLAGS(a JSON string). init-tomlCLI command removed. No replacement — feature flags are set by the Worker directly.- Force flags removed.
--force-gateway,--force-channels,--force-agentsCLI flags are gone. The$includemechanism is always authoritative. moltlazy-meta.jsonremoved. Patch tracking metadata no longer exists.$includeis idempotent.shouldPatchConfig()/computeConfigHash()/MOLTLAZY_TOML_ETAGremoved.- Deprecated flag aliases removed.
enableUnifiedBilling→unifiedBilling,enableMicrosoftGraph→microsoftGraph.
SDK Module
- Feature packs removed.
buildGatewayCalls(),buildSessionCalls(),buildToolsCalls(),buildLoggingCalls(),buildAgentsCalls(),buildChannelsCalls(),buildKnowledgeGraphCalls(),buildMicrosoftGraphCalls(),buildCfUnifiedBillingCalls()are all gone. applyConfig()orchestrator removed. No replacement — usecreateClient()and call domain modules directly.ConfigPatchParamsremoved.config.patch()method does not exist upstream. Useconfig.set()orconfig.apply()with{ raw: string }.config.set()/config.apply()params changed. Now accept{ raw: string, baseHash?: string }(serialised JSON string), not{ path: string, value: unknown }.AgentCreateParamschanged.idfield removed.nameandworkspaceare now required.modelis astring(not an object).ChannelParamsremoved. Replaced byChannelStatusParamsandChannelAccountInfo.
New features
Config Module
- Immutable
$include-based config.moltlazy patchgenerates/home/openclaw/.openclaw/moltlazy.jsonand injects$include: "./moltlazy.json"intoopenclaw.json. OpenClaw natively merges both files on startup. - New mandatory config modules:
config/tools.ts(tools.toolSearch) andconfig/logging.ts(logging.*) always run regardless of feature flags. config/include.ts— manages$includeinjection andmoltlazy.jsongeneration.config/skills.ts— always-onskills.entriesconfig section.
SDK Module
- New SDK typed RPC client (
sdk/) —createClient()returns aMoltlazyClientwith 7 domain modules:config,agents,channels,devices,cron,models,gateway. - Upstream-aligned types — all types in
sdk/types.tsaligned toProtocolSchemasfromopenclaw/plugin-sdk:ConfigSetParams/ConfigApplyParams:{ raw: string, baseHash?: string }CronJob/CronAddParams: discriminatedCronScheduleunion (at/every/cron)ChannelStatus: fullChannelsStatusResult-aligned shapeDevicePairRequest:displayName(notname), addeddeviceId/publicKey/tsModelInfo:name: stringrequiredRpcError.error: addeddetails?,retryable?,retryAfterMs?RpcClient.call()params widened tounknown
Other changes
- 608 tests across 33 test files (up from 399/21).
bun run typecheckpasses in strict mode with zero errors.AGENTS.mdupdated to v0.3 architecture (two-system overview, removed TOML/force references).- Docs rewritten:
concepts.md,quickstart.md,orchestration.md(now “Startup Flow”),feature-packs.md(now “SDK Domain Modules”).
Migration from v0.2
See Migration Guide for the full step-by-step guide.
| Old | New |
|---|---|
MOLTLAZY_TOML_CONTENT | MOLTLAZY_FEATURE_FLAGS (JSON string) |
MOLTLAZY_TOML_PATH | removed |
MOLTLAZY_TOML_ETAG | removed |
moltlazy init-toml | removed |
--force-gateway etc. | removed |
buildGatewayCalls() etc. | removed — use createClient() domain modules |
applyConfig() | removed — use createClient() domain modules |
config.patch() | removed — use config.set({ raw: '...' }) |
config.set({ path, value}) | config.set({ raw: string }) |
AgentCreateParams.id | removed (name + workspace required instead) |
Historical changes (imported from apps/fouria/AGENTS.md)
These entries predate the generated release sections above. They were maintained
by hand in apps/fouria/AGENTS.md and are kept here verbatim for traceability.
New entries belong in a changeset (see docs/VERSIONING.md); the sections above
are generated by Changesets (scripts/changeset-changelog.mjs).
- Fouria Builder build-method skill. The dev-only
fouria-builderagent now seedsfouria-product-buildas a per-agent workspace skill (packages/moltlazy/workspace/skills/fouria-product-build.ts→<workspace>/fouria-builder/skills/fouria-product-build/SKILL.md, plus an entry in itsskillsallowlist) that sequences the build method: frame the production roster → tool-first restriction model (each capability names the exact tool; no tool means no capability) → smallest MCP tool surface withpreview/applypairs → 3–6 channel quick actions (Telegram inline buttons; a callback is untrusted input, never authorization) → per-client tone matrix before writing a client-facingSOUL.md→ one vertical slice →cctracceptance corpus →POC.mdhandoff. Workspace skills are OpenClaw’s highest-precedence skill source and are per-agent, andworkspace/fouria-builderis excluded from promotions, so no production roster changes.seedWorkspaceFilesnow creates parent directories so workspace-file keys can be nested paths. This supersedes the pending Skill Workshop proposalfouria-product-build-20261021-bf543e21c1: a workspace copy of the same name shadows a workshop skill, so the repo copy is authoritative. Tests:packages/moltlazy/tests/agents.test.ts; docspackages/moltlazy/AGENTS.md,packages/moltlazy/src/agents/README.md,docs/DEVELOPMENT.md. - Dev-agent personas source the client proposal via the
fouria-leadsskill. The Fouria Builder and Q&A personas (packages/moltlazy/workspace/fouria-builder.ts+fouria-qa.ts) now read the skill first and fetch the proposal through the sandboxleads.r2.internalbridge (globalpaso4-leadsR2 bucket) instead of the legacy/home/openclaw/clawd/client-docs/path; the Worker’s dev-only docs materialization (materializeClientDocsIfDev) is no longer the personas’ input path. Docs updated alongside (packages/moltlazy/src/agents/README.md,packages/moltlazy/AGENTS.md,docs/DEVELOPMENT.md). - v0.3.x $include Configuration: immutable per-section $include files (session/tools/logging); gateway/agents inline; gateway token via env SecretRef
- Dev-only Fouria agents + client docs: moltlazy ships no production premade agents (vanilla
researcher/coderremoved) and injects Fouria Builder (fouria-builder) + Fouria Q&A agent (fouria-qa) only when the instance is a dev environment (OPENCLAW_DEV_MODE=trueon the container, derived by the Worker from the instance’s-devhostname — seesrc/dev-mode.ts); per-tenant client documentation lives in R2 undercustomers/<slug>/docs/and is materialized by the Worker into/home/openclaw/clawd/client-docs/before gateway start (src/services/fouria-docs/,materializeClientDocsIfDev), with a dev-only admin API at/api/admin/fouria-docs(404 outside dev); the Dockerfile installs thecctrbinary, platform docs are fetched from the instance’s channel ($FOURIA_DOCS_BASE_URL, fallback$FOURIA_DOCS_FALLBACK_URL—/lateston production,/stagingon staging/dev, starting at/llms.txt), andstart-openclaw.shkeepssecurity.installPolicy allowin dev so the Builder can self-install plugins