mirror of
https://github.com/openclaw/openclaw.git
synced 2026-11-20 17:54:15 +00:00
4 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
9b7dcdc7a6
|
feat(knowledge): lean agent tool results and hash-prefix write fences (#196767)
* feat(knowledge): lean agent tool results and hash-prefix write fences * fix(knowledge): address lean result review findings * test(knowledge): connections keep a null final nextOffset * feat(knowledge): lean agent tool results and hash-prefix write fences OpenClaw-Publication: 9de0af9f-3960-4a5d-8bb6-729235cf33ea * refactor(knowledge): agent tool inputs select data only; UI keeps detail operations * test(knowledge): use detail operations for complete reads * Publish openclaw/vivid-langoustine OpenClaw-Publication: 5e45559f-7f2d-4541-a194-dc82c1d35168 * fix(knowledge): satisfy lint, assertion and test-line ratchets * Publish openclaw/vivid-langoustine OpenClaw-Publication: aa4240cf-2d4f-43cb-a912-9d9c4e28f88f * fix(knowledge): keep fields, attribution doubt and exact claim windows in agent record reads * Publish openclaw/vivid-langoustine OpenClaw-Publication: ae107101-0dd6-4c8b-97cd-7059316a3108 * fix(knowledge): restart each record budget attempt from the whole body window * Publish openclaw/vivid-langoustine OpenClaw-Publication: 9e0b2be9-7c9b-45ac-b43c-2cd3766fef8c |
||
|
|
ff2d7187a5
|
feat(knowledge): agents can no longer grow pages past a read-sized budget, and can extract sections instead
Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> |
||
|
|
e665f5b70f
|
feat(knowledge): consolidate claims by scope and supersede snapshots by their outcome
Co-authored-by: jalehman <550978+jalehman@users.noreply.github.com> |
||
|
|
65ad180052
|
feat(knowledge): bundle the Knowledge memory plugin (#180139)
* feat(knowledge): import Knowledge plugin sources
Imported from openclaw/knowledge at 7847e55. Uses the public SDK root()
and the host's typed projectKey.
* style(knowledge): apply repository formatting and lint autofixes
* test(knowledge): port the Knowledge suite to vitest
* docs(knowledge): document the bundled Knowledge plugin
* refactor(knowledge): conform to bundled-plugin lint, types and file-size rules
* fix(knowledge): locate workers and packaged data from the runtime entry
Built output moves shared modules into host chunks, so module-relative
URLs no longer reach the storage and registry workers, the default
ontology or the sample vault. Resolve them from api.runtimeSource, ship
the data as static assets, and read files through @openclaw/fs-safe.
* chore(knowledge): register plugin inventory, config baseline and labels
* refactor(knowledge): drop standalone-host leftovers
Metadata-only registration has no runtime entry; locate packaged files
only when the host supplies one. Remove the older-host panel guard and
references to docs that did not move with the plugin.
* refactor(knowledge): remove unused exports and dead search helpers
* openclaw-ef3.7.3: open Knowledge databases through SDK helpers and stamp schema versions
Replace raw DatabaseSync construction and PRAGMA-based header versioning in the
operational (state.sqlite) and registry databases with openNodeSqliteDatabase,
runSqliteImmediateTransactionSync and a knowledge_schema version table. Stores
written before stamping are dated by their tables and migrated additively;
their native header is left untouched. Identity and registry upserts use Kysely.
* openclaw-ef3.7.2: port Knowledge transactions and conflict inserts to SDK patterns
BEGIN IMMEDIATE blocks become runSqliteImmediateTransactionSync, INSERT OR
IGNORE/REPLACE become Kysely onConflict inserts, and sqlite_master probes use
tableExists. Register Knowledge's worker-only SQL modules in workerModules.
* openclaw-ef3.7.4: move Knowledge JSON projections out of raw SQL
Publication source and receipt lookups use jsonPathValue with Kysely. The recent
projection parses each published plan once in TypeScript instead of json_each/
json_extract, and applies record eligibility and source grouping while streaming
newest-first events. Storage base transactions and upserts use SDK helpers.
* openclaw-ef3.7.6: document type assertion invariants in Knowledge storage modules
Every type assertion in the storage, registry, recent, retrieval, lifecycle,
session-activity and attachment modules now states its invariant, satisfying
the assertion SAFETY ratchet against main.
* openclaw-ef3.7.6: keep the Knowledge schema step type module-private
* openclaw-ef3.7.2: resolve Knowledge worker SQLite SDK modules through the host resolver
* openclaw-ef3.7.4: keep Knowledge SQL out of the control UI bundle
Recent activity SQL moves to recent-activity.ts so recent.ts only carries the
schemas the control UI imports, and session activity records retried calls with
a portable ON CONFLICT DO NOTHING prepared statement instead of the SQLite SDK.
* refactor(knowledge): move scan primitives to a leaf module
Breaks the evidence-files -> publication-files -> vault import cycle.
* openclaw-ef3.7: import digest from scan-primitives to break the lifecycle -> vault -> retrieval cycle
* openclaw-ef3.7.5: classify Knowledge keyword-index FTS5 as engine-private
Knowledge's keyword index is a rebuildable cache in each store's own
state.sqlite, opened by SqliteIdentityStore and never through the selected
Gateway engine. Classify its fts5, temp-schema and rowid constructs in
retrieval.ts as owned engine maintenance; other constructs there stay counted.
* chore(knowledge): justify or remove type assertions
Adds SAFETY invariants for the assertion ratchet and removes casts that
real types or narrowing make unnecessary.
* refactor(knowledge): drop the Publisher alias and unused MAX_ENTRIES re-exports
* fix(knowledge): bound Markdown block runs before link lexing
JavaScriptCore reports regexp matches that exceed its backtracking memory
cap as no match. marked's paragraph rule hits that cap after ~49K lines in
one block, then lexes the rest line by line, so scanning a near-limit
record took hours under Bun. Split runs over 10K non-blank lines before
lexing; links are unchanged.
* fix(knowledge): transfer workspace attachments without model byte copying
knowledge-live-728: reuse durable chunk uploads behind a scoped workspace-file tool and document programmatic source retention.
(cherry picked from commit d196fdc0b1c30c4850a1f97d94a512ae2b27aa74)
* fix(knowledge): declare knowledge_attach_file in the plugin manifest
* feat(knowledge): add knowledge-unlinked-claims skill for post-relink review
* fix(knowledge): resume interrupted store setup and admit state once
- Resume a store whose setup was interrupted: an empty state.sqlite is a new
database, and writeOnce completes an empty vault.json or registry sentinel.
- Admit each physical state database once per thread: the schema check,
history indexes and additive operational tables move out of every
connection and every operation.
- Keep maintenance schedule bookkeeping in registry meta instead of
maintenance.json.
* feat(knowledge): steer the memory prompt toward entity pages and recall before planning
Describe Knowledge as world knowledge about ontology entities, search named
entities once before planning, keep pages for sustained work through
knowledge-entities and knowledge-capture, record agent findings on pages
instead of skipping them, word remembered claims no more broadly than their
excerpt, and record supersession with knowledge-correct.
* fix(knowledge): keep knowledge_remember a search-free fast path for one-off claims
* fix(knowledge): complete an empty registry sentinel before checking it
A crash after the registry sentinel is created but before its ID is written
left an empty registry.id. The constructor compared it with the registry ID
before writeOnce could complete it, so every registry operation failed until
manual recovery. writeOnce now runs first and reports whether it wrote; the
comparison still refuses a sentinel that names another registry.
* feat(knowledge): append a generated Knowledge index to owner-private sessions
* fix(knowledge): honor operator roles and name the real memory audience denial
Operator browsing of an agent's private knowledge now stays within the caller's role agents and requires operator.admin on a shared Gateway. A missing memory audience no longer blames a parent reset; the error points to the memory_audience_denied Gateway log entry without naming other sessions.
(cherry picked from commit
|