You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Opt-in collection audit rules for gno audit links. A collection's new audit config block can list the other collections it may link to (linkCollections), report external URLs written in its notes (externalUrls: report), and require document paths to match globs (paths). Findings are warnings under links.collection-policy, links.external-url and links.path-layout; they only report and never block indexing, search or editing, and MCP gno_audit and the daemon findings pass pick them up from the same config. Without an audit block, audit output is unchanged. The gno agent skill documents the rules. Thanks to @ArnauvGilotra for the idea and the original pull request (#316).
gno ls --filter <json> lists the documents whose typed metadata matches a predicate, without a search term (for example every note with status: draft). It uses the same predicate syntax and semantics as gno search --filter, applies before pagination so meta.total counts matches, and warns with METADATA_COVERAGE_INCOMPLETE when documents with invalid or pending metadata were skipped. The SDK's list() takes the same filter. ls --json output now has a published schema, and the gno agent skill documents the listing; its JSON examples now read .documents[] and .results[] instead of a bare array. Thanks to @ArnauvGilotra for the idea and the original pull request (#315).
Fixed
gno profile apply (and gno setup --apply-profile) no longer drops collection settings the profile does not own. Re-applying a profile used to reset the collection's egressPolicy to local_only, its egressPolicyRevision to 0 and sourceAvailability to any, and to remove workspaceRoot and memoryManaged, so gno remember stopped accepting a memory collection. Apply now keeps every setting outside the profile. When a profile moves the collection root outside an explicit workspaceRoot, apply stops with WORKSPACE_ROOT_CONFLICT and leaves the config untouched instead of saving one that would no longer load.
With more than 128 collections configured, every call to the resident HTTP MCP endpoint failed with 500 Internal MCP transport error, scoped or not. A call that names its collections is now judged on those collections however many are configured, and an unscoped call over the limit gets the documented COLLECTION_LIMIT_EXCEEDED denial (403). Daemon status and unscoped MCP sync calls deny the same way instead of failing, and the browser clipper and publish exports, which name one collection, work again. The limits themselves are unchanged and are now documented in the configuration guide. Thanks to @ArnauvGilotra for the idea and the original pull request (#318).
The gno agent skill tells agents to retry a COLLECTION_LIMIT_EXCEEDED denial scoped to the collections they need, and sends an explicit request for a semantic, meaning-only search to gno vsearch instead of hybrid gno query.